Courses/Technology Product Entrepreneurship

Technology Product Entrepreneurship

CS9.424

Ramesh Loganathan + Prakash Yalla•Monsoon 2025-26•4 credits

Cheatsheet

Ultra-condensed. Revise a chapter in minutes.

Unit 1 — Foundations & The Spark

Startup DNA, Trends, Idea Hexagon, The Crucible

One-liners

Steve Blank: a startup is a temporary org in search of a repeatable, scalable, profitable model.
Startup DNA = Innovation × Scalability × Uncertainty.
Four phases: Idea→Hypothesis, Problem-Solution Fit, Product-Market Fit, Go-To-Market.
Pitch design: Act I ignites FOMO; Act II calms FOLS.
3C trend-spotting: Convergence, Connectedness, Context.
Hype Cycle 5 stages; founder lives on Slope of Enlightenment.
Idea Hexagon = idea STRETCHING from one seed, not generation from scratch.
Crucible: Oxygen Test (binary) → Five Filters (Problem/Market/Solution/Team/Business Model).
35% of startups die from no market need (Oxygen Test exists for this).
Phase 1 deliverable = HYPOTHESES, not products.

Formulas

$S t a r t u p = I nn o v a t i o n \cap S c a l abi l i t y \cap U n cer t ain t y$
$H e x a g o n : X^{d} / X + Y / X ↑ / X ↓ / X + + / \overset{ˉ}{X}$
$P ha se 1 f u nn e l : 3 see d s \times 6 s t r e t c h es = 18 \to C r u c ib l e \to 3 h y p o t h eses$

Definitions

FOMO = emotional pull (back something big).
FOLS = rational brake (avoid obvious failure).
Hype Cycle Slope = founder's sweet spot.
Hexagon = idea stretching across six dimensions.

Algorithms

Phase 1: Read 3C/Hype Cycle/Radar → Hexagon-stretch 3 seeds → Crucible-filter 18 variants → exit with 3 hypotheses.
Oxygen Test: ask 'would anyone struggle if this vanished?' Yes → proceed. No → kill.
Five Filters: walk through Problem → Market → Solution → Team → Business Model. Any veto = kill.

Comparisons

Startup vs Small Business: Startup has Scalability (designed for exponential growth); small business doesn't. Both can have innovation.
Startup vs Clone: Startup has Innovation (unique defensible advantage); clone copies an existing model.
FOMO vs FOLS: FOMO is emotional pull (don't miss next unicorn). FOLS is rational brake (don't back obvious failures). A pitch must address both.
Idea Hexagon vs Crucible: Hexagon generates variants (creative); Crucible filters them (critical). Sequential, not interchangeable.
Trough of Disillusionment vs Plateau of Productivity: Trough is where hype died — emerging real value, low competition. Plateau is where tech is mature, market saturated, winners decided.

Keywords

Steve BlankStartup DNAFOMOFOLS3CHype CycleSlope of EnlightenmentIdea HexagonIdea StretchingOxygen TestFive FiltersPainkillerDeeptech

Unit 2 — Problem Analysis

Defining the Problem, Quantifying Implications, Bias-Free Validation

One-liners

Levine's Law: fall in love with the problem, not the solution.
Levine's Tree: Problem (root) → Solution (trunk) → Product (leaves).
Three problem-statement levels: L1 vague → L2 end-user → L3 4Ws + When.
5Ws with Why as the keystone (the 'so what?' answer).
Seven stakeholder roles: Decision Maker, Influencer, Buyer, Manager, Operator, Evaluator, CFO.
Painkiller = High Magnitude × High Frequency. Vitamin = otherwise.
Implications Triad = Magnitude × Frequency × Population.
Bias is the enemy of validation.
Past behaviour > hypothetical future. Quantified pain > 'is this a problem?'
Your opinion doesn't matter. Only the customer's data does.

Formulas

