Chapter 27 — Week 9: The pitch and funding

Welcome to Week 9. The Week-8 deliverables are signed off: pricing, unit economics, market sizing, and GTM all in a defensible state. By Friday you will have a 10–12 slide pitch deck that integrates everything from Weeks 1–8 into a single thesis document, a 36-month financial model, a prepared Q&A response set covering the standard 30+ VC questions, and at least three rehearsal sessions with structured feedback. Monday of Week 10 is the mock VC panel — academic plus practitioner — and the work this week is what determines how the panel goes. The single most-common Week-9 mistake is to treat the pitch deck as a marketing document. It is not. It is the thesis document for the investability of your business: the argument an investor would make to their own partners about why your team should receive capital. The discipline that produces a credible thesis document, not a pretty marketing brochure, is the subject of this chapter.

Chapter overview

This chapter follows the same six-part structure. §27.1 (Concept) sets out the pitch deck as integration document, the story arc (Problem → Solution → Traction → Market → Team → Ask), the standard 10–12 slide structure with AI-product-specific adaptations, the standard 30+ VC question battery and how to anticipate it, the 2026 funding landscape (pre-seed, seed, Series A, with KL and Melbourne specifics), pitch delivery and presence, and the funding ask. §27.2 (Method) is the day-by-day Week 9 sprint: deck outline, slide construction, financial model, two rehearsal cycles, final polish. §27.3 (Lessons from the cases) pulls eight specific pitching lessons from Parts I–III, including Airbnb’s iconic deck structure, WeWork’s unit-economics burial, Anthropic’s constitutional-AI seed deck, and the YC pattern. §27.4 (Tools and templates) gives you the slide-by-slide outline, the financial-model 36-month template, the VC question battery, the killer-question handling guide, the rehearsal-feedback form, the follow-up email template, and the funding-tracker spreadsheet. §27.5 (Worked example) continues Team Aroma through their Week 9: 12-slide deck construction, 36-month financial model integration, three rehearsal sessions including one with their Chapter-19 mentor, and the refinement passes that move the deck from competent to compelling. §27.6 (Course exercises and deliverables) specifies the Week 9 submission with grading rubric.

How to read this chapter. Read §27.1 in full at Sunday evening of Week 8 or Monday morning of Week 9. The conceptual material on the standard slide structure and Q&A battery is what your slide construction will draw from all week. Read §27.2 with the team and assign per-slide owners — the team’s CEO/commercial lead typically owns the Problem, Solution, Market, and Ask slides; the CTO owns the Demo and Technology slides; the CFO/quantitative member owns the Unit Economics and Financial Projections slides. Treat §27.3 as Tuesday-evening reading; the case lessons are tactical advice for slide-by-slide construction. Use §27.4 throughout the week. Read §27.5 before Wednesday’s first rehearsal. Submit against §27.6 by Friday 23:59.

27.1 Concept

27.1.1 The pitch deck as integration document

The pitch deck is the most-misunderstood deliverable of an early-stage startup. Most founders treat it as a marketing document — a polished sales surface meant to make the company sound impressive. This is wrong. The pitch deck is a thesis document: the founder’s structured argument for why this business is investable, organised so that a busy investor can evaluate the argument in 5–10 minutes of reading or 10–15 minutes of presentation.

Three properties define a thesis-grade pitch deck:

Every claim is defended. A market size is bottom-up with sources; a revenue projection is grounded in unit economics; a competitive claim names specific competitors. Unsupported claims signal to investors that the team has not done the work; even if the claims happen to be true, the team’s credibility is damaged.

The argument has a structure. The deck is not a feature list or a chronology. It is a sequence of claims, each of which establishes a premise the next slide builds on: “this is the problem” (premise 1) → “this is our solution” (premise 2) → “we can build it” (the demo) → “users want it” (the traction) → “the market is large” → “the unit economics work” → “the team can execute” → “this is what we need.”

The deck stands alone. A good deck is intelligible without the founder’s narration. An investor will read it on a phone after the pitch; the slides must continue to make the argument when the founder is not in the room. This means slides are self-contained — each has a headline that states a claim and supporting content that defends it — rather than presentation aids that depend on a speaker.

The deck size is conventionally 10–12 slides for a seed pitch, 15–20 for Series A, with content density rising at later stages. For Week 9’s mock VC, a 10–12 slide deck is the right target. Each slide takes roughly 60–90 seconds in a 10–15-minute presentation; a 20-slide deck cannot be presented in the time allotted, and over-densifies the visual content.

The deck has two natural lengths: the short version (2–3 minutes; cover page, problem, solution-and-demo, traction, ask) for hallway pitches and warm-intro emails; and the full version (10–15 minutes; the full slide structure) for scheduled meetings. The team should be able to deliver both.

27.1.2 The story arc

The standard arc has six beats:

Beat 1: Problem. A specific pain in a specific segment, of sufficient severity and frequency to drive purchase behaviour. The Week-2 customer-discovery work and Chapter-23’s verbatim quotes are what makes this credible.

Beat 2: Solution. What you are building, in plain language. Not “an AI-powered platform”; “a tutor that teachers can use to draft SPM-aligned explanations in 10 seconds rather than 5 minutes.” Demonstrate before claim.

Beat 3: Traction. Why the solution is working. Real users; real engagement; real money committed. The strongest possible signal at student-team scale is the pricing-conversation commitments from Week 7.

Beat 4: Market. Why this is large enough to matter. TAM/SAM/SOM bottom-up from Week 8; reference comparables (similar companies in adjacent markets), with explicit caveats.

Beat 5: Team. Why this team is the right one to build this. Founder-market fit (Chapter 19); specific complementary skills; track record (graduate-level academic and professional credentials).

Beat 6: Ask. What you need to scale this. How much capital, for what 18-month milestones, at what valuation.

A common mistake is to spend disproportionate time on the Solution / Demo and skimp on Market / Unit Economics / Team / Ask. The investor’s attention is higher in the late beats than in the early ones, because that is where the investability question is decided. Calibrate slide time and content density toward the late beats.

27.1.3 The standard slide structure

The 10–12 slide structure, with content guidance per slide:

