Welcome to Framed Problem Solving

Great to have you here. Here's what we're doing together:

This workflow takes your completed Problem Framing—where you've already diagnosed the root causes, mapped the forces, and identified the constraints—and guides you through systematic solution generation, evaluation, implementation planning, and monitoring setup.

Over the next steps, we will:

1. Ground ourselves in the framing you've done (that's now)
2. Generate diverse solutions using structured methods—aiming for 10-15+ ideas, mixing incremental improvements with breakthrough approaches
3. Evaluate objectively against criteria that matter in your context, and select the strongest solution with clear rationale
4. Plan implementation in concrete, actionable steps with clear ownership and sequencing
5. Set up monitoring so you'll know early if the solution is working and have clear triggers for adjustment
6. Reflect on what worked in the process (optional, but valuable)

The output is a complete Solution Plan document that stands alone—you can share it with stakeholders, use it to guide execution, or use it to build buy-in.

---

Your Problem Framing: Summary

I've loaded your Problem Framing document. Let me summarize what you've diagnosed:

The Problem

Coaches without external forcing functions (warm prospects, audience commitments) publish their service pages but don't share them with their audience. You're seeing a 6% publish-to-first-sale conversion rate—strong activation (69% of signups publish), but a critical gap at the sharing moment. The product itself works beautifully (coaches publish in 5 minutes), but it's missing something at the exact moment they need both forcing function and social proof to overcome the vulnerability of asking for money.

