Founder Signals
Programme Map

The Signals System

Three stages. One direction. Build your core, validate demand, convert to revenue. Each prime reads from the last — clarity compounds.

Click any section to see exactly what you're doing and why.
v3.2 · Prime 3 restructured · Founder's Log replaces Soundboard · 5 blocks 15 sections

90-Day Sprint
Prime 1
Build The Core
5 blocks · 21 sections · Everything that follows is built on what you create here.
Who it's forWhat you're solvingHow you sell it
Onboarding Prime 1 · Read before you start
What this prime is

The foundation. Twenty-one sections that build your Core — the avatar, the offer, the messaging, the plan. Everything in Primes 2 and 3 reads from what you create here.

The big idea

Most founders skip the foundations and pay for it later. They build messaging before they know who they're talking to. They commit to a product before they understand the problem. They scale before validating the offer. The collapse always comes — but it comes weeks or months after the original mistake, and by then it's expensive to undo.

Prime 1 is the cheap way to get this right. Every section is a node in your Core, and every node reads from the one before it. A specific avatar produces specific problems. Specific problems produce a specific offer. A specific offer produces specific messaging. A specific message gets read by the right person. None of this is glamorous — but it compounds. Vague at the start means vague at the close, and vague at the close costs you customers.

Resist the urge to skip ahead to messaging or to start "doing." Outputs without foundation are noise. Build the Core first.

The blocks ahead
  • Block 1Foundations — your honest starting point, business fundamentals, credibility, and routing into the right path
  • Block 2Business Core — avatar, problems, product, offer, delivery, commercial reality, assumptions
  • Block 3Messaging Stack — value proposition, positioning, messaging architecture, conversation-ready copy
  • Block 4Business Plan — your Core compressed into a 10-slide deck and a live landing page
  • Block 5Review & Gate — binary verdict on whether you're ready to take this to market
What you'll have at the end

A Core you trust. A locked offer. Conversation-ready messaging. A landing page you can send. And a binary signal on whether to advance to Prime 2 — or fix what's still weak.

What comes after

Prime 2 — Validate Demand. Your Core meets the market. Structured conversations, milestone reviews at 3, 5, and 10 — and a verdict on whether the market agrees with your hypothesis.

Any questions before we begin? Ask anything about Prime 1, the Core concept, or how the system works. I have full context. When you're ready, say "go" and we'll start.
Block 1 · Foundations
Start Your honest starting point. The reference layer the entire Core reads from.
What you're doing
  • P1-1.1Founder Vision — why you started, what you're building toward, where the business is right now
  • P1-1.2Business Fundamentals — core facts about your business as it actually is, not as you want it to be
  • P1-1.3Proof & Credibility Inventory — your evidence inventory — experience, proximity, early proof
  • P1-2.1Business Type & Idea Intake — the system listens and routes you correctly through Business Core
Why it comes nowYou can't build a Core on a pitch. Foundations forces honesty — about why you're doing this, where you actually sit, and what evidence you have. Every section that follows reads from these four.
What you'll have at the endA locked starting point. The system knows who you are, what your business is, why you're credible, and which path through Business Core fits.
What comes nextBlock 2 — Business Core. Avatar, problems, offer, the commercial gate.
Any questions before we start Block 1? When you're ready, say "go".
P1-1.1Founder Vision
What you're doingCapture your honest starting point — why you started, what you're building toward, and what the business actually is right now. Three blocks: the why, your direction, and the current reality.
Why it mattersEvery section that follows reads from this one. Surface answers here produce surface outputs everywhere downstream. If it reads like a LinkedIn bio, it's not done.
P1-1.2Business Fundamentals
What you're doingLock in the core facts about your business — what you're building, what stage it's at, and where it actually sits right now. Not where you want it to be. Where it is.
Why it mattersFounders consistently describe their business as they want it to be, not as it is. This becomes the reference point the system uses throughout the entire programme to keep your outputs grounded in reality.
P1-1.3Proof & Credibility Inventory
What you're doingBuild an honest inventory of your credibility — specific background, experience, proximity to the problem, and early proof points. Not a pitch. An evidence inventory.
Why it mattersCredibility is a commercial asset. Founders who can clearly articulate why they're the right person to solve a problem get further faster in validation conversations.
P1-2.1Business Type & Idea Intake
What you're doingTalk through your business idea freely — what it is, who it's for, what problem it solves. The system listens and infers the right path through Business Core based on what you share.
Why it mattersNot every business follows the same route through the programme. This section routes you correctly so you're not working through sections that don't apply to your business type.
SystemBusiness Backlog
What it isYour permanent capture layer for every idea, decision, question, and insight that comes up while you build your business — wired directly into your The Core. You talk, the system captures. Then it works in the background: ranking, linking related items, and surfacing what matters when it matters. Say "backlog" anytime and it tells you what to focus on now, what's stale, and what you've forgotten you decided six weeks ago.
Why we use itFounders don't lose to bad ideas — they lose to good ideas they couldn't find when they needed them. Because every item is tied to your Core, the backlog doesn't just store — it reads against your current section, spots conflicts with decisions already made, and surfaces the one idea from week three that unblocks what you're stuck on in week nine. It's not a to-do list. It's a second brain that gets sharper the more you use it.
Block 2 · Business Core
Start The deepest block in the programme. Avatar, problems, product, offer, delivery, commercial check, assumptions — built in sequence.
What you're doing
  • P1-2.2Avatar Profile — one specific real person who experiences the problem
  • P1-2.3Avatar Problems — their problems in their language, ranked
  • P1-2.4Early Tribe & Market Timing — named individuals at highest intensity right now
  • P1-2.5Product Discovery — multiple product structures scored, strongest selected
  • P1-2.6Software Use Cases — exact jobs your software does (SaaS only)
  • P1-2.7Product Offer — locked offer — mechanism, outcome, pricing, structure
  • P1-2.8Delivery Blueprint — step-by-step of running this offer for a paying customer
  • P1-2.9Commercial Reality Check — unit economics, break-even, viability gate
  • P1-2.10Offer Assumptions — five testable hypotheses with thresholds
  • P1-2.11Value Equation Check — Outcome, Believability, Speed, Effort scored