Slide 1: Title. Company name, one-sentence positioning, founder names and contact, date. The one-sentence positioning is a discipline: you must be able to state the company in one sentence, and the sentence must be specific. “AI tools for the world” is bad; “AI explanations and practice for SPM Form-5 students, sold to tutoring centres” is good.

Slide 2: The Problem. A specific pain, in a specific segment, sized. Open with a concrete scenario or verbatim quote from a customer interview. The slide should leave no ambiguity about what problem is being solved and for whom.

Slide 3: The Solution. Your product in one screen. A screenshot, a short workflow description, and the wedge claim — what you do that the alternatives cannot. Avoid feature lists; emphasise the workflow change the user experiences.

Slide 4: The Demo. A 30–60 second demo embedded as a screen recording or shown live. The demo is what makes the solution real for the investor; without it, all later claims feel speculative. Practice the demo until it runs reliably; a glitchy demo undermines technical credibility.

Slide 5: Traction. The numbers that prove the product is working. Active users; week-over-week growth; engagement metrics; money committed; reference customers. Honest numbers beat impressive-sounding numbers; investors discount inflated claims aggressively.

Slide 6: Market. TAM, SAM, SOM with bottom-up methodology visible. The TAM should be at the right order of magnitude; SAM and SOM should be defensible. Reference comparables (similar companies in adjacent markets that exited or scaled successfully) anchor the upside.

Slide 7: Business Model and Unit Economics. Pricing, gross margin, CAC, LTV, payback period. From Chapter 26’s work. Stress-tested numbers (the conservative case) are what to lead with, not the optimistic ones.

Slide 8: Go-to-Market. The motion (founder-led → referral → channel), the bowling-pin segmentation, the Year-1 targets. The plan should be concrete and time-bounded; aspirational GTM (“we will use viral growth”) without specifics is not credible.

Slide 9: Competition and Differentiation. A 2x2 or feature-comparison table. Name competitors honestly; do not pretend the market is empty. The differentiation should be defensible and tied to your wedge.

Slide 10: The Team. Names, roles, photographs, key credentials. For a student team, lean on academic credentials (Monash University Malaysia / Australia, specific programs), prior professional experience (internships, side projects), and the specific founder-market fit each member brings. Avoid generic “passionate team” framing.

Slide 11: Financial Projections. A 3-year (36-month) revenue and cost trajectory. Months 1–6 detailed; Months 7–18 quarterly; Months 19–36 annually. Key assumptions (acquisition rate, churn, ARPU evolution) called out. The chart shape — typically a J-curve transitioning to acceleration — is what investors read.

Slide 12: The Ask. The capital sought, the valuation (or “valuation TBD” with a range), the 18-month milestones the capital will fund. Specific use of funds: engineering hires, sales hires, infrastructure, marketing. The ask is honest: too small undermines the team’s ambition; too large flags inexperience.

Optional slides for Series A or context-specific pitches: Vision (how this becomes a much-larger company), Risks and Mitigations, Roadmap, Past Funding (if any). For Week-9 seed pitches the 10–12 slide core is sufficient.

27.1.4 The standard VC question battery

Investors use a roughly-stable set of questions to probe pitches. Most early-stage investors will cover 30–40 questions across a 60-minute meeting, drawn from the following categories. The team should prepare a written response (2–3 sentences) for each question before any pitch.

Problem and customer (5–7 questions): - What is the customer doing today to solve this problem? - How urgent is the pain — what makes them switch to your product? - How did you choose this segment? Why not adjacent segments? - Who in the customer’s organisation makes the buying decision? - What is the cost of the problem to the customer in dollars/MYR/AUD?

Solution and product (5–7 questions): - What can your product do that the alternatives cannot? - How is this differentiated technically? - What happens when the foundation models improve substantially? - What’s the risk that OpenAI/Anthropic/Google launches this directly? - How do you handle hallucination / accuracy issues?

Traction and growth (4–6 questions): - What’s your week-over-week growth? - What’s your retention by cohort? - How are you acquiring customers today? Will it scale? - What’s your activation rate? Engagement? - What does the customer journey look like end-to-end?

Market (3–5 questions): - Walk me through your market sizing methodology. - What’s the realistic 5-year capture? - Who are the comparables that have scaled in this market? - What happens if your market is smaller than you think?

Business model and unit economics (5–7 questions): - What’s your gross margin? - What’s your CAC and how is it computed? - What’s your LTV? - What’s your payback period? - How do you defend pricing power as the market matures? - What does the unit-economics curve look like at 100 customers? 1,000?

Go-to-market (3–5 questions): - How are you reaching customers today? - What channels will you add at scale? - How do you avoid being commoditised? - What’s your sales playbook? Conversion rates by stage?

Team (3–5 questions): - Why this team for this problem? (Founder-market fit) - Who do you need to hire next, and why? - How are equity and decisions structured? - How do you handle disagreement within the team?

Risks (3–5 questions): - What’s the single biggest risk to the business? - What would cause this to fail in 18 months? - How do you protect against [obvious adjacent risk]? - What’s the regulatory / legal risk?

The Ask and use of funds (3–5 questions): - Why this raise size? - What does the next 18 months look like? - What milestones will the capital reach? - What’s the next round and when?

The 30–40 question battery is exhausting in real time but stable across investors. The team that prepares answers to all 40 in advance handles the actual Q&A with much greater poise than the team that improvises. Allocate Tuesday or Wednesday of Week 9 to writing out 2–3-sentence responses to each.

27.1.5 The 2026 funding landscape

Capital structures for AI startups in 2026 follow recognisable patterns, with regional adaptations.

Pre-seed (USD 100K–500K, ~6–12 month runway). Typically friends-and-family, angel investors, or accelerators. The first money in. Valuation typically uncapped (SAFE) or USD 3–8M cap. Used to build the MVP and validate the problem-customer hypothesis.

Seed (USD 500K–4M, ~12–18 month runway). Institutional seed VCs, micro-funds, larger angels. Used to grow from MVP to demonstrable traction. Valuation typically USD 6–15M post-money for non-AI seeds; USD 10–30M for AI seeds with strong technical teams; outliers (frontier-AI startups with credentialled teams) can raise at USD 50M+ valuations on seeds.

