
Track overview
About this track
Decision practice for solo, AI-native founders on where to spend finite build attention. The four-module course moves from build vs buy, to the MVP line, to how deep a defensible claim should go, and closes on when to stop polishing and open the door. Across the course, the method stays consistent: build only what creates a real edge, ship the smallest coherent promise, price defensibility against the market window, and treat launch attention as a finite room. AI makes implementation cheaper; it does not create more founder attention or restore an audience that already decided.
How each module works
Every module in this course runs the same three steps, from the first lesson to the debrief. The loop is what makes Decyde a place to practise, not just to read.
Step 1
Read
The lessons. Read the situation, the evidence and the shape of the trade-off before you commit.
Step 2
Size
The simulation. Put numbers on both sides of the trade-off, then make the call against the engine.
Step 3
Defend
The debrief and report. See what your call bought and why, so you can defend it or change it.
The same loop in every module, and a new decision each time. Judgment compounds.
Modules · In order
4 modules in this track
Each module is one decision: short readings, the decision itself, then a debrief and a replay in a shifted world.
01/04
Build vs Buy: Where to Build, Where to Borrow
Your product needs six components and you are one person. The Core (the thing it uniquely does), The Insight Engine and The Onboarding (two more places you could be different), and three nobody will ever thank you for: Auth / Login, Payments, Infra / Hosting. For each one you drag a card into BUILD (custom: it eats your capacity) or BORROW (buy it, wire up an AI version, partner: free), under a five-slot capacity bar that physically stops you. Every card that lands in BUILD burns its build-versus-buy delta onto its own face, and a moat meter reads your value minus the product a competitor assembles from the same bought parts. Then you ship, and two beats land: the clone test, where every card you borrowed greys out because the parts you can buy are the parts they can buy, and your moat resolves to only what you built; and the waste reveal, where the capacity pips lift off a hand-built component and carry onto the one you had to borrow. Four reflexes tempt you, and each has a logic. Then the line moves: when building gets cheap, and when your core commoditizes. Which components do you build?
12 lessons · 2 mini-sims · ~46 min
Begin module02/04
The MVP Line: What to Build First
Your product could ship six features and you have one launch to prove the bet. The candidates: the Core Loop (the aha itself), the Essential Input the loop runs on, the Basic Onboarding that gets a stranger to it, Polish, a Secondary Feature and Integrations. You drag the blocks onto a build timeline, order them, and plant the ship flag: everything left of the flag goes in v1. A proof meter fills as blocks land, a dashed PROVES IT line waits for the blocks it needs, and a learning clock dims every week the flag moves right. Then you launch, and two beats land: the viability line, where a cohort that cannot get through bounces and your proof counts for much less; and the decay, where everything past the line turns out to be learning you delayed. Four reflexes each tempt you. And the line itself moves, in both directions, when the world around the bet changes. Where do you plant the flag?
12 lessons · 2 mini-sims · ~44 min
Begin module03/04
The Wrapper Question: How Deep to Build
Your product is six layers deep and the bottom two are already free to everyone: the raw capability, and the shell around it. Above them sit four you could own, each priced twice over: weeks it costs YOU to build, and weeks it would cost a fast-follower to redo. They are The Prompt Craft, The Workflow, The Data Loop and The System of Record. You have 26 weeks before the category is decided, and building spends them. You press brass claim-plates up the stack, watch your launch marker slide down a calendar and a moat wall grow beside it on the SAME axis, and then stake the claim. Two beats land at launch: what happens when a clone is lit beside you, and how much of the moat you built you actually get to use. Then the ground moves, in both directions: a new general-purpose capability can absorb layers you own, and a huge, low-switching category changes what a moat is worth. Depth is not a virtue. It is a bet on a regime.
14 lessons · 2 mini-sims · ~64 min
Begin module04/04
Ship or Polish
A working build has four flaws and a thousand-person first-look room that empties over sixteen weeks. Seal flaws on the artifact, watch the crowd thin in the same frame, then push the build through the door. Which flaws do you seal, and when do you stop? Shipping raw and perfecting everything are both tempting. Replays change how fast the room closes and how long the need lasts, and the answer moves with them.
14 lessons · 2 mini-sims · ~68 min
Begin moduleAuthored on Decyde Practice loop curated for decision discipline
Vocabulary
What you'll engage
The decision skills you'll practice are paired with the underlying patterns you'll learn to recognize. Both vocabularies compound across the Startup Founder Decisions domain.
Decision skills you'll practice
Idea validationCustomer-evidence readingValue-of-information judgmentValidity-over-precision disciplineReshape-vs-kill judgmentRunway & window management
Patterns you'll see
Practice evidence recorded on Decyde
Every decision practiced builds your Decision Profile
Replays supported
Practice the same decision differently · iteration builds judgment
English
Additional languages on v1.3+ roadmap
What's next · One recommendation
The other Startup Founder Decisions courses each practise a different kind of decision.
Begin practice →FAQ
Questions about this track
Common questions about Build & Focus and how this track works.
Related · Other tracks