Why it comes nowFoundations told us who you are. Now we build what your business does — from the avatar inward. Every node connects: a specific avatar produces specific problems; specific problems produce a specific offer; a specific offer needs specific delivery and specific economics.
What you'll have at the endA locked offer with named mechanism, scored value, validated unit economics, five testable assumptions, and a delivery blueprint you could run tomorrow.
What comes nextBlock 3 — Messaging Stack. The offer compressed into language that lands.
Any questions before we start Block 2? When you're ready, say "go".
P1-2.2Avatar Profile
What you're doingDefine your Primary Avatar — a specific, real person who experiences the problem you're solving. Not a market segment. One person, described in precise situational detail.
Why it mattersThis is the most important section in the entire programme. Every output from this point forward is written for this person. A vague avatar produces vague outputs at every stage.
P1-2.3Avatar Problems
What you're doingList the real problems your avatar faces — in their language, not yours — then rank them by severity and drill into the top problems in depth.
Why it mattersMost founders solve the problem they think exists, not the one their avatar actually feels. The problem you land on here is what your entire offer is built on.
P1-2.4Early Tribe & Market Timing
What you're doingBuild your Early Tribe — a list of specific, named people who experience your avatar's primary problem right now, at the highest intensity, and have the most to gain from a solution.
Why it mattersYour first customers are not a demographic — they're individuals. Knowing exactly who to call on day one is worth more than knowing your TAM. The tribe you build here becomes your validation target list.
P1-2.5Product Discovery
What you're doingThe system generates multiple possible product structures that each solve one of your top problems. You score them, filter to the strongest candidates, and select the one to build your offer around.
Why it mattersMost founders jump to the first product idea without exploring the option space. Product Discovery is structured exploration before you commit — so the offer you develop next is built on the strongest possible foundation.
P1-2.6Software Use Cases
What you're doingMap out the specific use cases your software addresses — the exact jobs your avatar needs done. SaaS founders only. Service businesses proceed directly to P1-2.7.
Why it mattersVague use cases produce vague product decisions, vague pricing, and vague conversations. "Track which outreach messages got responses" is a use case. "Message tracking" is a feature. The distinction matters in every conversation.
P1-2.7Product Offer
What you're doingCompress everything into one locked offer — a named mechanism, outcome quantified, pricing anchored to the financial consequence your avatar faces, and a structure that could serve your first customers right now.
Why it mattersMost founders confuse their product with their offer. A great product with a weak offer fails. A strong offer with a clear mechanism wins — and this is where you build it.
P1-2.8Delivery Blueprint
What you're doingBuild a delivery blueprint — the step-by-step of how you would run this offer for a paying customer. Day one, week one, month one. What you need, what the customer provides, what completion looks like.
Why it mattersWhen a customer asks "how does this actually work?" you need a precise answer — not a vague outline. This section also reveals whether the offer is actually executable at your current capacity.
P1-2.9Commercial Reality Check
What you're doingRun the numbers — unit economics, break-even point, capacity constraints, and viability gate. What does one customer cost to deliver? How many do you need to reach your target income?
Why it mattersThis is the most commonly skipped step — and the most expensive to skip. Founders spend months validating an offer that could never generate the income they're targeting, even at full capacity.
P1-2.10Offer Assumptions
What you're doingConvert your offer into five testable, falsifiable hypotheses — each with a specific threshold, a number or percentage, and an observable behaviour that can confirm or disprove it.
Why it mattersEvery business runs on assumptions. Most founders never name them — which means they can't test them and can't recognise when they're wrong. These five become the backbone of your entire validation framework.
P1-2.11Value Equation Check
What you're doingScore your offer against four value levers — Desired Outcome, Believability, Speed, and Effort. Verify commercial viability from P1-2.9. Both must pass before messaging begins.
Why it mattersA strong offer that can't make commercial sense won't survive. A commercially viable offer that scores poorly on value levers won't convert. You need both gates to pass — not just one.
Block 3 · Messaging Stack
Start The offer translated into language. Compressed, positioned, sequenced, conversation-ready.
What you're doing
  • P1-3.1Value Proposition — four value statements and one Primary, max 25 words, in avatar language
  • P1-3.2Positioning Dynamics — five framings of the same offer — you select the one to test first
  • P1-3.3Messaging Architecture — emotional-to-logical narrative sequence, problem to decision
  • P1-3.4Messaging Foundations — copy ready for outreach, cold openers, DMs, verbal intros
Why it comes nowThe offer is locked. Now we make it land. Until your value can be expressed in one sentence in avatar language, it's not clear enough.
What you'll have at the endA 25-word Primary Value Statement, a chosen positioning frame, a structured narrative, and conversation-ready copy in avatar language.
What comes nextBlock 4 — Business Plan. The Core compressed into a deck and a landing page.
Any questions before we start Block 3? When you're ready, say "go".
P1-3.1Value Proposition
What you're doingBuild four value statements and a Primary Value Statement — one sentence, max 25 words, in avatar language, naming the mechanism, and falsifiable. No pitch language.
Why it mattersYour value proposition has to work in an outreach message, a landing page headline, and a verbal introduction. If you can't compress the offer into one precise sentence, the offer itself isn't clear enough yet.
P1-3.2Positioning Dynamics
What you're doingThe system generates five possible positioning interpretations of your offer. You select the one that best reflects its real value to test in conversations.
Why it mattersPositioning doesn't change the product — it changes how the product is understood. The same offer can be a time-saver, a revenue driver, or a risk reducer. Each framing attracts different buyers and faces different objections.
P1-3.3Messaging Architecture
What you're doingBuild a structured narrative that moves your avatar through a predictable psychological sequence: Problem recognition → Concern → Curiosity → Understanding → Evaluation → Decision.
Why it mattersEffective commercial messaging follows a sequence — emotional first, logical second. Most founders skip the emotional layer. The emotional layer is what creates receptivity to the logical layer.
P1-3.4Messaging Foundations
What you're doingBuild clear, conversation-ready messaging using avatar language — lines that work in an outreach message, a cold call opener, a Slack DM, and a verbal introduction.
Why it mattersMost founders write messaging that makes sense to them, not to their avatar. This section closes that gap. If the copy could belong to any other company, it's not done.
Block 4 · Business Plan
Start The payoff. Your Core compressed into the two artifacts that make the business real to the world.
What you're doing
  • P1-4.1Business Plan Deck (Internal) — 10-slide reading deck, Gamma-ready, one slide per Core node
  • P1-4.2Sales Landing Page — full landing page + first three personalised outreach messages