Series A (USD 5–25M, ~18–24 month runway). Larger VCs, typically the first “Tier 1” check. Used to scale GTM, hire the executive team, build the data flywheel at production scale. Valuation typically USD 30–100M for non-AI Series As; USD 60–300M for AI Series As; outliers above USD 1B for hot-category startups.

For the Week-10 mock VC, the realistic ask for student teams is pre-seed, USD 250K–500K if the team intends to continue post-graduation. The check size is calibrated to the team’s 12–15-month post-graduation runway needs.

The KL ecosystem (for Klang Valley founders):

Cradle Investment Programme (CIP). Government-backed, two-stage. CIP Spark up to RM 250K conditional grant; CIP Ignite up to RM 750K conditional grant. Sdn Bhd registration required. cradle.com.my.
MAVCAP (Malaysia Venture Capital Management Berhad). Government-linked VC; mid-stage focus.
Khazanah Nasional / Khazanah Innovation. Sovereign wealth investment; later-stage focus typically, but Khazanah’s various programmes touch earlier stages.
NEXEA. Active KL-based seed VC; ASEAN focus.
Gobi Partners. Pan-Asia VC with KL presence.
500 Global SEA (formerly 500 Startups SEA). Active early-stage; accelerator program.
Antler SEA. Pre-seed accelerator; Singapore-based but active across ASEAN.
The Hive Southeast Asia. Regional B2B VC.
MYStartup. Government accelerator program; non-funding but ecosystem visibility.
Bank Negara Malaysia Sandbox. Regulatory pathway for fintech specifically.

The Melbourne / Australia ecosystem (for Melbourne founders):

LaunchVic. Victorian-government-backed ecosystem support; funds accelerators rather than companies directly.
Skalata Ventures. Melbourne-based seed accelerator; AUD 250K initial check.
Startmate. Sydney-based accelerator with Melbourne presence; AUD 100K initial.
Blackbird Ventures. Active Tier-1 Australian VC; substantial AI portfolio.
Square Peg Capital. Sydney/Melbourne-based VC; cross-stage.
AirTree Ventures. Sydney-based VC; cross-stage.
Main Sequence (CSIRO Innovation Fund). Deep-tech focused; early-stage.
Tidal Ventures. Sydney-based seed VC.
Folklore Ventures. Sydney-based seed VC.
Industry Innovation and Science Australia (IISA). Government program offering Early Stage Innovation Company (ESIC) status, providing investor tax incentives.
R&D Tax Incentive. Up to 43.5% refundable tax offset on eligible R&D expenditure for qualifying companies.

Alternative paths. Not every team’s path is venture-funded. Three alternatives:

Bootstrapping: revenue from the first paying customers funds growth. Slower but lower dilution. For Team Aroma’s Pulse with MYR 11K+/month committed MRR by end-Year-1, bootstrapping is plausible.
Grants: Cradle CIP, R&D Tax Incentive, sector-specific grants (MOSTI, MOE for Malaysian education-tech; AURIN, Innovation Connections for Australian projects). Non-dilutive and slow.
Corporate partnerships: a paying customer becomes an investor or a strategic partner. Common in B2B with anchor customers. Can produce faster-than-VC capital but introduces strategic alignment costs.

The team’s pitch should acknowledge the alternative paths if they are realistic and explain the choice. A team explaining “we are seeking pre-seed capital because the bowling-pin sequence requires more sales velocity than bootstrapped revenue can fund” is more credible than a team that has not considered the alternatives.

27.1.6 Pitch delivery and presence

Three properties of the founder’s delivery materially affect investor perception, beyond the deck content.

Pace. A typical 12-slide pitch in 12 minutes is paced at 60 seconds per slide on average — but with substantial variation. The Problem slide may take 90 seconds; the Title 30 seconds. Pacing is the function of the founder’s preparation; an unprepared founder rushes through difficult slides and dwells on easy ones. Use the rehearsal sessions to time each slide and adjust.

Engagement. Eye contact with the panel; varied tone; controlled gestures. The founder’s confidence is read through these signals; nervous body language (hands clasped, voice trembling, eye contact avoided) is interpreted as low confidence in the business. Practice reduces these tells.

Handling interruptions. Investors will interrupt. This is not hostile; it is information-gathering. The team’s response to interruption signals composure. The right pattern: acknowledge the question, answer briefly, then either (a) return to the slide if the answer is short, or (b) handle the question fully and adjust the rest of the deck-time accordingly.

Handling difficult questions. When asked a question the team cannot answer well, two failure modes recur: bullshitting (the founder fabricates a confident-sounding answer the investor immediately recognises as fabricated) and panicking (the founder freezes or visibly loses composure). The right response: acknowledge the limit, offer what is known, commit to a follow-up. “That’s a fair question. We don’t have data on that yet; here’s what our current thinking is, and we can dig into it after the meeting.” This response is more credible than the bullshit and stronger than the panic.

The team’s three rehearsal sessions in Week 9 are where these properties are practised. The first rehearsal is rough; the second is competent; the third is fluent. Below three rehearsals, the team is not ready.

27.1.7 The funding ask

The ask is the slide investors read most carefully. Three things must be specified:

Amount. The capital sought. For a student team’s mock pitch, USD 250K–500K is the right zone. Below USD 250K signals lack of ambition; above USD 750K signals lack of awareness.

Use of funds. What the capital does. Specifics: “USD 250K for 12 months of runway covering 2 founder salaries (USD 60K each), 1 engineering hire (USD 80K), infrastructure (USD 24K), and customer acquisition (USD 26K).” The breakdown demonstrates the team has thought through the operating plan.

Milestones the capital reaches. What the team will have achieved when the capital is spent. Specifics: “By end of 12 months: 30 paying centres, MYR 540K ARR, churn <5%/month, founder-market fit validated across two adjacent segments, ready to raise Series A.”

The right ask is the smallest amount that reaches a credible milestone. Asking for less makes the team look unambitious; asking for more raises the question of whether the team can deploy the capital efficiently. The best approach is to compute the runway needed to reach the milestone, add 20% buffer for execution risk, and ask for that number.

