Turn your notes into a Build Brief
By now, you've shaped the idea enough to make a decision. Now pull the important parts into one clean Build Brief: what you're building, who it's for, why it matters, what the first version includes, what it leaves out, and what still needs to be validated.
Use it before you build or to tighten an existing app that needs clearer product direction.
By the end, you should have:
- the core problem
- the starting customer
- the market gap
- the product direction
- the first version scope
- the validation plan
- the distribution plan
- the brand baseline
- a Build Brief you can use as AI context
1. Pull the pieces together
Shape should leave you with one usable source of truth, not a pile of disconnected notes.
Your Build Brief should pull together:
- problem
- customer
- market
- product direction
- viability
- demand test
- distribution
- brand basics
If something still feels unclear, keep it visible. The brief should show the gaps before you build around them.
2. Keep it short enough to use
A Build Brief should be practical, not precious.
If it gets too long, you won't use it. Your AI tools won't get clean context, and the doc becomes another responsible-looking thing collecting dust.
Aim for one page or a few tight sections.
Long enough to guide the build. Short enough to paste into a working chat.
3. Use it as AI context
AI tools are better when they know what they're building toward.
A vague prompt gives you vague product decisions. A clear brief gives the tool the context it needs: who the product is for, what pain it solves, what v1 includes, what it avoids, and what kind of product it should become.
The difference is obvious.
Build me a dashboard for support teams.
Versus:
Build a first version of a lightweight support insights app for B2B SaaS support leads who need to spot recurring customer issues before they become account risks.
Better input. Better output. Fewer ghosts in the machine.
4. Decide your next move
At the end of Shape, make the call.
Maybe the idea is ready to move into Build. Maybe it needs another demand test. Maybe the customer is still too broad. Maybe the scope is already getting suspiciously large and needs to be cut down before it eats your weekend.
| If this is true | Next move |
|---|---|
| The pain, customer, and workflow are clear | Move toward Build |
| The customer is still too broad | Go back to Find your customer |
| The gap is weak | Go back to Map the market |
| The value is unclear | Rework Shape the product |
| The demand signal is weak | Run another demand test |
| The idea feels forced | Pause it and save the notes |
Prompt
This prompt is not here to create a business plan. It's here to turn your Shape work into a usable Build Brief.
Build Brief
Take all of my Shape notes and organize them into a concise Build Brief.
Please structure it into:
1. Product idea
2. Core problem
3. Starting customer
4. Current workaround or alternative
5. Market gap
6. Core use case
7. First value moment
8. Main workflow
9. First version scope
10. Non-goals
11. Viability risks
12. Demand test
13. Distribution plan
14. Brand baseline
15. Recommended next move
Then audit the Build Brief.
Please flag:
- where the problem is still unclear
- where the customer is still too broad
- where the market gap is weak
- where the first version is too bloated
- where the path to payment is unclear
- where the distribution plan is too vague
- where the idea needs more validation before building
Be direct. If this is not ready to build yet, tell me what needs to be fixed first.
Before you move on
| Check | What to look for |
|---|---|
| The brief is too long | If you won't actually use it, tighten it. |
| The customer is still broad | Your Build Brief should point to a real starting segment. |
| The first version is bloated | The brief should protect the build from scope creep. |
| The AI context is vague | Better context means better outputs from Lovable, Cursor, Claude, or whatever tool you use. |
| The next move is unclear | Shape should end with a decision: build, test, keep shaping, or pause. |
| You're treating the brief as final | This is a working source of truth, not a stone tablet. |