Why it comes nowYou've built the components. Now we compress them into the two assets you'll actually use: a deck for advisors and yourself, a landing page for the market. First time you see your business as a coherent whole.
What you'll have at the endA Gamma-ready 10-slide deck. A live landing page URL. Three personalised outreach messages drafted. The business made real.
What comes nextBlock 5 — Prime 1 Review & Gate. Binary verdict on whether the Core holds.
Any questions before we start Block 4? When you're ready, say "go".
P1-4.1Business Plan Deck (Internal) New
What you're doingCompress everything you've built across Prime 1 into a 10-slide reading deck. One slide per node of your Core — who you serve, what they struggle with, what you're building, how it works, what it costs, why it's worth it, what you're assuming, what you'll test first. Gamma-ready. Versioned — V1 at end of Prime 1, updated each time your Core upgrades.
Why it mattersThis is the first time you see your business as a coherent whole. Every section of Prime 1 is a fragment — the Business Plan Deck is the composite. It's yours to keep, share with advisors, and revisit as your thinking evolves. When someone asks "so what exactly are you building?" — this is the answer.
AIGamma
What it isAI presentation builder. Paste your Business Plan Deck content, choose a layout, and Gamma formats and designs it automatically. Share via link or download as PDF.
Why we use itThe deck copy from FS is Gamma-ready — each slide labelled, structured, and sequenced. Paste it in and you have a professional reading deck in minutes.
P1-4.2Sales Landing Page
What you're doingBuild a full landing page — hero, problem framing, solution, proof, offer, risk reversal, and CTA. Plus three personalised outreach messages addressed to the first three specific people from your Early Tribe list.
Why it mattersA landing page filters unqualified interest before you spend time on a conversation. It's your link-in-bio, your credibility anchor, and your authority signal when people are checking you out. You leave this block with a live URL and your first real outreach messages drafted.
AILovable
What it isAI-powered web builder. Describe your landing page in plain language — hero, offer, CTA, proof block — and get a live, shareable URL in minutes. No code, no designer.
Why we use itYour FS copy comes out structured and ready to paste. Lovable turns it into a real page instantly. You leave this section with a live URL — not a Google Doc no one visits.
Block 5 · Review & Gate
Start The honest gate. Are you ready to take this Core to the market — or are you not?
What you're doing
  • P1-5.1Prime 1 Review & Gate — ten binary checks across avatar, problem, offer, delivery, commercial, assumptions, value, messaging, outreach
Why it comes nowMost founders either aren't ready and don't know it, or are ready and lack the confidence to act. This gate fixes both. A single honest fail is more valuable than ten optimistic passes.
What you'll have at the endA binary verdict — pass = advance to Prime 2; fail = name what's weak and fix it before going further.
What comes nextPrime 2 — Validate Demand. The Core meets the market.
Any questions before we start Block 5? When you're ready, say "go".
P1-5.1Prime 1 Review & Gate
What you're doingThe system runs 10 binary checks against everything you've built — avatar specificity, problem consequence, offer mechanism, delivery blueprint, commercial viability, assumptions, value equation score, value statement, messaging, and outreach readiness.
Why it mattersMost founders are either not ready and don't know it, or ready and lack the confidence to act. This gate removes both problems. A single honest fail is more valuable than 10 optimistic passes.
Prime 2
Validate Demand
4 blocks · 7 sections · You have a hypothesis. Prime 2 finds out if the market agrees.
Market conversationsSignal scoredValidation verdict
Onboarding Prime 2 · Read before you start
What this prime is

The market test. Seven sections that take your Core out of theory and into structured customer conversations — and produce a verdict on whether the market agrees with your hypothesis.

The big idea

You built your Core in Prime 1. Until the market sees it, all of it is hypothesis — your best guess at what's true, dressed up as confidence. Prime 2 is where evidence updates hypothesis.

The hardest part of Prime 2 is telling signal from encouragement. "That's really interesting" is not signal. "I'd pay for that" without context is not signal. Real signal is specific, observable, and — often — uncomfortable for the founder to hear. Most founders run conversations to feel validated, not to learn. They walk out with anecdotes and call it data.

The system protects you from this. Every conversation is captured, scored against your assumptions, and patterned across the cohort. Sprint to 3, learn. Sprint to 5, decide. Sprint to 10, close. Three milestone reviews. One verdict at the end: CONTINUE, REFINE, or PIVOT.

You're not pitching. You're not closing. You're learning what's true.

The blocks ahead
  • Block 1Validation — the foundations of conversation skill and your structured deck
  • Block 2Outreach — baseline metrics, platform setup, first messages live
  • Block 3Market Feedback — log every conversation, score the signal, milestone reviews at 3/5/10
  • Block 4Review & Gate — Core update against evidence, structured three-path verdict
What you'll have at the end

Ten structured conversations on the record, your Core updated against real-market evidence, and a clean three-path verdict: continue to Prime 3, refine and run another five, or pivot before going further.

What comes after

Prime 3 — Early Access. The validated offer goes to your warmest signals as a paid early access cycle. First paying customers.

