Software built properly, at a price fixed before we start.
Product Build is custom software development without a retainer attached. You tell us what the software has to do and who it is for. We come back with a written scope and a fixed price, then design, build and launch it in your own repositories and cloud accounts, and fix whatever surfaces in the first ninety days after go-live.
Who it is for
- A business that has outgrown its tools. The spreadsheet, the stitched-together SaaS, the process that only works because one person remembers how it goes.
- A founder with an idea worth building properly. If you still need to prove the idea, MVP Launch is the smaller, faster version of this.
- A team that needs one more system built. An internal tool, a customer portal or an integration, built beside your own developers without taking them off their roadmap.
What you get
- The application itself, launched and in use.
- Every line of code in repositories your organisation owns.
- Hosting on your cloud account, with you as the owner. Nothing runs on infrastructure you cannot take over tomorrow.
- A release pipeline, so a change goes live through tests and a review rather than by hand.
- The architecture written down: what was chosen, what was ruled out, and why.
- A handover document a new developer could start from.
- Ninety days of fixes after go-live, included in the price.
How the price gets fixed
Most of the risk in custom software sits in the gap between what was asked for and what was understood. So the price comes after the scope, never before it.
- Twenty-minute call. You describe what the software has to do. We ask about the parts that usually decide the cost.
- Written scope within 48 hours. What we would build, in what order, what is deliberately left out, and the price.
- One fixed price. It does not move unless you change the scope. If you do, the change is quoted in writing before anyone works on it.
How the build runs
- Design. The screens and the data model are agreed before the code is written, so the expensive surprises arrive on paper.
- Build, shown every week. You see working software on a fixed day each week, not a status report. One channel we both live in, with answers the same working day.
- Launch. On your domain and your accounts, with monitoring in place from the first day.
- Ninety days of fixes. Whatever real users find in the first three months, we fix.
The people on the intro call are the people who write the code. Nothing is subcontracted, and the parts that matter are not handed to someone junior.
What decides the cost
The price is set by a handful of things, and the scope names each one so none of them surprises you later:
| Factor | Why it matters |
|---|---|
| Integrations | Every outside system (payments, a CRM, an accounting package, an API with its own quirks) adds work and its own failure cases. |
| Existing data | Moving records out of an old system is often bigger than it looks, because the old data rarely matches the new rules. |
| Users and permissions | One kind of user is simple. Admins, staff, customers and partners who each see different things are not. |
| Compliance | Payments, health or financial data bring obligations that shape the architecture from the first day. |
| Uptime | An internal tool can be down for an hour. A system your customers pay through cannot, and building for that costs more. |
After launch
At the end of the ninety days you are free to walk away with everything: the code, the accounts, the documents. Many clients keep going on a monthly plan once the software has users, either Technical Partner from $4K a month or Full Partnership from $7K. Neither is required.
The standard we build to
Our background is one of the biggest trading platforms in fintech, where an outage is a regulatory event rather than an apology. Release pipelines, Kubernetes and cloud infrastructure held to that standard are our everyday habits, and they come with the build. We work mostly in Node.js, Python, Go and React on PostgreSQL, hosted on AWS or Google Cloud, and we will tell you plainly if your problem needs something else.
Questions
How long does a build take?
It depends on the scope, and the scope gives you a date as well as a price. If you need something in front of users quickly, an MVP Launch cuts the scope to what proves the idea and ships it in one focused sprint.
What if we change our minds halfway through?
You can. The change is written down and priced before anyone works on it, and you decide whether it goes in now, after launch, or not at all. The original price holds for the original scope.
Can you work with the developers we already have?
Yes. We can build the whole thing, or build part of it while your team builds the rest, under one architecture and one review bar.
Who owns the code?
You do, from the first commit. It lives in your repositories and runs on your accounts. We take no equity and keep no licence over it.
What happens after the ninety days?
Fixes after that point are covered by a monthly plan if you have one, or quoted as a small piece of work if you do not. Either way you will have the documentation to hand it to anyone you choose.
Tell us what the software has to do. In 48 hours you will have the scope and the price in writing.
Book a 20-minute call or write to [email protected]
Weighing up a technical co-founder instead? Read a technical co-founder without equity: the real options.