$P aink i l l er = H i g h M a g ni t u d e \times H i g h F r e q u e n cy$
$T A P = M a g ni t u d e \times F r e q u e n cy \times P o p u l a t i o n$
$L e v e l 3 = W h o + C o n t e x t + D e f i c i t$

Definitions

Why is the keystone of the 5Ws.
Decision Maker ≠ Buyer ≠ User in most B2B sales.
Painkiller = pay now to stop pain. Vitamin = nice-to-have.

Algorithms

Phase 2: define (Levels → 5Ws → 7 stakeholders) → quantify (Magnitude × Frequency × Population) → validate (bias-free survey, ≥ 20 responses, past behaviour, quantified pain).
Write 7 problem statements (one per stakeholder role) for B2B questions.
Survey-question rewrite: spot leading/hypothetical phrasing → reframe to past behaviour + quantifiable.

Comparisons

Level 1 vs Level 3: L1: 'people need X' (vague). L3: Who + Context + Deficit (Indian Tier-1 working couples short on time → adaptive grocery planning).
Magnitude vs Frequency: Magnitude = consequence per occurrence. Frequency = occurrences per period per person. Multiply both with Population for TAP.
Painkiller vs Vitamin: Painkiller: pay now (high M × high F). Vitamin: nice-to-have (either low). Investors fund only painkillers.
Decision Maker vs Buyer: Decision Maker has approval/veto authority. Buyer owns procurement mechanics. Often different people, especially in B2B.
Past-behaviour question vs Hypothetical question: Past behaviour retrieves from memory (accurate). Hypothetical simulates future (2-3× over-stated). Use past.

Keywords

LevineTreeLevel 35WsWhyKeystoneStakeholderDecision MakerCFOMagnitudeFrequencyPopulationPainkillerVitaminTAPBiasPast-behaviourValidation

Unit 3 — Customer Development & Build-Measure-Learn

Discovery, Validation, BML, Earlyvangelists

One-liners

Old Map = linear. New Compass = loop with pivots.
Four stages: Discovery (PSF) → Validation (PMF) → Creation → Building.
Search before Execute. PMF is the gate.
No business plan survives first contact with customers. — Steve Blank.
Hypothesis Formula: My idea solves [problem] by [solution]. Narrow + emotional.
Detective Phase: find needs WITHOUT mentioning your solution.
Four questions: how you currently / how is that working / hardest part / improve anything.
Validation Board: up to 4 pivots. Riskiest Assumption first.
BML loop: Idea → Build (MVP) → Measure → Learn → Persevere or Pivot.
MVP = Minimum + Viable + Product. Cheapest experiment, not a half-built v0.1.
Earlyvangelist Pyramid apex = customers with budget. Sell here first.
GET OUT OF THE BUILDING.

Formulas

$H y p o t h es i s : M y i d e a so l v es [p r o b l e m] b y [so l u t i o n] .$
$B M L : I d e a \to B u i l d (M V P) \to M e a s u r e \to L e a r n \to (P er se v er e / P i v o t) .$
$E a r l y v an g e l i s tt i er s : Y o u - k n o w \to T h ey - k n o w \to L oo k in g \to W or k a r o u n d \to B u d g e t .$

Definitions

PSF = Discovery's deliverable. PMF = Validation's deliverable. Sequential.
Pivot = structured response to invalidated learning. Not a failure.
Wizard-of-Oz MVP = humans do manually what will later be automated.

Algorithms

Phase 3.1: write 6 hypotheses → Detective interviews → Validation Board tracks pivots → BML loops on Riskiest Assumption → find earlyvangelists → exit with acquisition + orders + sales-cycle.
Customer Development Insight Cycle (inner): Assumptions → Design Experiment → Test in Front of Customers → Insight → repeat.
MVP design: pick Riskiest Assumption → smallest artefact that tests it → must let customers interact (V) → measure behaviour, not opinion.

Comparisons

