Process
Four phases. You own the output of each.
This is not a diagram borrowed from a textbook — it is what appears on the invoice. Each phase produces something you keep, whether or not the next phase happens.
-
Wireframes and UI flows
Screens and the paths between them, in low fidelity first. Arguments about how the software should work are cheap here and expensive later.
You keep: wireframes, flows and an interface design that can be handed to any developer, including one who is not us.
-
Services and interface
The system itself: data model, business rules, permissions, integrations and the screens on top. Built in slices you can look at, not delivered as one reveal at the end.
You keep: the running system and its full source.
-
Deployment and operations
Environments, pipelines, backups and monitoring. The goal is that a release stops being an event, and that when something breaks the alert names the cause.
You keep: reproducible environments and the deployment setup, documented.
-
Coordination
Planning, written status, and the meetings that keep scope honest. Billed as its own line so you can see exactly how much of the budget is talk.
You keep: the plan, the decision log and the reports.
Billing
How the hours reach the invoice.
Itemised by phase
Each invoice line names the service, the hours and the rate — the same four rates published on this site. Nothing is aggregated into a single mystery figure.
Estimates before, not after
Each phase starts with an estimated range. If the work is heading past it, you hear about it while there is still a decision to make.
Stop whenever
Hourly billing means no lock-in. Every phase leaves you with something usable, so stopping after any of them is a decision, not a loss.
At the end
What you take away when the work is done.
A project that ends with a login and a shrug is not finished. Handover means the product is yours, documented well enough for someone else to run it, and covered if something turns out to be broken.
Warranty12 months
One-year warranty on the work
For twelve months after handover, defects in what we built are fixed at no charge. Not new features — the things that were supposed to work and don't.
OwnershipYours
The product belongs to you
Ownership and property rights to the delivered product transfer to you in full, including the right to take it to another supplier, extend it or resell it. We keep no licence over your system and no hold over your data.
ContinuityDocumented
Anyone can pick it up
The documentation is written so that an engineer who has never met us can deploy, operate and extend the system. That is the real test of a handover, and the reason the list on the right is not short.
Documentation handed over
- Physical system designServers, environments, network and storage layout.
- Logical system designData model, modules, interfaces and how they fit together.
- Operations manualRunning it day to day: deployment, monitoring, routine tasks.
- Commented source codeThe full source, commented where the reasoning is not obvious.
- Backup and recovery planWhat is backed up, how often, and how to restore it.
- Database schemaTables, relations and migration history.
- Deployment guideStanding the system up from nothing, step by step.
- Access inventoryEvery account and key involved — and which ones to revoke.
Ready to start with phase one?
Wireframes are the cheapest place to change your mind.