Chapter 28 — Week 10: Mock VC and commercialisation

Welcome to Week 10. Ten weeks ago you started with 30 candidate ideas, no team agreement, no customers, no product, no evaluation infrastructure, no economics, no pitch. This week you face a panel of academic and practitioner reviewers with a working product, paying-customer commitments, defended unit economics, a 36-month financial model, and a 12-slide thesis document — and you make the case for whether the project should continue past graduation, and on what terms. The single most-common Week-10 mistake is to treat the mock VC as the finish line. It is not. The mock VC is the gating event; the deliverable is the credible commercialisation plan that follows from it. Pitch quality determines feedback quality; commercialisation viability determines whether the project continues. Both matter; neither alone is sufficient.

Chapter overview

This chapter is the closing chapter of Part V and of the playbook track. It follows the same six-part structure as the prior nine playbook chapters. §28.1 (Concept) sets out what the mock VC is and is not, the panel composition and the dynamics of academic-plus-practitioner review, the structured pitch-plus-Q&A protocol, the commercialisation milestone (which is distinct from the pitch), the blameless post-mortem methodology, the handoff from MVP-team to operating-company-or-graceful-end, and the career-pathway mapping for the unit’s alumni. §28.2 (Method) is the day-by-day Week 10 sprint: dress rehearsal Monday, mock VC pitch Tuesday, feedback integration and post-mortem Wednesday, continuation decisions Thursday, submission and course wrap-up Friday. §28.3 (Lessons from the cases) pulls eight specific lessons that integrate Parts I–III’s analytical material with the playbook execution — including the patterns of YC Demo Day, Anthropic’s progressive funding cycle, Watson Health’s commercialisation failure, and the graceful-end pattern for projects that do not continue. §28.4 (Tools and templates) gives you the mock VC pitch protocol, the commercialisation plan template, the blameless post-mortem template, the founder-continuation matrix, the IP and entity-transfer documentation, the 12-month roadmap template, and the “graceful end” checklist. §28.5 (Worked example) continues Team Aroma through their Week 10: Monday dress rehearsal; Tuesday afternoon mock VC with a 4-panellist mixed academic-practitioner panel; Wednesday feedback integration and post-mortem; Thursday founder-continuation decisions (Aliyah + Wei Hao full-time post-graduation, Sara + Daniel + Priya in advisory / part-time roles); Friday final submission and the unit’s closing meeting. §28.6 (Course exercises and deliverables) specifies the Week 10 submission with grading rubric, and closes the playbook with the integration retrospective.

How to read this chapter. Read §28.1 in full at Sunday evening of Week 9 or Monday morning of Week 10. The conceptual material on the panel dynamics and the commercialisation milestone is what shapes the team’s posture through the week. Read §28.2 with the team and assign per-day owners. Treat §28.3 as Wednesday-evening reading after the post-mortem. Use §28.4 throughout. Read §28.5 before Thursday’s continuation decisions. Submit against §28.6 by Friday 23:59. This is the last set of submissions for the unit.

28.1 Concept

28.1.1 What the mock VC is — and is not

The mock VC pitch in Week 10 is a structured evaluation event with three audiences and three purposes.

The audiences: the academic panellists (Monash faculty, evaluating against the unit’s learning outcomes); the practitioner panellists (founders, investors, industry experts, evaluating against startup-realistic standards); and the team itself (using the panel’s response as feedback for the commercialisation decision).

The purposes: to assess the team’s investability narrative (the pitch quality from Chapter 27); to provide realistic feedback the team can act on (whether or not they continue post-graduation); and to gate the commercialisation milestone (which determines part of the unit grade and shapes the team’s continuation decision).

The mock VC is not a real investor pitch — no money is at stake — but it is structured to mirror the dynamics of a real one. Panellists are briefed to ask the questions a real investor would ask, with the same scrutiny on unit economics, market sizing, and team credibility. The teams that prepare for the mock VC as if it were real are the teams that produce the strongest deliverables.

The mock VC is also not a final exam in the conventional sense. There is no answer key; the panel’s evaluation is qualitative and judgement-based. What the unit is evaluating is the team’s ability to make a defensible argument for the project’s viability — which is what graduate-level startup work culminates in.

28.1.2 The panel composition and dynamics

A typical Week-10 panel for this unit is four panellists: two academic (typically the unit instructor and one other Monash faculty member with relevant expertise — finance, marketing, technology) and two practitioner (typically a founder of a VC-backed startup and a venture-stage investor or successful operator).

The viewpoint differences matter for the team’s preparation:

Academic panellists focus on: - Conceptual framing (does the team understand the theoretical foundations of their work?) - Methodological rigour (are the unit-economics calculations correct? is the market sizing methodologically defensible?) - Connection to course material (can the team cite the analytical-track readings that shaped their decisions?) - Honesty about limitations (do they acknowledge what they don’t know?)

Practitioner panellists focus on: - Commercial realism (would real customers actually pay this? would real investors fund this?) - Execution risk (can this team actually do what they claim?) - Market dynamics (is the competitive landscape real? are the moat claims defensible?) - The “would I invest?” question

The team’s pitch and Q&A responses must work for both audiences simultaneously. A pitch that satisfies the practitioners but loses the academics fails the methodological-rigour test; a pitch that satisfies the academics but loses the practitioners fails the commercial-realism test. The Week-9 preparation work covers the practitioner side; the connection to course material (Parts I–III readings) covers the academic side.

A specific note on the academic panellists’ questions: they will probably ask about the analytical-track readings that informed the team’s decisions. “In your strategy slide, you reference the Iansiti-Lakhani factory framework. Can you walk us through how that framework specifically shaped your architectural decisions?” The team that has read Chapter 3 thoroughly can answer; the team that has skimmed cannot. The integration of analytical depth with playbook execution is what the academic side is checking.

28.1.3 The structured pitch-plus-Q&A protocol

The mock VC session structure is approximately:

[12 minutes] Team's pitch
  - The full 12-slide deck
  - Lead presenter delivers; other team members assist with demo / specific slides
  - Strict time enforcement; the panel chair will signal when 12 minutes is up

[25 minutes] Q&A
  - Panellists alternate questions
  - Each question gets 1-3 minute response
  - Tough or follow-up questions are expected
  - The team may take one panellist's question and have a different team
    member answer (rehearsed in advance)

[5 minutes] Panel deliberation (team is asked to step out)

[5-8 minutes] Verbal feedback delivery
  - Panel chair summarises the panel's reaction
  - Each panellist offers 1-2 specific points
  - The team may ask 1-2 clarifying questions
  - No defensiveness; receive the feedback

[Within 1 week] Written feedback delivered
  - Structured per-component feedback
  - Specific suggestions for improvement
  - Some panellists may offer follow-up conversations or warm intros