Old Map vs New Compass: Old = linear plan-execution. New = loop with pivots, validated learning. Old assumes you know; New discovers.
Problem-Solution Fit vs Product-Market Fit: PSF (Discovery): problem real + solution addresses it. PMF (Validation): real customers use AND pay. Sequential.
Search vs Execute: Search (stages 1-2): pivots expected, hypotheses tested. Execute (stages 3-4): model validated, scale. PMF separates them.
Persevere vs Pivot: Persevere = data supports hypothesis; refine. Pivot = data invalidates a major assumption; change customer/problem/solution/channel/pricing/market type.
MVP vs v0.1 of final product: MVP = cheapest test of Riskiest Assumption (can be a landing page). v0.1 = early version of the actual product. MVP often has nothing in common with the final product.
Earlyvangelist apex vs Whole TAM: Apex = Tier-5 customers with allocated budget; first sales target. TAM = entire population with the problem; scale-stage target.

Keywords

Steve BlankCustomer DevelopmentEric RiesLean StartupOld MapNew CompassPSFPMFSearchExecuteHypothesis FormulaDetective PhaseValidation BoardRiskiest AssumptionBMLMVPWizard-of-OzPerseverePivotEarlyvangelistGET OUT OF THE BUILDING

Unit 4 — Value Proposition Canvas

PMF, VPC, the Uber Example, the Ten Characteristics

One-liners

