Stage 2 of The Compass Journey. A loop, not a straight line.
BUILD
Real products take longer to prove than a single sprint allows, and real proof should never be forced into a calendar that does not fit it. Build is structured as a cycle with formal decision gates: build, measure honestly, and go, hold, recycle, or return to Validate based on real evidence, not the date on the calendar.
This replaces a straight 30-day pipeline with something closer to how real product teams actually operate: work happens in stages, gates decide what happens next, and going backward when the evidence says so is a normal, respected outcome, not a failure to hide.
Gates decide, not the calendar
Every major transition is a Go, Hold, Recycle, or Kill decision against fixed criteria, never an automatic next step.
Adapted from the Stage-Gate model, Robert Cooper
Real usage before you measure it
Product-market fit is measured after people have actually lived with the product, not the day it ships.
Adapted from the Sean Ellis Product-Market Fit survey
Brand is informed by evidence, not guessed early
Your message is drafted early but only finalized once real usage tells you what people actually value.
Adapted from the StoryBrand SB7 Framework, Donald Miller
One channel, tested honestly, not oversold
A short channel test finds a real signal. It does not replace the weeks of testing real traction actually needs.
Adapted from the Bullseye Framework, Traction, Weinberg and Mares
The whole cycle, at a glance
The Build-Measure-Learn Cycle
Two tracks run in parallel at the start. Every gate has a named decision. Recycling back is built in, not an afterthought.
Build
Days 1–10
GATE 0 Build Ready
Live Usage Window
Days 11–20
GATE 1 PMF Test
Brand Finalize
Days 22–28
GATE 2 Clarity Test
Customer Sprint
Days 29–38
GATE 3 Revenue Night
Running underneath Days 1 to 10: a parallel Brand Lite track, drafting your message early so it is ready to test, not yet public.
Standing community rhythm
Founder Room and Founder Night Schedule
Founder Nights now sit at the gates themselves, not on a fixed weekly count, since the whole point of a gate is that it means something.
Founder Room
Tuesday and Thursday, 6 to 8 PM
Open every week of the cycle, however long it runs.
Founder Night, Gate 0
Day 10
Build demo before the usage window opens.
Founder Night, Gate 1
Day 21
Real PMF scores, read out loud, whatever they are.
Founder Night, Gate 2
Day 28
Public brand launch, after a real clarity test.
Revenue Night, Gate 3
Day 39
The cycle's real ending, whichever of three honest outcomes it is.
Days 1–10, two tracks in parallel
Build the Product, Draft the Brand
Track A ships the MVP. Track B, running underneath at low intensity, drafts your brand message early using what you already know from Validate, so it exists but is not yet public or final. Finalizing it too early was the flaw in the first version of this stage. Drafting it early, and finishing it only after real usage, is the fix.
Day 1, Mon Track A, Build
Lock the Build Plan
How
Pull your MVP scope from Validate.
Break it into daily build targets for the next 7 working days.
Assign who owns what on the team.
Output: a 7-day build plan with daily targets and owners.
Day 1, Mon Track B, Brand Lite
Draft the Character and Problem
Why
This draft exists so you are ready to test a message the moment you have real users, not so you can launch it yet.
How
Character: your customer, and what they want, in one sentence.
Problem: their external problem, the internal frustration, and why it feels wrong that it exists.
Output: a draft Character and Problem statement, marked not final.
Days 2 to 5, Tue to Fri Track A(Founder Room Tue, Thu)
Build Sprint
How
Build against your daily targets, not a perfect vision.
Cut anything that is not the core value.
Output: a working MVP by end of Day 5.
Days 2 to 5 Track B
Draft the Guide, Plan, and Stakes
How, 1 hour a day, not a full sprint
Guide: one line of empathy, one line of authority.
Plan: 3 simple steps a customer takes with you.
Failure and Success: what happens if the problem stays unsolved, and what changes if it does not.
Output: a full draft SB7 message, still marked not final.
Day 6, Sat: Build Check-In
Show What You Shipped, Even Half-Finished
Peer feedback on the build. Brand stays in the drawer, this night is about the product.
Day 7, Sun
Rest, or Keep Building
No mandatory task.
Day 8, Mon Track A
Finish the MVP
How
Close out remaining build targets.
Make sure the core value works end to end, not just in pieces.
Output: a complete, usable MVP.
Day 9, Tue Track A(Founder Room 6 to 8 PM)
QA and Critical Fixes
How
Walk through your own product as a brand-new user would.
Fix anything that blocks someone from reaching the core value.
Output: an MVP a stranger can use without help.
Day 10, Wed, Gate 0: Build Ready
Is the Product Actually Usable End to End?
This is a quality gate, not an opinion gate. It asks one question: can a first-time user reach your core value without help? A Go opens the usage window. A Recycle sends you back into the build sprint for a defined number of days, not an open-ended delay.
Days 11–20
The Live Usage Window
The single biggest fix in this redesign. A product-market fit score means nothing on day one of usage. This window exists so the Day 21 survey actually measures something real, in line with how the Sean Ellis test is meant to be run.
Days 11–20, Ten Days
Get Real Usage, Not Just Signups
Why
The Sean Ellis test is only valid for users who have experienced the core value at least twice over roughly two weeks. Surveying people the day they sign up measures curiosity, not fit.
How
Get 25 to 40 real users onto the live MVP.
Track who actually reaches the core feature, and who returns to use it again.
Use Founder Room, Tuesday and Thursday, for anything blocking adoption.
Do not survey yet. Let the window run its full length.
Output: at least 25 users who have used the core feature twice or more, ready to be surveyed honestly.
Day 13, Tue: Founder Room Check-In
Optional, If Adoption Is Stalling
Not a full Founder Night, just an open Founder Room slot if usage numbers look thin halfway through the window.
Day 21, Gate 1
The Product-Market Fit Gate
Run the Sean Ellis survey now, on users who have actually lived with the product. Then follow the branch your real score points to, not the one you hoped for.
Founder Night, Day 21
Run the Test, Read the Score Out Loud
How
Ask exactly: "How would you feel if you could no longer use [your product]?" with answers Very disappointed, Somewhat disappointed, Not disappointed.
Score equals the percentage who say Very disappointed.
Also collect: their main benefit received, and how you could improve, in their own words.
SCORE RANGES, NOT A RESULT, YOU FILL IN YOUR OWN NUMBER ON THE NIGHT
Under 25 percent, Kill or Hold branch. 25 to 39 percent, Recycle branch. 40 percent or higher, Go branch.
Go, 40% or Higher
Proceed to Brand Finalize, Days 22 to 28
Use your "main benefit" answers to sharpen the message, this is real evidence now, not a guess
Recycle, 25 to 39%
Segment respondents: what do the Very Disappointed users have in common
Run 5 to 8 Mom Test style interviews with that segment specifically, past behavior only, no pitching
Fix the top 1 to 2 complaints from the "how to improve" answers
Run a fresh 7-day usage window with a new cohort, then return to Gate 1
Kill or Hold, Under 25%
The product itself is not landing, not a messaging problem
Use Validate's existing re-entry path: pivot to your second-ranked pain point and return to Explore, rejoin the next cohort, or step away with no penalty
Nothing here is recorded as a failure, it is a result
Days 22–28, only reached after a Go at Gate 1
Finalize the Brand, Then Launch It
Your Track B draft from Days 1 to 10 gets finished here, now informed by what real users actually said, not guessed in advance.
Day 22, Thu (Founder Room 6 to 8 PM)
Refine the Message With Real Language
How
Pull the exact words users gave you for "main benefit received."
Rewrite your draft Problem and Guide lines using their language, not your original guess.
Output: a brand message grounded in real user language.
Day 23, Fri
Name, Logo, Visual Identity
How
Finalize a unique, memorable brand name.
Create a logo, color palette, and typography, even a first-pass version.
Output: finalized name and visual identity.
Day 24, Sat
Build the Landing Page
How
Rebuild your Explore-stage landing page using the refined message.
Put the Call to Action above the fold.
Output: a live landing page carrying the refined message.
Day 25, Sun (Founder Room 6 to 8 PM)
Trust-Building Elements
How
Add real reviews or quality proof from your usage-window users.
Add clear policies, guarantees, and an honest FAQ.
Output: a page with real trust signals, not just claims.
Day 26, Mon
Run a Clarity Test Before the Gate
Why
Donald Miller's rule is blunt: if you confuse them, you lose them. Test for confusion before the room does it for you.
How
Show the finished message to 5 people outside your team.
Ask them to explain back what you do and who it is for.
4 or 5 correct: ready for Gate 2. Fewer than that: revise Day 27 before the gate.
Output: a message that strangers can actually repeat back correctly.
Day 28, Founder Night, Gate 2: Clarity and Public Launch
If a Stranger Cannot Repeat It Back, It Is Not Ready
Go: launch the brand publicly, social profiles, first content, the works. Recycle: one focused revision day, then relaunch the clarity test with 5 new people before trying again.
Days 29–38, only reached after a Go at Gate 2
The Customer and Revenue Sprint
Said plainly: this is a signal-finding pass, not the full weeks-long channel testing Traction actually describes. Treat a result here as a lead worth following, not a final answer, and keep testing your chosen channel properly after this stage.
Day 29, Tue
Bullseye, Brainstorm Every Channel
How
Write one concrete strategy for each of the 19 traction channels below, even ones that feel unlikely.
Targeting Blogs
Publicity / PR
Unconventional PR
Search Engine Marketing
Social and Display Ads
Offline Ads
Search Engine Optimization
Content Marketing
Email Marketing
Viral Marketing
Engineering as Marketing
Business Development
Sales
Affiliate Programs
Existing Platforms
Trade Shows
Offline Events
Speaking Engagements
Community Building
Output: one strategy written for all 19 channels.
Day 30, Wed (Founder Room 6 to 8 PM)
Rank and Shortlist
How
Rank all 19 by cost, speed, and fit to your real audience.
Shortlist 3 to 5 for testing.
Output: 3 to 5 shortlisted channels.
Days 31 to 33, Thu to Sat (Founder Room Thu)
Run the Channel Tests
How
Run a small test in each shortlisted channel.
Track real cost per customer and rough audience size in each.
Output: real, if early, cost and volume data per channel.
Day 34, Sun: Founder Night, Early Signal
Pick a Channel, Report the Real Numbers
How
Compare results, choose one channel to focus on.
Share actual cost and volume figures with the room, not projections.
Output: one chosen channel, backed by early test data.
Days 35 to 36, Mon to Tue (Founder Room Tue)
Focus, First Real Sales Push
How
Put full effort behind the chosen channel.
Ask directly for the sale.
Output: real customer conversations, and paying customers if the category allows a fast sale.
Day 37, Wed
AARRR Funnel Audit
How
One real number per stage:
Acquisition
Found you this week
Activation
Took the key action
Retention
Came back again
Referral
Told someone else
Revenue
Actually paid
Output: your single biggest leak, named clearly.
Day 38, Thu (Founder Room 6 to 8 PM)
Act on the Leak You Just Found
Why
A diagnosis with no time to act on it is not useful. This day exists specifically so Day 37's finding goes somewhere before Revenue Night.
How
If Acquisition is the leak: adjust the channel message or spend.
If Activation is the leak: simplify the first-use experience.
If Retention is the leak: reach out to lapsed users directly and ask why.
If Revenue is the leak: revisit your pricing or your ask.
Output: one concrete fix, actually applied, before Revenue Night.
Day 39, Gate 3
Revenue Night
Three honest outcomes, not one expected number. Reporting zero, clearly and with a plan, is a legitimate result here, not a quiet failure.
Traction Confirmed
Real paying customers, a working channel, a funnel with no critical leak
Proceed to Stage 3, Scale
Signal Found, Not Yet Scalable
Real interest, pilots, or conversations, but no hard revenue yet, common for longer B2B or physical-product sales cycles
Loop back into a second 10-day Customer Sprint with an adjusted channel or offer
No Signal
Diagnose the real cause first: are people trying and not returning, or never discovering you at all
Trying and not returning: recycle back to Gate 1, this is a product issue
Never discovering you: recycle back to Gate 2, this is a channel or message issue
Founder Nights, Tied to Gates
Four checkpoints, each one a real decision, not a fixed weekly ritual: Day 10 at the Build Gate, Day 21 at the PMF Gate, Day 28 at the Brand Gate, and Day 39 at Revenue Night. Founder Room stays open Tuesday and Thursday evenings throughout, however long the cycle actually runs, including through any Recycle loop.
Ready to run the cycle for real?
Bring your Validate-stage report. Leave with a real usage-tested product, a brand grounded in real language, and an honest read on where your revenue actually stands.