Valuation is a related question that students often handle poorly. For pre-seed, the team can either propose a valuation cap on a SAFE (typical: USD 5–10M cap for non-AI; USD 8–15M for AI with strong technical teams) or defer the question to negotiation. Deferring is reasonable at student-team scale; the lead investor will set the terms and other investors follow.

27.2 Method — the Week 9 sprint

27.2.1 Day 1 (Monday): deck outline and story arc

By Monday end-of-day the team has a one-page deck outline with each slide’s headline, key claim, and content type (text / chart / image / table). Method:

Whiteboard the story arc. What is the single sentence that summarises the business? What three sub-claims support it? What evidence defends each sub-claim?
Map the arc to slides. Each sub-claim becomes 1–2 slides. Each piece of evidence becomes content within a slide.
Write headlines first. Each slide’s headline is a claim, not a topic. “The Malaysian SPM tutoring market is RM 57.6M annually” (headline as claim) beats “Market” (headline as topic).
Outline the content per slide. For each slide: 3–5 bullet equivalents, the chart or visual to include, and the verbal narration the presenter will use.

The Monday outline is the team’s contract for the rest of the week. Subsequent slide construction implements the outline; rehearsals stress-test it; final polish is iterative refinement on the same structure. Do not start polishing slide 1 before the structure is agreed; polishing premature structure wastes time.

27.2.2 Day 2 (Tuesday): slide construction

By Tuesday end-of-day the team has a v1 deck — every slide built, content populated, but rough. Method:

Visual consistency from the start. Pick the brand colours, fonts, and slide template at the start of the day, not at the end. Inconsistency across slides is read as carelessness.
One claim per slide. Each slide makes one point. If a slide has two points, split it.
Charts and visuals over bullet lists. A bullet list is what the founder reads; a chart is what the investor reads. Where data is available (traction, market sizing, financial projections), use charts.
Less is more. A typical slide has 30–80 words of text plus 1–2 visuals. Slides with 200+ words are unreadable; slides with 5 words feel under-supported.

A specific note on font and design. The most-common student-team pitch-deck mistake is over-styling (animations, gradient backgrounds, irregular layouts). The investor’s eye reads style-noise as inexperience; clean, simple, consistent design is read as confidence. For Nazirul’s font preference, Arial / Arial Narrow at the title-slide level (sans-serif body throughout the deck) is the right choice; the standard 16:9 aspect ratio on Google Slides / PowerPoint is the right format.

27.2.3 Day 3 (Wednesday): financial model integration

By Wednesday end-of-day the team has a 36-month financial model in Excel / Google Sheets, integrated with the unit-economics model from Week 8. The model has four components:

Revenue projection. - Customer acquisition rate per month (Year 1: founder-led-sales realistic; Year 2: founder-led + referral; Year 3: scaled GTM) - ARPU evolution (Year 1 introductory pricing → standard pricing in Months 13+) - Cohort retention (the 89% from beta as starting point; trending toward 95% as product matures) - Revenue = (cumulative active customers) × (ARPU per customer per month)

Cost projection. - Direct variable costs (foundation-model inference, hosting, payment processing) — ~MYR 230/centre/month from Week 8 - Founder salaries — typically MYR 5–8K/month each post-graduation if salaried - Engineering hires — Month 6 first hire at MYR 6–8K/month; Month 12 second hire - Sales hires — Month 9 first hire if budget supports - Marketing/customer acquisition — modest at student-team founder-led scale; scaling with hires - Infrastructure beyond unit-cost — fixed-cost SaaS subscriptions, legal, accounting

Cash flow projection. - Monthly net cash flow = Revenue − Total cost - Cumulative cash position (the J-curve) - Break-even month identification - Runway calculation given current capital and burn

Sensitivity analysis. - Three scenarios: pessimistic (slow acquisition; high churn), base (the team’s expected case), optimistic (fast acquisition; low churn) - Tornado chart of input sensitivity - Stress tests (foundation-model cost rise; competitor entry; key customer churn)

The financial model is the slide-11 content but is also a standalone working document. The team’s rehearsal Q&A will probe specific cells; the model must be navigable and defensible. For Team Aroma in §27.5, the base case crosses break-even at Month 14 (with founder salaries) and reaches MYR 540K ARR by Month 12.

27.2.4 Day 4 (Thursday): rehearsal 1 and Q&A prep

Thursday morning: the first rehearsal. The team presents the deck end-to-end in 12 minutes; non-presenting members watch silently and take notes. After the presentation, 30 minutes of Q&A, drawing from the §27.1.4 question battery (the non-presenters play VCs).

The rehearsal will be rough. Specific failure modes to expect:

The presenter goes over time on the early slides and rushes the late ones (compress the early; expand the late).
The presenter reads the slide content aloud (the slide should support, not be read).
The Q&A reveals specific question-categories the team has not prepared (typically: market sizing, competitor differentiation, regulatory).
The Q&A reveals contradictions between slides (e.g., the GTM plan implying a customer-acquisition rate that the financial model contradicts).

Thursday afternoon and evening: the team writes the Q&A response document — 2–3 sentence responses to all 30+ questions in §27.1.4 — and addresses contradictions identified in the morning rehearsal.

27.2.5 Day 5 (Friday): rehearsal 2, mentor session, final polish

Friday morning: the second rehearsal, with all team members presenting their assigned slides (the Week-9 work assigns slide-ownership; the Week-10 mock VC has the team’s strongest presenter as the lead). The second rehearsal should be visibly more fluent than the first.

Friday afternoon: an external rehearsal with a mentor — the team’s Chapter-19 mentor, the unit instructor, or another faculty member. The external feedback is invaluable; a fresh listener catches issues the team has stopped noticing.

Friday evening: the final polish pass. Consistent fonts, no typos, all numbers reconciled across slides, the demo working reliably, the financial model navigable, the Q&A document complete.

The Friday submission goes in by 23:59. The team-comprehension penalty applies; every team member must be able to present any slide of the deck and answer any of the 30+ Q&A questions.

27.3 Lessons from the cases

Eight specific pitching lessons from Parts I–III shape Week 9 work.

