How every build starts
Find out exactly what it will cost before you commit to it.
The Blueprint is the model of your project: a spec, an architecture, a clickable prototype and a real number. You do it before committing to anything large.
- Scope
- One system, defined together
- Who works on it
- One person, start to finish
- Result
- Spec, architecture, prototype, estimate
- The price
- Quoted up front, fixed once agreed
The problem
Software projects don't fail in the coding.
They fail at the start, when nobody has written down clearly what needs to exist. It begins with a conversation and a rough estimate, and three months later the unspoken assumptions surface. That is why the first thing we sell is not code.
What you get
- 01
Functional spec
What the system does, for whom, in what order. Written in your language, not in jargon.
- 02
Technical architecture
Which components, which technologies, what integrates with what.
- 03
Clickable prototype
Not a picture. You click through it and show it to your team.
- 04
Phased estimate
A range, not a single number. A single number is always a lie.
- 05
Execution plan and risks
What can break, and what we do when it does.
The process
- 01
- A long conversation. We ask the uncomfortable questions now, not in three months.
- 02
- We write the spec and the architecture. You get a draft and you correct it.
- 03
- The prototype.
- 04
- The estimate, the plan, the risks. We walk through them together, point by point.
The guarantee
The Blueprint fee comes off the build entirely.
If we go on to build together, the Blueprint cost you nothing.
If you decide not to build with us, the document is still yours.
You can take it to your own team or to another firm. We sell it that way because a client who feels trapped isn't a good client — not for them, not for us.
The deliverable
This is what you receive.
3.2 — The order flow
From quote request to confirmed order
- The client sends the request through the form or by email. client
- The system checks stock for every line and flags what is missing. automatic
- Sales fills in the delivery date for the missing lines. sales
- The quote goes out as a PDF, valid for 14 days. automatic
- On acceptance the order is created in the ERP and stock is reserved. automatic
What version 1 does NOT do
- It does not compute volume discounts — those are entered by hand
- It does not issue the invoice; it only prepares the data for it
- It has no mobile app
Who it is for, and who it is not for
- You have an idea with no shape yet and want to know the cost before committing.
- You have quotes that differ by a factor of three and no idea which to believe.
- You have a system that works but do not know what to change for it to scale.
- You want a price by email, with no conversation. I cannot give a real figure without understanding what I am building.
- You want to pay in full at the end. We work in phases, in both directions.
- You already have four suppliers on the same project. I will not be the fifth.
Questions
Why pay for a Blueprint? Others quote for free.
We also give you a free estimate, after a 30-minute call. The difference is what you get for the money: a free quote is a number nobody can stand behind, because nobody analysed anything. The Blueprint is the document the number comes from — and it stays yours.
Why not just build the whole thing?
We do, and in most cases that is what happens. But the Blueprint doesn't tie you to us. It is your document: you can take it to your own team or to another firm.
What if you disappear?
The code sits in your repository, on your account, from day one. Setup and run documentation is part of delivery. And we use nothing exotic — any ordinary developer can pick the project up.
It's too expensive.
Then we cut scope, not price. A Blueprint for a single feature costs less than one for the whole system. What we won't do is deliver the same thing cheaper — that would mean the original price was invented.
Can you start next week?
Usually not. We run one project at a time, so we don't do to you what firms juggling five at once do to their clients. You get the real date we can start — and if it doesn't work for you, you hear it in the first call.
Can you quote by email, without a call?
No. A price given without understanding what we are building is an invented number, and we would both find that out three months in. Thirty minutes is enough to give you a range we can stand behind.
What does a Blueprint NOT do?
It doesn't write production code and it doesn't ship your system. It is the document the system comes from. And it doesn't guarantee the project is worth building — if the analysis says it isn't, we tell you. That is the cheapest way to find out.