# Podcast Episode Outline ## How Early-Stage Startups Should Think About Pricing Before They Have Enough Data to A/B Test — Guest Name Not Provided (Returning Guest) --- ### CARD 1 — EXECUTIVE SUMMARY **Strongest hook available:** Most early-stage B2B SaaS founders don't have the traffic or paying-customer volume to run a real A/B test on pricing — yet they still have to set a number and defend it. This guest has spent her career on exactly that gap: as a consultant across 40+ B2B SaaS startups, and earlier as the person inside a mid-market SaaS company who personally drove pricing through 3 major model changes (PROVIDED). That combination — outside pattern-recognition plus inside accountability — is a strong premise for a low-data pricing episode. **What's missing to fully prep this episode:** - Guest name was not included in the brief (NEEDS GUEST DETAILS) — needed for intro, title, and show notes. - The brief describes her client base as "40+ B2B SaaS startups" and her in-house work as being at "a mid-market SaaS company" (PROVIDED), but does not specify that either experience set was specifically pre-Series A or specifically about pricing *before* sufficient data existed to test. Per Rule 6: the episode topic (pricing under data scarcity, pre-Series A stage) is narrower than what the guest info confirms she's worked on. This is a gap, not a disqualifier — her breadth of experience makes it plausible she's dealt with this directly — but it should be confirmed with the guest before recording rather than assumed in the questions (SUGGESTED: confirm in pre-call). - No detail on what was covered in her first appearance, so no callback content can be written; a callback question can only gesture at "you've been on before," not reference specific prior material (constraint per Rule 4). --- ### CARD 2 — EPISODE ARC **Cold Open (0:00–2:30) — SUGGESTED** Open on the core tension: founders are told to "test your pricing" but don't have the traffic to make an A/B test statistically meaningful. Tease that today's returning guest has run pricing through 3 major changes from the inside, plus 40+ outside engagements, and knows what to do when you can't just run the experiment. **Context Setting (2:30–8:00) — SUGGESTED** Quick re-introduction for a returning guest: her current work as a pricing consultant to B2B SaaS startups (PROVIDED), and briefly, her prior in-house role leading pricing strategy through 3 major changes (PROVIDED). Frame why pre-data pricing is a distinct problem from post-PMF pricing optimization. **Core Discussion — Segment A: Diagnosing the problem (8:00–18:00) — SUGGESTED** What actually goes wrong when technical, pre-Series A founders set price with no data. Patterns she's seen repeat across her 40+ engagements (PROVIDED anchor, SUGGESTED framing). **Core Discussion — Segment B: What to use instead of A/B data (18:00–30:00) — SUGGESTED** *Pacing note:* this segment risks getting jargon-heavy fast (pricing-model terminology, GTM shorthand) for an audience described as technical but with limited pricing/GTM experience (PROVIDED audience context). Host should ask the guest to anchor each concept in a plain example before naming it, and periodically translate jargon back into founder-facing terms. This addresses the MODERATE-HIGH Listener Retention Risk Index (OPERATIONAL EXTENSION — NOT A GUARANTEED AUDIENCE-BEHAVIOR PREDICTION) flagged for this segment in Card 4. **Core Discussion — Segment C: Lessons from running 3 pricing changes from the inside (30:00–38:00) — SUGGESTED** Draws directly on the one concrete, specific credential in the brief: 3 major pricing model changes led at a mid-market SaaS company (PROVIDED). Good place for war-story specificity after the more conceptual Segment B. **Takeaway / CTA (38:00–45:00) — SUGGESTED** One or two concrete "do this before your next pricing conversation" takeaways; plug guest's consulting work (PROVIDED that she consults; no contact details provided, so CTA stays generic unless supplied). --- ### CARD 3 — QUESTION BANK | Segment | Question | Why It's Interesting | |---|---|---| | Context Setting | "Welcome back — for anyone who missed your first appearance, what's the one-line version of what you do?" | Acknowledges returning-guest status (PROVIDED) without inventing content from the earlier episode. | | Segment A | "Across the 40+ B2B SaaS startups you've worked with, what's the pricing mistake you see founders make most often before they have any real usage data?" | Directly tied to her stated consulting scope (PROVIDED). | | Segment A | "How do you tell a founder their pricing intuition is wrong when neither of you has the data to prove it yet?" | Ties the episode's core tension (no A/B data) to her role as an outside consultant (PROVIDED). | | Segment B | "If A/B testing isn't an option yet, what do you actually tell founders to do instead?" | Direct topic question, framed as open rather than presupposing a specific named framework she wasn't stated to use. | | Segment B | "How does that advice change for a technical founder who's never run a pricing or GTM motion before?" | Ties question depth to the stated audience (pre-Series A, technical, limited pricing/GTM experience — PROVIDED audience context), without claiming the guest has specifically worked with that exact segment. | | Segment C | "You led 3 major pricing model changes at your last company — what triggered each one, and what would you do differently knowing what you know now?" | Directly tied to her single most specific stated credential (PROVIDED). | | Segment C | "What's different about making a pricing call when you're the one who has to live with it internally, versus advising a founder from the outside?" | Contrasts her two stated roles — in-house and consultant (PROVIDED) — a genuine structural question, not an invented claim. | | Takeaway/CTA | "If a founder listening today only does one thing differently with their pricing this quarter, what should it be?" | Standard, low-risk closer; SUGGESTED, not tied to a specific credential. | --- ### CARD 4 — SEGMENT DIAGNOSTIC | Factor | Score | Status | Rationale | |---|---|---|---| | Hook Strength | 4/5 | Strong | "You don't have enough data to A/B test, but you still have to price" is an immediately recognizable pain point for the stated audience (pre-Series A, technical founders — PROVIDED). | | Topic Depth | 4/5 | Strong | Narrow and concrete enough to sustain 45 minutes, and the guest has one specific credential (3 pricing model changes — PROVIDED) that can anchor a full segment. | | Guest Relevance Fit | 3/5 | Moderate | Her stated experience (40+ B2B SaaS startups, in-house pricing lead — PROVIDED) plausibly covers this topic, but the brief doesn't confirm the client base skewed early-stage or that her in-house changes happened under pre-data conditions specifically. Flagged in Card 1 per Rule 6; SUGGESTED to confirm pre-call rather than assume in questions. | | Listener Retention Risk Index (OPERATIONAL EXTENSION — NOT A GUARANTEED AUDIENCE-BEHAVIOR PREDICTION) | MODERATE-HIGH (Segment B) / LOW (elsewhere) | Flagged | Segment B (frameworks for pricing without data) is the point most likely to drift into jargon for an audience described as having limited pricing/GTM experience (PROVIDED). Addressed with the pacing note in Card 2's Segment B. | **Core Pacing Reading:** The arc's structural risk is concentrated entirely in one segment (B), and it's a segment the show can control for with a pacing instruction rather than a content problem — the underlying material (Segment A's diagnostic patterns, Segment C's concrete war stories) is naturally accessible to the stated audience. The bigger open risk isn't pacing, it's the Guest Relevance Fit question in Card 1: the episode's premise is narrower (pre-Series A, no-data-yet) than what's confirmed about the guest's experience. --- ### CARD 5 — SHOW NOTES DRAFT **Summary (SUGGESTED draft, facts PROVIDED only):** A pricing consultant who's worked with 40+ B2B SaaS startups — and who previously led pricing strategy in-house through 3 major pricing model changes — returns to the show to talk about how early-stage founders should approach pricing before they have enough traffic or customers to run a real A/B test. **Timestamped highlights (SUGGESTED, based on Card 2 arc):** - 00:00 — Cold open: the pre-data pricing problem - 02:30 — Who our guest is (returning guest) - 08:00 — The most common pre-data pricing mistakes - 18:00 — What to use instead of A/B tests - 30:00 — Inside story: leading 3 pricing model changes - 38:00 — Takeaways for founders **Guest bio (PROVIDED facts only):** Our guest is a pricing consultant who has worked with more than 40 B2B SaaS startups. Before consulting, she led pricing strategy in-house at a mid-market SaaS company, taking the business through 3 major pricing model changes. This is her second appearance on the show. [Name and links: UNKNOWN — not supplied] **Links:** — (placeholder; add guest's site/consulting page and prior-episode link once available) --- ### CARD 6 — TITLE & THUMBNAIL TEXT OPTIONS 1. "Pricing With Zero Data: What Early Founders Get Wrong" 2. "You Can't A/B Test Your Way Out of This" 3. "3 Pricing Overhauls Later: What She'd Tell Pre-Series A Founders" 4. "How to Price Before You Have the Data" 5. "The Pricing Advice Nobody Gives Pre-Revenue Founders" --- ### CARD 7 — AUDIENCE FIT NOTE Audience context was given: early-stage B2B SaaS founders, mostly pre-Series A, technical background, limited pricing/GTM experience (PROVIDED). Question depth was calibrated to assume real product and engineering fluency but no assumed familiarity with pricing-model or GTM terminology — Segment B in particular is built to require the guest to define terms plainly before using them (see Card 2 pacing note). Questions avoid presupposing prior exposure to pricing frameworks and instead ask the guest to explain from first principles what a founder with no GTM background should actually do. --- ### CARD 8 — PROMOTION SNIPPET "You don't have enough users to A/B test your pricing. So what do you do instead? Our guest has led 3 pricing overhauls from the inside and advised 40+ B2B SaaS startups from the outside — she's back on the show to walk through exactly that. 🎧 New episode out [date]." --- ### CARD 9 — METHOD NOTE This outline is a preparation aid for the host, not a finished script — the guest should be allowed to take segments in directions the outline doesn't anticipate, and the host should feel free to drop or reorder questions live. It's built on the Episode Arc Framework (Cold Open, Context Setting, Core Discussion, Takeaway/CTA), extended with a Listener Retention Risk Index (OPERATIONAL EXTENSION — NOT A GUARANTEED AUDIENCE-BEHAVIOR PREDICTION) — a structural pacing heuristic based on where the outline's own content gets denser or more jargon-heavy, not a measurement of how this specific audience will actually behave. Because audience context was supplied (pre-Series A, technical, limited pricing/GTM experience), question depth and Segment B's pacing note were both calibrated toward plain-language explanation over framework jargon. As with any outline, the host should treat this as a scaffold: adapt it in real time based on where the conversation naturally goes, especially if the guest's actual pre-Series-A experience turns out to be thinner or richer than the brief suggests. --- **VERDICT: NEEDS GUEST DETAILS — the outline is structurally ready to run, but the guest's name is missing and her experience with early-stage, pre-data pricing specifically (versus B2B SaaS pricing generally) hasn't been confirmed; both should be resolved with the guest before recording.**