PMF = market pulls product out of startup (Andreessen).
Value Hypothesis = features + audience + business model.
Experience Economy: Commodity → Goods → Service → Experience → Transformation.
Differentiation = Supply Side ∩ Demand Side. Both halves required.
Customer Value + Marketer Value = Total Value. Price = transfer line.
Value is always relative to the Next Best Alternative.
Christensen's VP: more effectively, affordably, conveniently.
VPC fill order: 1 Jobs → 2 Pains → 3 Gains → 4 Products → 5 Pain Relievers → 6 Gain Creators. Customer first.
VPC Fit: ∀ Pain ∃ Reliever; ∀ Gain ∃ Creator. Bijection.
Great VP = narrow + dramatic (Strategyzer #4 + #9).

Formulas

$C u s t o m er V a l u e = V a l u e C r e a t e d - P r i ce$
$M a r k e t er V a l u e = P r i ce - C os t$
$T o t a l V a l u e = V a l u e C r e a t e d - C os t$
$V a l u e = B e n e f i t s / C os t o f S ec u r in g t h e B e n e f i t s$
$P r i ce ban d = (N B A, V a l u e C e i l in g]$

Definitions

PMF reverses direction of force.
Jobs = functional + social + emotional.
Pain types: bad outcomes / obstacles / risks.
Gain categories: required / expected / desired / unexpected.

Algorithms

Phase 3.2: Discover customer Jobs/Pains/Gains (Detective Phase) → fill VPC slots 1-3 → design Products/Relievers/Creators → fill slots 4-6 → check 1:1 bijection → verify against 10 Characteristics (esp. #4, #9) → climb Experience Economy if margin allows → price in band (NBA, Ceiling].
VPC drawing for the exam: draw circle + square interlocking. Number slots 1-6. Draw mapping arrows between relievers↔pains and creators↔gains.
Pricing decision: compute NBA Customer Value; compute Your Offering's Customer Value; set price so your Customer Value > NBA's by a margin; cap at Value Ceiling.

Comparisons

Push (pre-PMF) vs Pull (post-PMF): Push: founder hustles, paid acquisition, discounts. Pull: customers find, refer, complain. PMF = the reversal.
Customer Value vs Total Value: Customer Value = what customer captures after Price. Total Value = the whole pie (Value Created − Cost). Price = transfer line.
Functional vs Social vs Emotional jobs vs —: Functional = task. Social = perception. Emotional = feeling. Founders default to functional; great VPs cover all three.
Pain Reliever vs Feature: Pain Reliever maps to a listed customer pain. Feature is a product capability that doesn't necessarily address a pain. Building features without relievers is wasted cost.
Wide + Incremental VP vs Narrow + Dramatic VP: Wide+Incremental = serves many jobs slightly better. Narrow+Dramatic = serves few jobs 10× better. Only the second wins.

Keywords

PMFMarc AndreessenPullValue HypothesisTren GriffinExperience EconomyPine & GilmoreCommodityGoodsServiceExperienceTransformationDifferentiation AdvantageSupply SideDemand SideCustomer ValueMarketer ValueTotal ValueNext Best AlternativeNBAValue CeilingChristensenVPCJobsPainsGainsPain RelieversGain CreatorsFitBijectionUber example10 CharacteristicsNarrowDramatic

Unit 5 — Business Model Canvas

Nine Blocks, Front/Back/Box Stage, Lean Canvas

One-liners

BMC = strategic bridge: how-you-make × who-you-sell-to × how-you-stay-viable.
Nine blocks, three zones, one bridge.
Front Stage (right): Customer Segments, Customer Relationships, Channels.
Back Stage (left): Key Partners, Key Activities, Key Resources.
Box Office (bottom): Cost Structure, Revenue Streams.
VP is the central pillar; both halves serve it.
Viability: Inflow (Revenue) > Outflow (Costs).
Lean Canvas swaps: KP→Problem, KA→Solution, KR→Key Metrics, CR→Unfair Advantage.
Canvas = hypothesis. Validation Board = scoreboard. BML = the game.
Test the Riskiest Assumption first — the block that kills the business if wrong.
VPC ⊂ BMC. Nested, not alternative.
GET OUT OF THE BUILDING applies to canvas validation too.

Formulas

$B M C = F r o n tS t a g e + V P + B a c k S t a g e + B o x O f f i ce$
$V iabi l i t y : I n f l o w > O u t f l o w$
$L e an C an v a s = B M C - K P, K A, K R, C R + P r o b l e m, S o l u t i o n, K ey M e t r i cs, U n f ai r A d v an t a g e$

Definitions

Front Stage = customer-facing right half.
Back Stage = operational left half.
Box Office = financial bottom strip.
Riskiest Assumption = the block whose failure kills the business fastest.

Algorithms

Phase 4.1: place VP at centre → fill Front Stage (CS, CR, CH) → fill Back Stage (KP, KA, KR) → fill Box Office (Costs, Revenue) → test Inflow > Outflow → identify Riskiest Assumption → cheap MVP to validate it → return to canvas.
Which canvas? If you're in Customer Discovery/Validation → Lean Canvas. If you have a known model → BMC. Migrate Lean → BMC as unknowns validate.
Cascading pivot: when one block changes (e.g., Channel falls through), propagate the change to dependent blocks (Customer Relationships, Cost Structure, sometimes VP).

Comparisons

BMC vs Lean Canvas: BMC = operational planning for known model. Lean Canvas = discovery for unknown model. Four swapped blocks (KP, KA, KR, CR → Problem, Solution, Key Metrics, Unfair Advantage).
Front Stage vs Back Stage: Front Stage = customer-facing (CS, CR, CH). Back Stage = operational infrastructure (KP, KA, KR). VP is the bridge.
Key Resources vs Key Partners: Resources = owned/controlled (IP, brand, team). Partners = external dependencies (suppliers, distributors, platforms). Don't conflate AWS-as-Partner with engineering-team-as-Resource.
Channels vs Customer Relationships: Channels = how you reach (web, retail, sales team). Relationships = what kind of relationship (personal, automated, acquisitive, retentive). Distinct dimensions.
Canvas vs Validation Board: Canvas = hypothesis (what we think the model is). Validation Board = experiment log (what we've actually tested). BML loops produce Board rows; the Board updates the Canvas.

Keywords

BMCBusiness Model CanvasStrategyzernine blocksthree zonesFront StageBack StageBox OfficeCustomer SegmentsValue PropositionChannelsCustomer RelationshipsRevenue StreamsKey ResourcesKey ActivitiesKey PartnersCost StructureInflowOutflowviability equationLean CanvasAsh MauryaProblemSolutionKey MetricsUnfair AdvantageRiskiest Assumptionstrategic bridge

Unit 6 — Strategic Positioning

STP, AHA Grid, Competition Matrix, Defensibility, SWOT, USP Venn

One-liners

A company doesn't exist in isolation — Demand × Supply × Rules.
STP three verbs: identify (Segment) → determine (Target) → create (Position).
You can't be everything to everyone, but you can be something great for someone.
Five-petal flower = 5 most compelling segments, overlapping.
AHA Grid: Contenders (top-left) = disruption sweet spot.
Competition Matrix surfaces gaps; weight by customer importance.
Customer Importance Mapping: Unique × High Importance = sweet spot.
Defensibility climb: T4 easy → T3 at cost → T2 difficult → T1 cannot.
SWOT axes: Internal/External × Helpful/Harmful. Make at least one SO/ST/WO/WT.
Find-Your-USP Venn: Winning ✅ | Risky ❓ | Losing ❌ | Who Cares.
Make Winning bigger. Go emotional in Risky. Avoid Losing. Ignore Who Cares.
STP feeds 4Ps (Price, Product, Promotion, Place).

Formulas

$S T P = I d e n t i f y \to D e t er min e \to C r e a t e$
$A H A G r i d = B e n e f i t s \times P r i ce \to 4 q u a d r an t s$
$D e f e n s ibi l i t y = T_{1} C ann o t ∣ T_{2} D i f f i c u l t ∣ T_{3} A t a cos t ∣ T_{4} E a sy$
$S W O T cr oss - q u a d r an t : S O, S T, W O, W T$
$M a r k e t in g M i x = 4 P s (P r i ce, P r o d u c t, P r o m o t i o n, P l a ce)$

Definitions

STP = Segmentation → Targeting → Positioning.
Contenders = High Benefits × Low Price; disruption sweet spot.
Tier 1 Defensibility = patents / legal protection / unique physical assets.
Risky Zone = all three circles intersect; go emotional.

Algorithms

Phase 4.2: Frame within Demand × Supply × Rules → Segmentation flower → Targeting (top 1-2) → Positioning concept → Ecosystem map → AHA Grid → Competition Matrix → Customer Importance Mapping → USP Defensibility tier → SWOT with connections → Find-Your-USP Venn → STP → 4Ps.
Strategic-allocation rule: invest in Winning Zone, emotionally fight in Risky Zone, retreat from Losing Zone, ignore Who Cares Zone.
Defensibility climb: T4 → T3 via skilled hiring; T3 → T2 via brand-and-network accumulation (years); T2 → T1 via patents/exclusive contracts/scarce assets.

Comparisons

Segmentation vs Targeting: Segmentation = identify (discover natural fractures). Targeting = determine (decide which to chase). Sequential verbs.
Targeting vs Positioning: Targeting = decide who. Positioning = create the perception that wins them. Decision → Engineered perception.
Contenders vs Leaders: Contenders: High Benefits × Low Price (disruption). Leaders: High Benefits × High Price (incumbents, vulnerable to Contenders).
Weakness vs Threat: Weakness = internal (you control). Threat = external (you don't). Most-confused SWOT distinction.
Unique (Customer Importance) vs Tier 1 (Defensibility): Unique = only we have it right now. Tier 1 = no one else can reasonably get it (legal moat). Different frameworks.
Winning Zone vs Who Cares Zone: Winning = Brand × Consumer (you do well at what consumer wants and competitor doesn't). Who Cares = Brand × Competitor (you and competitor both do well at what consumer doesn't care about). Winning ≫ Who Cares.
STP vs 4Ps: STP = strategic positioning (segment, target, position). 4Ps = tactical execution (price, product, promotion, place). STP feeds 4Ps.

Keywords

STPKotlerSegmentationTargetingPositioningfive-petal flowerecosystem mapAHA GridContendersLeadersChallengersLaggardsCompetition MatrixCustomer Importance MappingUniqueBestUSPDefensibilityTier 1Tier 2Tier 3Tier 4imitability ladderSWOTSO/ST/WO/WTFind Your USPWinning ZoneRisky ZoneLosing ZoneWho Cares4PsMarketing MixPriceProductPromotionPlace

Unit 7 — Synthesis, Pitch & Exam Strategy

Synthesis Map, Pitch Architecture, Exam Tactics

One-liners

Four phases: Idea→Hypothesis | Problem-Solution Fit | PMF | Go-To-Market. Pitch as capstone.
Cross-phase #1: VPC ⊂ BMC (blocks 1, 2). Nested, not alternative.
Cross-phase #2: Canvas = hypothesis. Board = scoreboard. BML = the game.
Cross-phase #3: 5Ws Who → BMC CS → STP Segmentation → AHA axes. One identity, four labels.
Cross-phase #4: Painkiller + Contenders + Tier 1-2 = defensible startup recipe.
Four canonical diagrams: Idea Hexagon | BML loop | VPC | BMC. Drill to 60 seconds each.
Pitch = Act I (FOMO ignition) + Act II (FOLS calming) + Specific Ask.
Always name the framework, draw the diagram first, apply ≥ 2 frameworks, quote a slide line, avoid the four mistakes, fall back to pipeline when stuck.
Four common mistakes: ad-hoc reasoning | confusing related concepts | vague filler | ignoring the verb.
When stuck → which phase? Picks the framework for you.

Formulas

$P i p e l in e = P 1 \to P 2 \to P 3 \to P 4 \to P i t c h$
$P i t c h = A c t I (F O M O) + A c t I I (F O L S) + S p ec i f i c A s k$
$D e f e n s ib l e S t a r t u p = P aink i l l er + C o n t e n d er s + T i er 1 - 2 D e f e n s ibi l i t y$
$M u l t i - f r am e w or k an s w er > S in g l e - f r am e w or k an s w er (b y sy n t h es i s w e i g h t)$

Definitions

FOMO Act I = market, traction, vision.
FOLS Act II = team, defensibility, unit economics, ask.
Canonical diagrams = Hexagon, BML, VPC, BMC.

Algorithms

Exam answer protocol: read verb → identify phase → pick framework → DRAW first → name + apply → layer second framework → connect cross-framework → quote a slide line → close with strategic verdict.
Pitch architecture: Slide 1-2 (TAM + opening hook), 3-4 (Problem + Validation), 5 (Vision of scale), 6-7 (Solution + Traction), 8 (Team), 9 (Unit Economics + Defensibility), 10 (Ask).
Recovery: identify phase → use that phase's frameworks → apply at least two → make connections explicit.

Comparisons

Single-framework answer vs Multi-framework answer: Single caps at ~70% (no synthesis). Multi reaches 100% via cross-framework connections. Always layer.
Prose-first answer vs Diagram-first answer: Prose-first risks rushing the diagram → loses diagram marks. Diagram-first secures independent diagram marks; prose follows.
Act I FOMO vs Act II FOLS: Act I ignites desire (market, traction, vision). Act II reassures rationality (team, defensibility, unit economics, ask). Both required.
Pipeline fallback vs Direct framework recall: Pipeline fallback used when right framework not obvious; narrows from ~15 frameworks to 4 via phase identification. Direct recall faster when obvious.
Cross-phase connection #1 (VPC⊂BMC) vs Cross-phase connection #4 (Painkiller+Contenders+Tier 1-2): #1 is structural (nested artefacts). #4 is recipe (defensible startup formula). Both score synthesis marks; cite by number to keep distinct.

Keywords

four-phase pipelinecross-phase connectioncanonical diagramsIdea HexagonBML loopVPCBMCFOMOFOLStwo-act pitchspecific askname the frameworkdraw the diagram firstmulti-framework answerslide quotablesynthesispipeline fallbackSteve BlankUri LevineMarc AndreessenClayton ChristensenPainkillerContendersDefensibilityexam tactics