Build product

Build Product

Turn a validated idea into a complete, verified, shippable digital product — to a top-tier bar, with every artifact checked rather than assumed.

When to use

After an idea passes research-brain/idea-scout, or whenever asked to "build the tracker / workbook / kit / app for X."

The protocol

1. Restate the buyer and the one job. A product that does one job superbly beats a bundle that does five jobs adequately. Write the single sentence of value the buyer gets.

2. Pick the smallest complete shape. Choose the format that fully delivers the job: a workbook, a single-file app, a playbook, a template set. Complete beats elaborate.

3. Design the spine first. Define the inputs, the core computation or logic, and the one or two views that prove it works. Everything else is overdelivery on top of a spine that must be correct.

4. Build with guards. For anything that computes:

   • Handle the empty state (no data yet) without breaking.
   • Make every total reconcile — to the cent — by an independent path.
   • Never let a display value and a computed value disagree.

5. Verify each artifact, do not assume it. Open what you built. Recompute the numbers a second way. Confirm the files exist and contain what you expect. "It should work" is not "it works."

6. Overdeliver deliberately. Add the one or two extras that turn a fine product into one worth recommending — a starter template, a quick-start, a clear example walked end to end.

7. Prepare the hand-off. Assemble the listing kit (clear title, honest summary, the visual sequence) so the product can actually be found and bought.

Output

The finished deliverable plus a short build report: what it is, what was verified and how, and any known limitation stated honestly. Hand the result to build-brain/ship-gate for an independent GO/NO-GO — never gate your own work.

Honesty rule

If a number did not reconcile or a file did not open, fix it before you call it done. Report what you actually verified, not what you intended.