The full session is approximately 45–55 minutes. Two teams can typically be processed per panel session of ~120 minutes total; some unit configurations have the panel run sessions back-to-back over Tuesday afternoon.

A specific procedural note: the team’s preparation should anticipate the verbal-feedback delivery as a learning opportunity, not as a verdict. Defensiveness during feedback is read as inability to take input — a fatal trait in real founders. Receive the feedback graciously, ask one clarifying question if needed, thank the panel.

28.1.4 The commercialisation milestone

The commercialisation milestone is distinct from the pitch and is what the unit’s grading is partly gated on. It is a written document, typically 4–8 pages, that answers: if this project were to continue past graduation, what would that actually look like?

The document covers:

Continuation status. Will the project continue? At what level — full-time, part-time, advisory? Which founders are continuing, in what roles, on what timeline?

Entity and IP arrangements. Will a Sdn Bhd / Pty Ltd be registered? Has the IP been transferred from the team’s individual ownership to the entity? What are the founder-equity arrangements going forward?

Capital path. Is the team raising capital? From whom? On what timeline? Or is the team bootstrapping? What is the runway plan?

Operating plan, 12 months. What does Year-1 look like? Customer acquisition, hires, milestones, cash flow.

Regulatory and compliance plan. What regulatory approvals or registrations are needed? PDPA / GDPR compliance for products handling personal data; sector-specific regulation; tax registration.

Risk register and mitigation. The major risks (technical, market, competitive, financial, team) and the team’s plans for handling them.

Graceful-end alternative. If the project does not continue, what happens to the work? Open-source release? Transfer to another team? Documentation for future reference? The graceful-end planning is itself a sign of maturity.

The milestone is not asking for certainty — student-team commercialisation is inherently uncertain. It is asking for thoughtfulness: has the team considered the realistic paths forward and made informed decisions? A team that submits “we will continue and raise USD 5M in 6 months” without supporting analysis fails the milestone; a team that submits a thoughtful continuation plan with explicit caveats and contingencies passes.

28.1.5 The blameless post-mortem

Software-engineering culture has developed the blameless post-mortem methodology (Beyer et al., Site Reliability Engineering, 2016) for post-incident learning. The methodology applies to startup-team retrospectives at the end of a project phase: focus on systemic learnings rather than individual blame; assume good faith; prioritise process improvements over personal failings.

The Week-10 post-mortem covers the 10-week project. Format:

What worked. The 3–5 things that worked well. Specific to the project, not generic (“the team communicated well” is generic; “the Tuesday + Friday meeting cadence with explicit timezone-rotation prevented the coordination breakdowns we feared” is specific).

What did not work. The 3–5 things that did not work, with diagnosis. Specific causes. The Watson Health case is the canonical reminder: failure modes are typically structural (broad framing, no evaluation infrastructure) rather than personal.

What we would do differently. Concrete process or decision changes for next time. “We would invest in evaluation infrastructure earlier — by Week 3 rather than Week 5” is concrete; “We would manage time better” is not.

The biggest single learning. The one insight per founder that they will carry forward. Often this is a piece of received wisdom that the founder previously heard but did not internalise until now.

The post-mortem is structurally important because it produces transferable learning. A founder who has done one playbook well does not yet know what they actually learned (vs what they happened to do). The retrospective forces explicit articulation. A team that submits a thoughtful post-mortem demonstrates the meta-skill that distinguishes good founders from lucky ones.

28.1.6 The handoff — continuation, transition, or graceful end

By end of Week 10 the team must decide: what happens to the project after the unit ends?

Three patterns recur:

Full continuation. Some or all founders commit to continuing the project full-time post-graduation. The team registers an entity, transfers IP, raises capital or bootstraps, and begins the post-graduation operating cycle. Typically 20–40% of student-team projects in Year 10-week courses fit this pattern; the others vary.

Partial continuation. Some founders continue full-time; others continue part-time or in advisory roles; others have completed the unit and move to other paths (employment, further graduate study, different startup ideas). This is the most-common pattern. The continuing founders maintain the project; the departing founders typically retain a small equity stake reflecting their Week 1 founder agreement.

Graceful end. No founders continue full-time. The project is wound down. The IP, code, and customer relationships are documented; if appropriate, an open-source release closes out the work. The team’s investment is captured as learning, not as ongoing operating commitment.

There is no judgement attached to which pattern a team chooses. A team for whom none of the founders is positioned to continue full-time is not a failed team; the unit’s purpose is to teach, not to seed venture-funded startups. The graceful-end pattern, executed well, produces a clean end and preserves the team relationships for future ventures.

The key is that the decision is explicit and documented, not drift. A team that lets the project fizzle without explicit decision produces ambiguity (who owns the GitHub repo? what happens to the alpha users? who responds when a beta customer emails?) that creates confusion for everyone involved. The Friday submission requires the explicit decision.

28.1.7 Career pathways from the unit

The unit produces alumni who follow different pathways. The team’s reflection should document the per-founder career direction:

• Founders continuing the project. What does the next 12 months look like? What is the funding plan? What is the personal financial runway?
• Founders joining AI-native startups. Which companies are realistic targets? What is the network through which the team’s reputation transfers?
• Founders joining enterprise AI teams. Which companies and roles? How does the unit experience translate to job-application material?
• Founders pursuing graduate study. Which programs? How does the practical work relate to the academic interests?
• Founders pursuing other entrepreneurship. Different ideas, similar approach. The Week-1-through-Week-10 playbook transfers; the specific project does not.

Each pathway is legitimate; the unit’s purpose is met when the founders have substantive career direction shaped by the work. Documenting the pathways is part of the Week-10 submission because it forces explicit reflection.

28.1.8 The retrospective on the analytical track

The unit’s two tracks — analytical (Parts I–IV readings) and playbook (Part V execution) — are designed to integrate. By Week 10, the team can articulate which analytical concepts most-shaped their playbook execution. The retrospective documents this integration.

For Team Aroma’s Pulse, the integration patterns are typical:

• Chapter 3’s Iansiti-Lakhani factory framework shaped the architectural decisions in Chapter 22 (the four-layer stack). The team’s instinct to build Layer-3 (intelligence) deeply while buying Layers 1, 2, and 4 came directly from the Chapter 3 reading.
• Chapter 5’s strategic frameworks (collisions, the new meta) shaped the competitive analysis in Chapter 27. The team’s positioning against Snapask and Pandai used Chapter 5’s vocabulary.
• Chapter 6’s banking-AI cases (especially JPMorgan COiN) shaped the Chapter 21 narrow-framing discipline. The team’s resistance to “broad EdTech platform” framing came from the Watson Health and COiN comparisons.
• Chapter 23’s evaluation methodology (drawing on Chapter 2’s statistical learning theory) shaped the Week-5 golden-set construction. The Vapnik-bound discussion was abstract until the team had to size their own golden set.
• Chapter 26’s unit-economics framework drew on Iansiti-Lakhani plus the SaaS-metrics literature. The team’s sensitivity-analysis discipline came from the Chapter 26 modelling.