Any questions before we begin? Ask anything about Prime 2, the conversation discipline, or how milestones work. I have full context. When you're ready, say "go" and we'll start.
Block 1 · Validation
Start The setup before any market conversation happens. Skill-building first, then a structured deck.
What you're doing
  • P2-1.1Validation Foundations — five foundations: signal vs encouragement, milestone structure (3-5-10)
  • P2-1.2Conversation Deck Rebuild — fully labelled 10-slide deck, each question tagged to an assumption it tests
Why it comes nowMost founder conversations produce polite interest, not real signal. Skill comes first. The deck is not a pitch — it's a learning instrument. Build the skill and the instrument before you start the conversations.
What you'll have at the endThe filters to extract real signal from real conversations, and a Gamma-ready conversation deck that compounds with every transcript.
What comes nextBlock 2 — Outreach. Platform setup, baselines, first messages live.
Any questions before we start Block 1? When you're ready, say "go".
P2-1.1Validation Foundations
What you're doingLearn the five foundations of validation conversations — what signal looks like, what encouragement looks like, and how to tell the difference. Understand the milestone structure: sprint to 3, learn, sprint to 5, decide, sprint to 10, close.
Why it mattersMost founder conversations produce polite interest, not real signal. "That's really interesting" proves nothing. This section gives you the filters to extract real evidence — not encouragement you'll later mistake for validation.
P2-1.2Conversation Deck Rebuild
What you're doingBuild a fully labelled 10-slide conversation deck — each question tagged by what assumption it tests, with A/B opening variants. Includes Gamma-ready copy and presenter notes. Designed to learn from market evidence, not to pitch.
Why it mattersThe deck is not a presentation — it's a structured conversation instrument. Every question is tagged to a specific assumption. When you paste a transcript back in, the system scores it against these exact questions. The deck compounds as evidence accumulates.
AIGamma
What it isAI presentation builder. Paste your content, choose a layout, and Gamma formats and designs the deck automatically. Share via link or present live.
Why we use itThe conversation deck copy from FS is Gamma-ready — each slide labelled, structured, and sequenced. Paste it in and you're in front of prospects the same day. No design work.
Block 2 · Outreach
Start The system before the messages. Baselines set, platform configured, pipeline built, first outreach sent.
What you're doing
  • P2-2.1Funnel Conversion Intro — conversion benchmarks — outreach to reply, reply to conversation, conversation to signal
  • P2-2.2Platform & Outreach Setup — platform configured, pipeline built, qualification criteria set, first messages live
Why it comes nowOutreach is a system: find, qualify, approach, follow up. Most founders send ten messages, get two responses, and conclude nobody wants this. Build the system before you send.
What you'll have at the endConversion baselines locked. Platform configured. First contact pipeline built. First messages sent.
What comes nextBlock 3 — Market Feedback. The longest block in the programme. You're in the market now.
Any questions before we start Block 2? When you're ready, say "go".
P2-2.1Funnel Conversion Intro
What you're doingSet your conversion benchmarks — outreach to reply, reply to conversation, conversation to signal. Understand what realistic conversion rates look like and what targets you're working toward across your first 10 conversations.
Why it mattersWithout a baseline, you can't tell if you're doing well or badly. One reply from ten messages might be a great start or a warning sign — this section means you'll know which it is when it happens.
P2-2.2Platform & Outreach Setup
What you're doingSet up your outreach platform, build your first contact pipeline, and send your first messages. Platform-specific search approaches, qualification criteria, and warm and cold approach scripts.
Why it mattersOutreach is a system — find, qualify, approach, follow up. Most founders send one message to ten people, get two responses, and conclude nobody wants this. This section builds the system before you send a single message.
Block 3 · Market Feedback
Start The market work. Longest block in the programme. Conversations, debriefs, milestone reviews, pattern analysis.
What you're doing
  • P2-3.1Market Activity & Debrief Loop — log every conversation, score the signal, automatic milestone reviews at 3/5/10 with pattern analysis
Why it comes nowWithout a capture structure, conversations produce anecdotes. With one, they produce data. Pattern analysis across 10 structured conversations is a dataset. Three you remember approximately is not.
What you'll have at the endTen structured conversations on the record, three milestone reviews completed, convergent customer language extracted, and your Core updated by every transcript along the way.
What comes nextBlock 4 — Review & Gate. What did the market tell you, and what's the verdict?
Any questions before we start Block 3? When you're ready, say "go".
P2-3.1Market Activity & Debrief Loop
What you're doingLog each conversation, score the signal, and track patterns across your pipeline. Milestone reviews trigger automatically at conversations 3, 5, and 10. Each milestone produces a pattern analysis and a specific recommendation.
Why it mattersWithout a capture structure, conversations produce anecdotes. With one, they produce data. Pattern analysis across 10 conversations is a dataset. Three conversations you remember approximately is not. Sprint to 3, learn. Sprint to 5, decide. Sprint to 10, close.
SystemTranscript Debrief
What it isThe debrief engine. Paste any conversation transcript and the system scores it against your assumptions, extracts customer language, identifies convergent phrases across prior calls, and flags any signal that should update your The Core. Runs automatically every time you upload a transcript.
Why we use itYour The Core needs to learn from every conversation, not just the ones you remember. The debrief catches the patterns across all your calls — convergent language, repeated problems, shifting assumptions — and updates your Core as you go. Your messaging gets sharper with every conversation.
SystemPipeline
What it isYour AI-enabled CRM — built into the programme, not bolted on. Every prospect, conversation, signal score, and next action lives alongside your The Core. Ask the system anything about your pipeline — "who's close-ready", "who haven't I followed up with", "which prospects named the same problem" — and it answers from the same data your debrief engine reads from.
Why we use itShort-term: no more spreadsheets, no more lost prospects, no more "who was that person I spoke to three weeks ago." Every conversation compounds. Long-term: your pipeline is your most valuable commercial dataset. As the AI reads your Core and your CRM together, it starts surfacing patterns no human would catch — which avatars close fastest, which messaging converts, which prospects look like the ones who paid. The founders who keep this clean from Prime 2 onward get compounding returns by Prime 3 and beyond.
Block 4 · Review & Gate
Start The structured close. Your Core meets the evidence. Verdict is produced.
What you're doing
  • P2-4.1Core Update Review — every node of your Core reviewed against what the market actually said — confirmed, updated, or rework
  • P2-4.2Prime 2 Close & Verdict — three-path verdict: CONTINUE, REFINE (one variable, another five), or PIVOT
