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

How we engage. Every stage. Every artefact.

We publish the method because the method is the product. If you are considering working with us you should know, in detail, how an engagement actually runs — the paperwork, the cadence, the deliverables, the point at which you can stop without penalty.

Operating principles

Five things we always do.

  1. 1. Discovery is always paid. Free "scoping calls" produce proposals that are wrong because the person writing them did not understand the problem.
  2. 2. Fixed fees after discovery. Day rates only when scope is genuinely unknowable, with a written cap.
  3. 3. You own the code the moment we are paid. Repository lives in your GitHub, not ours.
  4. 4. Fortnightly demos on live infrastructure. No screen-sharing of local code.
  5. 5. The final deliverable is always a written runbook. A system you cannot operate without us is a system we failed to deliver.
Phase 01
Discover

Understand before we quote.

Discovery runs one to five working days depending on the complexity of the engagement. It is paid work — typically £1,500 for a one-day discovery through £7,500 for a full week of workshops, interviews and system review. The output is a written proposal with a fixed-fee quote; if you proceed, the discovery fee is credited against the build.

What we do during this phase

  • · 90-minute kickoff workshop with the primary stakeholder
  • · 30-minute interviews with 3-6 people who will use or own the system
  • · Review of any existing systems, spreadsheets or documentation
  • · Draft of a one-page problem statement for your sign-off
  • · Draft of a scoped proposal with assumptions, risks and a fixed price

What you leave with

  • · A problem statement you can circulate internally
  • · A scoped proposal with a fixed fee and a named delivery window
  • · A tech-stack recommendation with reasoning
  • · A "what we are not doing" list, so expectations are aligned
Phase 02
Design

Prove the idea on paper before we prove it in code.

Design runs between one and three weeks, folded into the first part of the build budget. You review and sign off on every artefact before implementation starts. Changes made during this phase cost nothing; changes made after it cost real money — this is the clearest incentive we can give you to pay attention here.

Artefacts produced

  • · Wireframes for the two or three screens that matter most
  • · Entity-relationship diagram for the data model
  • · Integration plan listing every third-party system and data flow
  • · Non-functional requirements note covering compliance, performance, hosting, retention
  • · A test plan with acceptance criteria you sign
Phase 03
Build

Fortnightly demos. Main-branch deploys. No surprises.

Build cadence is two-week sprints with a 45-minute demo at the end of every sprint. The demo is always on a live staging environment at a real URL — you can click, test, and leave feedback. We do not screen-share from a local machine; it is too easy to show software that works in that specific window and nowhere else.

Per-sprint rhythm

  • · Monday — sprint plan published; what we will ship by Friday fortnight
  • · Daily — async progress update in your team's chat tool of choice
  • · Friday week 1 — mid-sprint review if anything has shifted
  • · Friday week 2 — 45-minute live demo + sprint retrospective
  • · Deploy to staging every green main-branch push; deploy to production on sign-off

Change management

Scope changes mid-build are normal. We handle them with a short written change-order: what, why, cost impact in days or pounds, your email approval. No change happens without that trail; nothing surprises you on the invoice.

Phase 04
Harden

The unglamorous week that saves you.

Every project has a dedicated harden sprint — usually one week — between "feature-complete" and "live to real users". This phase is where launches without 03:00 phone calls come from. It is also the phase we see cut most often by teams who want to ship sooner; we do not cut it.

Checklist

  • · Load testing against expected and 3x-expected traffic
  • · Data-migration dry run against a copy of production
  • · Security headers, CSP, HSTS, SameSite cookies
  • · Backup restoration drill (restore to a scratch environment and smoke-test)
  • · Written incident-response playbook covering top-5 failure modes
  • · Cutover plan with roles, timings, rollback procedure
Phase 05
Operate

Live with SLAs — or clean handover. You choose.

Two paths at project end. Either we continue to run the system under an operate-plan retainer (from £1,500 per month, with an SLA defined per band), 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.

What is in an operate retainer

  • · Hosting and database management
  • · Monitoring, alerting, backups
  • · Incident response within SLA
  • · Monthly cost and uptime report
  • · Quarterly architecture review
  • · Dependency patching

What is in a handover

  • · Written runbook with every known operational procedure
  • · A two to five day knowledge-transfer workshop with your engineers
  • · Transfer of hosting, DNS and secrets to accounts you control
  • · 30-day warranty against defects in code we wrote
  • · Optional retainer for ad-hoc questions after the warranty ends

Still reading? Then you already like how we work.

Start a project →