Engagement model
One price, one plan,
one team that ships it.
A fixed-scope build suits teams with a settled product and a fixed budget. We scope it, price it, then build it to that number. You get working software on dated milestones. The scope only changes when you sign for it.
- EU-based engineers
- MiCA-ready architecture
- Client-owned code
Fit
When a fixed scope is the right call
Fixed price rewards clarity. Four conditions tell us the model will hold. Miss two of them and we will say so before you sign.
-
01
The scope is settled
You know the product you need. The feature list is agreed inside your team. Nothing major is still open.
- Signed scope
- Named owner
- Agreed launch date
-
02
The budget is fixed
A board or an investor approved one number. You need that number to hold from kick-off to launch.
- One price
- Phase payments
- No hourly drift
-
03
The rules are known
Your licence path is clear. We build to a MiCA or VASP scope and leave the legal calls to your advisers.
- MiCA-ready design
- GDPR-aware data
- Audit evidence
-
04
You want one owner
One EU team runs discovery, build, hardening and launch. You brief once. You chase nobody.
- Single contract
- Named engineers
- 24/7 cover after launch
Delivery
How the money and the work line up
Each phase has an output you can inspect and a payment tied to it. Nothing is billed against a promise.
Building a venue? The technical detail sits on our crypto exchange development page.
- 01
Scoping sprint
2–4 weeks · Paid separately
Architecture view, risk list, test plan and the priced scope we then sign.
- 02
Build blocks
Fixed milestones · On milestone sign-off
Working software each block. You review it in a real environment, not a slide.
- 03
Hardening
Runs in parallel · Inside the price
Security review, load tests, AML and Travel Rule paths, plus the audit trail.
- 04
Launch & handover
1–2 weeks · Final milestone
Cut-over, runbooks, source handover and a support plan with named engineers.
Scope
What the price covers
A fixed price is only useful if the boundary is clear. Here is what sits inside every build we sign.
-
A signed scope
Every screen, service and interface is listed before we start. What is out is listed too.
-
A dated plan
Milestones carry dates. You see slippage in the same week it happens, not at the end.
-
Client-owned code
You own the source, the infrastructure and the docs. No white-label lock-in, no seat fees.
-
Tests and evidence
Automated tests ship with the build. Logs and reports go to your reviewer on request.
-
One change process
New ideas get priced as a change order. The base price stays honest.
-
A warranty window
Defects against the signed scope are fixed free for thirty days after launch.
Alternatives
If a fixed scope does not fit
Pick the model that matches how settled your plan is. You can switch later. Many clients start with one and move to another.
-
Dedicated team
A standing squad with a lead. Best for long roadmaps that keep moving.
-
Staff augmentation
Senior engineers inside your team. Best when you own the plan already.
-
CTO advisory
Architecture and hiring guidance. Best before you commit to a build.
Questions
Before you sign
The four things buyers press us on. Bring the rest to the call.
Why is the scoping sprint priced on its own?
Nobody can price a venue from a brief. The sprint buys the detail. You keep every document even if you stop there.
What happens when we want a new feature mid-build?
We price it as a change order with its own date. You approve it or park it. The signed scope never moves quietly.
Is a fixed price safe for regulated work?
Yes, when compliance sits inside the scope. We design to the rules from day one, so nothing gets unpicked late.
What if our scope is still moving?
Then a fixed price is the wrong tool. Start with a standing squad or advisory instead, and switch when the plan settles.
Send us the scope you already have
Even a rough list is enough to start. We come back with the gaps, the risks and the shape of a priced plan. No demo theatre.