Prototype Readiness

Complete a focused intervention that advances Prototype Readiness. The objective is to remove ambiguity around prototype type, user test, feedback quality and iteration plan, give the founder a decision-ready output, and make it clear whether the venture should progress, repeat the task with stronger evidence, escalate to expert support, or move into a linked stage.

Bertie or a programme manager assigns Prototype Readiness when the venture needs a decision-ready output for this group. Typical triggers include group-gate reviews, evidence gaps identified by the co-pilot or founder request.

validated problem evidence; target user; solution concept; technical constraints; current product artefacts; specific context for prototype type, user test, feedback quality and iteration plan.

1. 1Clarify the Purpose of Prototype Readinessexpand_more

   Define precisely why testing a prototype at this stage is necessary to validate core commercial and technical hypotheses. Establish the specific risk signals, decision gates, and boundary conditions that determine whether the venture proceeds or pivots. Align the founding team on what success looks like before deploying testing resources.

   Objective

   Completing this action defines the strategic rationale and validation goals for testing the early product interface or workflow. It prevents wasted build effort by ensuring the prototype directly answers the venture's most critical unanswered questions.

   What's expected

   The founder must document a clear hypothesis map linking prototype features to key risk factors. This must include explicit criteria for what constitutes a passing test result versus a failure signal. The output must detail the exact decision gate this prototype readiness exercise will unlock.

   Consultant stress-test · 5 questions

   1. 1.What specific commercial or technical hypothesis is this prototype designed to prove or disprove?
   2. 2.Why is a prototype required now rather than gathering further qualitative discovery data?
   3. 3.What exact failure threshold will force you to stop and re-evaluate your value proposition?
   4. 4.How does proving readiness at this stage derisk your upcoming technical roadmap?
   5. 5.Which key customer assumptions remain unvalidated if this prototype test succeeds?

   Open action arrow_forward
2. 2Define Prototype Scope and Test Parametersexpand_more
3. 3Assemble Critical Venture Inputs and Artefactsexpand_more
4. 4Draft the Prototype Readiness Artefactexpand_more
5. 5Audit Prototype Evidence and Quality Standardsexpand_more
6. 6Update Venture DNA and Select Next Taskexpand_more

• A data-room asset titled Prototype Readiness
• A clear task output, updated venture DNA and recommended next action
• It should update the venture DNA with specific evidence or decisions about prototype type, user test, feedback quality and iteration plan, create a visible milestone in the founder journey, and generate one or more recommended next tasks

A mentor or evaluator can review the output at the group gate. Programme managers can require an advisor checkpoint before Bertie moves the venture forward.

Draft your output and let Bertie review it