// The offer ladder
One week and one price, before anything else.
Three steps, each with its scope agreed before it starts. No proposals-by-negotiation, no hourly meters.
The Blueprint
We map how the business runs, audit whatever software exists, and specify the system you need.
- Full written specification
- Architecture & fixed build quote
- Yours to keep — take it to any developer
- If it doesn't end in a plan you could hand any developer, it's free
The build
The system, built module by module against the approved spec.
- Live in production from week one
- A working demo every Friday, or that week is free
- Tested, documented, deployed
- You own code, data, and infrastructure
The partnership
The system grows with the business — and someone senior answers when it matters.
- New modules & improvements
- Monitoring, maintenance, hosting
- A direct line to your engineer
The standing promise: nothing is built before you've approved a written spec, the software is live in production from the first week, and you see a working demo every Friday. If a week ends with nothing to show, that conversation happens in the demo — not in month three.
From first message to live system.
- 01
Day 0
You send the form or an email. A human reads it — no qualification bot, no drip sequence.
- 02
Day 1
I reply, and we book a 20-minute call. A fit check in both directions; if I'm wrong for it, I say so on the call.
- 03
Week 1
The Blueprint: your operation mapped, existing software audited, and a written spec with a fixed quote at the end — yours to keep either way.
- 04
Week 2
If you take the build: work starts, and the software is live in production before the week ends. Small, real, growing.
- 05
Every Friday
A live demo of the working system. If a Friday comes with nothing to show, that week is free.
- 06
Acceptance
The final slice passes your acceptance criteria; docs and accounts are already yours. Partnership continues only if you want it to.
The questions this raises.
Can I stop after the Blueprint?
Yes — that's the design. The spec and quote are yours to take to any developer. About the worst outcome available is spending one week to discover exactly what your system takes, which is not a bad worst case.
What if the build quote feels too high?
Then you decline it and keep the spec. You've spent one week to avoid guessing at a decision worth many times that — and if you build later, with anyone, the Blueprint still holds.
Start where every engagement starts.
One week, one written verdict, and a plan you could hand to any engineer — including one who isn't me.