Why it comes nowA verdict without evidence is just an opinion. A verdict backed by ten structured conversations and a Core update is a business decision. Everything in this prime exists to make this moment honest.
What you'll have at the endA Core updated by real-market evidence and a structured three-path verdict on whether to advance to Prime 3.
What comes nextPrime 3 — Early Access. Validated offer, paid early access cycle, first paying customers.
Any questions before we start Block 4? When you're ready, say "go".
P2-4.1Core Update Review
What you're doingReview every node of your Prime Core — avatar, problems, offer, assumptions — against what you actually heard in the market. Each node: confirmed, updated, or needs rework. One variable at a time.
Why it mattersYour Prime Core is a living entity. What you built in Prime 1 was your best hypothesis. What you've learned in Prime 2 is evidence. This is where evidence updates hypothesis — systematically, not reactively.
P2-4.2Prime 2 Close & Verdict
What you're doingReceive a structured verdict: CONTINUE (proceed to Prime 3), REFINE (adjust one key variable and run another 5 conversations), or PIVOT (significant misalignment — return to core assumptions).
Why it mattersA verdict without evidence is just an opinion. A verdict backed by 10 structured conversations is a business decision. This is why the debrief loop, milestone reviews, and Core Update Review all exist before this moment.
Prime 3 — v3
Early Access
5 blocks · 15 sections · 4 system tools · Lock, convert, execute, validate, verdict.
Lock & PlanConvertExecuteValidateVerdict
Onboarding Prime 3 · Read before you start
What this prime is

The bridge from validated demand to first paying customers — and the structured cycle that gets you there.

The big idea

Early Access is not your product. It's a container that wraps your product for the first 1, 2, or 3 cycles — and it's a joint learning environment by design.

Your customers get a discount, real access to you, and clear expectations going in.

You get something more valuable: a live audience to test product delivery for the first time. What lands, what breaks, what numbers strain the quality, what stories convert future customers. This is the only place you can learn that — and the only time the cost of getting it wrong is small.

Trying to skip EA and go straight to scaled marketing is how founders lose. Delivery breaks under volume. The case studies you need to close at scale never get captured. The model collapses before it compounds.

Build the product through EA. Capture the proof through EA. Scale the product — with confidence and case studies — after EA.

The blocks ahead
  • Block 1Lock the Offer & Plan the Cycle — learn the EA arc, build your programme plan, delivery blueprint, tracking sheet template, and finally your customer-facing offer doc
  • Block 2Convert — get your offer letters out, run the close sequence, lock the cohort
  • Block 3Execute — EA prep calls, Day 1, set up the delivery rhythm
  • Block 4Validate (concurrent) — coaching/customer calls, founder's log, case study calls — runs throughout delivery
  • Block 5Verdict — three-path commercial verdict on your first EA cycle
What you'll have at the end

First paying customers, structured proof, and a clean commercial verdict on whether you scale, run another EA cycle better, or rework before selling again.

What comes after

Prime 4 — Go-To-Market at scale. The EA container disappears. The product, sharpened by your EA cycles, is sold via real channels.

Any questions before we begin? Ask anything about Prime 3, the Early Access concept, or how this connects to what you've built. I have full context. When you're ready, say "go" and we'll start.
Block 1 · Lock the Offer & Plan the Cycle
Start Education-heavy. Founder learns the full EA arc and builds every planning document — culminating in the customer-facing offer doc.
What you're doing
  • P3-1.1EA Programme Overview — read the full EA arc end-to-end before building anything
  • P3-1.2EA Programme Plan — internal structural baseline — the journey across the cycle
  • P3-1.3Delivery Blueprint — internal anchor — dependencies, resources, time, structure
  • P3-1.4Customer-Shaped Tracking Sheet — template that becomes per-customer instances later
  • P3-1.5Early Access Offer — synthesises all of the above into the offer doc that goes to warm signals