27.3.1 Airbnb’s iconic 10-slide deck — clarity over polish (Founder mythology)

Airbnb’s 2008 seed deck (10 slides; raised USD 600K from Sequoia) is now part of pitching folklore. The deck is unpolished by 2026 standards — basic typography, simple charts — but the clarity is exceptional. Each slide makes one specific claim, the claims build cumulatively, and the deck stands alone without narration.

Operational implication. Polish is overrated; clarity is undervalued. A team with rough design but clear thesis outperforms a team with beautiful design but unclear thesis. Spend Week 9 effort on the thesis (claims, evidence, structure) before spending it on visual design.

27.3.2 WeWork’s pitch deck failure — unit economics buried (Cautionary tale)

WeWork’s pitch decks through 2016–2019 emphasised vision, brand, and “community-as-a-service” framing while burying the unit-economics analysis. When the IPO process forced unit-economics disclosure in mid-2019, the company’s negative gross margins on individual locations became visible, and the IPO was withdrawn. The valuation collapsed from USD 47B to USD 8B over months.

Operational implication. Hide nothing. If your unit economics are weak, lead with them and explain the path to improvement; do not bury them under vision-language. Investors know the standard sources of unit-economics weakness; trying to obscure them produces deeper scepticism than acknowledging them.

27.3.3 Stripe — “we are users” pitch (Chapter 6, forthcoming)

The Collisons’ early Stripe pitches emphasised that the founders were themselves the customer — they had built tools they wanted to use. The framing was credible because it was true and was supported by the founders’ technical credentials. Stripe’s first checks (USD 750K from Sequoia in 2010) reflected this founder-market-fit signal.

Operational implication. Where founder-market fit is genuine (Chapter 19’s discipline established this), make it a slide-level claim. The team slide is not just biographies; it is an argument that this team is uniquely positioned to build this product. For Team Aroma’s Pulse: Aliyah has tutored SPM Add Maths personally; Daniel has 5 years’ edtech experience; Priya has curriculum-design background. The team-slide narrative is not “5 smart people”; it is “the specific people for this specific problem.”

27.3.4 Anthropic’s seed deck — the constitutional-AI thesis (Chapter 13)

Anthropic’s USD 124M Series A in 2021 (and the prior seed) was raised on a thesis-driven deck: the constitutional-AI methodology, the safety positioning, the technical-team credentials. The deck did not lead with traction (the company had no commercial product); it led with the thesis that aligned-by-default models were the right architectural bet, and the team’s credentials supported the bet’s executability.

Operational implication. For deeply technical AI startups, thesis-driven pitches are appropriate even before revenue. The thesis must be defensible (why this technical bet?), the team must be credentialled to execute it, and the trajectory must be plausible. For most student-team pitches, traction-driven (revenue-and-customers-first) is the right approach because the technical thesis at the team’s stage is rarely sufficiently differentiated to lead with.

27.3.5 Notion’s pitch progression — from team productivity to “all-in-one” (Chapter 5)

Notion’s early pitches emphasised team productivity; by 2020 the pitch had broadened to “all-in-one workspace.” The progression reflected actual product evolution, not pitch-deck retconning. The lesson: the pitch must match the product the company is actually building, not the company the founders aspire to in five years.

Operational implication. Resist over-claiming the eventual scope of the product. Your Week-9 pitch should describe what your MVP does today, the credible 2–3 year evolution, and the long-term ambition — but the long-term ambition should be appropriately separated from the current claims. “Today: SPM tutor for Klang Valley centres. In 3 years: tutoring across Malaysian secondary curriculum. In 10 years: regional ASEAN edtech platform.”

27.3.6 Carsome’s regional-play pitch (Malaysian unicorn case)

Carsome’s investor pitches emphasised the regional opportunity (Malaysia + Indonesia + Singapore + Thailand) as a coherent market, not a sequence of country-specific markets. The framing was supported by the founders’ country-by-country knowledge and by the company’s actual cross-country execution. Investors valued the company at unicorn scale partly because of the regional thesis.

Operational implication. For SE Asia-focused student-team pitches, the regional-expansion thesis is a credible scaling story when the founders have the relevant cross-country knowledge. For Team Aroma’s Pulse, the SPM-aligned product cannot directly export to Indonesia or Thailand (different curricula), but the workflow (tutoring-centre teacher productivity) is generalisable. The pitch can position SPM as the Year-1 wedge and curriculum-agnostic centre productivity as the Year-3+ expansion.

27.3.7 Cursor’s developer-love pitch (Chapter 5)

Anysphere’s pitches in 2023–2024 emphasised the developer love metric: the rapid organic adoption among engineers, the unprompted social-media testimonials, the conversion rates from free-tier to paid. The pitch did not lead with technology differentiation (the technology was obvious); it led with the user-engagement evidence.

Operational implication. Where you have strong organic engagement evidence (NPS, retention, word-of-mouth referrals, unprompted endorsements), lead with it. The evidence is more persuasive than any abstract claim about product quality.

27.3.8 The Y Combinator pitch format — the standard everyone learns (Methodology)

Y Combinator’s pitch training is the most-influential pitching curriculum in startup work. The YC format is broadly: 1-line description → mission → problem → why now → solution → demo → traction → team → ask. The format is the source of much of the §27.1.3 standard structure; YC’s “we want to make money” anti-pretentious framing is the operating discipline.

Operational implication. The standard structure is standard for a reason. Investors expect it. Following the structure makes the deck easier to evaluate; deviating from the structure for stylistic reasons creates evaluation friction. Innovate within the structure (slide design, narrative voice, specific framings of claims), not by changing the structure.

27.4 Tools and templates

27.4.1 The 12-slide deck outline template

SLIDE-BY-SLIDE OUTLINE — [PROJECT]

S1 — Title
   Headline: [company name]
   Subheading: [one-sentence positioning]
   Other: [founders, contact, date]
   Visual: Logo

S2 — Problem
   Headline (claim): [the specific pain]
   Content: [scenario or quote, sized cost, segment]
   Visual: [chart or image]

S3 — Solution
   Headline: [the workflow change]
   Content: [the wedge claim]
   Visual: [product screenshot]

