Architecture and cloud
System design, cloud migration and the unglamorous work that decides whether a product survives its second year: boundaries, data flow, cost, observability and the ability to deploy on a Friday without holding your breath.
Projects
Everything below includes design, engineering, testing, deployment and one round of revisions per increment.
Full price list- Size of the estate
- Downtime tolerance
- Data volume
- Team size
- Seniority mix
- Time-zone overlap required
How a project runs
The same five steps every time, so you always know what happens next.
Scoping call
Thirty minutes, no charge. We ask what the system has to do, who uses it and what happens if it is late. You leave with a range and the things that would change it.
Paid discovery
One to three weeks. Written scope, technical approach, risks and a clickable prototype where it helps. It is credited in full against the project if you proceed, and it is yours if you do not.
Build in two-week increments
Working software at the end of every increment, on a real environment you can open. A written status you can forward to your own board, without us in the room.
Handover
Repository, documentation, infrastructure, accounts and a runbook. We walk your team through it. Another team can pick this up, and that is deliberate.
Support
Thirty days of defect fixes at no charge. After that, a retainer if you want one and a clean goodbye if you do not.
Questions we get before the first call
How much does a project cost?
+
Our ranges are published on the pricing page, with the four or five things that move them. A fixed price follows a scoping call, and it lands inside the published range or we explain why.
How quickly can you start?
+
Usually within two to three weeks. Discovery can start sooner, and it is often the right first step anyway: it turns a conversation into a written scope you can take to another supplier if you want to.
Who owns the code?
+
You do, on final payment. Source code, design files, infrastructure and accounts. This is in the contract, not a favour we grant later.
Do you work fixed price or hourly?
+
Both. Fixed price when the scope is known and unlikely to move. Time and materials with a ceiling you set when it will evolve. We tell you which one fits on the first call, including when that means less money for us.
Where is the team?
+
The company is American and the contract is with an American company. The people are in Europe, Asia and Latin America, and we tell you who is where before you sign. Time-zone overlap is agreed at the start rather than discovered in week three.
What if it goes wrong?
+
Defects are fixed free for thirty days after handover. If we are late for a reason that is ours, we say so in the status report on the day we know, not at the deadline. And you can leave with everything: you have access to the repository, the documentation and the accounts from day one, and ownership transfers on final payment.
Tell us what you are building
A short description is enough to start. We reply with questions, a range and the two or three things that would change it.