Why it comes nowYou can't write a confident offer until you know what you're actually delivering. Education first, internal planning second, customer-facing offer last. Each section gives the next one richer context — the offer doc compounds from everything before it.
What you'll have at the endFive locked artifacts: programme plan, delivery blueprint, tracking sheet template, and the customer-facing EA Offer Doc — ready to send.
What comes nextBlock 2 — get the offer doc out, run the close sequence, lock the cohort.
Any questions before we start Block 1? When you're ready, say "go".
P3-1.1EA Programme Overview
What you're doingA reading section. Walk through the full EA arc end-to-end before you build anything: prep calls, kickoff, delivery rhythm, coaching/customer calls, founder's log, case study calls, verdict. You leave with the complete mental model of what's coming, in what order, and why.
Why it mattersMost founders enter EA without a clear mental model of how it actually works. They learn in fragments, mid-execution, when the cost of misalignment is highest. This section front-loads the whole shape so every subsequent build slots into a complete picture.
Why nowIt's the first thing in Prime 3 because it shapes how you read every section that follows. Skip it and you'll miss the connective tissue between blocks.
P3-1.2EA Programme Plan New
What you're doingBuild your internal structural baseline for the EA cycle: the journey customers will take, week by week, what happens when, what milestones land where. Output is a Gamma-built PDF — your internal reference for what you're committing to deliver.
Why it mattersWithout a structured plan you're improvising delivery in real time. With one, you have a frame to map customer signal against, a baseline to revise, and a document to anchor every Block 4 capture against. This is your internal source of truth.
Why nowIt comes before Delivery Blueprint because the journey shape determines what infrastructure you need. Plan the experience first, then check the operational reality.
P3-1.3Delivery Blueprint
What you're doingBuild the operational anchor: dependencies, resources, time per customer, capacity, what could break at scale, what stays the same vs what flexes per customer. Gamma-built PDF — internal only.
Why it mattersThe Programme Plan tells you what to deliver. The Delivery Blueprint tells you whether you actually can. Most EA cycles fail on operational reality not on idea — the blueprint catches that before customers commit.
Why nowIt comes after the Programme Plan because you need to know the journey before you can pressure-test the delivery of it. And before the Tracking Sheet because tracking depends on what you can actually deliver.
P3-1.4Customer-Shaped Tracking Sheet New
What you're doingBuild the cohort-level tracking sheet template — a Gamma-built PDF that defines how customers will see their progress through your programme. After EA Prep Calls in Block 3, you'll create per-customer instances populated with their specific journey.
Why it mattersThe Tracking Sheet is the answer to 'how do we keep founders and customers engaged during delivery.' It's not a passive doc — it's the touchpoint. Both sides see progress in the same artifact. Customer feels oriented, founder feels in control.
Why nowIt comes after the Programme Plan and Delivery Blueprint because the tracking structure follows from what's being delivered. The template here gets personalised per customer at P3-3.1 close.
P3-1.5Early Access Offer
What you're doingBuild the customer-facing Early Access Offer Doc — what they're paying for, why now, how to commit. Synthesises everything from P3-1.2, P3-1.3, P3-1.4 into a single Gamma-built PDF that goes to warm signals in Block 2. Issy's 'Make Brands Understand You' PDF is the benchmark.
Why it mattersFounders who write the offer first overpromise. Founders who write the offer last commit to what they can actually deliver. By this point you've structured the journey, pressure-tested delivery, and shaped customer experience — the offer writes itself in language that's already grounded in reality.
Why nowIt comes last in Block 1 because it reads from every preceding artifact. End of Block 1 = Offer Doc ready. Block 2 = get it out.
Block 2 · Convert
Start Operational close. Get the offer letters out, run the close sequence, lock the cohort.
What you're doing
  • P3-2.1Warm Pipeline Follow-up — operational checklist — who haven't you followed up with, who's stuck, backout handling
  • P3-2.2Early Access Close Sequence — three-path scripts (yes/maybe/not yet), objection handling grounded in Prime 2 data
  • P3-2.3Commitment Tracking — log every confirmed customer with name, start date, price paid, expectations, shared start
Why it comes nowInterest from Prime 2 is already there — you wouldn't be here if it wasn't. This block is operational execution, not strategic ranking. Get the offer doc out, follow up systematically, log every commitment.
What you'll have at the endN confirmed paying customers with a shared start date. The cohort is live.
What comes nextBlock 3 — execute the cycle. Prep calls, Day 1, set up the delivery rhythm.
Any questions before we start Block 2? When you're ready, say "go".
P3-2.1Warm Pipeline Follow-up
What you're doingOperational follow-up checklist against your Prime 2 contact list. Who haven't you followed up with? Who's stuck? What's the next move per contact? How do you handle backouts? Light-touch sales process, not strategic ranking.
Why it mattersInterest already exists from Prime 2 — if it didn't, you should be running Prime 2 again until it does. This section is just the discipline of systematic follow-up so warm contacts don't go cold from neglect.
Why nowIt comes first in Block 2 because the offer letters need to land before the close sequence runs. Knowing who to contact and in what order is the precondition for everything that follows.
P3-2.2Early Access Close Sequence
What you're doingBuild and run a structured close sequence — the messages, calls, and follow-ups that take warm contacts from 'expressed interest' to 'paid.' Three-path structure (yes / maybe / not yet). Objection handling grounded in Prime 2 conversation data.
Why it mattersClosing is a skill with a structure. Most founders send one message and read silence as rejection. A structured sequence removes improvisation from the most commercially critical moment in the programme.
Why nowIt comes after pipeline follow-up because you need to know who you're talking to and what they care about before you write the close. Reads from your Prime 2 conversation debriefs to keep language aligned with what they actually said.
P3-2.3Commitment Tracking New
What you're doingTrack every close conversation outcome: confirmed, maybe, not yet, never. For every confirmed customer — lock a name, a start date, a price paid, and any specific expectations already voiced. Build the shared-start-date cohort that Block 3 works with.
Why it mattersEvery confirmed customer is a real commercial commitment with their own expectations. Tracked systematically, they become Block 3's input. Untracked, they become chaos at Day 1.
Why nowIt closes Block 2 because the cohort needs to be locked before delivery starts. Block 3's EA Prep Calls fire against this exact list.
Block 3 · Execute
Start Cycle execution. Prep calls happen, Day 1 lands, delivery rhythm gets set up.
What you're doing
  • P3-3.1EA Prep Calls — 1-2 calls per customer to understand what they want from delivery, then plan rebuild
  • P3-3.2Day 1 & First 48 Hours — hour-by-hour onboarding shaped by EA Prep Call signal
  • P3-3.3Ongoing Delivery Rhythm — weekly cadence setup — Coaching Call handler takes over from here
