OpenBuilder

Disciplined Entrepreneurship

Move from a broad idea to a focused market, tested value and an evidence-backed product plan.

What you will produce

Venture dossier

Choose the right starting point

Stage: Pre-idea → growth. Study at your own pace and allow time for fieldwork. Reading and watching alone do not establish a venture result.

Course outline

  1. Decide whether you are ready to explore this venture

    A disciplined process begins with the founder and the team

    Work to bring back: Separate what the team knows from its initial idea. Name a milestone, owner and review date; setup selections alone are not an output.

  2. Segment the market before you choose it

    Specificity is a learning advantage

    Work to bring back: Attach a research source or explicit hypothesis label to each important distinction. Keep alternative segments and the reason for including them.

  3. Primary market research lab

    Learn about a real situation before proposing a solution

    Work to bring back: Participant reference, method, date, observation and limitation. State whether research happened or is still planned; planned work is not validation.

  4. Select one first market

    A beachhead is a deliberate starting point

    Work to bring back: Comparison criteria and sources for the choice. A falsifiable reason to revisit the decision.

  5. Build an end-user profile

    A profile is a pattern across real people

    Work to bring back: Concrete inclusion and exclusion rules. Link each important pattern to notes or mark it untested.

  6. Calculate the beachhead TAM

    TAM is a test of the market story, not a trophy number

    Work to bring back: Customer count, revenue unit, annual frequency, currency and source/range. Explain the largest uncertainty and a way to improve it.

  7. Choose one representative persona

    A persona is a real reference point, not a mascot

    Work to bring back: Participant reference, context, ranked priorities and observed support. Explain what this participant does not represent.

  8. Map the full life-cycle use case

    Customers experience a system, not a feature

    Work to bring back: Roles, actions, delays and handoffs at relevant stages. Flag observed friction separately from proposed fixes.

  9. Write a high-level product specification

    A specification is a conversation starter

    Work to bring back: A clear promise, essential interactions and unresolved assumptions. Explain how the concept addresses the persona's priority.

  10. Build a quantified value proposition

    Value is a change in the customer's world

    Work to bring back: As-is and to-be values, units, method and limitations. A customer test that could reject the promised improvement.

  11. Identify and learn from your next 10 customers

    Ten conversations are a pattern-finding exercise

    Work to bring back: Qualification, current status, source and next action for the ten prospects, or explicit recruitment gaps. Record disagreement and the resulting revision.

  12. Define your Core

    Core is more than a feature

    Work to bring back: Capability, customer benefit, compounding mechanism and evidence still needed. Name one practical investment or test of the capability.

  13. Chart your competitive position

    The alternative is often doing nothing or using a workaround

    Work to bring back: Customer-ranked priorities, relevant alternatives and sources for comparisons. State the implication for the product or first market.

  14. Map the Decision-Making Unit

    The user is not always the buyer

    Work to bring back: Role, priority, influence and a source for each material actor. Mark uncertain roles for follow-up research.

  15. Describe how a prospect becomes a paying customer

    A sale is a process the customer must complete

    Work to bring back: Stages, actors, expected timing, evidence and payment event. A bottleneck, proposed change and observable result.

  16. Buying windows and triggers lab

    A receptive moment still needs a useful next action

    Work to bring back: Timing source, actor, actual offer, measure and predetermined decision rule. Record results or label the test as not yet run.

  17. Calculate follow-on TAM

    Scale through adjacency

    Work to bring back: Annual market assumptions for each option and the capability overlap. A prerequisite and review trigger before entering.

  18. Choose a business model

    A business model is a value-exchange design

    Work to bring back: Payer, beneficiary, charging unit, delivery costs and payment timing. An explicit trade-off and evidence required to decide.

  19. Build the pricing framework

    Price is a hypothesis about value and behaviour

    Work to bring back: Price, charge unit, included service, buyer context and observed action or scheduled test. A threshold for revising the price or package.

  20. Calculate lifetime value

    LTV links customer behaviour to the model

    Work to bring back: Revenue streams, margins, retention, horizon, period timing, rate and currency. Show uncertainty and the acquisition or retention decision the model informs.

  21. Design a scalable revenue engine

    Revenue grows through acquisition and customer success

    Work to bring back: Motion, owner, measure and cost logic for each horizon. A transition threshold and learning feedback loop.

  22. Calculate customer-acquisition cost

    Acquisition cost is a system measure

    Work to bring back: Period/cohort, cost allocation, cash versus time assumptions and count of new paying customers. LTV comparison, gross-profit payback assumptions and remaining operating cash needs.

  23. Identify key overall assumptions

    Assumptions are the hidden structure of a plan

    Work to bring back: Specific belief, consequence if false, current evidence and uncertainty. Name the decision and test affected by the priority assumption.

  24. Test the key assumptions

    The best early test changes a decision

    Work to bring back: Hypothesis, method, participants, measure, threshold, result status and next decision. If not yet run, give a concrete fieldwork plan and do not claim validation.

  25. Define the Minimum Viable Business Product

    The MVBP is a business test, not only a product mock-up

    Work to bring back: Customer outcome, minimum delivery/payment/support components and measurement. Explicit exclusions, resource cap and remaining high-consequence risk.

  26. Show that customers will use and pay

    A product is not validated because people like the demo

    Work to bring back: Sample, period, use/repeat-use counts, value method, payments/refunds and costs. A decision that acknowledges limitations and contradictory findings.

  27. Develop a product plan

    A roadmap should follow evidence and Core

    Work to bring back: Evidence-linked priorities, dependencies, deferrals and review signals. Separate observed results, hypotheses and fictional case material throughout the dossier.

OpenBuilder is an independent course provider. The course credits its source frameworks and separately licensed resources; participation does not imply source-author or university accreditation.