No discovery calls that turn into unpaid consulting, and no twelve-month fixed bids that are wrong by month two. Four phases, priced per phase.
1–2 weeks · fixed fee
We map the problem, inspect the systems and data involved, and write a technical scope with an architecture outline and a fixed price for the build. Paid, because doing it properly takes real engineering time — and yours to keep whether or not you continue with us.
two-week increments
Each increment ends with working software deployed to a real environment, not a status report. Priorities can be reordered between increments at no penalty — that flexibility is the point of working this way.
before go-live, not after
Deployment pipelines, monitoring, alerting, backups and documentation are finished before launch. Handover is a scheduled event with a transition period, not an email with a repository link.
monthly retainer, or handover
We operate the system — patching, monitoring, support and the next round of changes — on a retainer with agreed response times. Or we hand it to your team with the documentation to take it on. Both are normal outcomes.
Three ways to work with us.
Fixed fee
One to two weeks producing a technical document, architecture outline and fixed build price. The deliverable is yours regardless of what happens next.
Best when the problem is clear but the solution is not.
Agreed per phase
A defined scope, a fixed price, a fixed date. Scope changes are re-scoped and re-priced openly rather than absorbed silently and delivered late.
Best for a first project together.
Monthly
A defined amount of senior engineering capacity each month, plus agreed response times for incidents. Priorities set by you at the start of each cycle.
Best for ongoing development and support.
We do not publish rate cards, because a number without a scope is meaningless in both directions. You get a fixed price before committing to anything beyond scoping.
Because doing it properly means engineers reading your systems, inspecting real data and writing an architecture — which is work. Suppliers who give it away recover the cost inside an inflated build price, or produce a sales document rather than a technical one. You keep ours either way, which is what makes the fee defensible.
Yes, before any detailed discussion if you prefer. Send yours or use ours.
We keep a defined overlap window with your working day for calls and reviews, agreed at the start. Asynchronous updates are written, not verbal, so nothing depends on catching someone live.
Defined in the retainer and varying by severity — a production outage and a cosmetic bug do not warrant the same commitment. We agree the tiers before signing rather than pointing at a policy afterwards.
You do, on payment, including code, infrastructure configuration and documentation. Repositories, cloud accounts and domains are in your name from the beginning rather than transferred at the end.
Retainers end with a notice period stated in the contract. Because everything already lives in your accounts with documentation kept current, stopping means we stop working — not a migration project.
A short call first to work out whether it is worth doing at all. That part is free.