Why it comes nowCohort is live. Now you actually run the cycle. Prep calls land first to shape delivery to what customers asked for. Day 1 lands cleanly because you already know what each customer wants. Then the delivery rhythm gets set up and the system takes over the ongoing capture.
What you'll have at the endFirst customers onboarded with personalised tracking sheets, Day 1 playbook executed, weekly delivery rhythm established.
What comes nextBlock 4 — Validate. Coaching/customer calls, founder's log, case study calls run throughout delivery to capture proof and surface signal.
Any questions before we start Block 3? When you're ready, say "go".
P3-3.1EA Prep Calls New
What you're doingEducator section that teaches the EA Prep Call process: schedule 1-2 calls per confirmed customer before delivery starts, set expectations, capture what they specifically want. Output: invitation script + question framework. Then run the calls — system handles the rest via the EA Prep Call handler. Section closes when you trigger 'lock final delivery plan' — customer-shaped delivery plan v_final supersedes Block 1's v0, and per-customer Tracking Sheets get created.
Why it mattersPaying customers are more honest than prospects. They tell you what they actually need because they've paid for it. Capture that signal before you build for them — not after delivery starts and you discover the gap.
Why nowIt comes first in Block 3 because everything that follows reads from the customer-shaped plan that gets locked here. Day 1 reads from this. Ongoing rhythm reads from this. Get this right and the rest of the cycle stays aligned with what customers actually want.
SystemEA Prep Call
What it isDedicated handler for the EA Prep Call transcripts. Founder uploads each call recording or transcript, the system runs structured debrief, captures verbatim language, identifies convergent themes across the cohort, and updates the customer-shaped delivery plan artifact iteratively. After the last call, a final synthesis is produced.
Why we use itEach EA Prep Call is high-signal data — what each customer specifically wants, in their words, at the moment they've committed but before delivery starts. The handler captures that pattern across the cohort so Day 1 and beyond reads from real customer signal, not founder assumptions.
P3-3.2Day 1 & First 48 Hours
What you're doingBuild the hour-by-hour onboarding playbook for Day 1. Welcome flow, first touchpoint, first value moment landed within 48 hours. Reads from the locked customer-shaped plan, the EA Programme Plan, and per-customer tracking sheets — so Day 1 lands as the answer to what customers told you in EA Prep Calls.
Why it mattersHow you onboard determines whether customers become advocates or refund requests. A precise 48-hour playbook grounded in their stated expectations means you arrive at Day 1 confident, not improvising.
Why nowIt comes after EA Prep Calls because Day 1 should reflect what you heard. It comes before Ongoing Rhythm because Day 1 sets the tone the rhythm sustains.
P3-3.3Ongoing Delivery Rhythm New
What you're doingSet the weekly cadence: what you send, what you capture, where the feedback loop runs, what touchpoints exist with each customer. Reading section + setup. After this section closes, the Coaching/Customer Call handler in Block 4 takes over the ongoing work of running each weekly call.
Why it mattersWithout a defined rhythm, delivery becomes ad-hoc. With one, every week has structure: customers know what to expect, you know what to capture, and the system has a predictable pattern to debrief against.
Why nowIt comes last in Block 3 because the rhythm depends on what was learned in EA Prep Calls and what was set up in Day 1. Block 3 closes here — Block 4 picks up the ongoing capture work.
Block 4 · Validate
Start Concurrent during delivery. Coaching/customer calls, founder's log, case study calls — all running together throughout the 30-90 day cycle. Founder reads these sections upfront and returns to them during delivery.
What you're doing
  • P3-4.1Coaching/Customer Calls — 1-2 calls per customer per week — what's working, what's not, what they need next
  • P3-4.2Founder's Log — weekly capture of delivery state — what's working, what's not, what to address now or later
  • P3-4.3Case Study Calls — engineered case study scripts per customer, captured at end of cycle as final proof
Why it comes nowBlock 4 is read upfront but lives across delivery. Three handlers run concurrently: customer-facing calls capture progression signal weekly, founder's log captures internal state weekly, case study calls capture outcome verbatim at end. All feed Block 5 verdict.
What you'll have at the endWeekly capture across the full delivery cycle: every customer call debriefed, every founder log archived, every case study captured. The complete record of what happened.
What comes nextBlock 5 — Prime 3 Verdict. PASS, ITERATE, or PIVOT, grounded in everything captured here.
Any questions before we start Block 4? When you're ready, say "go".
P3-4.1Coaching/Customer Calls New
What you're doingEducator section: how to schedule, run, and capture 1-2 customer calls per week during delivery. Service businesses run Coaching Calls; SaaS runs Customer Calls — same structure, different name, different framing. Founder runs each call, uploads transcript, handler debriefs. Section closes once the cadence is set up; ongoing call work happens via the handler throughout delivery.
Why it mattersCustomer signal during delivery is the highest-signal data you have. Without structured weekly capture, you only learn at churn. With it, you learn week by week — and every call's signal feeds Block 5's verdict and the case study scripts.
Why nowIt comes first in Block 4 because the customer-facing call cadence is the primary delivery touchpoint. Founder's log and case study calls layer on top of this rhythm.
SystemCoaching Call
What it isDedicated handler for weekly customer call transcripts. Founder uploads each call, system runs structured debrief, captures what's landing, what's friction, what they need next, and updates per-customer signal patterns. Same handler structure as EA Prep Call but focused on progression signal during delivery.
Why we use itCoaching/customer calls are where the real delivery signal lives — what customers actually do with what you give them. Without structured capture, each call feels useful and nothing compounds. With it, weekly calls become a map of what's working, what isn't, and where the next product upgrade comes from.
P3-4.2Founder's Log New
What you're doingEducator section: how to use Founder's Log during delivery. Weekly (or twice-weekly) check-in space where you capture what's working, what's not, what needs addressing now, what to backlog for post-EA. System reflects, prioritises, surfaces patterns across weeks. During delivery you'll be very busy — Founder's Log is how you stay focused without losing signal.
Why it mattersFounders running first delivery cycles get overwhelmed and lose track of what they're learning. Founder's Log is the lightweight discipline that keeps internal state captured without adding overhead. It's also where the system can support you when you're heads-down delivering.
Why nowIt comes alongside customer calls because internal founder state and external customer state are two halves of the same picture. Block 5 verdict reads both.
SystemFounder's Log
What it isThe system's running journal for founders during delivery and beyond. Available throughout Prime 3 — say 'log' or 'sb' or describe what's on your mind. Captures verbatim, generates summary, surfaces patterns weekly, spawns backlog items for action when you're ready. Replaces and extends the Soundboard tool.
Why we use itDuring delivery, founders don't have time to write structured updates. Founder's Log lets them think out loud and the system does the structuring. The compounding dataset is gold — across weeks of delivery, you (and the system) can see what stayed constant, what shifted, and what surprised you.
P3-4.3Case Study Calls New
What you're doingEducator section: how to plan, schedule, and run end-of-cycle case study calls. The system dynamically generates per-customer scripts using your Core (avatar, offer, value prop), each customer's EA Prep Call signal, their Coaching/Customer Call progression, and the next cohort's avatar — questions are engineered to elicit answers that become high-converting proof for your next cycle's marketing.
Why it mattersCase studies written after the fact are your guesses about what the customer experienced. Case studies captured from their own words, structured by questions designed to surface the proof your next cohort needs, are commercially compounding. This is proof generation as a system, not a happy accident.
Why nowIt comes at the end of Block 4 because the scripts read from everything that came before — Core, EA Prep Call signal, Coaching/Customer Call progression. Run the calls in the final stretch of delivery, capture proof live, feed Block 5 verdict.
SystemCase Study Call
What it isDedicated handler for case study call transcripts. Founder runs each call (recorded video preferred), uploads transcript, handler synthesises against the script's intent: before-state, mechanism, shift, result, in customer's own words. Outputs structured case study + verbatim quotes + marketing copy snippets to your Proof Library.
Why we use itOne well-captured case study changes every conversation afterward. The handler turns one call into a permanent commercial asset that works for every conversation, every prospect, every funnel after this cycle. Compounding effect across cohorts.
Block 5 · Review & Gate
Start The commercial verdict on your first EA cycle.
What you're doing
  • P3-5.1Prime 3 Verdict — three-path verdict: PASS (advance to Prime 4), ITERATE (another EA cycle), PIVOT (offer or delivery needs rework)