A team that can articulate three or more such integration patterns demonstrates the academic dimension of graduate-level startup work. The integration is what distinguishes the unit’s deliverable from a non-academic startup-accelerator output.

28.2 Method — the Week 10 sprint

28.2.1 Day 1 (Monday): dress rehearsal and commercialisation plan v1

By Monday end-of-day:

• Dress rehearsal completed. The team runs a full 12-minute pitch + 25-minute Q&A in the actual format that will be used Tuesday, with two non-team members (faculty, mentor, or other team) playing the panel. The rehearsal catches last-minute issues (timing slips, slide-display problems on the presentation laptop, demo glitches).
• Commercialisation plan v1 drafted. A 4–6 page document covering continuation, IP, capital path, operating plan, regulatory plan, and risks per §28.1.4. The v1 is rough; the v2 after Tuesday’s mock VC integrates panel feedback.

The dress-rehearsal feedback is critical and will produce specific changes to the deck or delivery before Tuesday. Allow 2 hours for the rehearsal plus 4 hours for incorporating changes.

28.2.2 Day 2 (Tuesday): the mock VC pitch

The mock VC session typically runs Tuesday afternoon. Specific preparation:

Tuesday morning: - Final tech check (laptop charged; deck on multiple devices; demo runs reliably; HDMI / display adapters confirmed). - Final read of the Q&A response document (every team member should be able to answer any of the 30+ prepared questions). - Coffee, water, light meal — do not pitch on an empty or over-full stomach. - Logistics confirmation (room, time, panellist names, attendance).

Tuesday during the pitch: - Arrive 30 minutes early to set up. - Lead presenter delivers the pitch; other founders are visible at the front but seated until their assigned slide. - During Q&A, the lead presenter or designated answerer takes each question. A founder who is asked something outside their domain may pass to a teammate. - During panel deliberation, the team waits outside calmly. Do not over-analyse during the wait. - Receive feedback graciously. Take notes. Do not argue with feedback in real time.

Tuesday after the pitch: - 60-minute post-pitch team debrief (the same evening, while the experience is fresh). - What was the strongest moment? What was the weakest? What did the panel signal about specific concerns? - Identify the 3–5 specific feedback items the team will respond to in the commercialisation plan v2.

28.2.3 Day 3 (Wednesday): feedback integration and post-mortem

Wednesday is dedicated to two parallel workstreams.

Track 1: Commercialisation plan v2. The team integrates panel feedback into the plan. If the panel raised concerns about Mandarin Q2 timing (as Team Aroma’s panel does in §28.5), the v2 addresses the concern with specific timing and resourcing. If the panel raised concerns about CAC at scale, the v2 addresses with sensitivity scenarios. The v2 is the version that will be submitted Friday.

Track 2: The post-mortem. Each founder writes their individual post-mortem (1–2 pages) covering what worked, what did not, what they would do differently, and their biggest single learning. The team then meets to discuss the individual post-mortems and produces a team post-mortem (3–4 pages) that synthesises the individual learnings into systemic findings.

The post-mortem discipline is structurally important because it forces the team to articulate transferable learnings while the experience is fresh. A team that defers the post-mortem until after graduation typically loses 30–40% of the specific learnings to fading memory.

28.2.4 Day 4 (Thursday): continuation decisions and final documentation

Thursday is decision day. The team meets — synchronously, all members present — and makes the explicit continuation decisions:

• Per-founder commitment. Each founder states their continuation level: full-time / part-time / advisory / completed. The conversation is uncomfortable for some pairings; the discipline of having it explicitly is what produces clean handoffs.
• Entity and equity. If the project continues, what entity will be registered (Sdn Bhd or Pty Ltd)? What does the equity look like with the new commitment levels? Founders shifting from full-time to advisory typically have their unvested equity reduced; the founders’ agreement from Chapter 19 governs.
• IP transfer. If an entity is registered, the team’s individual IP contributions (code, prompts, designs, customer relationships) transfer to the entity per the IP-assignment clauses of the founder agreement.
• Customer communication. The beta and committed customers need to be told what happens next. A team where 2 of 5 founders continue with the others advisory needs to communicate this transition to customers; the communication is itself Week-10 work.
• Documentation handoff. The team produces a comprehensive documentation package covering the project’s state: code repository, deployment access, customer contacts, financial model, brand assets, alpha-and-beta user database. The package is what enables continuation (or graceful end) operations.

28.2.5 Day 5 (Friday): submission and course wrap-up

Friday morning: final polish on the commercialisation plan, post-mortem, and supporting documents. By Friday afternoon:

• The Week-10 submission goes in by 23:59.
• The team’s complete 10-week archive is bundled and submitted. All deliverables from Weeks 1–9 plus Week-10 deliverables, organised in a coherent folder structure (typically by week, with a summary index).
• The team’s career-pathway statements are submitted. One paragraph per founder covering their immediate post-graduation plan and how the unit experience shapes it.

Friday evening: the unit’s closing meeting. Typically a meal or low-key social gathering of the cohort, plus reflection. Informal but emotionally important; teams that have worked closely for 10 weeks have built relationships that the unit’s closing should mark explicitly.

28.3 Lessons from the cases

Eight specific lessons from Parts I–III shape Week 10 work and the integration of the unit’s two tracks.

28.3.1 The YC Demo Day pattern — pitch as integration milestone (Methodology)

Y Combinator’s Demo Day is the structural reference for this unit’s mock VC. YC teams pitch to ~500 investors at the end of a 12-week batch; the pitch is the integration milestone, not the deliverable. The deliverables (the working business, the customer relationships, the team) are what the pitch is evidence of. The pattern transfers: the Week-10 pitch is evidence of the 10 weeks of work, not the work itself.

Operational implication. Treat Tuesday’s pitch as a demonstration of work done, not as the work itself. If the work is not done by Monday evening, no amount of pitching skill will save Tuesday. The discipline is to invest in the work and let the pitch reflect it; the alternative (investing in the pitch and obscuring weak work) is read by experienced panellists immediately.

28.3.2 Anthropic’s progressive funding cycle — staged validation (Chapter 13)

Anthropic raised in stages: pre-seed friends-and-family in early 2021, seed and Series A in 2021–2022, Series B and C in 2022–2023, larger rounds with strategic investors (Google, Amazon) in 2023–2024. Each round was gated on specific milestones — research progress, product release, commercial traction. The progression reflected actual validation, not just larger rounds.

