Case files · 5 programs · example data

Five programs, start to signed.

One program per file: who was invited, what changed at the review, what closed. Anonymized examples, tagged until client-approved results replace them.

Start the engine →See the pipeline math
case.index / 5 filesExample data
source: client CRM · counting rules on the results wall

B2B podcast case studies, start to signed.

These five B2B podcast case studies are illustrative examples across SaaS, devtools, fintech, consulting and fundraising, each showing the program, the guest profile and how conversations became pipeline.

// filter by market

showing 5 of 5 files

case_file / cf-01 · series a · b2b data platform saasEngineExample data

24 episodes. $1.4M in pipeline.

Thirteen weeks after go-live, conversations with heads of data had put $1.4M into the CRM.

situation

Series A, 40 people, data-quality software. Two SDRs, 6,000 cold emails a month, under 2% replies. The founder’s calls converted; there weren’t enough of them.

program

Engine · $6,900 / mo. Two ICP segments, run side by side.

80 invite mailboxes · 5 clips + quote cards per episode · CRM handoff to both SDRs · bi-weekly strategy call.

guest profile

titlesHead of Data · VP AnalyticssegmentsA: marketplaces · B: vertical SaaStriggernew data leader hired in the last 6 months

timeline

  1. days 1–5 · brief

    Show and segments locked

  2. day 18 · go live

    First invitations

    Under the founder’s name, ramping weekly.

  3. day 25 · first recording

    Episode 1

    A VP Analytics whose pre-interview flagged a warehouse migration this half.

  4. day 60 · review

    Segment B rewritten

  5. week 13 · quarter close

    $1.4M in the CRM

    24 recorded, 8 opportunities, ~2 host hours a week.

what worked

  • Trigger lists: new data leaders like discussing their stack on the record.
  • Question 5, “whose phone rings first?”, named the economic buyer early.

what we changed

Segment B’s invitations led with the company and lagged segment A. From day 60 they led with the episode topic: a new data leader’s first 90 days. Acceptance caught up within a month.

Placeholder testimonial
We stopped asking for meetings and started asking for interviews. Our calendar changed in three weeks.
Founder & CEO, Series A data platform
↑ Market filter
case_file / cf-02 · seed · devtools devtoolsPilotExample data

11 design partners from 18 episodes.

CTOs who ignored sales email said yes to an interview.

situation

Seed stage, 9 people, test infrastructure in private beta. Needed 10 design partners before v1 and had 3.

program

Pilot · $3,900 / mo + $1,500 setup. One segment: engineering leaders.

40 invite mailboxes · pre-interviews · 3 clips per episode · weekly report.

guest profile

titlesCTO · VP Engineering · Head of PlatformcompanySeries A–C software, 20–150 engineerssignalhiring platform or developer-experience engineers

timeline

  1. days 1–5 · brief

    One segment: how teams ship

  2. day 18 · go live

    First invitations

    To 300 engineering leaders, under the co-founder’s name.

  3. day 25 · first recording

    CTO, Series B fintech

    Asked what the team was building before the recording ended.

  4. week 6 · first paid pilot

    Signed before air date

    An episode-3 guest, episode still in edit.

  5. month 4 · 18 episodes

    11 design partners

    Pilot target of 4–6 recorded guests met from month 2.

what worked

  • Asking about the build, not the product. CTOs talk freely about what slows them.
  • The pre-interview flagged teams mid-migration. Those signed fastest.

what we changed

VP Engineering guests said yes, then went quiet before the pre-interview. At day 60 we replaced three scheduling emails with one booking link. The drop-off closed.

Placeholder testimonial
I got 30 minutes with CTOs who’d ignored six of our sales emails.
Co-founder, devtools startup
↑ Market filter

Reading for your own market? Run your ACV through the model these files use.

See the pipeline mathStart the engine →
case_file / cf-03 · series b · fintech infrastructure fintechNetwork + Closing DeskExample data

$420k closed. 38-day cycles.

A 94-day cycle cut to 38 by recorded conversations and a closer who owned every handoff.

situation

Series B payments and ledger infrastructure. Long security reviews, a 94-day average cycle, and compliance sign-off on anything published.

program

Network · $11,500 / mo plus Closing Desk · $2,500 / mo + 8% of first-year value on deals it closes. Roundtables included.

guest profile

titlesCFO · VP Finance · Head of Paymentscompaniesmarketplaces · vertical SaaS · lenderscomplianceepisodes and clips approved before publishing

timeline

  1. days 1–17 · brief + warm

    Legal signed off first

    Review workflow approved before the first invitation.

  2. day 18 · go live

    Invitations under the CEO’s name

    Three segments, ramping weekly.

  3. day 60 · review

    CFOs moved to roundtables

  4. month 4 · 40 guests

    13 opportunities

    Each at the desk within 24 hours, notes attached.

  5. month 5 · 3 signed

    $420k first-year value

    38-day average cycle, handoff to signature.

