System Build.
Custom software built to a fixed scope and a fixed price, for projects that need an agreed budget before they start.
When the budget has to be fixed up front.
Some projects need a defined scope and an agreed price before anything starts: a grant-funded build, a procurement process, a board that wants a single number.
For those, we build to a fixed scope. We agree what’s being built, how it will be tested and what it costs, then deliver it in releases you can see and test along the way. The EAL grading engine is a good example: tightly defined, test-driven, and delivered on time and within budget.
If your scope is likely to change as you learn, the subscription is usually the better deal: no change orders, and the queue absorbs new ideas as they come.
How a fixed-scope build runs.
Scope
Usually after a Discovery Sprint. What’s being built, for whom, and how we’ll know it works.
Fixed price
One number for the agreed scope, with acceptance criteria written in plain language.
Build in releases
Working software at each milestone, reviewed by a senior developer and tested by you.
Hand over or carry on
You own everything. Run it yourselves, or keep improving it on the subscription.