Skip to content
Engagement · Per project — pay as you go

A defined scope. A date. Pay for what ships.

The right shape for a first version, a rebuild, or a system with clear edges. We estimate together, break the work into milestones, and you pay as each one lands in production — not before.

Request an estimate

How it works

1

Scope together

A working session that turns your request into a specification with edges — and cuts what doesn't earn its cost.

2

Fixed estimate

Price and timeline per milestone. What you sign is what you pay — estimation risk is ours.

3

Ship in milestones

Each milestone is working software in production. You pay on acceptance, milestone by milestone.

4

Warranty & handover

A 90-day warranty on everything shipped, full documentation, and a clean handover — or an operate retainer.

Terms most vendors bury

We put them on the page instead.

Payment
Per accepted milestone. No large deposits — the first invoice follows the first delivery.
Scope changes
Re-estimated openly and priced before work continues. Never discovered on an invoice.
Overruns
If we under-scoped, the overrun is ours. The estimate you sign is the price you pay.
IP & ownership
Yours in full, transferred milestone by milestone as each payment clears.

What a milestone plan looks like

An illustrative plan for a mid-size operational platform. Yours will differ — but it will have this shape: each milestone is usable software, and each payment follows acceptance.

MILESTONESCOPEPROOF OF DONETIMELINE
M1Core data model + first workflow (e.g. quoting) usable by a pilot groupPilot team quotes real ordersWeeks 1–5
M2Second workflow + integrations with existing ERP/CRMData flows both ways, no re-keyingWeeks 6–10
M3Full rollout: permissions, reporting, edge cases from pilot feedbackWhole team switched overWeeks 11–16
M4Hardening, documentation, monitoring, handover or retainer setupYour team can operate itWeeks 17–20
Illustrative — the real plan is produced in the estimate phase, priced per milestone.

A good fit when

— The outcome can be described in a page: "a system that does X for team Y"— A first version genuinely useful within 3–6 months— You want the total cost known before committing— There's an internal owner who can accept milestones

Consider another model when

— The roadmap is open-ended and evolving → dedicated team— You're pre-revenue with strong distribution → partnership— The scope changes weekly by design (early product discovery)— Nobody internally can own acceptance decisions

Common questions

What do projects typically cost?

It depends entirely on scope — that's why the estimate phase exists — free of charge. You'll know the full number before committing anything.

What counts as "accepting" a milestone?

Each milestone has acceptance criteria written into the estimate — concrete, testable statements. You check them against the running software, not against a demo.

What if we want changes mid-build?

Normal and expected. Changes are re-estimated openly and priced before work continues — you decide with the numbers in front of you, never on an invoice afterwards.

What happens after the last milestone?

The 90-day warranty starts, and you choose: an operate retainer (we run and improve it) or a documented handover to your team — including hiring support.

Standing commitments, every model

The estimate holds

If we under-scoped, the overrun is ours — never discovered on an invoice.

90-day warranty

Defects in anything we ship are fixed free after acceptance.

First invoice after first delivery

No large deposits; payment follows working software.

Exit at any phase

Stop after any milestone and keep everything produced.

Case study · Legal · Per project

A law firm first-passes every contract through its own review model

Lawyers review flagged clauses instead of reading page one to signature — delivered on the signed estimate.

Read the case study →
−82%
first-pass review time
< 1 year
payback

Bring the brief. Leave with an estimate.

Scoped, milestone-priced, and signed before any work starts.