S4 — Demo
   Headline: [what you see]
   Content: [30-60s video or live demo]
   Visual: [video embed]

S5 — Traction
   Headline: [the proof]
   Content: [customers, revenue, retention]
   Visual: [growth chart]

S6 — Market (TAM/SAM/SOM)
   Headline: [the size]
   Content: [bottom-up methodology]
   Visual: [TAM/SAM/SOM funnel]

S7 — Business Model & Unit Economics
   Headline: [GM, LTV:CAC]
   Content: [Pricing, GM, CAC, LTV, payback]
   Visual: [unit-economics summary table]

S8 — Go-to-Market
   Headline: [the motion]
   Content: [Pin sequence, Year-1 targets]
   Visual: [GTM diagram or pipeline]

S9 — Competition
   Headline: [the differentiation]
   Content: [2x2 or feature comparison]
   Visual: [competitive landscape]

S10 — Team
   Headline: [why this team]
   Content: [photos, names, roles, credentials]
   Visual: [photo grid]

S11 — Financial Projections
   Headline: [the trajectory]
   Content: [Revenue 36-month projection, key assumptions]
   Visual: [revenue / cost chart]

S12 — Ask
   Headline: [amount and milestone]
   Content: [Use of funds, 18-month milestones]
   Visual: [funds breakdown]

27.4.2 The 36-month financial model template

A four-tab Excel / Google Sheets:

Tab 1: Inputs and Assumptions - Pricing (introductory + standard, evolution timing) - Acquisition (centres/month per quarter) - Retention (monthly churn assumption with maturation curve) - Cost (per-customer variable cost; founder salaries; engineering / sales / marketing hire schedule; infrastructure) - Discount rate (for any NPV calculations)

Tab 2: Monthly Detail (Months 1–18) - Per-month customer count (gross adds, churn, net) - Per-month revenue (customers × ARPU) - Per-month cost (variable + fixed) - Per-month net cash flow - Cumulative cash position - Monthly burn rate

Tab 3: Quarterly / Annual View (Months 19–36) - Same metrics aggregated quarterly through Year 2; annually through Year 3 - Year-end summaries: ARR, customers, gross margin, net income

Tab 4: Scenarios and Sensitivity - Three scenarios (pessimistic / base / optimistic) with key inputs varied - Tornado chart showing input sensitivity - Stress tests (foundation-model cost +50%; CAC ×2; churn +5pp)

27.4.3 The 30-question VC battery checklist

(See §27.1.4 for the question categories. The team builds a 2–3 sentence response to each in a shared document; rehearsal Q&A reveals which categories need deeper preparation.)

27.4.4 The killer-question handling guide

KILLER-QUESTION HANDLING

When a question lands that you don't have a strong answer to:

DO:
  - Acknowledge: "That's a fair question."
  - State what's known: "Here's what we have today: [...]"
  - Offer current thinking: "Our current hypothesis is [...]"
  - Commit to follow-up: "We'll dig into this and come back with
    a complete answer by [date]."

DON'T:
  - Bullshit a confident-sounding answer
  - Panic or freeze
  - Argue with the questioner
  - Pretend the question is bad

The investor is asking partly for the answer and partly to see how
you handle uncertainty. The composed acknowledgement-and-follow-up
response is read as more credible than a fabricated confident answer.

27.4.5 The rehearsal feedback form

REHEARSAL FEEDBACK — [DATE]
Rehearsing team: [names]
Audience: [who watched and asked questions]

DELIVERY (1-5 scale; 5 = fluent, 1 = needs major work)
  Pace:                          [score]
  Engagement:                    [score]
  Slide-time balance:            [score]
  Handling of interruptions:     [score]
  Energy level:                  [score]

DECK CONTENT
  Strongest slide(s):            [list]
  Weakest slide(s):              [list]
  Cross-slide contradictions:    [list]
  Missing content:               [list]

Q&A PERFORMANCE
  Questions handled well:        [list]
  Questions handled poorly:      [list]
  Categories needing more prep:  [list]

OVERALL
  Ready for investor pitch?      [yes / not yet / no]
  Top 3 things to fix:           [list]

27.4.6 The follow-up email template

FOLLOW-UP EMAIL — [investor name]

Subject: Following up after our conversation — [project]

Hi [name],

Thank you for the time today. Three things by way of follow-up:

1. [Specific item discussed; restate what you committed to send]
2. [Specific question they asked that you couldn't answer; here's
   the answer or here's what we'll have by date]
3. [Specific thing you forgot to mention or want to reinforce]

Attached:
  - Updated pitch deck
  - Financial model
  - [Other materials they asked for]

Next step: [what you propose; e.g., another conversation in 2 weeks
when we have [specific milestone]]

Best,
[name]

27.4.7 The funding-tracker spreadsheet

A funding-pipeline tracker, used to manage multiple investor conversations in parallel:

| Investor | Stage | Source | First contact | Last action | Status | Probability % |
|---|---|---|---|---|---|---:|
| [name] | Pre-seed | Warm intro | [date] | [date] | Soft yes | 60% |
| ...

For Week 9 the tracker is mostly aspirational (the team has not actually contacted investors); it becomes the team’s working pipeline document if they continue post-graduation.

27.4.8 The Week-9 deliverable bundle structure

WEEK 9 DELIVERABLE BUNDLE

1. Pitch deck (12 slides, PDF + native format)
2. Financial model (Excel / Sheets, 36-month, 4 tabs)
3. Q&A response document (30+ questions answered)
4. Demo video (2-4 min screen recording)
5. Rehearsal feedback forms (3 rehearsals minimum)
6. Updated risk register
7. Funding tracker (template, populated with context)
8. Mentor / external review summary

27.5 Worked example — Team Aroma’s Week 9

Team Aroma starts the week with 8 weeks of accumulated work: the customer-discovery corpus, the MVP, the alpha and beta reports, the unit economics, the market sizing, the GTM plan, and 5 of 6 centre-owner commitments. The integration challenge is significant; the team budgets the week aggressively.

Day 1 (Monday): outline

Aliyah, Daniel, and Sara whiteboard the deck outline together via Miro (cross-campus). The structure they settle on:

