Software engineering, data and AI · Headquartered in Scotland, delivering internationally| Start a project →
Service

Software development that behaves on day one — and still behaves in year three.

Custom web applications, SaaS platforms and internal tooling built for organisations in the UK and beyond. Django and Python on the back end, TypeScript where interactivity earns its keep, PostgreSQL as the system of record — with audit trails, encryption, CI, backups and SSL baked in from the first commit.

Start a project → See pricing bands
§ 01 — What you get

A production system, not a prototype dressed up in production clothes.

Shippable by end of week two

Every engagement starts with a visible end-to-end slice deployed to a staging environment inside the first two weeks. You will not spend six months "waiting for the build" without seeing anything move.

Encryption and audit from day one

Field-level AES-256 on PII. A hash-chained audit log that captures every save and delete across every model. GDPR compliance is not a retrofit — it is how we start.

Role-based access, modelled properly

A numeric role hierarchy, soft-deletes everywhere, UUID primary keys on every customer-facing table. If an auditor asks "who changed this and when", there is one answer and it is defensible.

Zero-downtime deploys

CI runs on every push. Migrations are tested against a copy of your production database before they touch the real thing. Rolling deploys so your users never see a maintenance page.

Observability baked in

Sentry for errors, request logging to a drain you can query, health checks that the load balancer actually honours. When something goes wrong at 03:00 you will know before your users do.

Documentation your team can read

An architecture note, an operations runbook, and a plain-English README. If we stop working together tomorrow, the next engineer can continue without archaeology.

§ 02 — How we build

A five-step process. No surprises.

01 Discover

Understand before we quote

A short paid discovery — usually one to five days — where we map your current workflow, the data you handle, who touches what, and what "success" looks like in numbers. You leave this phase with a one-page problem statement and a scoped proposal with a fixed fee.

02 Design

Prove the idea cheaply

Wireframes for the two or three screens that matter, an ERD for the data model, a short integration plan, and a non-functional requirements note covering compliance, performance, hosting and retention. You sign this off before we write a line of production code.

03 Build

Fortnightly demos, main-branch deploys

Weeks are two-week sprints. Every sprint ends with a live demo on real infrastructure — never a Zoom share of code. You can click, test, change your mind. Changes feed the next sprint, not an unending backlog.

04 Harden

The unglamorous week that saves you

Before launch we run a dedicated harden sprint: load tests, data-migration dry runs on a staging copy of production, security headers, backup restore drills, runbooks, and a written cutover plan. Launches without this step are how you earn 03:00 phone calls.

05 Operate

Live with SLAs — or handover, clean

You choose. Either we keep running it under an operate-plan with a defined response-time SLA, or we execute a clean handover to your in-house team — the runbook, a knowledge-transfer week, and a 30-day post-handover warranty on anything we built.

§ 03 — Deliverables

What lands in your hands at the end of each engagement.

  • ✓ A running production application
  • ✓ Source code in a private repository owned by you
  • ✓ Architecture note (1–3 pages)
  • ✓ Database ERD with all constraints
  • ✓ Operations runbook with incident playbooks
  • ✓ Backup and restore drill results
  • ✓ Security headers & CSP policy
  • ✓ CI pipeline configuration
  • ✓ User-facing README and admin guide
  • ✓ Signed-off test plan
  • ✓ Audit-log sample extract
  • ✓ 30-day post-handover warranty
§ 04 — Pricing bands

Fixed fees for scoped work. Day rates when scope is uncertain.

Every real engagement is quoted in writing after discovery. The bands below set the right expectation before we talk.

Small build
£10–25k

Single-purpose internal tool. 4–8 week build, one or two integrations.

  • · Up to ~8 tables
  • · Hosted on Render / Fly
  • · 30-day warranty
MOST ENGAGEMENTS
Mid-scale build
£25–75k

Multi-user platform with roles, billing, email, reporting. 8–16 week build.

  • · Up to ~25 tables
  • · Stripe / SendGrid / Cloudinary wired
  • · 2–3 integrations
  • · 60-day warranty
Platform build
£75k+

Multi-tenant SaaS, regulated data, or deep workflow coverage. 4–9 month build.

  • · Custom modules
  • · Enterprise SSO / audit
  • · On-call SLA included
  • · Dedicated squad

Day rate available for discovery or fixed-term team augmentation: £750/day + VAT.

§ 05 — Scenarios

What a typical engagement looks like.

Scenario A

A charity replacing three spreadsheets with one web app

Grant data, volunteer hours and small-grants decisions are all tracked in different workbooks. We build a single Django app with per-charity role separation, exportable reports for the trustees, and automatic reminders. 8-week build; sits in the £25–40k band.

Scenario B

An SME launching a paid SaaS product

Multi-tenant Django + Postgres, Stripe subscriptions, role-based admin, customer self-serve dashboard, SendGrid transactional email, Sentry monitoring. 12–16 week build with a staged rollout; £45–75k.

Scenario C

A regulated organisation needing audit-grade internal tooling

Encrypted PII fields, hash-chained audit logs, multi-step approval workflows, SSO. 6–9 month build with a formal UAT phase; £85–150k.

§ 06 — FAQ

The questions buyers actually ask.

Do you take fixed-fee work or only day rates?

Fixed fee is our default once discovery is done. We only move to day rates when the scope is genuinely unclear or when you want us to sit inside your team for a bounded period.

Who owns the code?

You do, in full, as soon as the final invoice is paid. The repository is created inside your GitHub or Bitbucket organisation from day one — we are collaborators on it, not owners.

Can you work with an existing codebase?

Yes. Rescue, migration and gradual modernisation of Django and Flask codebases is a regular part of what we do. We start with a short paid technical audit before committing to the larger work.

Do you handle hosting too?

We can. See the data & hosting service. We default to Render for web and managed Postgres, Cloudflare for DNS and CDN, and AWS S3 or Cloudinary for media. If you prefer AWS, Azure or GCP, we can go there too.

How is this different from a freelancer or a UK consultancy?

You get a founder-led engagement — the person doing the work is also the person who scoped it. No handoffs to junior staff. And every project is delivered on the same opinionated production stack that already powers this site, which means we are shipping proven patterns, not experimenting on your budget.

Do you sign NDAs?

Yes, both ways, before any detailed discussion. Our standard NDA is one page and reciprocal; we are happy to sign yours if you have one.

Ready to put a number on your project?

Tell us the outcome you need. We come back within three working days with a scoped proposal and a fixed fee.

Start a project →