The real barrier isn't technical or logistical—it's psychological and emotional. Coaches load their entire identity onto this page (the first concrete claim they've ever made about being a paid professional), and that weight triggers a freeze. They hide in the editor tweaking, waiting for permission that the product can't give them.

Root Causes

The freeze is sustained by a reinforcing loop:

• High identity stakes (the page represents their entire identity transition) → psychological freeze → editor as hiding place (tweaking creates illusion of progress) → sunk cost accumulation → stakes climb → loop deepens

Upstream, the real root causes are:

• Imposter syndrome specific to coaching (haven't resolved their own transitions yet, but coaching requires claiming "I can help you change")
• Moral weight about charging for influence (fear of being a fraud, of taking money for nothing, of being one of the bad coaches they judge)
• Weak gatekeeping in coaching (no licensing, creating fraud fears)
• Fear of failure amplified by the above (failure feels like exposure, not business risk)

Key Forces

Working FOR you:

• Runway pressure (7 months, acute)
• Clear customer signal (78 frozen, 5 successes proving it's solvable)
• Speed of iteration (1-2 weeks to ship)
• Clear diagnosis (reduces false starts)

Working AGAINST you:

• Coach psychology is upstream and mostly unfixable
• Target market is allergic to anything that feels like marketing tactic
• Solo founder bandwidth (real but has some flex)
• Small sample size (only 5 successes to learn from)

Key Constraints

Hard constraints:

• Runway is finite (7 months)
• Coach psychology is upstream and unfixable
• Solo founder (entire team is you)
• Stripe checkout flow can't materially change

Soft constraints (negotiable):

• The 5-minute build promise is non-negotiable, but the 5-minute launch promise was a misframing—you can separate build speed from launch speed

The Critical Insight: The 72-Hour Window

The decision to not share is made in the first 72 hours. After that, momentum is gone and coaches enter slow acceptance. This is the only real intervention window.

The 5 successes all had external accountability (warm prospects or audience expectations) that made sharing feel inevitable rather than optional. The 78 who froze had none. The 8-10 who shared but didn't sell (Group B) prove courage can be built—they had willingness but not reach.

The 5-Minute Promise Paradox

This is the core tension: the product's strength (fast page building) is also its liability (gets people to publish before they're psychologically ready). This isn't a constraint to work around—it's a permanent feature of the product. The solution must live inside this paradox: keep the 5-minute build, but introduce a slower, supported arc for the launch itself.

---

Ready to Move Forward?

Does this capture where you left off? Anything you'd update or clarify before we move into solution generation?

Perfect. Those are both critical clarifications and I'll make sure they're embedded:

1. Success metric softened: Primary target is 25%, but 15%+ is directionally meaningful and worth building on given the small sample size. We're testing a hypothesis, not hitting a KPI.

2. Founder bias as explicit evaluation risk: When we get to Step 3 (solution evaluation), we'll name this explicitly as a filter: "Does this solution fit the customer I wish I had, or the customer I actually have?" This keeps you honest during evaluation.

Both of those go into the document and will show up when we need them.

---

Ready for Solution Generation

We have reviewed the problem framing and have a solid understanding of what we are solving. Ready to shift into creative solution generation? This is where we go wide — generating as many ideas as possible before narrowing down.

The energy here is divergent thinking: no filtering, no ranking, no "that won't work" yet. We're building a solution set, not picking a winner.

---

Energy Checkpoint ✓

Great. Let's go wide.

---

Root Causes & Constraints (Grounding)

Before we generate, let me recap what we're solving for:

Root causes we need to address:

• High identity stakes on the page (first concrete claim coaches have ever made)
• Psychological freeze triggered by that weight
• The reinforcing loop (freeze → editor hiding → sunk cost → deeper freeze)
• Absence of external accountability (the 5 successes all had it; the 78 who froze didn't)
• The 72-hour window closing after publish (decision to not share is made in first 3 days)

Key constraints shaping our solution space:

• Coach psychology (imposter syndrome, moral weight, fraud fears) is upstream and unfixable—we can't grant legitimacy the field doesn't grant
• Target market is allergic to anything that feels like a marketing tactic—solution must feel like peer support or it dies on contact
• The 5-minute build promise is non-negotiable, but the 5-minute launch promise was a misframing—we can separate them
• Solo founder bandwidth (can ship in 1-2 weeks, could stretch to 3-4 if other work is batched)
• Small sample size (5 successes, 78 frozen, 8-10 sharers)

The strongest force working for us:

• Accountability interrupts the loop—it doesn't solve imposter syndrome, it just prevents coaches from hiding in the editor indefinitely while processing it
• The 72-hour window is the entire game—this is the only real intervention point
• The 5 successes prove it's solvable (they had external accountability; we can manufacture it)

---

Solution Generation Methods

Based on the problem you've framed, I want to recommend 3 methods that fit different angles of attack:

1. Lateral Thinking Techniques (Primary recommendation)

Why: You're stuck in a pattern where the solution space feels limited ("we can only tweak the product, we can't change coach psychology"). Lateral thinking breaks that pattern by using provocations and random entry to access novel ideas. This is especially valuable when the obvious solutions feel insufficient.

2. Morphological Analysis (Secondary recommendation)

Why: This problem has multiple parameters (timing of intervention, who delivers it, what form it takes, what the accountability mechanism is, how it's framed). Morphological analysis systematically explores combinations to find non-obvious configurations. You might discover that a combination you haven't considered yet is actually the strongest.

3. Assumption Busting (Tertiary recommendation)

Why: Your framing is solid, but there are likely assumptions baked in about what coaches will accept, what the product can do, what "launch" means. Busting those assumptions opens the solution space. This is also a guard against the founder bias risk—it forces you to question assumptions you're making about your customers.

---

Which of these appeal to you? Should we work through all three, or would you prefer to focus on one or two?

---

Perfect order. You're right—clearing assumptions first prevents generating inside the same constraints. Let's start.

---

Method 1: Assumption Busting

The goal here is to surface the assumptions you're making about coaches, the product, the problem, and the solution space—then challenge them to see what becomes possible.

Let me start with some prompts, but I want you to push back and name assumptions I'm missing:

Assumptions About Coaches:

1. "Coaches need to feel like they're part of a peer community to overcome the freeze."

   • What if that's backwards? What if some coaches actually freeze harder when watched by peers? What if the intervention needs to be private, not public?
   • Challenge: Is it really peer community, or is it just external accountability? Could accountability come from somewhere else?

2. "Coaches are allergic to anything that feels like a marketing tactic or sales push."

   • What if that's only true for some coaches? What if the 78 who froze are actually a specific subset who are allergic, and there's a different subset who would want direct help with the sales moment?
   • Challenge: Are we designing for the entire market, or for a specific psychographic within it?

3. "Coaches need permission from the field or from other coaches to claim their identity."

   • What if they don't need permission—what if they need permission to experiment? Permission to fail, permission to charge wrong, permission to learn?
   • Challenge: Is the barrier "I'm not a real coach" or "I'm not allowed to test whether I'm a real coach"?

4. "The page is loaded with identity weight because it's permanent and public."

   • What if the weight is actually about irreversibility? What if coaches would share more if it felt like an experiment, not a declaration?
   • Challenge: Does the page need to feel like a permanent identity claim, or could it feel like a beta test?

Assumptions About the Product:

5. "The 5-minute build promise means we can't add friction or process around launch."

   • What if the 5-minute promise is about build, not launch? What if coaches would accept a slower launch arc as long as the build stayed fast?
   • Challenge: Have you explicitly separated build speed from launch speed in how you talk about the product?

6. "We can't materially change the Stripe checkout flow or the publish moment."

   • What if we don't need to? What if the intervention lives entirely after publish, in a new surface or experience?
   • Challenge: Is the constraint real, or is it assumed?

7. "The product needs to work for all coaches equally."

   • What if it doesn't? What if the solution is to segment: some coaches get one intervention, others get a different one based on their readiness or psychology?
   • Challenge: Are we trying to solve for everyone, or could we solve for the segment most likely to respond?

Assumptions About the Problem:

8. "The freeze is caused by imposter syndrome and moral weight that we can't fix."

   • What if we're right that we can't fix those upstream issues, but we're wrong about what that means for the solution? What if the solution isn't about fixing imposter syndrome—it's about making it irrelevant to the decision?
   • Challenge: Does the coach need to feel confident, or do they just need to feel accountable?

9. "The 72-hour window is the only intervention point."

   • What if there are other windows? What if the real window is before publish (when they're building)? Or what if there's a second window at day 7 or day 14 when they're considering abandoning the page?
   • Challenge: Is 72 hours the only moment, or is it just the best moment?

10. "The 5 successes prove the solution is accountability."

    • What if they prove something else? What if the 5 successes had accountability and something else you haven't named yet (warm prospect + existing audience, or warm prospect + high coach confidence, or existing audience + lower imposter syndrome)?
    • Challenge: What did the 5 successes actually have in common? Is it really just accountability, or is there a second variable?

---

Your Turn: Name the Assumptions You're Making

I've surfaced 10. But you're inside this problem more than I am. What assumptions are you aware of making that might be wrong? Think about:

• Assumptions about what coaches will respond to
• Assumptions about what the product can or can't do
• Assumptions about the timeline or the intervention window
• Assumptions about what "success" looks like
• Assumptions about what you can't change

What assumptions are you holding that you're not sure about?

---

This is the work. You've just cracked open the solution space.

Let me name what just happened: You've surfaced seven assumptions, and each one opens a different branch of possibility:

1. Cohort as asynchronous feed (not real-time) — Solves minimum viable cohort, removes timing dependency
2. Intervention as human forcing function (not product feature) — Shifts from "give them a product" to "help them create accountability"
3. Share = one warm person (not broadcast to audience) — Reframes launch as relationship activation, not marketing
4. Where they share matters as much as whether — Introduces targeting/matching into the solution
5. Actively offboard unready coaches — Trades volume for signal and unit economics
6. Help them decide if they should launch (not just help them launch) — Honest filtering upstream
7. Service layer first, product second — Keep doing it manually until the pattern emerges, then automate

These aren't small tweaks. These are different solutions. And they're all worth exploring.

Here's what I notice: Six of these seven directly challenge the founder bias risk you named. They're all moving away from "the product I wish I could build" toward "what the customer actually needs." That's the signal to take them seriously.

---

Now We Generate

You've cleared the box. Now let's go wide using Lateral Thinking to explore what becomes possible once those assumptions are questioned.

Lateral Thinking: Provocations

I'm going to use your assumptions as provocations. For each one, we'll ask: "What if this were true? What would that unlock?"

Provocation 1: "Cohorts are asynchronous, not real-time"

If coaches don't need to publish in the same week, the intervention becomes:

• A feed of recent launches with outcomes (social proof, not live accountability)
• Coaches can see "these 5 people launched last month, here's what happened"
• This works at any volume—even 1-2 launches per week is enough signal
• The page becomes less of an identity moment and more of a "here's what other people did" comparison

What ideas does this spark?

• A "Recent Launches" feed on the dashboard showing coaches who've shared, what they shared to, and results (if they opt in to sharing results)
• A "Launch Stories" email series: "Here's what happened when [Coach] shared their page to their email list"
• A public gallery of coach pages with permission, showing range of positioning and pricing
• Anonymous outcome data: "Of the 10 coaches who launched this month, 6 shared to a warm audience, 4 to cold, conversion was 3x higher for warm"

What else? What other ideas come to mind when you remove the real-time constraint?

---

Provocation 2: "The intervention is helping coaches create a human forcing function, not a product one"

If your job is to help them identify and activate one warm person before they share, the intervention becomes:

• Coaching moment, not product moment
• "Who is one person who would want to know about this?" (not "how do you share broadly?")
• The product enables it, but you're the one asking the question
• This is high-touch, which you're already doing for the 5 successes

What ideas does this spark?

• A pre-launch checklist: "Before you share, identify one warm person who should know. Email them first. See what happens."
• A "Warm Prospect Finder" prompt in the editor: "Who do you know who's actively looking for coaching? Start there."
• A service where you (the founder) do a 15-minute call with coaches post-publish: "Let's identify who you should contact first"
• A template for the first outreach email: "Here's how to reach out to one person without it feeling like a pitch"
• A "Launch Partner" feature: coaches nominate someone to be their accountability buddy, that person gets a notification when they publish

What else? What other ideas come to mind when you shift from product forcing function to human forcing function?

---

Provocation 3: "Share means one warm person, not broadcast to audience"

If the unlock is helping coaches identify and contact one specific person, the intervention becomes:

• Matching problem (who should they contact?)
• Relationship activation, not marketing
• Measurable: did they contact the person? Did the person respond?
• Completely different from "how do I reach a crowd?"

What ideas does this spark?

• A matching system: coaches list 3-5 warm prospects (people they know), the product suggests which one to contact first based on fit
• A "First Contact" flow: fill in details about one prospect, get a templated outreach email, track if they opened it
• A peer matching system: coaches who've launched recently get matched with coaches about to launch, the recent launcher becomes the "warm person" to contact
• A "Warm Prospect Validator": before coaches share, they name one person they're going to contact. You ask: "Is this person actually warm? Do they know you? Have they asked about coaching?" (filtering for real warm prospects, not wishful thinking)
• A "Contact Tracker": after sharing, coaches log who they've contacted and track responses. Visibility into "I contacted 3 people, 2 responded" becomes the metric, not "I published"

What else? What other ideas come to mind when you reframe share as "contact one warm person"?

---

Provocation 4: "Where they share matters as much as whether they share"

If the quality of the audience is the variable, the intervention becomes:

• Audience matching (not just activation)
• Diagnosis before solution (is this coach ready to reach their existing audience? Do they need to build one first?)
• Group B becomes a learning opportunity, not a failure (they shared to the wrong people, not the wrong way)

What ideas does this spark?

• A pre-launch audience audit: "How many warm prospects do you have? How many cold? What's your ratio?" (filtering for coaches who actually have reach)
• A segmented intervention: coaches with warm audiences get one path (contact them), coaches without get a different path (build an audience first, or rethink positioning)
• A "Audience Readiness" gate: coaches answer 3 questions about their existing relationships, get a score. If score is low, the product suggests "you might not be ready to launch yet" instead of pushing them through
• A "Warm List Builder": for coaches without an audience, a tool to help them identify and cultivate warm prospects before launching
• A "Positioning for Your Audience" prompt: coaches describe their actual audience (not their dream audience), then refine positioning to match that audience, not the other way around

What else? What other ideas come to mind when you separate "share" from "share to the right people"?

---

Provocation 5: "Actively offboard unready coaches"

If you're willing to lose some customers to keep signal clean, the intervention becomes:

• Filtering, not forcing
• Honesty about readiness
• Better unit economics on the ones who stay
• Smaller, more cohesive cohort of people who actually respond

What ideas does this spark?

• A "Readiness Quiz" post-publish: coaches answer 5 questions about their internal state (imposter syndrome level, clarity on positioning, warm prospects available, willingness to charge). Low scores get honest feedback: "You might not be ready yet. Here's what to work on first."
• A "Pause Button": coaches can mark their page as "paused" instead of abandoned. You reach out: "Want to talk about what's blocking you? Or should we put this on ice?"
• A "Cohort Opt-In": coaches who've published get invited to a small group only if they meet readiness criteria. Unready coaches get a different path (resources, community, but not the forcing function).
• A "Founder Call" gate: coaches who want to share have to do a 10-minute call with you first. You assess readiness and alignment. Some don't make it through. Those are the ones most likely to freeze anyway.
• A "Refund + Offboard" option: coaches who've published but are frozen get offered a refund + a recommendation to come back in 6 months. You're betting on the ones who stay being the ones who convert.

What else? What other ideas come to mind when you're willing to lose volume for signal?

---

Provocation 6: "Help them decide if they should launch, not just how"

If your job is honest filtering upstream, the intervention becomes:

• Coaching product, not build product
• Help coaches resolve imposter syndrome before they publish
• Different target market (coaches who want to think before they act, not coaches who want to move fast)
• Completely different positioning and business model

What ideas does this spark?

• A "Launch Readiness" course: 5-7 modules coaches work through before they publish. Covers imposter syndrome, pricing psychology, positioning, warm prospects, first outreach. Only after completion can they publish.
• A "Coaching Clarity" questionnaire: coaches answer deep questions about their transition, their positioning, their audience. If answers are unclear, the product says "you're not ready yet, here's what to clarify first."
• A "Founder Coaching" layer: you do 30-minute calls with coaches before they publish. You help them think through positioning, pricing, warm prospects. Some decide not to publish. That's the win.
• A "Peer Cohort Pre-Launch": coaches who want to launch join a 4-week group. You facilitate conversations about imposter syndrome, moral weight, positioning. They publish together at the end. This is the real product.
• A "Decision Framework": instead of "build your page," the product becomes "decide if coaching is right for you, and if so, what kind." The page is the artifact of that decision, not the decision itself.

What else? What other ideas come to mind when you shift from "help them launch" to "help them decide if they should"?

---

Provocation 7: "Service layer first, product second"

If you keep doing it manually until the pattern emerges, then automate, the intervention becomes:

• High-touch, not scalable (yet)
• Pattern discovery through doing, not guessing
• Founder bias check (you'll learn what actually works, not what you think should work)
• Automation comes later, based on real patterns

What ideas does this spark?

• A "Founder Office Hours" model: coaches who publish get 1 optional call with you in the first 72 hours. You ask: "Who are you going to contact first?" and help them think through it. Track what happens.
• A "Launch Buddy" service: you manually match coaches who've published with coaches about to publish. The recent launcher becomes the accountability partner. You run this manually for 20 coaches, see if it moves the needle.
• A "Warm Prospect Coaching" call: post-publish, coaches get one call where you help them identify and draft an outreach to one warm person. You do this manually, track outcomes.
• A "Weekly Launch Check-in" email: you send a personal message to coaches who published that week: "How's it going? Who have you contacted?" You read responses, learn patterns, iterate.
• A "Founder Feedback Loop": instead of building a feature, you spend 2 weeks doing manual outreach to the 78 frozen coaches. You ask: "What would actually help you share this?" You take notes. Then you build based on what you heard, not what you guessed.

What else? What other ideas come to mind when you're willing to do the work manually first?

---

Pause Here

Before we move to Morphological Analysis, let me check in:

What ideas are resonating from the lateral thinking?

And more importantly: Are there other provocations or wild directions we should explore? You've opened the box—what else is possible now that those assumptions are questioned?

(Don't worry about organizing yet. We're still in divergent mode. I want to capture everything before we systematize.)

---

This is exactly the move. You've gone from "what if we add a feature" to "what if we fundamentally change how we activate coaches." These aren't product tweaks—they're different business models.

Let me organize what you've named:

Ideas resonating most (strong conviction):

1. Launch Buddy peer matching — Recent launcher becomes accountability partner for someone about to launch. 1:1, no batch timing needed, peer evidence + fresh memory of the freeze
2. Warm Prospect Validator — "Is this person actually warm?" filter before sharing. Surfaces wishful vs real prospects
3. Founder Office Hours (explicit + tracked) — You're already doing this for the 5 successes. Make it systematic, track outcomes, test whether accountability is the mechanism or if it's just your presence
4. Readiness Quiz with honest offboarding — Low scores get "you might not be ready" feedback. Honest framing that might attract the right coaches

New directions (opening more space): 5. Publish gate: name a warm prospect first — The publish button doesn't unlock until they've filled in "the first person I'm going to send this to." Embeds human forcing function into the build flow 6. Public commitment board (opt-in) — "20 coaches launching this week, here's mine." Public list is the accountability, respects the allergy by being opt-in 7. Non-coach accountability partner — Match coaches with someone in their life (friend, partner, family) who they nominate. Product just facilitates and sends check-in at day 7. Outsource accountability to people who already care 8. Soft first ask — Instead of "share the page," first ask is "send a private message saying I'm thinking about launching, would you want to see it." Smaller ask, creates soft response loop before hard share 9. 30-day no-product test — Stop building, do 20-minute calls with every coach who publishes. Just conversation about who they're going to contact first. Cleanest test of whether product is the answer at all

---

Now: Morphological Analysis

You've gone wide. Now let's sweep systematically to make sure we haven't missed obvious combinations and to organize what's emerged.

Morphological analysis works by identifying key parameters of the solution and exploring all combinations of options for each parameter. This often reveals non-obvious configurations.

For your problem, the key parameters are:

Parameter 1: WHO provides the accountability?

• Peer launcher (recent coach who's been through it)
• Founder (you, directly)
• Non-coach friend (someone in their life they nominate)
• Public commitment (anonymous crowd)
• Cohort (group of coaches publishing together)

Parameter 2: WHEN does the intervention happen?

• Pre-publish (before they build/publish)
• At-publish (during the publish moment, like a gate)
• Post-publish (first 72 hours after)
• Ongoing (continuous throughout the freeze)

Parameter 3: WHAT is the forcing mechanism?

• External deadline (someone waiting, expectation set)
• Public commitment (visibility creates pressure)
• Warm prospect identification (naming who you'll contact first)
• Readiness filtering (honest assessment of whether you should launch)
• Peer evidence (seeing others do it successfully)

Parameter 4: HOW is it delivered?

• Product feature (built into the tool)
• Service layer (you do it manually, high-touch)
• Hybrid (you do it manually until pattern emerges, then automate)
• Async system (feeds, emails, dashboards, no real-time interaction)
• Sync system (calls, group sessions, real-time interaction)

Parameter 5: WHO is the target?

• All coaches who publish (try to help everyone)
• Coaches who opt in (self-select into the intervention)
• Coaches who pass readiness filter (only the ones most likely to respond)
• Coaches with warm prospects (pre-filtered for reach)

---

Now Let's Explore Combinations

I'm going to walk through some combinations and you tell me which ones feel right or spark new ideas.

Combination A: Peer Launcher + Post-Publish (72hr window) + Warm Prospect ID + Hybrid Service/Product

• You manually match coaches who just published with a recent launcher
• That recent launcher reaches out in first 72 hours: "I just did this. Who are you going to contact first?"
• You do this manually for 20 coaches, track outcomes
• Once pattern is clear, you build a matching algorithm and automate
• Does this feel right? This combines Launch Buddy + Founder Office Hours + the manual-first approach

Combination B: Non-Coach Friend + At-Publish Gate + Warm Prospect ID + Product Feature

• Publish button doesn't unlock until they nominate one person they're going to contact first
• That person's email is captured
• On day 7, the product sends that person a check-in: "How did [Coach]'s launch go? Have they reached out?"
• Outsources accountability to people who already know and care about them
• Does this feel right? This embeds the human forcing function into the build flow and uses product to facilitate

Combination C: Founder + Post-Publish + Readiness + Service Layer

• Every coach who publishes gets offered a 20-minute call with you in the first 72 hours
• On the call, you assess readiness and help them identify who to contact first
• Low readiness coaches get honest feedback: "You might not be ready yet. Here's what to work on."
• Some coaches don't take the call. You track who does and what happens.
• Does this feel right? This is the explicit Founder Office Hours + Readiness Quiz combo

Combination D: Public Commitment + Post-Publish + Peer Evidence + Async Product

• Coaches who publish can opt in to a public board: "20 coaches launching this week"
• Daily email showing who else launched, what happened (if they opt in to sharing results)
• No real-time interaction, fully async, fully opt-in
• Asynchronous cohort solves the timing problem
• Does this feel right? This is the public commitment board + asynchronous feed idea

Combination E: Peer Launcher + Pre-Publish + Warm Prospect ID + Hybrid

• Before coaches publish, they get matched with a recent launcher
• That launcher helps them think through positioning, warm prospects, pricing
• They co-create the first outreach message
• Coach publishes when ready
• Does this feel right? This moves the intervention upstream, before the freeze locks in

Combination F: Self-Select Cohort + At-Publish Gate + Readiness + Service Layer

• Coaches who want to publish join a 4-week pre-launch cohort
• You facilitate conversations about imposter syndrome, positioning, warm prospects
• Warm prospect identification and first outreach planning happens in the group
• They publish together at the end, with peer accountability
• Does this feel right? This is the upstream readiness + cohort idea, but done as service not product

Combination G: All Coaches + Post-Publish + Warm Prospect Validator + Product Feature

• Every coach gets a post-publish prompt: "Who is the first person you're going to contact?"
• You ask 3 validation questions: "How do they know you? Have they asked about coaching? Are they actively looking?"
• If answers are weak, the product says "this person might not be warm enough. Try someone else."
• Surfaces wishful vs real prospects, no gatekeeping, just honesty
• Does this feel right? This is the Warm Prospect Validator as a product feature

Combination H: Founder + Post-Publish + No Product Intervention + Service Only

• For 30 days, you stop building features entirely
• Every coach who publishes gets a 20-minute call with you
• Conversation: "Who are you going to contact first? Let's think through it."
• You track outcomes, learn patterns, then decide what to build
• Does this feel right? This is the pure service test to see if the product is the answer at all

---

Your Turn: Which Combinations Feel Right?

Looking at A through H:

1. Which 2-3 combinations feel most aligned with what you're trying to test?
2. Are there combinations I missed? (e.g., combining parameters in a way I didn't show)
3. What would you add or remove from the combinations that resonate?

The goal is to identify which of these feels like the strongest hypothesis to test, and which feel like supporting experiments.

---

Perfect. You've just moved from generating solutions to prioritizing a testing sequence. That's the signal that solution generation is complete.

Let me organize what you've named:

---

Generated Solutions (Organized by Testing Sequence)

Tier 1: Clean Signal Generators (Test First)

Solution 1: Pure Founder Service Test (Combination H)

• Every coach who publishes gets offered a 20-minute call with you in the first 72 hours
• Conversation: "Who are you going to contact first? Let's think through it."
• Track outcomes against 6% baseline
• Hypothesis: Accountability is the mechanism, or human presence matters, or the problem is upstream of any intervention
• Signal value: Highest. Answers the fundamental question: does presence move the needle?
• Effort: Minimal (you're doing this manually anyway)

Solution 2: Warm Prospect Validator (Combination G)

• Post-publish product feature: coaches answer 3 validation questions about their first prospect
• Product gives honest feedback: "This person might not be warm enough. Try someone else."
• Runs in parallel without interfering with other experiments
• Hypothesis: Wishful prospects are a hidden failure mode; validation surfaces real vs fake warm prospects
• Signal value: High. Tests a specific, measurable variable
• Effort: Small product change, can ship in 1-2 weeks

---

Tier 2: Motivation Isolators (Test After H)

Solution 3: Self-Selected Founder Office Hours (Combination I)

• Post-publish, coaches can request a 20-minute call (not offered to everyone)
• Only coaches who opt in get the intervention
• Hypothesis: Self-selecting coaches convert at high rates anyway; the call isn't doing the work, the coach's readiness is
• Signal value: High. Isolates motivation from intervention mechanism
• Effort: Minimal (same call, different framing)
• Timing: Run after H to isolate what H revealed

---

Tier 3: Productized Versions (Test After Signal Confirmed)

Solution 4: Founder Office Hours + Readiness Filter (Combination C)

• Every coach who publishes gets offered a 20-minute call
• On the call: assess readiness, help identify first prospect, give honest feedback
• Low readiness coaches get: "You might not be ready yet. Here's what to work on first."
• Hypothesis: Honest offboarding + accountability + readiness assessment moves conversion
• Signal value: Moderate (adds variables, but tests the productized version of what H proved)
• Effort: Moderate (service layer, but structured)
• Timing: Run after H confirms the call matters

Solution 5: Launch Buddy Peer Matching (Combination A, folded into H)

• Manually match coaches who just published with recent launchers
• Recent launcher reaches out in first 72 hours
• Hypothesis: Peer accountability + fresh memory of the freeze creates sustainable support
• Signal value: Moderate (tests scalability of what H proved works)
• Effort: Moderate (matching algorithm, manual for first 20 coaches)
• Timing: Only test after H confirms founder presence works; this is the scalable version

---

Tier 4: Supporting Infrastructure (Deploy After Core Hypothesis Confirmed)

Solution 6: Asynchronous Cohort Feed (Combination D)

• Post-publish, coaches see a feed of recent launches with outcomes
• "These 5 coaches launched last week, here's what happened"
• Async, opt-in, no real-time interaction
• Hypothesis: Peer evidence + social proof supports whatever core intervention works
• Signal value: Low (supporting feature, not core hypothesis)
• Effort: Medium (requires outcome tracking and UI)
• Timing: Deploy after core mechanism is proven, as supporting layer

Solution 7: Public Commitment Board (Combination D variant)

• Coaches can opt in to a public board: "20 coaches launching this week"
• Daily email showing who else launched
• Hypothesis: Public visibility creates accountability for coaches with lower allergy to marketing
• Signal value: Low (supporting feature)
• Effort: Low (simple feature)
• Timing: Deploy after core mechanism is proven

---

Creative Alternatives (Deprioritized, But Worth Naming)

Solution 8: Publish Gate with Warm Prospect Nomination

• Publish button doesn't unlock until they name one person they'll contact first
• Embeds human forcing function into the build flow
• Why deprioritized: Tests a mechanism (gating) before testing whether the mechanism is needed. H answers that first.
• When to revisit: If H shows the call works, this becomes a way to automate the "who will you contact" conversation

Solution 9: Pre-Publish Peer Coaching (Combination E)

• Before publishing, coaches get matched with recent launchers
• Co-create positioning, warm prospect list, first outreach
• Why deprioritized: Slows down the 5-minute build promise; conflicts with core product principle
• When to revisit: Only if data shows coaches need pre-publish support (unlikely given the 5 successes all published quickly)

Solution 10: Self-Selected Pre-Launch Cohort (Combination F)

• 4-week cohort before publish, work through imposter syndrome, positioning, warm prospects
• Publish together with peer accountability
• Why deprioritized: Pre-publish, adds friction, upstream of the real intervention window
• When to revisit: Only if you decide to reposition as a coaching product, not a build product (major pivot)

Solution 11: Non-Coach Accountability Partner with Day 7 Check-in

• Coaches nominate someone in their life
• Product sends that person a check-in email at day 7
• Why deprioritized: Day 7 email to nominated person feels invasive, could damage relationships
• When to revisit: Only if H shows accountability works and you want to test outsourced vs founder-provided

---

Summary: Solution Set

Total solutions generated: 11 across 3 categories

• Tier 1 (Clean signal): 2 solutions
• Tier 2 (Motivation isolation): 1 solution
• Tier 3 (Productized): 2 solutions
• Tier 4 (Supporting infrastructure): 2 solutions
• Creative alternatives (deprioritized): 4 solutions

Testing sequence:

1. H (Pure Founder Service) — Cleanest signal, run first
2. G (Warm Prospect Validator) — Parallel, doesn't interfere
3. I (Self-Selected Office Hours) — Follow-up to isolate motivation
4. C (Founder Office Hours + Readiness) — Productize what H proved
5. A (Launch Buddy) — Scalable version after H confirmed
6. D & 7 (Feeds + Public Board) — Supporting infrastructure after core confirmed

---

Ready to Move Forward?

Does this organization feel right? Is there anything in the solution set that should be added, removed, or repositioned?

Once you confirm, I'll emit the initial Solution Plan document skeleton with all these solutions organized, and we'll move to Step 3: Evaluation & Selection.

---

Perfect adjustments. Done.

Solution 8 (Publish Gate with Warm Prospect Nomination) moved to Tier 1 alongside G. Both are small product changes that test specific mechanisms in parallel without interference. Clear call.

Solution 11 (Non-Coach Accountability Partner) removed entirely. You're right—relationship damage risk is real, and the solution doesn't deserve document legitimacy if you wouldn't build it anyway.

---

Final Solution Set (Locked)

Tier 1: Clean Signal Generators (Test First)

1. Pure Founder Service Test (H)
2. Warm Prospect Validator (G)
3. Publish Gate with Warm Prospect Nomination (8)

Tier 2: Motivation Isolators (Test After Signal) 4. Self-Selected Founder Office Hours (I)

Tier 3: Productized Versions (Test After Signal Confirmed) 5. Founder Office Hours + Readiness Filter (C) 6. Launch Buddy Peer Matching (A)

Tier 4: Supporting Infrastructure (Deploy After Core Confirmed) 7. Asynchronous Cohort Feed (D) 8. Public Commitment Board (D variant)

Creative Alternatives (Deprioritized) 9. Pre-Publish Peer Coaching (E) 10. Self-Selected Pre-Launch Cohort (F)

---

---

Excellent. The solution set is locked and the skeleton is live.

Ready to move to Step 3: Evaluation & Selection?

This is where we shift from "how many ideas can we create?" to "which idea is the best fit?" We'll define evaluation criteria, apply a systematic method, and select the optimal solution with clear rationale.

---

Transition from Generation to Selection

We generated 10 solutions—great creative work. Now we shift gears: from "how many ideas can we create?" to "which idea is the best fit?" This requires a different kind of thinking — objective, criteria-driven evaluation.

Let me briefly recap the solution list for reference:

Tier 1 (Clean Signal Generators):

• Pure Founder Service Test (H)
• Warm Prospect Validator (G)
• Publish Gate with Warm Prospect Nomination (8)

Tier 2-4 (Productized versions, infrastructure, alternatives):

• Self-Selected Founder Office Hours (I)
• Founder Office Hours + Readiness Filter (C)
• Launch Buddy Peer Matching (A)
• Asynchronous Cohort Feed (D)
• Public Commitment Board (D variant)
• Pre-Publish Peer Coaching (E)
• Self-Selected Pre-Launch Cohort (F)

Now we evaluate.

---

Define Evaluation Criteria

Before we evaluate solutions, we need to define what "best" means in your context. Let me start with some common criteria relevant to your situation, then we'll expand based on what matters to you.

Suggested criteria:

1. Signal Clarity — Will this test directly answer the core question about what's blocking coaches? Does it isolate a variable or does it confound multiple variables?

2. Speed to Learning — How quickly can you run this test and get meaningful data? (Remember: 72-hour window is the intervention point, so learning speed matters)

3. Resource Efficiency — What's the founder time + product engineering required? Solo founder bandwidth is a real constraint.

4. Risk to Customer Relationship — Does this experiment feel gimmicky, invasive, or misaligned with coach values? Or does it feel like genuine support?

5. Runway Impact — Does this test help you prove unit economics within 7 months, or does it consume runway without clear signal?

6. Scalability Signal — If this works, can you scale it? Or is it a one-off that doesn't lead to a repeatable model?

7. Founder Bias Check — Does this solution fit the customer you wish you had, or the customer you actually have? (This is the explicit risk you named earlier)

---

These are common criteria, but your situation may need others. What else matters for evaluating solutions in your context? Think about:

• Your stakeholders (are there investors, advisors, or others who need to see certain kinds of progress?)
• Your organization (solo founder constraints, what you can actually execute)
• The specific constraints from the framing (the 5-minute promise, the allergy to marketing tactics, the 72-hour window)
• What would make you confident moving forward vs. what would feel like wasted time

What criteria would you add or adjust? And once we've defined them, which matter most? (We'll weight them so some carry more influence than others in the evaluation.)

---

Perfect. You've just designed an evaluation framework that protects against your own bias. Let me lock in what you've defined:

---

Evaluation Criteria (Finalized)

High Weight Criteria (Learning & Direction)

1. Signal Clarity — How cleanly does this test answer the core question? Does it isolate a variable or confound multiple variables?
2. Insight Beyond Outcome — How much do you learn even if the test fails? Does a negative result teach you something valuable?
3. Founder Bias Check — Does this fit the customer you wish you had, or the customer you actually have?
4. Speed to Learning — How quickly can you run this test and get meaningful data?

Medium Weight Criteria (Execution Feasibility)

5. Resource Efficiency — What founder time + product engineering required? (Solo founder constraint)
6. Risk to Customer Relationship — Does this feel like genuine support, or gimmicky/invasive?
7. Reversibility — If it goes badly, how easy to undo? What's the blast radius?

Low Weight Criteria (Company-Level Constraints)

8. Runway Impact — Does this help prove unit economics within 7 months?
9. Scalability Signal — If this works, can you scale it? (Deprioritized at this stage; learning comes first)

---

Quick Screen: Eliminate Obviously Infeasible Solutions

Before we do deep evaluation, let's quickly screen: are there any solutions that are obviously infeasible, clearly don't address root causes, or violate a hard constraint?

Looking at the 10 solutions:

• Tier 1 (H, G, 8): All viable, all test core hypotheses
• Tier 2 (I): Viable, tests motivation isolation
• Tier 3 (C, A): Viable, productized versions of what Tier 1 proves
• Tier 4 (D, D-variant): Viable, supporting infrastructure
• Creative alternatives (E, F): Both conflict with 5-minute build promise (pre-publish friction)

Quick call: Should we eliminate E and F now since they conflict with the hard constraint (5-minute build), or keep them in as deprioritized alternatives in case the evaluation reveals something unexpected?

My recommendation: Eliminate E and F from the evaluation. They're already deprioritized, they conflict with a non-negotiable constraint, and evaluating them will just create noise. Keep them in the document as "not considered" but focus evaluation on the 8 solutions that are actually in play.

Does that feel right, or do you want to evaluate all 10?

---

Perfect. We're evaluating 8 solutions across 9 criteria (4 high weight, 3 medium weight, 2 low weight).

---

Shortlist Before Deep Evaluation

Before we apply the full Decision Matrix, let me ask: Looking at the 8 solutions against your criteria, are there any we can eliminate quickly?

Thinking out loud:

• All 8 seem viable and test real hypotheses
• None seem obviously infeasible or misaligned
• The Tier 1 solutions (H, G, 8) are the primary candidates; Tiers 2-4 are follow-ups
• But we could theoretically evaluate all 8 and let the matrix show which rank highest

My suggestion: Evaluate all 8. The matrix will show you which Tier 1 solution ranks highest (that's your primary recommendation), and it will also show how the Tier 2-4 solutions compare (useful for sequencing). Nothing jumps out as "obviously eliminate this."

Does that feel right, or do you want to shortlist further?

---

Apply Decision Matrix

We'll use a Decision Matrix: list the 8 solutions as rows, the 9 weighted criteria as columns, rate each solution against each criterion, calculate weighted scores, and see what emerges.

I'll walk through this collaboratively. For each criterion, I'll ask you to rate each solution on a scale of 1-5 (1 = weak, 5 = strong), and we'll discuss your reasoning as we go.

Let's start:

---

Criterion 1: Signal Clarity (High Weight)

How cleanly does this test answer the core question? Does it isolate a variable or confound multiple variables?

Let me rate each solution and you tell me if I'm reading it right:

Solution H (Pure Founder Service Test):

• Cleanest possible signal. Single variable: does a 20-minute call with you move conversion?
• If it works: accountability or human presence is the mechanism
• If it fails: even founder presence isn't enough, problem is upstream
• My rating: 5/5 — Isolates one variable perfectly
• Does that match your thinking?

Solution G (Warm Prospect Validator):

• Tests one specific hypothesis: are wishful prospects a hidden failure mode?
• If it works: coaches will choose warmer prospects when validated
• If it fails: prospect warmth isn't the blocker
• My rating: 4/5 — Clean signal, but depends on whether coaches actually use the feedback
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• Tests whether forcing explicit prospect nomination at publish moment moves behavior
• Confounds two variables: the nomination itself + the gating mechanism
• If it works, you don't know if it's the nomination or the gate that moved it
• My rating: 3/5 — Tests a mechanism but doesn't isolate cleanly
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• Tests whether the call itself does the work, or whether self-selecting coaches convert anyway
• Isolates motivation from intervention
• My rating: 4/5 — Clean isolation, but depends on H showing the call matters first
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• Tests multiple variables together: the call + readiness assessment + honest offboarding
• If it works, you don't know which variable moved it
• My rating: 2/5 — Multiple variables confound the signal
• Does that match?

Solution A (Launch Buddy Peer Matching):

• Tests whether peer accountability works as well as founder accountability
• But only makes sense to test after H confirms founder accountability works
• My rating: 2/5 — Not a standalone signal generator, dependent test
• Does that match?

Solution D (Asynchronous Cohort Feed):

• Tests whether peer evidence (seeing others' outcomes) moves behavior
• But requires outcome data, which you won't have until other tests run
• My rating: 1/5 — Supporting feature, not a signal generator; too dependent on other tests
• Does that match?

Solution D-variant (Public Commitment Board):

• Tests whether public visibility creates accountability
• But is opt-in, so confounds motivation (who opts in?) with mechanism
• My rating: 2/5 — Interesting hypothesis but confounded by self-selection
• Does that match?

---

Pause here: Do these Signal Clarity ratings feel right to you? Anything I'm misjudging?

---

Locked in:

Signal Clarity (High Weight)

• H: 5/5
• G: 3/5
• 8: 3/5
• I: 3/5
• C: 2/5
• A: 2/5
• D: 1/5
• D-variant: 1/5

---

Criterion 2: Insight Beyond Outcome (High Weight)

How much do you learn even if the test fails? Does a negative result teach you something valuable?

Let me rate each:

Solution H (Pure Founder Service Test):

• If conversion moves: accountability or presence is the mechanism
• If conversion doesn't move: even founder presence isn't enough, the problem is upstream of any intervention (this is huge learning—reshapes roadmap)
• My rating: 5/5 — Either answer is valuable and changes direction
• Does that match?

Solution G (Warm Prospect Validator):

• If coaches use feedback and convert higher: prospect warmth was a hidden blocker
• If coaches ignore feedback or convert the same: either they don't trust the validator, or prospect warmth isn't the blocker
• My rating: 3/5 — Moderate insight; failure tells you validator doesn't work, but not necessarily that prospect warmth isn't the issue
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• If coaches fill it in and convert higher: nomination at publish moment matters
• If coaches resent the gate or abandon: you've learned the gate itself creates friction
• If they fill it in but don't convert higher: nomination alone doesn't move behavior
• My rating: 4/5 — Multiple failure modes each teach something different
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• If self-selectors convert higher than non-selectors: motivation matters more than the call
• If self-selectors and non-selectors convert the same: the call is doing the work
• My rating: 3/5 — Moderate insight; teaches you about motivation vs mechanism, but only if H already confirmed the call matters
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• If low-readiness coaches accept offboarding: honest feedback is valued
• If they churn on the honesty: the framing backfires
• But you still don't know which variable (call, readiness assessment, or honesty) moved conversion
• My rating: 2/5 — Some insight about readiness filtering, but confounded by multiple variables
• Does that match?

Solution A (Launch Buddy Peer Matching):

• If peer matching works: peer accountability scales what founder accountability proved
• If peer matching fails: peer presence isn't enough (only founder presence works)
• My rating: 2/5 — Moderate insight, but only in context of H already confirming founder works
• Does that match?

Solution D (Asynchronous Cohort Feed):

• If coaches engage with feed and convert higher: peer evidence moves behavior
• If they ignore it: peer evidence doesn't matter
• My rating: 2/5 — Some insight, but feed requires outcome data you won't have yet; it's a supporting feature testing
• Does that match?

Solution D-variant (Public Commitment Board):

• If coaches opt in and convert higher: public commitment works
• If low opt-in: coaches reject public commitment (confirms allergy to marketing)
• My rating: 2/5 — Insight about the allergy, but self-selection confounds the mechanism
• Does that match?

---

Pause here: Do these Insight Beyond Outcome ratings feel right?

---

Locked in:

Insight Beyond Outcome (High Weight)

• H: 5/5
• G: 3/5
• 8: 3/5
• I: 3/5
• C: 2/5
• A: 2/5
• D: 2/5
• D-variant: 2/5

---

Criterion 3: Founder Bias Check (High Weight)

Does this solution fit the customer you wish you had, or the customer you actually have?

This is the explicit risk you named. Let me think through each:

Solution H (Pure Founder Service Test):

• Tests what coaches actually respond to (presence, conversation, accountability)
• You're not assuming anything; you're asking them directly
• No bias baked in
• My rating: 5/5 — Maximally honest test of actual behavior
• Does that match?

Solution G (Warm Prospect Validator):

• Assumes coaches will respond to feedback about prospect warmth
• Assumes they want validation before reaching out
• This could be the customer you wish you had (thoughtful, reflective) rather than the one you have (impulsive, freeze-prone)
• My rating: 3/5 — Some bias risk; you're assuming coaches will use the feedback
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• Assumes coaches will fill in the nomination field and that it will move their behavior
• Assumes they'll accept the gate as helpful, not as friction
• Moderate bias risk
• My rating: 3/5 — You're designing what you think should work, not testing what does
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• Assumes coaches who opt in are self-selecting for motivation
• Tests actual behavior, not assumed behavior
• My rating: 4/5 — High honesty; you're letting coaches reveal their actual motivation
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• Assumes coaches will accept honest feedback about readiness
• Assumes readiness filtering is the right intervention
• Could be the customer you wish you had (coachable, self-aware) rather than the one you have
• My rating: 2/5 — Moderate-high bias risk; you're designing a solution based on an assumption about who coaches are
• Does that match?

Solution A (Launch Buddy Peer Matching):

• Assumes peer support is what coaches want
• Assumes recent launchers are the right support source
• This could be the customer you wish you had (community-oriented) rather than the one you have
• My rating: 2/5 — Bias risk; assumes coaches want peer support specifically
• Does that match?

Solution D (Asynchronous Cohort Feed):

• Assumes coaches want to see peer evidence and outcomes
• Assumes they'll find that motivating
• Could be the customer you wish you had (inspired by peer success) rather than the one you have (frozen by comparison)
• My rating: 2/5 — Bias risk; assumes peer evidence is motivating
• Does that match?

Solution D-variant (Public Commitment Board):

• Assumes coaches will opt in to public visibility
• Assumes public commitment creates accountability for coaches with allergy to marketing
• High bias risk; this is designing for a customer you wish you had
• My rating: 1/5 — High bias risk; contradicts what you know about the market
• Does that match?

---

Pause here: Do these Founder Bias Check ratings feel right? This is the dimension where you're most likely to fool yourself, so I want to make sure we're honest.

---

Locked in:

Founder Bias Check (High Weight)

• H: 5/5
• G: 2/5
• 8: 3/5
• I: 3/5
• C: 2/5
• A: 2/5
• D: 2/5
• D-variant: 1/5

---

Criterion 4: Speed to Learning (High Weight)

How quickly can you run this test and get meaningful data?

The 72-hour window is the intervention point, so speed matters. Let me rate:

Solution H (Pure Founder Service Test):

• You can start offering calls tomorrow
• First meaningful data (1-2 weeks of calls, 5-10 coaches)
• Full signal (20-30 coaches) in 3-4 weeks
• My rating: 5/5 — Can start immediately, signal in weeks
• Does that match?

Solution G (Warm Prospect Validator):

• Requires product shipping (1-2 weeks)
• Then needs coaches to use it and see results
• Meaningful data in 4-6 weeks
• My rating: 3/5 — Moderate speed; product dependency adds delay
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• Requires product shipping (1-2 weeks)
• Then coaches encounter it at publish
• Meaningful data in 3-4 weeks after ship
• My rating: 4/5 — Reasonably fast; product ship is the only delay
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• Requires H to run first and show signal
• Then you offer calls only to coaches who request
• Can't start until H is done (4+ weeks in)
• My rating: 1/5 — Dependent test; can't run until H completes
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• Can start after H shows the call matters
• But adds the readiness assessment layer
• Meaningful data in 4-6 weeks after H completes
• My rating: 1/5 — Dependent; waits for H
• Does that match?

Solution A (Launch Buddy Peer Matching):

• Requires H to confirm founder presence works
• Then requires matching algorithm or manual matching
• Can't start until H is done and you've identified recent launchers
• My rating: 1/5 — Dependent; waits for H
• Does that match?

Solution D (Asynchronous Cohort Feed):

• Requires outcome tracking infrastructure
• Requires H, G, or other tests to generate outcome data
• Can't start until you have data to show
• My rating: 1/5 — Dependent; waits for other tests
• Does that match?

Solution D-variant (Public Commitment Board):

• Can ship in 1-2 weeks
• But depends on coaches opting in (low probability given allergy)
• Meaningful data in 4-6 weeks
• My rating: 2/5 — Fast to ship, but adoption risk makes signal slow
• Does that match?

---

Pause here: Do these Speed to Learning ratings feel right? The dependency structure is becoming clear—H is the prerequisite for most others.

---

Locked in:

Speed to Learning (High Weight)

• H: 5/5
• G: 3/5
• 8: 4/5
• I: 1/5
• C: 1/5
• A: 1/5
• D: 1/5
• D-variant: 2/5

---

Criterion 5: Resource Efficiency (Medium Weight)

What founder time + product engineering required? Solo founder constraint.

Let me rate:

Solution H (Pure Founder Service Test):

• 20-minute calls with each coach who publishes
• No product engineering
• Founder time: 3-4 hours per week (manageable, you're already doing this)
• My rating: 5/5 — Minimal resource lift; you're already doing it
• Does that match?

Solution G (Warm Prospect Validator):

• Requires product engineering: validation questions + feedback logic
• Estimate: 4-6 hours of engineering
• Founder time: minimal (set it up, monitor)
• My rating: 3/5 — Moderate engineering lift, low ongoing founder time
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• Requires product engineering: add one field to publish flow, make it required
• Estimate: 2-3 hours of engineering
• Founder time: minimal
• My rating: 4/5 — Small engineering lift; straightforward feature
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• Same as H (20-minute calls)
• Founder time: 3-4 hours per week
• My rating: 5/5 — Same resource as H
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• Same as H (20-minute calls) plus readiness assessment logic
• Could be product feature or manual assessment
• Founder time: 4-5 hours per week (slightly more than H)
• My rating: 4/5 — Manageable; slightly more than H
• Does that match?

Solution A (Launch Buddy Peer Matching):

• Manual matching for first 20 coaches: 2-3 hours per week
• Later: matching algorithm engineering (not needed yet)
• Founder time: moderate
• My rating: 3/5 — Moderate founder time for manual matching
• Does that match?

Solution D (Asynchronous Cohort Feed):

• Requires product engineering: feed UI, outcome tracking, data pipeline
• Estimate: 8-12 hours of engineering
• Founder time: moderate (managing outcomes, writing stories)
• My rating: 2/5 — Significant engineering lift
• Does that match?

Solution D-variant (Public Commitment Board):

• Requires product engineering: board UI, daily email logic
• Estimate: 4-6 hours of engineering
• Founder time: minimal (set it up, monitor)
• My rating: 3/5 — Moderate engineering lift
• Does that match?

---

Pause here: Do these Resource Efficiency ratings feel right?

---

Locked in:

Resource Efficiency (Medium Weight)

• H: 4/5
• G: 3/5
• 8: 4/5
• I: 5/5
• C: 4/5
• A: 3/5
• D: 2/5
• D-variant: 3/5

---

Criterion 6: Risk to Customer Relationship (Medium Weight)

Does this feel like genuine support, or gimmicky/invasive?

This is about whether coaches will feel helped or manipulated. Let me rate:

Solution H (Pure Founder Service Test):

• Offering a call feels like genuine support
• Founder presence feels authentic, not gimmicky
• Coaches who don't want the call can ignore it
• My rating: 5/5 — Feels genuine and helpful
• Does that match?

Solution G (Warm Prospect Validator):

• Feedback on prospect warmth feels helpful, not invasive
• But depends on the tone of the feedback
• Risk: if feedback feels harsh or judgmental, it backfires
• My rating: 4/5 — Helpful if done right; tone matters
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• Gating the publish button could feel restrictive
• But if framed as "who are you going to contact first?" it feels supportive
• Risk: feels like you're forcing them to commit before they're ready
• My rating: 3/5 — Depends on framing; moderate risk of feeling pushy
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• Coaches opt in; feels voluntary and genuine
• No risk of feeling forced or manipulated
• My rating: 5/5 — Feels supportive and voluntary
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• The call feels genuine
• But honest offboarding ("you might not be ready") could feel rejecting
• Risk: coaches feel judged or pushed away
• My rating: 3/5 — Honest but risky; depends on tone and how coaches interpret rejection
• Does that match?

Solution A (Launch Buddy Peer Matching):

• Peer support feels genuine and aligned with market values
• But if matching feels random or forced, it backfires
• My rating: 4/5 — Feels supportive if matching is thoughtful
• Does that match?

Solution D (Asynchronous Cohort Feed):

• Seeing peer outcomes feels like social proof, not manipulation
• But if it feels like you're comparing coaches to each other, it backfires
• My rating: 4/5 — Helpful if framed as inspiration, not comparison
• Does that match?

Solution D-variant (Public Commitment Board):

• Public visibility could feel gimmicky or like a marketing tactic
• Coaches with allergy to marketing will feel manipulated
• High risk
• My rating: 2/5 — High risk of feeling like a tactic, not support
• Does that match?

---

Pause here: Do these Risk to Customer Relationship ratings feel right?

---

Locked in:

Risk to Customer Relationship (Medium Weight)

• H: 5/5
• G: 4/5
• 8: 2/5
• I: 5/5
• C: 3/5
• A: 4/5
• D: 4/5
• D-variant: 2/5

---

Criterion 7: Reversibility (Medium Weight)

If it goes badly, how easy to undo? What's the blast radius?

Let me rate:

Solution H (Pure Founder Service Test):

• Stop offering calls tomorrow
• No product change, no blast radius
• Completely reversible
• My rating: 5/5 — Fully reversible, zero blast radius
• Does that match?

Solution G (Warm Prospect Validator):

• If it backfires, you can disable the feature or remove the feedback
• Coaches who've already used it are fine; new coaches don't see it
• Mostly reversible, small blast radius
• My rating: 4/5 — Easy to turn off; minimal blast radius
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• If coaches resent the gate, you have to ship a fix to remove it
• Every coach who hits it before you fix it has a bad experience
• High blast radius while the gate is live
• Technically reversible but creates customer friction before you can undo it
• My rating: 2/5 — Reversible but high blast radius during the failure window
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• Stop offering calls to self-selectors
• No product change
• Fully reversible
• My rating: 5/5 — Fully reversible, zero blast radius
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• If readiness assessment backfires, stop doing it
• No product change required
• Fully reversible
• My rating: 5/5 — Fully reversible, zero blast radius
• Does that match?

Solution A (Launch Buddy Peer Matching):

• If peer matching doesn't work, stop matching
• Manual process, easy to stop
• Fully reversible
• My rating: 5/5 — Fully reversible, zero blast radius
• Does that match?

Solution D (Asynchronous Cohort Feed):

• If feed backfires, you can disable it
• But coaches who've already seen it have the experience
• Mostly reversible, small blast radius
• My rating: 4/5 — Easy to turn off; small blast radius
• Does that match?

Solution D-variant (Public Commitment Board):

• If it backfires (coaches feel manipulated), you can turn it off
• But coaches who've already opted in have the experience
• Mostly reversible, small blast radius
• My rating: 4/5 — Easy to turn off; small blast radius
• Does that match?

---

Pause here: Do these Reversibility ratings feel right? Solution 8 is standing out as high-risk because the gate touches the publish flow that 120 coaches have already used.

---

Locked in:

Reversibility (Medium Weight)

• H: 5/5
• G: 4/5
• 8: 2/5
• I: 5/5
• C: 5/5
• A: 5/5
• D: 4/5
• D-variant: 4/5

---

Criterion 8: Runway Impact (Low Weight)

Does this test help prove unit economics within 7 months, or consume runway without clear signal?

Let me rate:

Solution H (Pure Founder Service Test):

• Tests the core hypothesis (accountability moves conversion)
• If it works, you have a path to unit economics (service + product)
• If it fails, you learn the problem is upstream (saves runway by stopping wrong bets)
• My rating: 5/5 — Directly tests unit economics viability
• Does that match?

Solution G (Warm Prospect Validator):

• Tests a specific blocker (prospect warmth)
• If it works, marginal improvement to conversion
• If it fails, you learn this isn't the blocker (saves runway)
• My rating: 3/5 — Tests a variable but not the core hypothesis
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• Tests a mechanism but confounds multiple variables
• If it works, you still don't know which variable moved it
• Uses runway on a test with muddy signal
• My rating: 2/5 — Tests something but signal is unclear for unit economics
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• Depends on H first
• Tests motivation vs mechanism (useful for understanding, but not core hypothesis)
• My rating: 2/5 — Useful follow-up, not core to proving unit economics
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• Depends on H first
• Tests the productized version of what H proved
• More relevant to unit economics than I, but still dependent
• My rating: 2/5 — Useful follow-up, not core to proving unit economics
• Does that match?

Solution A (Launch Buddy Peer Matching):

• Depends on H first
• Tests scalability of what H proved
• Relevant to unit economics if H works
• My rating: 2/5 — Useful follow-up, not core to proving unit economics
• Does that match?

Solution D (Asynchronous Cohort Feed):

• Supporting feature, not core to unit economics
• Consumes runway on infrastructure before core hypothesis is proven
• My rating: 1/5 — Uses runway without testing core hypothesis
• Does that match?

Solution D-variant (Public Commitment Board):

• Supporting feature, not core to unit economics
• Consumes runway on a feature with low adoption probability (allergy to marketing)
• My rating: 1/5 — Uses runway without clear unit economics signal
• Does that match?

---

Pause here: Do these Runway Impact ratings feel right?

---

Locked in:

Runway Impact (Low Weight)

• H: 5/5
• G: 3/5
• 8: 2/5
• I: 2/5
• C: 2/5
• A: 2/5
• D: 1/5
• D-variant: 1/5

---

Criterion 9: Scalability Signal (Low Weight)

If this works, can you scale it? Or is it a one-off that doesn't lead to a repeatable model?

Let me rate:

Solution H (Pure Founder Service Test):

• If it works, you have a service model (founder calls) that you can scale into a team
• Or you learn that human presence is the mechanism and build product around it
• Scalable either way
• My rating: 5/5 — Proves a mechanism that scales (service or product)
• Does that match?

Solution G (Warm Prospect Validator):

• If it works, it's a product feature that scales infinitely
• If it doesn't work, you've learned something but it doesn't lead anywhere
• My rating: 4/5 — Scalable if it works; product feature
• Does that match?

Solution 8 (Publish Gate with Warm Prospect Nomination):

• If it works, it's a product feature that scales
• But you won't know which variable (gate or nomination) moved it
• My rating: 3/5 — Scalable if it works, but unclear what to scale
• Does that match?

Solution I (Self-Selected Founder Office Hours):

• If it works, you have a self-selecting segment of coaches
• But self-selection might be the only reason they convert (not scalable to the broader market)
• My rating: 2/5 — Might not scale; depends on motivation being the variable
• Does that match?

Solution C (Founder Office Hours + Readiness Filter):

• If it works, you have a service model with filtering
• Scalable into a team, but requires honest offboarding (cultural fit)
• My rating: 3/5 — Scalable as a service, but requires team alignment
• Does that match?

Solution A (Launch Buddy Peer Matching):

• If it works, you have a peer matching algorithm that scales
• Scalable into a product feature
• My rating: 4/5 — Scalable if it works; can become a product
• Does that match?

Solution D (Asynchronous Cohort Feed):

• If it works, it's a product feature that scales infinitely
• Fully scalable
• My rating: 4/5 — Scalable if it works; product feature
• Does that match?

Solution D-variant (Public Commitment Board):

• If it works, it's a product feature that scales
• But adoption is uncertain (allergy to marketing)
• My rating: 2/5 — Technically scalable, but uncertain if it works at all
• Does that match?

---

Pause here: Do these Scalability Signal ratings feel right?

---

Locked in:

Scalability Signal (Low Weight)

• H: 5/5
• G: 4/5
• 8: 3/5
• I: 2/5
• C: 3/5
• A: 4/5
• D: 4/5
• D-variant: 2/5

---

Calculate Weighted Scores

Now let's calculate. Here are the weights:

High Weight (4x multiplier): Signal Clarity, Insight Beyond Outcome, Founder Bias Check, Speed to Learning Medium Weight (2x multiplier): Resource Efficiency, Risk to Customer Relationship, Reversibility Low Weight (1x multiplier): Runway Impact, Scalability Signal

Let me build the matrix:

Solution	SC	IBO	FBC	STL	RE	RCR	REV	RI	SS	Weighted Score
H	5×4	5×4	5×4	5×4	4×2	5×2	5×2	5×1	5×1	20+20+20+20+8+10+10+5+5 = 118
G	3×4	3×4	2×4	3×4	3×2	4×2	4×2	3×1	4×1	12+12+8+12+6+8+8+3+4 = 73
8	3×4	3×4	3×4	4×4	4×2	2×2	2×2	2×1	3×1	12+12+12+16+8+4+4+2+3 = 73
I	3×4	3×4	3×4	1×4	5×2	5×2	5×2	2×1	2×1	12+12+12+4+10+10+10+2+2 = 74
C	2×4	2×4	2×4	1×4	4×2	3×2	5×2	2×1	3×1	8+8+8+4+8+6+10+2+3 = 57
A	2×4	2×4	2×4	1×4	3×2	4×2	5×2	2×1	4×1	8+8+8+4+6+8+10+2+4 = 58
D	1×4	2×4	2×4	1×4	2×2	4×2	4×2	1×1	4×1	4+8+8+4+4+8+8+1+4 = 49
D-var	1×4	2×4	1×4	2×4	3×2	2×2	4×2	1×1	2×1	4+8+4+8+6+4+8+1+2 = 45

---

Results

Ranked by Weighted Score:

1. Solution H (Pure Founder Service Test): 118/160 ⭐ Clear winner
2. Solution I (Self-Selected Founder Office Hours): 74/160
3. Solution G (Warm Prospect Validator): 73/160
4. Solution 8 (Publish Gate): 73/160
5. Solution A (Launch Buddy Peer Matching): 58/160
6. Solution C (Founder Office Hours + Readiness): 57/160
7. Solution D (Asynchronous Cohort Feed): 49/160
8. Solution D-variant (Public Commitment Board): 45/160

---

What the Matrix Shows

H dominates across all four high-weight criteria:

• Signal Clarity: 5/5 (cleanest test)
• Insight Beyond Outcome: 5/5 (learns something either way)
• Founder Bias Check: 5/5 (maximally honest)
• Speed to Learning: 5/5 (can start immediately)

H also scores well on medium-weight criteria (Resource Efficiency 4/5, Risk to Relationship 5/5, Reversibility 5/5). The only place it's slightly lower is Resource Efficiency (4 instead of 5), which you correctly noted—it's manageable now but won't stay that way as volume grows. That's honest and acceptable.

The next tier (I, G, 8) are much closer to each other (74, 73, 73), which tells you they're all viable follow-ups, but none of them should be your primary test. They all depend on H or are supporting features.

The bottom tier (A, C, D, D-var) all score 45-58, which confirms they're Tier 2-4 follow-ups, not primary tests.

---

Recommendation

The recommended solution is Solution H: Pure Founder Service Test.

Rationale

H is the only solution that directly tests the core hypothesis (does accountability or human presence move conversion?) with maximum signal clarity and minimum bias. It:

• Tests what matters most: Whether the mechanism is accountability, founder presence, or whether the problem is upstream of any intervention
• Learns either way: If it works, you have a direction. If it fails, you learn the problem is upstream and reshape the roadmap accordingly
• Avoids founder bias: You're testing actual coach behavior, not assuming what they want
• Can start immediately: No product engineering required; you're already doing this for the 5 successes
• Is fully reversible: Stop offering calls tomorrow if needed
• Directly impacts runway: Either validates the unit economics path or saves runway by stopping wrong bets

Key Strengths

• Highest score across all high-weight criteria (learning, clarity, bias check, speed)
• Manageable resource lift (4/5 efficiency)
• Zero customer relationship risk (5/5)
• Completely reversible (5/5)
• Proves a scalable mechanism (5/5)

Honest Concerns

• Resource scaling: At 3-4 hours per week now, but could hit 10-15 hours per week as volume grows. This is manageable for a test but not sustainable long-term. However, that's a good problem to have—it means the test is working.
• Sample size: You'll have meaningful signal in 3-4 weeks with 20-30 coaches, but the framing document noted small sample size as a risk. This test doesn't solve that entirely, but it's the fastest way to move from 6% to a meaningful baseline.

What Happens Next

If H works (conversion moves to 15%+):

• You've proven accountability/presence is the mechanism
• Move to C (Founder Office Hours + Readiness) as the productized version
• Then A (Launch Buddy) as the scalable version
• Then D/D-var as supporting infrastructure

If H doesn't work (conversion stays near 6%):

• You've learned even founder presence isn't enough
• The problem is upstream (imposter syndrome, moral weight, fraud fears)
• You pivot to either: (a) repositioning as a coaching product that addresses upstream issues, or (b) accepting that some coaches will never launch and focusing on the segment that will
• This is huge learning worth the runway investment

---

Does This Recommendation Feel Right?

Does H feel like the right primary solution to test? Any concerns about the rationale or the next steps?

---

Perfect catch. You're right—running I in parallel to H would confound the results, but running I after H confirms the call matters makes sense. Let me reframe the sequence:

If H works (conversion moves to 15%+):

• You've proven something is moving conversion
• Immediately run I (Self-Selected Office Hours) in parallel to isolate: is it the call, or is it self-selection/motivation?
• H + I together answer: "Is the mechanism accountability/presence, or is it just that motivated coaches convert anyway?"
• Once H + I clarify the mechanism, move to C (productized version) and A (scalable version)
• Then D/D-var as supporting infrastructure

If H doesn't work (conversion stays near 6%):

• Even founder presence isn't enough
• The problem is upstream
• Pivot to either repositioning as a coaching product or accepting segment limitations

This is the honest sequence—you're not assuming the call is doing the work, you're testing it.

---

---

Locked in. Ready to move to Step 4: Implementation Planning?

This is where we turn the recommended solution into concrete action steps with clear ownership, sequencing, and resource requirements.

---

Transition from Evaluation to Implementation

We have chosen our solution and we are confident in the rationale. Now comes the critical part — turning it into reality. A brilliant solution without a solid implementation plan stays theoretical. Let us make this concrete.

Recap of the recommended solution:

Solution H: Pure Founder Service Test

• Every coach who publishes gets offered a 20-minute call with you in the first 72 hours
• Conversation focuses on: "Who are you going to contact first? Let's think through it."
• Track outcomes against 6% baseline conversion rate
• Hypothesis: Accountability/presence moves conversion, or the problem is upstream
• Timeline: Meaningful signal in 3-4 weeks with 20-30 coaches

---

Define Implementation Approach

Before we break this into action steps, let's clarify the overall strategy.

You have three options for how to run this test:

Option A: Pilot First

• Offer the call to the next 10-15 coaches who publish
• Run for 2-3 weeks, learn, then decide whether to expand
• Best if: You want to test the mechanics of the call before committing to a larger cohort
• Risk: Smaller sample size means longer to meaningful signal

Option B: Phased Rollout

• Offer the call to all coaches who publish, starting immediately
• Phase 1 (weeks 1-2): Offer to everyone, track mechanics and outcomes
• Phase 2 (weeks 3-4): Refine based on learnings, continue offering
• Best if: You want to maximize sample size and learning speed
• Risk: You're running at scale from day one, which could be overwhelming

Option C: Full Implementation

• Offer the call to all coaches who publish, immediately and continuously
• Track everything, iterate based on patterns
• Best if: You're confident in the mechanics and ready to run at whatever volume comes
• Risk: If volume spikes, you hit the resource ceiling fast

---

My recommendation: Option B (Phased Rollout) feels right for your situation. You get meaningful sample size quickly (weeks 1-2 give you 10-15 coaches, enough to learn), you can refine the mechanics in phase 2, and you avoid the resource ceiling hitting you unexpectedly.

What approach feels right to you? Pilot, phased, or full?

---

Perfect. Phased rollout it is. Week 1-2 is your learning window; week 3-4 is your refinement window. You'll have 20-30 coaches by end of week 4, which is your meaningful signal threshold.

---

Create Action Steps

Now let's break the implementation into specific, sequenced action steps. For each step, we'll define:

• What needs to happen (specific, observable action)
• Who is responsible (you, since you're solo)
• What sequence makes sense (dependencies)
• What resources are needed

Let me walk through the logic with you, and you tell me if I'm missing anything or if the sequence feels wrong.

Phase 1: Setup (Before first call — Days 1-2)

Step 1: Design the Call Template

• What: Create a simple call structure/script for the 20-minute conversation
• Why: You want consistency in how you're running the test, so you can compare outcomes
• What the call covers:
  • First 5 min: "Congrats on publishing. Tell me about your positioning."
  • Next 10 min: "Who is one person you're going to contact first? Let's think through it together."
  • Last 5 min: "Here's what I'd do: [specific advice]. Will you reach out to them in the next 48 hours?"
• Owner: You
• Resources needed: 30 minutes to write it out
• Dependency: None (can start immediately)

Step 2: Set Up Tracking System

• What: Create a simple tracking doc to record outcomes
• Why: You need to compare conversion rates (6% baseline vs. call participants)
• What to track per coach:
  • Date of call
  • Name/email
  • Who they said they'd contact first
  • Did they contact that person? (follow up at day 3, day 7)
  • Did they get a response?
  • Did they make a sale?
  • Any other notes about the call
• Owner: You
• Resources needed: Simple spreadsheet or Notion doc, 30 minutes to set up
• Dependency: None

Step 3: Communicate the Offer to Coaches

• What: Create a message to coaches who've just published, offering the call
• Why: You need a clear, consistent way to invite them
• What the message says:
  • "Congrats on launching! I'm doing 20-minute calls with coaches in the first 72 hours to help you think through your first outreach. Want to chat?"
  • Include calendar link (Calendly or similar) for them to self-book
  • Make it clear it's optional, not required
• Owner: You
• Resources needed: Calendly account (free tier works), 30 minutes to write message and set up calendar
• Dependency: Depends on Step 1 (need call template ready first)

Step 4: Integrate the Offer into Your Workflow

• What: Decide where/how this message gets sent to coaches who publish
• Why: You need a systematic way to reach every coach who publishes
• Options:
  • Automated email triggered on publish (if you have that infrastructure)
  • Manual: You check the dashboard daily and send the offer to new publishers
  • Notification in the product: Show coaches who publish a prompt to book a call
• Owner: You (or product engineer if you have one, but you don't)
• Resources needed: 15 minutes to set up the workflow
• Dependency: Depends on Step 3 (need the message ready)

---

Pause here: Do these four setup steps feel complete? Am I missing anything before you start offering calls?

---

Locked in. Two critical additions:

Step 1.5: Define Success Thresholds and Interpretation Framework

• What: Lock in what "the call worked" means before you start, in measurable terms
• Why: Prevents unconscious goalpost-moving and ensures honest interpretation of results
• What to define:
  • 15%+ conversion rate: Directional signal confirmed. The call is moving something. Proceed to Phase 2 refinement, then I (Self-Selected) to isolate mechanism.
  • 10-14% conversion rate: Ambiguous zone. Meaningful movement from 6%, but below directional threshold. Decision point: run longer to get more data, or treat as "call matters but not enough to be the core solution"?
  • 6-9% conversion rate: No meaningful movement. The call isn't moving conversion. Problem is upstream. Pivot to repositioning or segment focus.
  • Below 6% conversion rate: The call might be making things worse. Stop immediately, analyze what went wrong.
• Owner: You
• Resources needed: 30 minutes to write this down (lock it in a doc you won't change)
• Dependency: None (do this before Step 1)

Step 2.5: Define Follow-Up Protocol for Non-Bookers

• What: Create a protocol for coaches who don't book the call after the initial offer
• Why: Ensures consistency and prevents bias from chasing some coaches harder than others
• What to define:
  • First offer: Sent at publish (Step 4 workflow)
  • Follow-up 1: If no booking within 24 hours, send a reminder: "Still happy to chat if you want to think through your first outreach. [Link]"
  • Follow-up 2: If no booking within 48 hours, send one final message: "Last chance—I'm here if you want to talk through this. [Link]" Then stop.
  • Tone: Warm, optional, no pressure. "I'm here if you want it" not "you should do this"
  • Tracking: Note in your tracking doc who booked vs. who didn't, to see if there's a pattern (e.g., do coaches who don't book also not convert?)
• Owner: You
• Resources needed: 30 minutes to write the protocol
• Dependency: None (do this before Step 1)

---

Revised Setup Phase (Days 1-2)

Step 1.5: Define Success Thresholds (do first) Step 1: Design the Call Template Step 2: Set Up Tracking System Step 2.5: Define Follow-Up Protocol Step 3: Communicate the Offer Step 4: Integrate into Workflow

Does this revised setup sequence feel complete now?

---

Phase 2: Launch & Learn (Weeks 1-2)

Step 5: Begin Offering Calls to All New Publishers

• What: Execute the workflow defined in Step 4—send the offer to every coach who publishes
• Why: You're running the test at volume to get meaningful data fast
• Owner: You
• Cadence: Daily or as-needed (check dashboard, send offers)
• Resources needed: 15-30 minutes per day to send offers and manage calendar
• Dependency: Steps 1-4 complete

Step 6: Conduct Calls and Take Notes

• What: Run the 20-minute calls using the template from Step 1
• Why: You're testing the hypothesis directly
• Owner: You
• Cadence: As coaches book (likely 3-5 calls per week in week 1, ramping to 5-10 in week 2)
• Resources needed: 20 minutes per call (including prep and notes)
• What to capture in notes:
  • Who they said they'd contact first
  • Tone/energy (were they excited, anxious, frozen?)
  • Any objections or hesitations they named
  • Your advice/recommendation
  • Their commitment level ("I'll do it today" vs. "I'll think about it")
• Dependency: Step 5 (coaches need to book first)

Step 7: Track Outcomes in Real-Time

• What: Update your tracking doc after each call and every 3 days, follow up with coaches to see if they contacted their prospect
• Why: You need to see patterns emerging in real-time, not wait until week 4
• Owner: You
• Cadence: Update tracking doc within 24 hours of call, send follow-up check-ins at day 3 and day 7 post-call
• Resources needed: 10 minutes per call to update tracking; 5-10 minutes per day for follow-up messages
• Follow-up messages: "Hey [Coach], just checking in—did you reach out to [person's name]? How'd it go?"
• Dependency: Step 6 (need call data first)

Step 8: Look for Patterns Weekly

• What: Every Friday, review the week's calls and outcomes to spot patterns
• Why: You need to notice if something is working or breaking early, so you can adjust in Phase 2
• Owner: You
• Cadence: Weekly review (Friday end-of-day)
• Resources needed: 30 minutes per week
• What to look for:
  • Are coaches who take the call contacting their prospect at higher rates than baseline?
  • Are there common objections or hesitations?
  • Is the call template working, or do you need to adjust it?
  • Are follow-ups working, or are coaches ghosting?
  • Any surprises in who books vs. who doesn't?
• Dependency: Step 7 (need tracking data)

---

Pause here: Does the Phase 2 (Weeks 1-2) sequence feel right? Anything missing or out of order?

---

Perfect. You're protecting against data bias and gut bias. That's exactly right.

Step 8.5: Midpoint Gut Check (End of Week 2)

• What: Before moving to Phase 2, pause and do an honest subjective assessment separate from the data
• Why: Your intuition after 10-15 calls matters. If your gut and the data disagree, that tension is worth naming explicitly
• Owner: You
• Timing: End of week 2, after Step 8 pattern review is done
• Resources needed: 30 minutes to write down your honest read
• What to assess:
  • Gut feeling: Is the test working? Are coaches responding to the call? Is something shifting?
  • Energy: Do you feel energized by the calls or drained? Are they revealing something or just confirming what you already know?
  • Surprises: Anything unexpected in how coaches are showing up or responding?
  • Honest tension: If gut and data disagree, name it explicitly. "The numbers look flat but I feel like something is shifting" or "The numbers look okay but I feel like I'm forcing it"
  • Decision: Based on gut + data together, do you want to continue Phase 2, adjust the approach, or pause the test?
• Dependency: Step 8 (pattern review)

---

Phase 3: Refine & Scale (Weeks 3-4)

Step 9: Adjust Based on Weeks 1-2 Learning

• What: Based on Step 8 patterns + Step 8.5 gut check, make adjustments to the call template, follow-up protocol, or offer messaging
• Why: You want to refine what's working before scaling to weeks 3-4
• Owner: You
• Timing: Early week 3 (Monday)
• Resources needed: 1-2 hours to review learning and adjust
• What might change:
  • Call template (maybe the "who will you contact" question needs a different framing)
  • Follow-up protocol (maybe 2 follow-ups is too many, or not enough)
  • Offer messaging (maybe the tone needs adjustment)
  • Tracking (maybe you need to track different variables)
• Dependency: Steps 8 + 8.5 (need learning first)

Step 10: Continue Offering Calls (Weeks 3-4)

• What: Keep offering calls to all new publishers, using the refined approach from Step 9
• Why: You're building sample size to reach 20-30 coaches by end of week 4
• Owner: You
• Cadence: Same as Step 5 (daily or as-needed)
• Resources needed: 15-30 minutes per day
• Dependency: Step 9 (need refinements in place)

Step 11: Continue Tracking & Follow-Ups (Weeks 3-4)

• What: Same as Step 7—update tracking, send follow-up check-ins, capture outcomes
• Owner: You
• Cadence: Same as Step 7
• Resources needed: Same as Step 7
• Dependency: Step 10

Step 12: Weekly Pattern Reviews (Weeks 3-4)

• What: Same as Step 8—every Friday, review patterns
• Owner: You
• Cadence: Weekly (Friday end-of-day)
• Resources needed: 30 minutes per week
• Dependency: Step 11

---

Phase 4: Evaluate & Decide (End of Week 4)

Step 13: Analyze Final Results Against Success Thresholds

• What: At end of week 4, calculate final conversion rate for coaches who took the call
• Why: You need to measure against the thresholds you defined in Step 1.5
• Owner: You
• Timing: End of week 4 (Friday or Monday of week 5)
• Resources needed: 1-2 hours to analyze
• What to calculate:
  • Total coaches who published in weeks 1-4
  • Total coaches who booked a call
  • Total coaches who contacted their prospect (from tracking)
  • Total coaches who made a sale (or are on track)
  • Conversion rate for call-takers vs. non-bookers
  • Compare to 6% baseline
• Dependency: Step 12 (need all tracking data)

Step 14: Interpret Results Using Thresholds

• What: Apply the interpretation framework from Step 1.5 to your results
• Why: You've already decided how to interpret each outcome; now you execute that decision honestly
• Owner: You
• Timing: Same as Step 13
• Resources needed: 30 minutes
• Outcomes:
  • 15%+ conversion: Signal confirmed. Move to Phase 5 (I in parallel).
  • 10-14% conversion: Ambiguous zone. Decision: run longer, or treat as "call matters but not enough"?
  • 6-9% conversion: No meaningful movement. Problem is upstream. Pivot decision.
  • Below 6%: Stop, analyze what went wrong.
• Dependency: Step 13

Step 15: Document Learning & Next Steps

• What: Write up what you learned, what surprised you, what worked and didn't, and what you're doing next
• Why: This becomes your decision record and informs the next test (I in parallel, or pivot)
• Owner: You
• Timing: Same as Step 14
• Resources needed: 1 hour to write
• What to document:
  • Results vs. thresholds
  • Key patterns from the calls
  • What surprised you
  • What worked in the call template
  • What didn't work
  • Gut check from week 2 + final results
  • Next step (run I in parallel, or pivot)
• Dependency: Step 14

---

Summary: Implementation Sequence

Setup (Days 1-2): 1.5 → 1 → 2 → 2.5 → 3 → 4

Phase 1: Launch & Learn (Weeks 1-2): 5 → 6 → 7 → 8 → 8.5

Phase 2: Refine & Scale (Weeks 3-4): 9 → 10 → 11 → 12

Phase 3: Evaluate & Decide (End of Week 4): 13 → 14 → 15

---

Resource Requirements Summary

Founder Time (You):

• Setup (Days 1-2): ~4 hours total
• Weeks 1-2: ~10-15 hours per week (calls + follow-ups + tracking + weekly review)
• Weeks 3-4: ~10-15 hours per week (same)
• End of week 4: ~3-4 hours (analysis + documentation)
• Total: ~50-60 hours over 4 weeks

Tools/Systems Needed:

• Calendly (free tier) for call booking
• Spreadsheet or Notion for tracking (free)
• Email (you have this)
• Phone/video call tool (you have this)

No product engineering required. This is entirely a service test.

---

Does This Implementation Plan Feel Solid?

Does the sequencing make sense? Are the steps specific enough that you could execute them? Anything missing or out of place?

---

Perfect flags. All three are critical:

Flag 1: Deprioritize Marketing During Test Window

• Added to plan: During weeks 1-4, pause or significantly reduce marketing/growth work
• Why: 10-15 hours per week on calls + normal operations is the ceiling; adding marketing will break you
• Owner: You
• Action: Block this on your calendar now as "test window—marketing paused"
• This goes into the Implementation Plan as an explicit constraint

Flag 2: Step 9 Adjustments Are Tone/Operations Only

• Revised: Adjustments in Step 9 can only touch:
  • Tone of the offer message (warmer, clearer, etc.)
  • Operational mechanics (timing of follow-ups, calendar settings, etc.)
  • Tracking clarity (better questions, clearer data capture)
• What CANNOT change:
  • The core call template (the "who will you contact first" conversation)
  • The 20-minute duration
  • The 72-hour window
  • The success threshold definitions
• Why: Changing the core mechanic mid-test confounds the results
• This goes into Step 9 as an explicit constraint

Flag 3: Step 15 Documentation Preserves Ambiguity

• Revised: If results land in 10-14% zone, Step 15 explicitly names the ambiguity
• What the documentation says:
  • "Results: X% conversion (10-14% range)"
  • "Interpretation: Meaningful movement from 6% baseline, but below directional signal threshold"
  • "What this means: The call appears to be moving something, but not enough to confirm the hypothesis cleanly"
  • "Decision: [Run longer to clarify, OR treat as 'call matters but insufficient' and pivot]"
  • NOT: "This worked, moving to next phase" (that's resolution, not honesty)
• Why: Ambiguous results are valuable learning, not failures. You need to see them clearly.
• This goes into Step 15 as an explicit instruction

---

Revised Implementation Plan (Locked)

Setup (Days 1-2):

• Step 1.5: Define Success Thresholds
• Step 1: Design Call Template
• Step 2: Set Up Tracking System
• Step 2.5: Define Follow-Up Protocol
• Step 3: Communicate the Offer
• Step 4: Integrate into Workflow

Phase 1: Launch & Learn (Weeks 1-2):

• Step 5: Begin Offering Calls
• Step 6: Conduct Calls and Take Notes
• Step 7: Track Outcomes in Real-Time
• Step 8: Look for Patterns Weekly
• Step 8.5: Midpoint Gut Check
• Constraint: Marketing paused during this window

Phase 2: Refine & Scale (Weeks 3-4):

• Step 9: Adjust Based on Learning (tone/operations only; core mechanic fixed)
• Step 10: Continue Offering Calls
• Step 11: Continue Tracking & Follow-Ups
• Step 12: Weekly Pattern Reviews

Phase 3: Evaluate & Decide (End of Week 4):

• Step 13: Analyze Final Results
• Step 14: Interpret Results Using Thresholds
• Step 15: Document Learning & Next Steps (preserving ambiguity if 10-14% zone)

Resource Requirements:

• Founder time: ~50-60 hours over 4 weeks (10-15 hrs/week on test)
• Marketing: Paused
• Tools: Calendly (free), spreadsheet/Notion (free)
• Product engineering: None

---

Ready to lock this in and move to Step 5: Monitoring & Validation?

Perfect. The implementation plan is solid and locked. Let me emit the updated document with the Implementation Plan section now.

---

Excellent. The Implementation Plan is now complete and locked in the document.

---

Ready for Step 5: Monitoring & Validation?

This is the final planning piece. We'll define:

• Success metrics — How you'll know the solution is working
• Validation approach — How you'll prove the call is actually moving conversion
• Risk mitigation — What could go wrong during implementation and how to prevent it
• Adjustment triggers — What signals should prompt a pause, pivot, or escalation

---

Energy Checkpoint

Almost there! We have got the solution selected and the implementation planned. This final planning piece — setting up metrics and validation — is what separates plans that succeed from plans that drift.

How is your energy for this?

---

Define Success Metrics

Let's start by defining concrete, measurable success metrics. We'll anchor to the success criteria from your problem framing and make them specific and trackable.

For each metric, we need:

• What are we measuring? (specific indicator)
• What target or threshold indicates success? (already defined in Step 1.5, but let's lock it here)
• How will we measure it? (data source, method)
• How often will we review it? (cadence)

Let me start with what's obvious, then we'll expand:

Primary Metric: Conversion Rate for Call-Takers

What we're measuring: Of the coaches who take a 20-minute call with you, what percentage contact their prospect and make a sale?

Target/threshold:

• 15%+ = Directional signal confirmed
• 10-14% = Ambiguous (meaningful movement but unclear)
• 6-9% = No meaningful movement
• Below 6% = Possible negative effect

How we measure it:

• Tracking doc: Coach takes call → Did they contact prospect? (day 3 follow-up) → Did they make a sale? (day 7+ follow-up)
• Data source: Your manual follow-ups + coach responses

Review cadence:

• Weekly during weeks 1-4 (Friday pattern review)
• Final calculation end of week 4

---

Secondary Metric: Call Booking Rate

What we're measuring: Of coaches who publish, what percentage book a call?

Target/threshold:

• High booking rate (50%+) = Coaches find the offer valuable
• Medium booking rate (25-50%) = Some interest, some resistance
• Low booking rate (below 25%) = Coaches don't want the call (signal about the intervention itself)

How we measure it:

• Tracking doc: Total publishers → Total who booked call
• Data source: Calendly booking data + your manual tracking

Review cadence:

• Weekly during weeks 1-4
• Final calculation end of week 4

Why this matters: If only 10% of coaches book the call, you've learned something important about whether they want this intervention at all. This is valuable learning even if it's "negative."

---

Tertiary Metric: Contact Rate (Coaches Who Reach Out)

What we're measuring: Of coaches who take the call, what percentage actually contact their prospect within 7 days?

Target/threshold:

• 70%+ = The call is moving them to action
• 40-70% = Some follow-through, some freeze remains
• Below 40% = The call isn't moving them to action (problem is deeper than accountability)

How we measure it:

• Tracking doc: Coach takes call → Did they contact prospect? (day 3 and day 7 follow-ups)
• Data source: Your follow-up messages + coach responses

Review cadence:

• Weekly during weeks 1-4
• Final calculation end of week 4

Why this matters: This is the intermediate step. Even if they don't make a sale, are they moving past the freeze? This tells you if the call is breaking the paralysis.

---

Quaternary Metric: Non-Booker Conversion Rate (Baseline Control)

What we're measuring: Of coaches who publish but DON'T book a call, what percentage convert?

Target/threshold:

• Should be close to 6% baseline (your current rate)
• If it's significantly lower, something about the offer is filtering out the people who would convert anyway
• If it's close to or higher than 6%, that's useful learning too

How we measure it:

• Tracking doc: Coaches who didn't book call → Did they contact prospect? → Did they make a sale?
• Data source: Your follow-up check-ins + coach responses

Review cadence:

• Weekly during weeks 1-4
• Final calculation end of week 4

Why this matters: This is your control group. It tells you if call-takers convert at a different rate than non-bookers, or if they're the same (which would mean motivation, not the call, is the variable).

---

Your Turn: Are These the Right Metrics?

Looking at these four metrics:

1. Conversion rate for call-takers — The primary outcome (does the call move conversion?)
2. Call booking rate — Signal about whether coaches want the intervention
3. Contact rate — Intermediate outcome (is the call breaking the freeze?)
4. Non-booker conversion rate — Control group (is it the call or motivation?)

Do these feel like the right things to track? Are there other metrics that matter to you? Think about:

• What would tell you the call is working?
• What would tell you it's not?
• What would you need to see to feel confident moving to the next phase (I in parallel)?
• What would tell you to pivot instead?

---

Locked in:

Success Metrics (4 total):

1. Conversion Rate for Call-Takers — Target: 15%+ (directional signal), 10-14% (ambiguous), 6-9% (no movement), below 6% (negative)
2. Call Booking Rate — Target: 50%+ (high interest), 25-50% (medium), below 25% (low interest)
3. Contact Rate — Target: 70%+ (moving to action), 40-70% (some follow-through), below 40% (call not breaking freeze)
4. Non-Booker Conversion Rate — Target: ~6% baseline (control group comparison)

---

Plan Validation Approach

Now let's design how you'll validate that the solution actually works. This is about the methodology for proving the call is the mechanism, not just luck or sample bias.

Validation Strategy

During Weeks 1-4 (The Test Window):

• You're collecting data continuously through tracking and follow-ups
• You're looking for patterns in real-time (Step 8 weekly reviews)
• You're checking your gut against the data (Step 8.5 midpoint check)

At End of Week 4 (The Validation Point):

• You calculate final metrics against thresholds
• You interpret results using the framework from Step 1.5
• You decide: Does the call work, or is the problem upstream?

The Validation Question: "Did coaches who took a 20-minute call with me contact their prospect and convert at a meaningfully higher rate than the 6% baseline?"

Evidence of Validation:

• If conversion rate ≥15%: Yes, the call works. The mechanism (accountability/presence) is proven.
• If conversion rate 10-14%: Maybe. Meaningful movement, but ambiguous. Run longer or treat as "not sufficient."
• If conversion rate 6-9%: No, the call didn't work. Problem is upstream.
• If conversion rate <6%: No, and possibly harmful. Stop immediately.

---

Validation Checkpoints During the Test

You also have earlier validation checkpoints:

Week 2 (Midpoint Gut Check - Step 8.5):

• Are coaches showing up for calls? (booking rate signal)
• Are they engaging during calls? (your subjective read)
• Do you feel like something is shifting, or are you forcing it?
• This is a "should we continue?" checkpoint, not a final validation

Week 4 (Final Validation - Steps 13-15):

• Calculate all four metrics
• Compare to thresholds
• Make the call: Does the hypothesis hold?

---

Identify Risks and Mitigation

Now let's think ahead about what could go wrong during implementation. I'll use a simple framework: What could go wrong? How do we prevent it? How do we detect it early? What do we do if it happens?

Let me identify the top risks, and you tell me if I'm missing any or if the mitigations feel right.

Risk 1: Sample Size Too Small to Reach Signal

What could go wrong: You only get 10-15 coaches in weeks 1-4 (low signup volume), so even if the call works, you don't have enough data to confirm it statistically.

Likelihood: Medium (you have 78 frozen coaches, but they're already in the product; new signups might be slower)

Impact: High (you can't validate the hypothesis and have to run longer, consuming more runway)

How to prevent it:

• Don't pause marketing entirely; reduce it but keep some growth flowing
• Adjust Step 1 constraint: "Marketing is paused" should be "Marketing is reduced to 5 hours/week minimum to maintain baseline signup volume"

How to detect early:

• By end of week 2, if you have fewer than 5 coaches who published, signup volume is too low
• This becomes a "adjust marketing" decision, not a test failure

What to do if it happens:

• Increase marketing effort slightly in weeks 3-4 to boost signups
• Extend the test window to week 6 to reach 20-30 coaches
• Document the extension and adjust your runway estimate

---

Risk 2: Coaches Ghost After the Call (No Follow-Up Response)

What could go wrong: Coaches take the call, seem engaged, but then don't respond to your day 3 and day 7 follow-ups. You can't tell if they contacted their prospect or not.

Likelihood: High (coaches are already freeze-prone; following up on their own actions is hard)

Impact: Medium (you lose data quality, but you can still track sales if they happen)

How to prevent it:

• During the call, ask them directly: "Can I check in with you in 3 days to see how it went?" Get explicit permission.
• Make follow-up messages short and easy to respond to: "Did you reach out to [person]? Just curious—no pressure."
• Offer multiple ways to respond: text, email, quick voice note

How to detect early:

• By end of week 1, if you're getting 0% response rate to follow-ups, ghosting is a problem
• This is a data quality issue, not a test failure

What to do if it happens:

• Adjust follow-up approach in Step 9: shorter messages, different timing, different channels
• Accept that some data will be incomplete and note it in your final analysis
• Track what you can see (sales that happen) and note the data gaps

---

Risk 3: You Unconsciously Coach Differently Based on Your Expectations

What could go wrong: In week 1, you're excited about the test. In week 3, if early results look flat, you unconsciously change how you're running the call (pushing harder, giving different advice, following up more aggressively). This confounds the test.

Likelihood: High (you're human; unconscious bias is real)

Impact: High (you lose the ability to interpret results cleanly)

How to prevent it:

• Write the call template in Step 1 and commit to it unchanged
• Record yourself doing one call in week 1 and listen back to it—notice your tone, pacing, questions
• In Step 9, explicitly constrain adjustments to "tone/operations only"—the core template stays fixed
• Have a rule: if you notice yourself deviating from the template, pause and reset

How to detect early:

• During Step 8 weekly reviews, compare your notes from call 1 vs. call 10—are they consistent?
• Ask yourself: "Am I running the same conversation with everyone, or am I improvising?"

What to do if it happens:

• Document the deviation explicitly in Step 15: "I noticed I was pushing harder in weeks 3-4. This may have confounded the results."
• Note it as a limitation of the test, not a failure
• Use this learning for the next test (I in parallel) to be more disciplined

---

Risk 4: Marketing Pause Backfires (Signups Drop, Runway Pressure Spikes)

What could go wrong: You pause marketing for 4 weeks. Signups drop. Runway pressure spikes. You abandon the test early to restart growth work.

Likelihood: Medium (depends on your current growth rate and runway cushion)

Impact: High (you don't finish the test and lose the learning)

How to prevent it:

• Adjust the constraint: Marketing is "reduced" not "paused" (5 hours/week minimum to maintain baseline)
• Calculate in advance: "What's the minimum signup volume I need to keep runway healthy?" and set that as your floor
• Front-load any high-ROI growth work before week 1 starts, so you have momentum going in
• Set a rule: "If runway drops below 6 months, I restart marketing immediately—no exceptions"

How to detect early:

• Track signup volume weekly (Step 8 weekly reviews)
• If week 1 signups drop 50%+ from baseline, adjust immediately
• Don't wait until week 3 to notice

What to do if it happens:

• Increase marketing effort back to normal
• Accept that the test window is shorter than planned
• Analyze what you have (even if it's only 10 coaches) and make a decision based on partial data
• Document: "Test was cut short due to runway pressure. Results are based on [N] coaches, below target sample size."

---

Risk 5: Coaches Interpret the Call as Sales Pressure (Not Support)

What could go wrong: Some coaches feel like you're pushing them to sell, not supporting them. They resent the call and are less likely to share (negative effect).

Likelihood: Low-Medium (depends on your tone and framing)

Impact: Medium (you learn something important about positioning, but you might get below-6% conversion)

How to prevent it:

• In Step 3, craft the offer message carefully: "help you think through your first outreach" not "help you sell"
• During the call, ask permission-seeking questions: "Can I share what I'd do?" not "Here's what you need to do"
• Make it clear: "This is optional. If you don't want to chat, no pressure."
• During Step 9 adjustments, if you're getting feedback that the call feels pushy, adjust the tone

How to detect early:

• During calls, notice if coaches seem defensive or resistant
• In your notes, capture: "How did this coach feel about the call?" (welcomed it, tolerated it, resented it?)
• If 50%+ of coaches seem to resent it, this is a signal

What to do if it happens:

• Adjust the tone/framing in Step 9
• If the problem is structural (the call itself feels like sales pressure), this is a learning: "The intervention backfired. Coaches don't want founder presence; they want something else."
• Document this in Step 15 as a key finding

---

Risk 6: You Burn Out (10-15 hrs/week + normal work = unsustainable)

What could go wrong: By week 3, you're exhausted. The calls feel like a burden, not an experiment. Your energy drops, your tone changes, the test gets confounded by burnout.

Likelihood: Medium-High (solo founder, tight runway, multiple priorities)

Impact: Medium (test quality degrades, you might abandon it)

How to prevent it:

• Go into this with eyes open: 10-15 hours/week is real time
• Protect it fiercely: block it on your calendar, don't let other work creep in
• Take breaks: don't do more than 3 calls in a row without a break
• Check in with yourself weekly: "Am I sustainable? Do I need to adjust?"
• If you hit the wall, it's better to pause the test than to push through burned out

How to detect early:

• During Step 8.5 midpoint gut check, explicitly ask: "Am I burned out? Is this sustainable?"
• If the answer is yes, adjust immediately in Step 9

What to do if it happens:

• Reduce call volume (offer to fewer coaches, or extend the test window)
• Pause the test if needed and restart when you have capacity
• Document: "Test was paused due to founder capacity. Restarting in [timeframe]."

---

Your Turn: Risks and Mitigations

I've identified 6 major risks. Do these feel like the right risks to watch for? Are there others that worry you more?

And for each one: Do the prevention and detection strategies feel realistic? Or do you need to adjust them?

---

Locked in with adjustments:

Risk 1 Mitigation (Concrete):

• Marketing reduced (not paused) during weeks 1-4
• Keep Reddit posts going at half cadence (proven channel)
• Pause all other experimental growth work
• Minimum signup volume maintained to keep runway healthy

Risk 3 Mitigation (Stricter):

• Write call template in Step 1 and commit to it unchanged
• After call 5 and call 15: re-read the template and compare to what you actually did in the last 3 calls
• If drift is detected, reset before the next call
• This catches drift faster than weekly review and keeps the core mechanic clean

---

Define Adjustment Triggers

Now let's define clear triggers that would prompt a change in approach. These are specific, observable conditions that tell you to pause, adjust, or pivot.

Trigger 1: Booking Rate Below 25%

What it means: Fewer than 1 in 4 coaches who publish are booking the call. They don't want this intervention.

What to do:

• Pause and review: Is the offer message unclear? Is the timing wrong? Is the call itself the problem?
• Adjust offer messaging in Step 9 (tone, framing, clarity)
• If booking rate stays below 25% after adjustment, consider: maybe coaches don't want founder presence. Move to testing I (Self-Selected) or G (Warm Prospect Validator) instead.

---

Trigger 2: Contact Rate Below 40% (Coaches Not Following Through)

What it means: Even coaches who take the call aren't contacting their prospect. The call isn't breaking the freeze.

What to do:

• Pause and analyze: What's happening on the calls? Are coaches committing to contact? Are they ghosting after?
• Review your notes from calls—what are coaches saying about why they're frozen?
• Adjust the call in Step 9: Maybe the "who will you contact" question needs different framing. Maybe you need to get explicit commitment on the call itself.
• If contact rate stays below 40% after adjustment, this is a signal: "Even accountability isn't moving them to action. Problem is deeper (imposter syndrome, moral weight)."

---

Trigger 3: Conversion Rate Below 6% (Call Making Things Worse)

What it means: Call-takers are converting at the same rate or lower than the baseline. The intervention is neutral or negative.

What to do:

• Stop offering the call immediately
• Analyze: What went wrong? Are coaches resenting the call? Are you pushing too hard?
• Document findings and pivot to next hypothesis (G, I, or upstream repositioning)

---

Trigger 4: Burnout Signal (You Hit the Wall)

What it means: During Step 8.5 gut check or any weekly review, you notice you're exhausted, the calls feel like a burden, your energy is gone.

What to do:

• Pause the test immediately
• Reduce call volume or take a week off
• Restart when you have capacity
• Document the pause and adjust runway estimate
• Better to pause than to push through burned out (which confounds the test anyway)

---

Trigger 5: Signup Volume Drops 50%+ (Runway Pressure)

What it means: Marketing reduction is working too well. Signups are down significantly. Runway pressure is spiking.

What to do:

• Increase marketing effort back to normal immediately
• Accept that the test window is shorter than planned
• Analyze what you have (even if it's only 10-15 coaches)
• Document: "Test was cut short due to runway pressure. Results based on [N] coaches."

---

Trigger 6: Midpoint Gut Check (Week 2) Says "This Isn't Working"

What it means: After 10-15 calls, your gut says something is off, even if early numbers look okay.

What to do:

• Name the tension explicitly in Step 8.5 documentation
• Decide: Do you want to continue, adjust, or pivot?
• This is a "pause and think" moment, not an automatic stop
• But trust your gut—if something feels wrong, it probably is

---

Trigger 7: Ambiguous Results (10-14% Conversion Rate)

What it means: Meaningful movement from 6%, but below directional signal threshold. The answer is unclear.

What to do:

• This is explicitly addressed in Step 1.5 interpretation framework
• Decision options:
  • Run longer: Extend test to week 6 to reach 30-40 coaches for clearer signal
  • Run I in parallel: Test self-selection immediately to see if motivation is the variable
  • Treat as "not sufficient": Accept that the call moves conversion, but not enough to be the core solution. Pivot to repositioning or segment focus.
• Document the ambiguity explicitly—don't resolve it quietly into "it worked"

---

Your Turn: Adjustment Triggers

Looking at these 7 triggers:

1. Booking rate <25% — Coaches don't want the intervention
2. Contact rate <40% — Call isn't breaking the freeze
3. Conversion <6% — Call making things worse
4. Burnout signal — You hit the wall
5. Signup drop 50%+ — Runway pressure
6. Gut check says no — Your intuition at week 2
7. Ambiguous results (10-14%) — Unclear answer

Do these feel like the right triggers? Are there other conditions that would make you pause or pivot?

And for each one: Do the "what to do" responses feel right? Or would you adjust them?

---

Perfect. You're protecting against the assumption that low booking = messaging problem. It might be that coaches just don't want founder presence, period.

Trigger 1 Revised:

What it means: Fewer than 1 in 4 coaches who publish are booking the call. They don't want this intervention (or don't want it as framed).

What to do:

• Pause and diagnose before adjusting
• Reach out to 3-5 coaches who didn't book and ask directly: "I offered a 20-minute call. You didn't book. Curious—what would have made you want to take it?" or "What made you skip it?"
• Listen to their answers—are they saying:
  • "I didn't have time" (messaging/timing problem → adjust offer)
  • "I didn't want to talk to the founder" (intervention problem → pivot to I, G, or different approach)
  • "I wasn't sure what it was for" (messaging clarity problem → adjust offer)
  • "I felt like you were pushing me to sell" (tone problem → adjust offer)
• Based on what you learn, decide:
  • If it's a messaging/framing issue: Adjust offer in Step 9
  • If it's "don't want founder presence": Pivot to testing I (Self-Selected) or G (Warm Prospect Validator) instead
• If booking rate stays below 25% after adjustment, this is a signal to pivot

---

Locked in:

Adjustment Triggers (7 total):

1. Booking rate <25% — Diagnose first (ask non-bookers why), then adjust messaging OR pivot
2. Contact rate <40% — Call isn't breaking the freeze; adjust call template or pivot
3. Conversion <6% — Call making things worse; stop immediately and pivot
4. Burnout signal — You hit the wall; pause or reduce volume
5. Signup drop 50%+ — Runway pressure; increase marketing immediately
6. Gut check says no (Week 2) — Trust your intuition; decide to continue, adjust, or pivot
7. Ambiguous results (10-14%) — Run longer, run I in parallel, or treat as "not sufficient"

---

Validate the Monitoring Plan

Let me present the complete monitoring and validation plan back to you:

Success Metrics:

• Conversion rate for call-takers (target: 15%+)
• Call booking rate (target: 50%+)
• Contact rate (target: 70%+)
• Non-booker conversion rate (control: ~6%)

Validation Approach:

• Continuous tracking during weeks 1-4
• Weekly pattern reviews (Step 8)
• Midpoint gut check (Step 8.5)
• Final metrics calculation and interpretation (Steps 13-15)
• Decision: Does the call work, or is the problem upstream?

Risk Mitigation (6 risks):

• Sample size too small → Keep Reddit marketing at half cadence
• Coaches ghost → Get explicit permission for follow-ups, adjust messaging
• Unconscious coaching drift → Reset template after calls 5 and 15
• Marketing pause backfires → Reduce (not pause), maintain baseline
• Call feels like sales pressure → Careful tone in offer and on calls
• Burnout → Monitor weekly, pause if needed

Adjustment Triggers (7 triggers):

• Booking <25% → Diagnose first, then adjust or pivot
• Contact <40% → Adjust call or pivot
• Conversion <6% → Stop and pivot
• Burnout → Pause or reduce
• Signup drop 50%+ → Restart marketing
• Gut says no → Decide to continue/adjust/pivot
• Ambiguous results → Run longer, run I parallel, or treat as insufficient

Does this give you confidence that you'll know early whether the solution is working and have clear guidance on what to do if it's not?

---

Perfect. You've got a clear, concrete monitoring framework with decision rules built in. This is exactly what separates plans that drift from plans that execute.

Let me emit the Monitoring & Validation section now.

---

Excellent. The Monitoring & Validation section is now complete and locked in the document.

---

Ready for Step 6: Lessons Learned & Completion?

This is the final step. We'll do a brief reflection on the problem-solving process itself (optional), and then wrap up with a completion summary and next steps.

---

Perfect. You've got everything you need.

Let me present the completion summary:

---

Framed Problem Solving Complete!

What you have:

A complete solution plan covering:

• Solution Generation — 10 solutions generated using Assumption Busting, Lateral Thinking Techniques, and Morphological Analysis
• Solution Evaluation — Evaluated across 9 criteria (4 high weight, 3 medium weight, 2 low weight), recommended: Solution H (Pure Founder Service Test) with 118/160 weighted score
• Implementation Plan — Phased rollout (weeks 1-4) with 15 concrete action steps, clear ownership, resource requirements, and explicit constraints (marketing reduced, core mechanic fixed, ambiguity preserved)
• Monitoring & Validation — 4 success metrics, 7 adjustment triggers, 6 risk mitigations, and a validation approach that tells you early whether the hypothesis holds

Recommended next steps:

1. Lock in the thresholds and triggers — Before week 1 starts, write down the success thresholds (Step 1.5) and adjustment triggers somewhere you won't change them. This prevents goalpost-moving.

2. Complete the setup — Days 1-2: Design call template, set up tracking, define follow-up protocol, integrate into workflow. These are your foundation.

3. Begin Phase 1 — Start offering calls to all coaches who publish. Track everything. Week 2 is your gut check moment.

4. Make Phase 2 adjustments — Based on week 2 learning, refine tone/operations (not core mechanic). Keep Reddit marketing at half cadence.

5. Analyze and decide — End of week 4: Calculate metrics, interpret against thresholds, decide next step (run I in parallel, or pivot).

6. Document honestly — Whatever the results, preserve the ambiguity if it exists. This learning is valuable either way.

---

You're ready. Go run the test.