Operational implication. Plan your team’s funding path as a sequence, not a single event. The Week-10 ask is for a pre-seed; the next gate (12 months later) is for a seed; the gate after that is for a Series A. Each round has its own validation requirements; planning the sequence backward from the Series A milestones (Year 2–3) is what makes the Year-1 path coherent.

28.3.3 Notion’s bootstrap-then-raise path — patient capital strategy (Chapter 5)

Notion was largely bootstrapped through 2018 — generating revenue from early users to fund continued development — before raising substantially in 2019 and 2020. The bootstrap period gave the team time to find product-market fit without the dilution of early venture capital. By the time the company raised, the team had pricing power that an earlier raise would have foregone.

Operational implication. Not every project should raise VC. For products with strong early unit economics and modest capital requirements, bootstrapping or grant-funded paths preserve founder equity and reduce the timeline pressure that VC funding introduces. The team’s commercialisation plan should consider the bootstrap option seriously, not just default to “raise capital.”

28.3.4 Carsome’s incremental fundraising — tracking progress against commitments (Malaysian unicorn case)

Carsome raised at increasing valuations through Series A, B, C, and D from 2018 to 2023. Each round was raised against specific commitments to investors made at the prior round; the team’s track record of meeting commitments was what made each subsequent round possible.

Operational implication. The Week-10 commercialisation plan’s 12-month milestones are not just for the panel’s evaluation; they are the foundation of the Year-2 funding round. Choose milestones the team can actually deliver, and keep them. Over-promising in the Week-10 ask creates the credibility cost that future rounds will pay.

28.3.5 Watson Health — commercialisation failure traceable to early decisions (Chapters 2, 7)

IBM’s Watson Health failure was substantially a commercialisation failure: the team did not have a clean view of what the product was, who the customer was, what the unit economics were, or what the realistic GTM path looked like. The investment continued for years on the strength of the Jeopardy! brand moment, without the commercialisation discipline to convert that moment into a defensible business. By the time the commercialisation problems surfaced, the cumulative investment was billions.

Operational implication. Your Week-10 commercialisation plan is the precise antidote to the Watson Health pattern. The plan forces explicit definition of product, customer, economics, and GTM. If your plan cannot answer these questions in 4–6 pages with specific numbers, the team has not done the underlying work; do the work before the plan, not after.

28.3.6 JPMorgan COiN — internal-tool commercialisation as a path (Chapter 6)

COiN was deployed internally at JPMorgan rather than commercialised as an external product. The “commercialisation” was internal: the bank captured the value through its own use rather than by selling the tool to other banks. The path is appropriate when (a) the tool’s value is large enough internally to justify the investment, and (b) external commercialisation would expose competitive advantage.

Operational implication. Some projects in the unit may be appropriate to not commercialise externally — particularly internal-tool projects developed in collaboration with corporate partners. The team’s commercialisation plan can specify “internal use within partner organisation, with knowledge transfer and operating-handoff to partner” as a legitimate path. Document explicitly.

28.3.7 The graceful-end pattern — projects that do not continue (Methodology)

Most student-team projects do not continue full-time post-graduation. Of those that do not, the difference between projects that ended gracefully and projects that fizzled is whether the team made explicit decisions about wind-down: customer communication, IP and code archival, alpha-and-beta-user notification, founder-relationship preservation. The graceful-end pattern produces clean closure that preserves the team relationships and the learnings.

Operational implication. A team that does not continue full-time should follow the graceful-end checklist (§28.4.7). The closure is itself work; do it explicitly. Customers who paid in beta deserve a final update, even if it is “we are winding down; here is the data export.” The team’s reputation is preserved or damaged in this final week.

28.3.8 The integration of analytical and playbook tracks — the unit’s signature

The unit’s signature pedagogical move is the integration of the analytical track (Parts I–IV: theory, frameworks, case literature) with the playbook track (Part V: execution). The integration is most-visible in retrospect: the team’s Week-22 architectural decisions traced to Chapter 3 reading; the Week-23 evaluation methodology traced to Chapter 2 statistical learning theory; the Week-26 unit-economics traced to Chapter 6 financial-services-AI case material. The pattern is what makes graduate-level startup work distinct from MBA case work or undergraduate-startup-club work.

Operational implication. Your Week-10 retrospective should articulate the integration explicitly. “In Chapter 22 we used X framework from Chapter 3, which shaped our architecture in the following ways…” The articulation is what demonstrates the academic dimension of the work; it is also what makes the work transferable. A founder who can articulate the framework-to-decision connections can apply the same patterns to subsequent ventures.

28.4 Tools and templates

28.4.1 The mock VC pitch protocol (for the team and panel)

MOCK VC PITCH PROTOCOL — WEEK 10

DURATION: ~50 minutes per team