what worked

  • Pre-interview notes became the desk’s deal brief. First calls started at pricing.
  • The CEO kept the relationship; the desk ran the paperwork.

what we changed

CFOs kept moving their dates. At day 60 they moved to a monthly roundtable, three CFOs to a table. Reschedules dropped. A roundtable guest signed the largest deal.

Placeholder testimonial
The pre-interview notes were better than our discovery calls.
VP Sales, fintech infrastructure
↑ Market filter

Three files, three markets, one method. Yours starts with a brief on day 1; invitations go live on day 18.

Start the engine →See pricing
case_file / cf-04 · 30-person b2b consultancy servicesPilot → EngineExample data

$610k booked. 9 referrals.

Warm intros on a schedule. Past guests introduced peers, and one roundtable special produced two retainers.

situation

30 people, RevOps consulting for PE-backed software. Every client came through a partner’s network, so growth stalled when their calendars filled.

program

Pilot · $3,900 / mo + $1,500 setup. Engine from day 84, inside the 90-day window, so setup was credited.

guest profile

titlesCRO · VP Revenue OperationscompaniesPE-backed B2B software, $20–100M revenuesegment 2operating partners at growth-equity firms

timeline

  1. day 18 · go live

    One segment, one host

    CROs, invited under the managing partner’s name.

  2. month 2 · first project

    Booked before air date

    An episode-2 guest asked for a pipeline audit.

  3. month 3 · roundtable special

    Three past guests, one table

    A one-off episode on board-level forecasting. Two signed retainers.

  4. day 84 · upgrade

    Engine, segment 2 live

  5. month 6 · cohort closed

    $610k booked

    Episodes 1–16. 9 referrals, each tagged to its guest.

what worked

  • Hosting gave the managing partner a reason to call CROs who avoid consultancies.
  • Every episode ended on one question: who else should be on the show?

what we changed

Early invitations offered “a conversation about RevOps” and got general conversations. From month 2 each invitation named one board-reporting problem the guest’s company likely had. Pre-interview scores rose.

Placeholder testimonial
Past guests keep introducing us to their peers. That never happened with outbound.
Managing Partner, B2B consultancy
↑ Market filter
case_file / cf-05 · pre-seed ai founder fundraisingLaunch Sprint + Host CoachingExample data

27 investors hosted. Round filled in 7 weeks.

The founder hosted investors instead of pitching them. Same engine, different guest list.

situation

Pre-seed, two founders, applied AI with early usage and no investor network. Cold decks got form replies.

program

Launch Sprint · $4,500 once, 14 days, then Host Coaching · $1,800 / mo. Every invitation went out under the founder’s name, sent by the founder’s team.

guest profile

titlespartners at pre-seed and seed funds · operator angelscheck size$250k–$2Msignalled an applied-AI round in the last 12 months

timeline

  1. days 1–5 · brief

    Buyers swapped for investors

    Criteria: thesis, stage, check size.

  2. day 14 · handover

    Founder takes the controls

    Sprint delivered. Host Coaching starts.

  3. day 18 · go live

    First invitations

    From the 30 mailboxes the sprint warmed.

  4. day 25 · first recording

    Week 1 of 7

    The hosted count starts here.

  5. day 32 · first coaching call

    Invitation rewritten

  6. day 74 · 7 weeks in

    Round filled

    27 investors hosted, 4 term sheets.

what worked

  • Investors came to talk about the market. Several asked for the deck.
  • Pre-interviews screened for thesis fit, so hours went to funds that could lead.

what we changed

Line two of the first sequence mentioned the raise, so investors read a pitch. The first coaching call cut the round from the invitations and from the recordings. Investors asked about the company after the recording, off air.

Placeholder testimonial
I hosted investors instead of pitching them. The round closed in seven weeks.
Founder, AI startup
↑ Market filter
// patterns

What the five files have in common.

Different markets and tiers. Four constants.

Example data
[01]review

One change, not a rebuild

One fix at the first review: an angle, a format, a booking step.

in: review → out: one fix
[02]timing

Deals before air dates

CF-02’s first pilot and CF-04’s first project, both booked with the episode still in edit.

in: episode → out: deal
[03]host time

The host’s week stayed small

In CF-01 to CF-04, research, invitations, pre-interviews and edits ran without the host.

in: ~2 hrs/wk → out: 4–16 / mo
[04]reporting

Counted in the CRM

Recorded guests, opportunities, signed contracts. No download counts. How we count →

in: CRM → out: weekly report
Start the engine →Check your fitRun the numbers →
case_file / cf-06 · yours

Your file starts on day 1.

Apply with your ICP, ACV and host. A producer replies within one business day; a guest forecast follows within 72 hours of a fit call.

Start the engine →See pricing