Buteo
04 · Build

Plan the build from what you validated

A Buteo build plan turns a validated idea into what to build first: 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 build plan · its chapters

  1. 01MVP scope
  2. 02Product wedge
  3. 03Products to learn from
  4. 04Technology choices
  5. 05System shape
  6. 06Data model
  7. 07Build vs buy
  8. 08Build sequence
  9. 09Effort & running cost
  10. 10What breaks the build
Illustrative · 10 chapters, the plan's own contents

How it works

  1. Start from your validation

    Its checked findings and its open claims are carried into the plan.

  2. Buteo researches the build

    4 passes in parallel: the technology, products to learn from, tooling and pitfalls.

  3. Read the plan, 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 build plan?

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 go-to-market study.

What the plan 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.

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 plan. It is private: a build plan quotes your own evidence and names what your idea has not yet proved, so only you can read it. See the pricing.

From idea to startup

Where it sits on the way to a startup

FAQ

Questions people ask about this

Do I need a validation before a build plan?

A build plan 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 the build plan 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.

Bring the idea you intend to build.

Describe it in a paragraph. Your first validation is free, with no card, and every finding links to the page it came from.

Validate an idea