Get the blueprint for what you validated
A Buteo blueprint is the build plan for a validated idea: the scope of the first version, the technology choices and the order to build in. It is drawn from the evidence your validation already checked, so the plan argues from what you know rather than from a blank page.
By Buteo · Updated
Your validation
- Findings a source backs
- Claims still unproven
- The verdict, and how firmly it stands
Your blueprint · its chapters
- 01MVP scope
- 02Product wedge
- 03Products to learn from
- 04Technology choices
- 05System shape
- 06Data model
- 07Build vs buy
- 08Build sequence
- 09Effort & running cost
- 10What breaks the build
How it works
Start from your validation
Its checked findings and its open claims are carried into the plan.
Buteo researches the build
4 passes in parallel: the technology, products to learn from, tooling and pitfalls.
Read the blueprint, chapter by chapter
10 chapters, each citing its sources and labelling what is assumed.
What you get
A first version with a cut line
What goes in, what waits, and the open question each inclusion answers.
Technology choices, decided
One recommendation per layer and one named alternative, with the reason.
A build sequence
What to build in which order, and why that order.
Build or buy
Which parts to write yourself and which to take off the shelf.
Effort and running cost
What it takes to build, and what it costs to keep running.
What breaks the build
The ways a build like this one fails, researched rather than imagined.
What is in a blueprint?
10 chapters that answer how to build the thing you validated: MVP scope, Product wedge, Products to learn from, Technology choices, System shape, Data model, Build vs buy, Build sequence, Effort & running cost, and What breaks the build. It is the build side only. Market, messaging and pricing belong to the business case.
What the blueprint reports cites a page you can open, and a line with no source behind it is labelled as an assumption rather than passed off as a finding. Every chapter's next steps are gathered into one action plan you tick off, and every line is yours to edit by hand.
How is it tied to my validation?
It starts from the evidence your validation already checked. The claims, the findings and what stayed unproven are carried in, then 4 research passes add what a build needs: the technology, products to learn from, tooling, and the ways builds like this one go wrong.
That is why the first chapter can draw the line for the first version against the questions your validation left open. Everything it puts in names the question it answers.
Does it tell me which technology to use?
Yes, with one recommendation for each layer and exactly one named alternative. A list of options hands the decision back to you; a recommendation with its reason and one fallback is something you can accept or argue with.
What does it cost, and who can read it?
6 credits a blueprint. It is private: a blueprint quotes your own evidence and names what your idea has not yet proved, so only you can read it. See the pricing.
Where it sits, from the idea to the blueprint
01 Find the idea
03 Test
04 Business case
05 Blueprint
- Blueprint
Questions people ask about this
Do I need a validation before a blueprint?
A blueprint is drawn from a validation's evidence, so that is where it starts. The validation is what tells the plan which claims held, which are still open, and therefore what the first version has to prove.
Is a blueprint a guarantee the product will work?
No. It is a plan that shows its sources and labels its assumptions. It tells you what to build first and why, and what could break the build. Whether customers pay is still settled by putting something in front of them.