ORDER:
  T0      [team enters and sets up]
  T+0     [team's pitch begins; 12-minute timer starts]
  T+12    [12-minute hard stop; panel chair signals]
  T+12    [Q&A begins; 25-minute timer]
  T+37    [Q&A ends; team is asked to step out]
  T+37    [panel deliberation, 5 minutes]
  T+42    [team returns; verbal feedback delivered, 5-8 minutes]
  T+50    [session closes]

PANEL ROLES:
  Chair (typically unit instructor):
    - Opens, sets timer, enforces structure
    - Synthesises feedback for closing
  
  Other panellists:
    - Ask questions during Q&A
    - Provide written feedback within 1 week

TEAM ROLES:
  Lead presenter: delivers the 12-minute pitch
  Other founders: assist with demo / specific slides; answer 
    questions in their domain during Q&A
  All: poised, professional, receive feedback gracefully

28.4.2 The commercialisation plan template

COMMERCIALISATION PLAN — [PROJECT]
Submitted [date]

1. EXECUTIVE SUMMARY
   One paragraph stating the project's continuation status,
   the level of founder commitment, and the headline path.

2. CONTINUATION STATUS
   2.1 Per-founder commitment level
   2.2 Project continuation: full / partial / graceful end
   2.3 Rationale for the chosen path

3. ENTITY AND IP ARRANGEMENTS
   3.1 Entity registration: [Sdn Bhd / Pty Ltd / none / TBD]
       - Jurisdiction, timing, founders involved
   3.2 IP transfer: [description of how IP moves from individual
       founders to the entity, or to whichever entity holds it]
   3.3 Founder equity: post-Week-10 cap table

4. CAPITAL PATH
   4.1 Year-1 funding plan: [bootstrap / grants / pre-seed / mix]
   4.2 Specific funding sources targeted (if applicable)
   4.3 Runway calculation
   4.4 Milestones the funding reaches

5. OPERATING PLAN, MONTHS 1-12
   5.1 Customer acquisition plan
   5.2 Hires planned (if any)
   5.3 Product roadmap (high level)
   5.4 Cash flow projection (from Chapter 26 model)
   5.5 Key risks for Year 1 and mitigations

6. REGULATORY AND COMPLIANCE PLAN
   6.1 PDPA / GDPR / sector-specific regulation applicable
   6.2 Compliance work needed and timeline
   6.3 Tax registration and advisory engagement

7. RISK REGISTER
   7.1 Top 5 risks (technical, market, competitive, financial, team)
   7.2 Mitigation per risk
   7.3 Sensitivity to identified risks (linking to Chapter 26 stress tests)

8. GRACEFUL-END ALTERNATIVE
   If the project does not continue:
   8.1 Wind-down timeline
   8.2 Customer communication plan
   8.3 IP, code, and documentation archival
   8.4 Open-source release plans (if applicable)
   8.5 Team relationship preservation

9. APPENDICES
   - Updated cap table
   - 12-month financial projection (from Chapter 27)
   - Founder commitment letters
   - Customer reference list

28.4.3 The blameless post-mortem template

POST-MORTEM — [PROJECT]
Period: Weeks 1-10

INDIVIDUAL POST-MORTEMS (one per founder, 1-2 pages each)

[FOUNDER NAME]
  Strongest moments of the 10 weeks:
    1. [...]
    2. [...]
  
  Hardest moments / things that didn't work:
    1. [...]
    2. [...]
  
  What I would do differently:
    1. [...]
    2. [...]
  
  Biggest single learning:
    [one or two sentences capturing the most-important
     transferable insight]

TEAM SYNTHESIS POST-MORTEM (3-4 pages)

What worked:
  1. [Specific systemic strength, with example]
  2. [...]
  3. [...]

What did not work:
  1. [Specific systemic weakness, with diagnosis]
  2. [...]
  3. [...]

What we would do differently:
  1. [Concrete process or decision change]
  2. [...]

The biggest single team learning:
  [One paragraph]

Cross-track integration:
  Three to five specific examples of analytical-track
  reading shaping playbook-track decisions:
  1. [Chapter X concept] shaped [specific decision] in
     [specific way].
  2. [...]

28.4.4 The founder-continuation matrix

FOUNDER-CONTINUATION MATRIX

| Founder | Pre-Week-10 commitment | Post-Week-10 commitment | Equity adjustment | Role | Notes |
|---|---|---|---|---|---|
| [Founder 1] | Full-time | Full-time | None | CEO | Continuing |
| [Founder 2] | Full-time | Full-time | None | CTO | Continuing |
| [Founder 3] | ~25 hrs/week | ~10 hrs/week | Reduced from 20% to 12% | Advisor / Head of Design | Reduced commitment; advisory role |
| [Founder 4] | ~20 hrs/week | Completed | Vested fraction retained | — | Moving to enterprise role; advisory available |
| [Founder 5] | ~20 hrs/week | ~5 hrs/week | Reduced from 15% to 8% | Curriculum advisor | Master's degree continuation |

28.4.5 IP and entity transfer documentation

For projects continuing as a registered entity, the IP transfer documentation includes:

• Founder IP assignment letters. Each founder formally assigns their individual contributions (code, designs, prompts, customer relationships) to the entity, in exchange for the founder equity stipulated in the cap table.
• Open-source-license clearances. Verification that the project’s use of open-source code (libraries, models, frameworks) is compliant with the licenses (typically MIT, Apache 2.0, BSD; occasionally GPL with implications).
• Trademark searches and filings. Where the project name is intended for long-term use, a trademark search and (post-funding) trademark filing.
• Patent considerations. Most student projects do not file patents; where the project has genuine patentable innovation (rare; unlikely at the MVP stage), a provisional patent application may be appropriate.

For projects in graceful end mode, the IP arrangements typically default to: each founder retains rights to their individual contributions; the team agrees not to use the project’s specific brand or customer relationships without mutual consent; open-source release is decided collectively.

28.4.6 The 12-month roadmap template

12-MONTH ROADMAP — [PROJECT]

QUARTER 1 (Months 1-3 post-graduation)
  Customers: [target]
  Revenue: [target]
  Hires: [planned]
  Product: [milestones]
  Risks: [...]

QUARTER 2 (Months 4-6)
  ...

QUARTER 3 (Months 7-9)
  ...

QUARTER 4 (Months 10-12)
  ...
  END-OF-YEAR-1 STATE: [the picture of what the company looks
                        like at month 12]

YEAR-2 ENTRY GATE
  Specific milestones that gate entry to the Year-2 plan
  (typically tied to a Series A raise or sustainability
  milestone)

28.4.7 The graceful-end checklist

For projects that do not continue full-time:

GRACEFUL-END CHECKLIST

CUSTOMER COMMUNICATION
  [ ] Beta and committed customers notified by [date]
  [ ] Data export provided for any customer with data in the system
  [ ] Final billing or refund handled (if money was charged)
  [ ] Last-day-of-service date communicated clearly

CODE AND IP ARCHIVAL
  [ ] GitHub repo: archived (not deleted) with README explaining
      the project's history
  [ ] Foundation-model API keys: revoked or transferred
  [ ] Hosting accounts: scheduled for cancellation after data export
  [ ] Third-party integrations: disconnected

DOCUMENTATION
  [ ] Project README updated with full history and learnings
  [ ] Post-mortem published (internally or, if appropriate, publicly)
  [ ] Architecture-decision records preserved

OPEN-SOURCE RELEASE (if applicable)
  [ ] License chosen (typically MIT or Apache 2.0)
  [ ] Codebase prepared for public release (secrets removed,
      proprietary content stripped)
  [ ] Initial documentation written for new contributors

TEAM RELATIONSHIPS
  [ ] Final team meeting held
  [ ] Future-collaboration norms discussed
  [ ] LinkedIn / personal references exchanged

28.4.8 Career-pathway statement template

(One paragraph per founder, ~150–250 words)

CAREER-PATHWAY STATEMENT — [FOUNDER NAME]

Immediate post-graduation plan (12 months):
  [Continuing the project full-time / Joining startup X /
   Joining enterprise role at Y / Pursuing graduate study at Z /
   Other]

How the unit experience shapes this plan:
  [Specific learnings, skills, or relationships from the
   unit that connect to the immediate plan]

Longer-term direction (3-5 years):
  [Where the founder sees themselves in 3-5 years; how the
   unit experience builds toward it]

The integration of analytical and practical work:
  [One specific insight from the analytical track + one
   specific skill from the playbook track that the founder
   carries forward]

28.5 Worked example — Team Aroma’s Week 10

Team Aroma starts the week with a strong Week-9 deliverable: a 12-slide pitch deck, a 36-month financial model, a 12-page Q&A document, and three rehearsals completed.

Day 1 (Monday): dress rehearsal and commercialisation plan v1

Monday 11am KL / 2pm Melbourne, the team runs the dress rehearsal with the unit instructor and one other faculty member playing the panel. Pitch length: 12 minutes 20 seconds (slightly over). Q&A: 28 minutes.

The instructor’s feedback: - The Demo (S4) is excellent — the 95-second walkthrough is clear and the Excel-Education-style branding speaks for itself. - The Unit Economics (S7) leads with the stressed case (8:1 LTV:CAC) which is the right move; the headline 48:1 figure is in the appendix-style support material. - The Financials (S11) shows the J-curve well but the 3-year revenue trajectory deserves a verbal annotation from Daniel during the presentation. - The Ask (S12) is well-specified.

Two things to fix Monday afternoon: - The pitch is 20 seconds long; cut from S2 (Problem; can compress to 70 seconds without losing the verbatim quote) or S6 (Market; can compress the methodology overview). - The Demo had a brief audio sync issue when transitioned from screen-share to desktop video; rerecord with synchronised audio.

Aliyah and Daniel begin the commercialisation plan v1 in parallel. By Monday evening, the v1 is at ~5 pages: continuation status (Aliyah and Wei Hao plan to continue full-time; Sara, Daniel, Priya in advisory or part-time roles); planned Sdn Bhd registration in Q1 2027; Cradle CIP Spark application as the primary pre-seed funding path; 12-month operating plan; risk register.

Day 2 (Tuesday): the mock VC pitch

The mock VC session is Tuesday 2:30 PM KL / 5:30 PM Melbourne. The panel: the unit instructor, a Monash finance faculty member, a founder of an edtech-adjacent Malaysian startup, and a partner at a regional VC firm.

Aliyah leads the pitch. Demo runs cleanly. Pacing matches the rehearsal: 11 minutes 50 seconds. The team is composed; the panel is engaged.

Q&A pattern (paraphrased):

• Practitioner-1 (founder): “Your LTV:CAC of 48:1 looks high. Walk me through your stress test.”
  • Aliyah: leads with the 8:1 stressed case from the Week-8 work; explains the assumptions (10% monthly churn, 3× CAC); references the Sensitivity tab of the financial model.
  • Practitioner-1: “OK, that’s reasonable. Question follow-up: what’s your CAC at scale, after the founder-led-sales channel saturates?”
  • Aliyah: acknowledges the question is one the team has thought about but does not have data for; offers the current hypothesis (referral becomes primary by Month 9; channel marketing by Month 18); commits to come back with sharpened analysis when actual referral data arrives.
• Practitioner-2 (VC): “Snapask raised USD 35M in 2018. What stops them from launching SPM-rubric-aligned features tomorrow?”
  • Wei Hao takes the question (he has prepared this domain): the SPM-rubric alignment is non-trivial — it requires curriculum-design work that Snapask’s pan-Asian team has not invested in; the centre-side workflow integration is a moat Snapask would have to rebuild from scratch; the team’s beta cohort produces a 6-month incumbency advantage.
  • Practitioner-2: “Reasonable. But you’re betting Snapask doesn’t pay attention to Malaysia specifically. That’s a structural bet.”
  • Wei Hao acknowledges this is the bet; the team’s mitigation is speed (be embedded in centres before Snapask responds).
• Academic-1 (Monash finance faculty): “Walk me through your unit-economics model. How did you handle the cost-side variance you must have seen during beta?”
  • Daniel takes this: explains the foundation-model cost calculation (4.2 inferences/student/active-day × 14 active days/student/month × MYR 0.04 = MYR ~0.94/student/month); references the Chapter-23 evaluation work where the team observed the variance distribution; notes that the model uses the 75th-percentile cost as the planning input.
  • Academic-1: “Good. Follow-up: the Iansiti-Lakhani framework you referenced — how does that shape your architectural decisions specifically?”
  • Daniel cites Chapter 3’s four-factor decomposition; explains the team’s Layer-3-build, Layer-1/2/4-buy approach; ties to the team’s Week-22 stack decisions.
• Academic-2 (unit instructor): “Your ‘why now’ frame is good but I want to push on it. What if foundation-model BM capability stops improving?”
  • Aliyah: the team’s bet is that BM capability continues to improve through 2027–2028 because of Chinese-language model investment (Qwen, DeepSeek) and ASEAN-specific government investment; the team’s product would still work at current capability, just with more teacher-side editing required; the moat is workflow integration, not model capability.
  • Academic-2: “OK, that’s defensible.”

The panel asks ~12 questions across the 25 minutes. The team answers all of them with composure.

Panel deliberation (5 minutes; the team waits in the corridor). Verbal feedback (8 minutes):

• Chair (instructor): “The team’s preparation is evident. The pitch is fluent; the deck is well-structured; the Q&A handling is composed.”
• Practitioner-1: “If this came across my desk as a real seed pitch, I’d take a follow-up meeting. The unit economics are credible; the team is credible. I’d push hard on the competitive moat in that follow-up.”
• Practitioner-2: “Concerns: founder-time-allocation post-graduation. Two of you full-time; three of you advisory. You can do the Year-1 plan with two full-time founders, but Year 2 needs hires. Plan for that explicitly. Also: Mandarin in Q2 is realistic only if you delay the customisation work; choose.”
• Academic-2 (instructor): “The integration with the analytical track is visible — the team can articulate the Chapter-3 framework, the Vapnik-bound discussion, the unit-economics methodology. This is the graduate-level dimension that distinguishes this work.”

The team thanks the panel. The session closes at 3:30 PM KL.

The team meets at 5 PM KL for a 60-minute debrief. The strongest moment was the Demo and Aliyah’s handling of the LTV:CAC question. The weakest was Wei Hao’s competitor response, which needed sharpening (he conceded the structural-bet framing rather than turning it into the team’s advantage). The 3 specific feedback items to integrate into the commercialisation plan v2: founder-time post-graduation analysis with named hires; Mandarin-vs-customisation trade-off resolution; competitive-moat sharpening for the next pitch (post-graduation).

Day 3 (Wednesday): feedback integration and post-mortem

Wednesday morning the team works in parallel.

Aliyah and Daniel revise the commercialisation plan to v2 (~7 pages now). Key changes: the Year-1 hire schedule includes a third engineer at Month 8 to allow Mandarin development without delaying customisation; the founder-time-allocation table specifies how Aliyah and Wei Hao will cover product, sales, and operations between them in the first 6 months; the competitive moat section is tightened with the workflow-integration argument elaborated.

Wednesday afternoon the team writes individual post-mortems. Selected excerpts:

• Aliyah (CEO; full-time continuing): “Biggest single learning: the discipline of pre-committed pivot conditions. The Week-1 founder agreement included pivot conditions for the original B2C-parent framing; the Week-2 customer discovery surfaced the centre-side opportunity; the pivot was procedural rather than emotional because we had pre-committed. Without that discipline, I would have argued for the original framing for two more weeks while the evidence accumulated against me.”

• Wei Hao (CTO; full-time continuing): “Biggest single learning: the four-layer stack decomposition. Before this unit, I would have built the entire stack myself out of preference for control. The Layer-3-build, Layer-1/2/4-buy framing forced me to identify what was actually distinctive (the SPM-rubric-aligned prompts and workflow) versus what was commodity (auth, hosting, basic UI). The intellectual move from ‘build everything’ to ‘build the wedge’ is the most-valuable thing I learned.”

• Sara (Head of Design; advisory continuing): “Biggest single learning: the workflow-mapping insight from Week 2’s customer discovery. I would have designed the teacher-review interface as a binary accept/reject before observing that teachers actually inline-edit explanations like draft documents. Watching one user (Cikgu Aishah) for 25 minutes produced an architectural insight that no internal team conversation would have.”

• Daniel (Curriculum lead; advisory continuing, employment in edtech firm): “Biggest single learning: the unit-economics discipline. I had taken business courses before, but the LTV/CAC/payback framework had been abstract. Working through Team Aroma’s actual numbers, with sensitivity analysis, made the framework concrete. I will use it in every business decision going forward.”

• Priya (Content lead; pursuing master’s degree): “Biggest single learning: the integration of theory and practice. The chapter readings became real when we faced their corresponding decisions. The Vapnik bound was abstract until we sized the golden set; the unit-economics framework was abstract until we computed our own LTV. The integration is what graduate-level startup work means.”

The team synthesis post-mortem (3 pages) draws on the individual ones. Key team-level findings: (1) the cross-campus working agreement worked but required maintenance — the timezone-aware standup discipline paid off; (2) the Week-2 pivot would not have happened without the Week-1 founder agreement’s pivot-conditions clause; (3) the data-flywheel instrumentation in Week 7 was the most-leveraged single technical investment of the 10 weeks.

Day 4 (Thursday): continuation decisions and final documentation

Thursday morning the team meets for the continuation decision. The conversation has been pre-discussed individually; the formal session ratifies the agreed plan:

• Aliyah: Full-time continuation. CEO. Cradle CIP Spark application Q1 2027. Plans to take a small Aliyah-personal stipend through the first 6 months from her parents’ support; market-rate salary from Month 7 if revenue supports.
• Wei Hao: Full-time continuation. CTO. Salary deferred until Month 6 in exchange for retaining 25% equity (vs the 20% the original founder agreement implied for full-time-with-salary).
• Sara: Part-time / advisory. Will continue ~10 hours/week as Head of Design while taking a full-time role at a local digital agency. Equity adjusted from 20% to 12%.
• Daniel: Advisory. Joining a Sydney-based edtech startup full-time. Will provide ~5 hours/week curriculum advisory to Team Aroma. Equity reduced to 8%.
• Priya: Advisory. Pursuing master’s degree. Will provide ~5 hours/week content advisory. Equity reduced to 8%.

Total post-Week-10 cap table: - Aliyah 30% (up from 25% reflecting full-time continuation) - Wei Hao 30% (up from 25%) - Sara 12% - Daniel 8% - Priya 8% - Reserved for advisory pool / future hires 12%

Sdn Bhd registration timeline: Aliyah submits the SSM forms in week 3 of post-graduation; entity expected to be live by week 6. IP-transfer letters drafted with the entity formation.

Customer communication: the 18 beta users get a personal email from Aliyah on Friday explaining the post-graduation transition: the product continues, the team continues (with the reduced surface), and pricing transitions per the Week-7 commitments.

Documentation handoff: the team prepares the comprehensive documentation package — repo access, deployment configs, customer database, financial model, brand assets — for ongoing operations. Sara, Daniel, and Priya retain access in their advisory roles.

Day 5 (Friday): submission and course wrap-up

Friday morning Aliyah finalises the commercialisation plan v2. By 11 am KL the document is signed off by all five founders.

Friday afternoon the team submits the final bundle:

• Mock VC pitch (deck PDF, financial model Excel, demo video)
• Commercialisation plan v2 (7 pages)
• Post-mortem (5 individual + 1 team synthesis)
• Founder-continuation matrix
• Updated cap table
• Career-pathway statements (5 founders)
• The complete 10-week archive (Weeks 1–10 deliverables, organised by week)

Friday 6 PM KL: the unit’s closing meeting. The team shares dinner with the cohort and the unit instructor at a Sunway food court. There is no formal speech; just the cohort debriefing the experience over food. Aliyah makes a brief informal toast to the team’s work; the others reciprocate.

Sunday: Aliyah sends the team a reflection email. “Ten weeks ago I had 32 ideas in a spreadsheet. Today we have 5 paying centre commitments, a working product used by 18 students and 3 teachers, and a Sdn Bhd plan submitted to SSM. Thank you all. This is the start, not the end.”

What Team Aroma got right and what they almost got wrong

Three things they did well: (1) the dress-rehearsal Monday caught the timing slip and the demo audio sync issue 24 hours before the mock VC, allowing fix without panic; (2) the verbal-feedback receipt during Tuesday’s panel was composed — no defensiveness, no arguing — and the team integrated the specific feedback into the v2 plan within 48 hours; (3) the continuation decisions Thursday were explicit and pre-discussed, so the formal session ratified the plan rather than negotiating it (the alternative — fuzzy commitments and trailing decisions — is what produces post-graduation drift and conflict).

Three things they almost got wrong: Wei Hao’s structural-bet concession during Q&A almost set a defensive frame for the rest of the Q&A (the team’s recovery on the next question — Daniel’s confident handling of the unit-economics question — restored the dynamic, but it was a near-miss); the team almost set founder-equity changes without explicit IP-assignment letters (which would have created legal ambiguity with the Sdn Bhd registration); and they almost let the Friday wrap-up meeting drift into informal social rather than the explicit closing it should be (the toast Aliyah made marked the closure that an entirely social meal would have left undone).

The pattern is general. Week 10 is high-leverage because the integration of 10 weeks of work into a single defended argument tests every dimension of the team’s preparation. The team that treats the mock VC as theatre rather than evaluation produces theatre; the team that treats it as the gating event for commercialisation, with the discipline that follows, produces the credible business case the unit’s structure is designed to elicit.

28.6 Course exercises and Week 10 deliverable

Submit the Week 10 deliverable bundle by Friday 23:59. This is the final submission of the unit. Required artefacts:

28.6.1 Required artefacts

1. Mock VC pitch deck and financial model (final versions, with any post-pitch revisions integrated).
2. Commercialisation plan v2 following the §28.4.2 template; 4–8 pages.
3. Individual post-mortems (one per founder, 1–2 pages each).
4. Team synthesis post-mortem (3–4 pages).
5. Founder-continuation matrix with explicit per-founder commitment, role, and equity.
6. IP and entity transfer documentation (or the graceful-end equivalent).
7. 12-month roadmap following the §28.4.6 template.
8. Career-pathway statements (one per founder, ~150–250 words).
9. The complete 10-week archive — all Weeks 1–10 deliverables organised in a clear folder structure with an index.

28.6.2 Grading rubric (50 points)

Component	Points	Distinction-level criteria
Mock VC pitch performance	15	Pitch fluent; demo reliable; Q&A composed; verbal feedback received without defensiveness
Commercialisation plan viability	15	All 8 sections populated; specific timelines and resources; risks and mitigations explicit; capital path defended
Post-mortem honesty	5	Both individual and team post-mortems specific, evidence-based, and reflective; cross-track integration articulated
Founder-continuation clarity	5	Per-founder commitment explicit; equity changes documented; IP arrangements specified
Documentation completeness	5	10-week archive complete; folder structure clear; supporting documents in place
Career-pathway specificity	5	Each founder’s pathway stated with specifics; integration of unit experience visible

Pass: 30. Credit: 36. Distinction: 42. High Distinction: 47.

The team-comprehension penalty applies. Additionally, any team member who cannot articulate one specific analytical-track concept that shaped a specific playbook-track decision is deducted 2 points individually (the integration is the unit’s signature; absence of integration on the part of any team member is concerning).

28.6.3 The unit’s closing

This is the last formal deliverable of the unit. The team’s work over 10 weeks — from Chapter 19’s 30-idea brainstorm to Chapter 28’s commercialisation plan — is now archived. What happens next depends on each team member’s chosen pathway.

For teams that continue: the post-graduation 12 months follow the commercialisation plan; the analytical-and-playbook integration of the unit is the foundation of subsequent work; the founder-market-fit established in Chapter 19 becomes the basis of the Year-2 funding round.

For teams that wind down gracefully: the project’s learnings transfer to subsequent ventures or to the founders’ next career steps. The post-mortem’s articulation of what worked and what did not is the durable take-away.

For all teams: the integration of analytical depth (Parts I–IV: theory, frameworks, case literature, governance) with playbook execution (Part V: ten weeks of building a real AI startup) is the unit’s signature pedagogical move. Graduate-level startup work is distinguished from MBA case work and undergraduate startup-club work by this integration. The analytical concepts are not abstract; they shape specific decisions in specific weeks. The playbook execution is not unmoored; it is grounded in the case literature and theoretical frameworks that constitute the unit’s analytical track.

References for this chapter

Mock VC and pitch evaluation methodology

• Y Combinator (2014–2026). Demo Day pitch standards. startupschool.org.
• Sequoia Capital (2024). The Sequoia early-stage evaluation framework. sequoiacap.com.
• Suster, M. (2012–2026). Both Sides of the Table Blog on investor evaluation.

Post-mortem methodology

• Beyer, B., Jones, C., Petoff, J., and Murphy, N. R. (2016). Site Reliability Engineering: How Google Runs Production Systems. O’Reilly. (Chapter 15: Postmortem Culture.)
• Allspaw, J. (2012). Blameless PostMortems and a Just Culture. Etsy Code as Craft Blog.
• Schein, E. H. (2017). Organizational Culture and Leadership. (5th ed.) Wiley.

Entrepreneurship — continuation and exit

• Wasserman, N. (2012). The Founder’s Dilemmas. Princeton University Press.
• Christensen, C. M. and Raynor, M. E. (2003). The Innovator’s Solution. Harvard Business Review Press.
• Aulet, B. (2013). Disciplined Entrepreneurship. Wiley.

Commercialisation methodology

• Birkinshaw, J. (2003). Inventuring: Why Big Companies Must Think Small. McGraw-Hill.
• Bessemer Venture Partners (2024). State of the Cloud Report. bvp.com.
• The Lean Startup Co. (2024–2026). Commercialisation guides. leanstartup.co.

Cases referenced in §28.3

• Iansiti, M. and Lakhani, K. R. (2020). Competing in the Age of AI. Harvard Business Review Press.
• Anthropic (2021–2026). Series A and Series B coverage.
• Notion Labs (Zhao, I., interviews 2018–2024).
• Carsome Group. (2018–2024). Annual reports.
• Y Combinator (annual). Demo Day proceedings.

Further reading

For the post-mortem methodology in detail, the Beyer et al. Site Reliability Engineering book is the foundational reference; Allspaw’s “Blameless PostMortems” essay on the Etsy engineering blog is the most-readable practitioner introduction. For organisational-culture context, Schein’s Organizational Culture and Leadership provides the academic depth.

For continuation and graceful-end methodologies, Wasserman’s Founder’s Dilemmas covers the team-dynamics dimension; the Lean Startup commercialisation materials cover the operational dimension. For the broader question of entrepreneurial career pathways, Aulet’s Disciplined Entrepreneurship and Christensen-Raynor The Innovator’s Solution provide complementary frameworks.

For the integration of analytical and playbook work — the unit’s signature — the modal references are not yet collected in a single text. The closest substitutes are the practice-oriented Y Combinator curricula (which integrate theory implicitly) and the academic-oriented Iansiti-Lakhani treatment (which provides the theory but not the playbook). The unit’s design is, in part, an attempt to fill that gap.

Closing — the playbook ends here

This is the last chapter of Part V and of the playbook track. The 10 chapters from Chapter 19 (Idea, team, pain) through Chapter 28 (Mock VC and commercialisation) form a single 10-week build sequence. Each chapter pairs with one or more analytical-track chapters from Parts I–IV. The pairing is the unit’s pedagogical signature.

The work the team has done over 10 weeks — from idea generation to a functioning product to a defended commercialisation plan — is what graduate-level startup work consists of. The integration of theoretical depth with practical execution is what makes the work distinctive. The career pathways the founders take from here will vary; what is shared is the methodology that has been internalised through ten weeks of disciplined practice.

The next time you face a startup decision — pricing, team formation, MVP scoping, evaluation, alpha launch, customer discovery — the analytical concepts and the playbook procedures are available to you as durable patterns. That is the take-away.

Whatever path you take from Week 10 onward, the discipline you have built over the unit transfers. Use it.