Why it comes nowOne EA cycle is not proof of a business. A clean verdict distinguishes 'first revenue' from 'repeatable revenue.' Most founders skip this and either overclaim Product-Market Fit or under-use the learnings from their first cycle.
What you'll have at the endA three-path verdict: PASS → Prime 4. ITERATE → another EA cycle, smarter. PIVOT → upstream rework before selling again.
What comes nextPASS → Prime 4. ITERATE → run another EA cycle with named improvements. PIVOT → return upstream before selling again.
Any questions before we start Block 5? When you're ready, say "go".
P3-5.1Prime 3 Verdict New
What you're doingReview the full EA cycle: offer performance, conversion rate, delivery signal across all coaching/customer calls, founder's log themes, customer outcomes, proof captured, case studies framed. Produce a three-path verdict: PASS (advance to Prime 4 — Go-To-Market at scale), ITERATE (run another EA cycle with specific improvements identified), or PIVOT (the offer, avatar, or delivery model needs deeper rework before another cycle).
Why it mattersOne EA cycle is not proof of a business. A clean verdict distinguishes 'first revenue' from 'repeatable revenue.' Most founders skip this and either overclaim Product-Market Fit or under-use the learnings from their first cycle. This gate stops both failure modes.
Why nowIt runs at the end because it reads everything from Blocks 1-4. The full body of evidence — sales data, customer signal, delivery reality, founder's log themes, captured proof — collapses into one decision.
Programme Changelog v3.2 — 26 Apr 2026

v3.2 — Prime 3 Restructure

Prime 3 reshaped from 12 sections across 5 blocks into 14 sections across 5 blocks with materially different block jobs.

1. Block 1 expanded and reordered. Now 5 sections: Overview → Programme Plan → Delivery Blueprint → Tracking Sheet → Offer Doc (last). Education front-loads, internal planning compounds, customer-facing offer doc synthesises everything.

2. Block 4 redefined as Validate, runs concurrently. Three sections (Coaching/Customer Calls, Founder's Log, Case Study Calls) all active throughout the 30-90 day delivery period. Founder reads upfront, returns throughout. Three handlers fire in parallel, all writing into the proof and signal layer.

3. Founder's Log replaces Soundboard. New product framing for the founder's running journal — used during delivery for weekly state capture, used anywhere for general founder thinking. Backed by new founder_logs table for durable cohort-wide dataset.

4. Case Study Calls reframed as engineered proof generation. Per-customer scripts dynamically composed from Core, EA Prep Call signal, Coaching/Customer Call progression, and next cohort's avatar. Questions engineered to elicit answers that convert next cohort's prospects. Proof generation as a system.

5. Block 5 stays as Verdict. Single section, three-path: PASS (Prime 4), ITERATE (another EA cycle), PIVOT (upstream rework).

v1.3 — Foundations Rebalance

Small structural move to reduce the optical weight of Block 2 and give Foundations its natural landing point before the Core work begins.

P1-2.1 Business Type & Idea Intake moved to Block 1 Foundations. The section that routes founders into the right path through Business Core now sits at the end of Foundations — so the routing happens before the Core work begins, not as the first step inside it. Business Core is now 10 sections instead of 11. Ref stays P1-2.1.

v1.2 — Prime 1 Payoff Block

Prime 1 grew from 4 blocks to 5 blocks. The new Block 4 gives Prime 1 a clear payoff before the gate:

1. New Block 4 · Business Plan. Your work across Prime 1 compressed into a 10-slide reading deck — in your voice, about your business, for you first. Then your sales landing page, built from the same Core. Internal artifact first, external next.

2. Sales Landing Page moved. No longer the final slot in Block 3 Messaging Stack. Now sits alongside the Business Plan Deck as the external-facing version of the same story.

3. Review & Gate now Block 5. Same binary verdict logic — moved down one block to make room for the payoff work that now precedes it.

v1.1 — Prime 3 Reshape

Prime 3 reshaped from 3 blocks and 6 sections to 5 blocks and 12 sections. Three things changed:

1. The validation loop continues into delivery. Once customers commit, the same listen → capture → refine cycle from Prime 2 continues — applied to what you're about to deliver. New Block 3 "Validate the Delivery" gives this a structured home.

2. The gap between close and delivery is now a structured cycle. Block 1 locks the offer. Block 2 converts leads. Block 3 captures what customers actually expect before you build it. Block 4 delivers against what you heard.

3. Prime 3 now has its own gate. New Block 5 asks the commercial question: was the EA successful enough to scale? PASS moves to Prime 4. ITERATE runs another EA cycle better. PIVOT means something deeper needs rework first.

Founder Signals System™ · Programme Map · v3.2