S1: Pulse — AI tutor for Malaysian SPM centres
S2: Problem — Klang Valley tutoring centres are teacher-time-bound
S3: Solution — AI explanations + teacher-review workflow
S4: Demo — 90-second walkthrough video
S5: Traction — 18 beta users, 5/6 committed at GA pricing
S6: Market — RM 57.6M Malaysia TAM; SAM RM 23.4M
S7: Unit economics — 85% GM, 48:1 LTV:CAC (8:1 stressed), 0.5-mo payback
S8: GTM — founder-led B2B → referral → channel; Pin sequence
S9: Competition — Snapask / Pandai / centre status quo
S10: Team — 5 founders with founder-market fit
S11: Financials — RM 540K ARR Y1, RM 2.7M ARR Y3
S12: Ask — pre-seed USD 350K → 30 paying centres + Mandarin product + Series A readiness

The whiteboard also identifies the three slides that will require the most work: S5 (Traction; needs charts of beta engagement), S7 (Unit Economics; the table from Week 8 needs visual treatment), and S11 (Financial Projections; the 36-month model needs a clean visualization).

Day 2 (Tuesday): slide construction

Sara owns the visual design (she has the strongest design background). She picks the colour palette (deep blue + white + accent yellow, evoking academic authority) and the typography (Arial Narrow for headlines, Arial for body — matching Nazirul’s preference and Monash brand alignment). The slide template is built first; populating with content follows.

Each slide is constructed:

Aliyah owns S1, S2, S5, S6, S12 (Title, Problem, Traction, Market, Ask)
Wei Hao owns S3, S4, S9 (Solution, Demo, Competition)
Daniel owns S8, S10, S11 (GTM, Team, Financials)
Sara owns visual design, S7 (Unit Economics)
Priya owns content review and the Q&A document foundation

By Tuesday end-of-day, the v1 deck is complete. Visible issues: the Demo (S4) is a screen recording of the production app but is 4 minutes long (needs cutting to 90 seconds); the Financials (S11) chart is hard to read at distance; the Team slide (S10) has stock-photo-like headshots that feel sterile.

Day 3 (Wednesday): financial model

Daniel rebuilds the Week-8 unit-economics spreadsheet into a proper 36-month financial model. The structure follows §27.4.2.

The base case: 30 centres by end of Year 1 (acquisitions ramping from 1/month in Q1 to 4/month in Q4); 80 centres by end of Year 2; 150 centres by end of Year 3. Revenue: MYR 540K ARR Y1; MYR 1.4M Y2; MYR 2.7M Y3. Costs include founder salaries from Month 1 (MYR 6K each, two co-founders salaried initially); first engineering hire Month 6 (MYR 8K); first sales hire Month 12.

The model crosses break-even at Month 14 (with founder salaries) or Month 4 (without). The team’s narrative will use the no-salary break-even (because the founders are taking founders’ equity in lieu of salary in early months) but will disclose the full-cost figure when asked.

The sensitivity analysis: even at 8:1 LTV:CAC (the stressed case from Week 8), 7%/month churn, and CAC tripling by Year 3, the business reaches MYR 1.8M ARR Y3 — still healthy. The team’s pitch will lead with the stressed case.

Wednesday afternoon, the team also addresses the Tuesday issues: Wei Hao re-edits the demo to 95 seconds; Sara redesigns the Financials chart with cleaner axes and annotations; Aliyah and the team take fresh photos for the Team slide.

Day 4 (Thursday): rehearsal 1 and Q&A prep

Thursday morning at 9am KL / 12pm Melbourne, the first full rehearsal. Aliyah leads the presentation; the rest of the team watches and takes notes. Time: 13.5 minutes (target: 12). Q&A: 28 minutes.

Issues identified:

Pacing: Aliyah spent 2 minutes on the Problem (target: 90 seconds); compressed Slide 11 (Financials) to 30 seconds. Need to move the Problem detail to Q&A and expand the Financials slide presentation.
Slide 7 (Unit Economics): the panel asked twice why the LTV:CAC is so high. The team’s response in rehearsal was defensive (“our calculations are right”). The right response: lead with the stressed case (8:1) and acknowledge that the headline number reflects the early founder-led-sales advantage that will moderate at scale.
Slide 9 (Competition): the panel asked about Snapask + Pandai’s ability to launch competing features. The team had not prepared this response well. The defensible answer: the SPM-rubric alignment is a real moat (data + curriculum work) and our centre-side workflow integration is an additional moat.
Slide 12 (Ask): the team had not specified the milestones the USD 350K reaches. The panel asked for the 18-month roadmap; the team improvised. Need to add specific milestones to the Ask slide.

Thursday afternoon and evening: the team writes the 30-question Q&A response document. Each question gets 2–3 sentences. By Thursday end-of-day, the document is ~12 pages of structured responses. Aliyah and Daniel review for inconsistencies with the deck.

Day 5 (Friday): rehearsal 2, mentor session, polish

Friday 10am: rehearsal 2. Time: 12 minutes 15 seconds (within target). Q&A: 35 minutes (the team is now welcoming questions because they have prepared responses).

Friday 2pm: a 45-minute external rehearsal with the team’s Chapter-19 mentor (a Monash alumna who has founded an edtech company). The mentor’s feedback:

The deck is clear and well-structured. The Problem slide (S2) is particularly strong because it leads with a specific verbatim quote.
The Demo (S4) is good but Wei Hao’s narration during the live demo is too technical. Re-record without the technical details; let the workflow speak for itself.
The Team slide (S10) under-sells Aliyah’s tutoring background and Daniel’s edtech experience. Both should have explicit lines about their domain credibility, not just titles.
The Ask (S12) is well-specified now (after Thursday’s adjustments). The 18-month milestone breakdown is concrete.
The mentor’s strongest single suggestion: the deck has a strong “what” (product, market, unit economics) but a weaker “why now” (why is this the right moment for this product?). Add a brief “why now” framing to Slide 2 — the foundation-model capability for SPM-Malay content has crossed the usability threshold in 2024–2026; the centre-side teacher-time pressure is post-COVID-elevated; the SPM-aligned alternatives are weak. Two sentences max.

Friday 4pm: the team makes the mentor-suggested changes. Wei Hao re-records the demo without technical narration. Aliyah rewrites the Team slide with explicit founder-market-fit language. The “why now” is added to Slide 2 as 3 sub-bullets.

Friday 8pm: rehearsal 3 (the final). Time: 12 minutes 5 seconds. The presentation is fluent; the Q&A is composed. The team is ready.

The Friday submission goes in at 11pm KL: the 12-slide deck (PDF + Google Slides), the 36-month financial model (Excel and CSV), the Q&A response document (12 pages, all 30+ questions answered), the demo video (95 seconds, MP4), three rehearsal feedback forms, the mentor session notes, and the updated risk register.

What Team Aroma got right and what they almost got wrong

Three things they did well: (1) the deck outline was completed Monday — every subsequent action implemented the structure rather than re-debating it; (2) the rehearsal Q&A revealed the LTV:CAC defensiveness pattern early enough to fix (the stressed-case-first framing is what the Week-10 mock VC will see); (3) the mentor session caught the “why now” gap that no team member had identified.

Three things they almost got wrong: the team almost ran the demo at 4 minutes (too long; would have crashed the presentation timing); they almost left the Ask without specific milestones (which would have produced an embarrassing improvisation in front of the mock VC); they almost included a slide on long-term vision (Year-10 ASEAN expansion) that the mentor pointed out was distracting from the seed-pitch focus. The discipline of cutting was as important as the discipline of building.

The pattern is general. Week 9 is high-leverage because it integrates 8 weeks of work into a single argument; missing parts of the integration (an inconsistent number, a missing milestone, an overclaim on traction) damage credibility disproportionately. The work this week is half slide construction and half consistency checking across the accumulated body of evidence.

27.6 Course exercises and Week 9 deliverable

Submit the Week 9 deliverable bundle by Friday 23:59. Required artefacts:

27.6.1 Required artefacts

Pitch deck (10–12 slides, PDF + native Google Slides / PowerPoint format).
Financial model (Excel / Sheets, 36-month, 4-tab structure per §27.4.2).
Q&A response document (2–3 sentences per question for the §27.1.4 question battery; 12+ pages typical).
Demo video (90–120 seconds, MP4 or unlisted YouTube link).
Rehearsal feedback forms for at least 3 rehearsals (one with external feedback if possible).
Mentor / external review summary (1 page, with the mentor’s specific suggestions and the team’s response).
Updated risk register including any new risks identified during pitching preparation.
Funding tracker (template populated; the team’s actual funding-pipeline thinking even if not yet executing).
Two-minute version of the deck (scripted; for hallway-pitch contexts).

27.6.2 Grading rubric (50 points)

Component	Points	Distinction-level criteria
Deck structure and integration	10	All 10–12 slides populated; arc clear; consistency across slides verified
Slide-level claim quality	10	Every slide has a claim-as-headline; every claim defended with evidence
Financial model rigour	10	36-month projection; sensitivity analysis; stress tests; all inputs traceable
Q&A preparedness	5	All 30+ questions answered; responses internally consistent with deck
Rehearsal discipline	5	3+ rehearsals; feedback captured; iterative improvement visible
Demo quality	5	90–120s; production-app screen recording; clear and reliable
Mentor / external feedback integrated	5	External review documented; specific changes traceable to feedback

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

The team-comprehension penalty applies; additionally, every team member must be able to present any slide and answer any of the 30+ Q&A questions by Friday end-of-day.

27.6.3 Things to do before Monday of Week 10

By Sunday evening of Week 9, in addition to the deliverable submission:

Final tech check: the demo runs reliably; the deck loads on the presentation machine; the financial model is queryable; the Q&A document is shared with the team.
Day-of logistics: arrival 30 minutes early; deck on multiple devices (laptop + USB drive + cloud link); the team’s seating arrangement for the Q&A.
Read Chapter 5 (Strategy, collisions, and the new meta), Chapter 18 (Cases of AI in business — frameworks and synthesis if available), and §28.1–§28.3 of Chapter 28 (Mock VC and commercialisation) before Monday of Week 10. Chapter 28 covers the mock VC mechanics specifically; reading it Sunday evening is the right preparation for Monday morning.

References for this chapter

Pitching methodology

Kawasaki, G. (2015). The Art of the Start 2.0: The Time-Tested, Battle-Hardened Guide for Anyone Starting Anything. Portfolio.
Berkun, S. (2010). Confessions of a Public Speaker. O’Reilly.
Anderson, C. (2016). TED Talks: The Official TED Guide to Public Speaking. Houghton Mifflin Harcourt.
Y Combinator (2014–2026). YC startup school resources. startupschool.org.

Pitch deck structure and case material

Sequoia Capital (2010). The Sequoia pitch deck template. sequoiacap.com.
Airbnb (2008). Airbnb seed deck. (Now widely circulated as case study.)
Anthropic (2021). Series A pitch (referenced in subsequent press coverage).

Financial modelling for early-stage startups

Damodaran, A. (2009). Valuing Young, Start-Up and Growth Companies: Estimation Issues and Valuation Challenges. SSRN.
Skok, D. (2014–2026). forEntrepreneurs Blog on SaaS metrics and modelling. forentrepreneurs.com.
Berkery, D. (2007). Raising Venture Capital for the Serious Entrepreneur. McGraw-Hill.

Funding landscape and capital structures

Feld, B. and Mendelson, J. (2019). Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist. (4th ed.) Wiley.
Suster, M. (2012–2026). Both Sides of the Table Blog. bothsidesofthetable.com.
Cradle Fund Sdn Bhd (2024–2026). Cradle Investment Programme guidelines. cradle.com.my.
LaunchVic (2024–2026). Victorian startup ecosystem materials.

Cases referenced in §27.3

Iansiti, M. and Lakhani, K. R. (2020). Competing in the Age of AI. Harvard Business Review Press.
Stripe (Collison, P. and J., interviews and engineering blog 2010–2025).
Anthropic (2021–2026). Series A and Series B coverage in The Information, Forbes.
Carsome Group. (2018–2024). Annual reports and investor materials.
Cursor / Anysphere (2023–2026). Founder communications.