Each program runs on a pod: a producer, a guest researcher, a deliverability specialist and an editor. A strategy lead sets the targets. The Closing Desk joins if you add it. You get a named owner for every step and a report every Friday.
Each show gets a B2B podcast production team of four: a producer, a guest researcher, a deliverability lead and an editor, working to one weekly pipeline report.
Every seat maps to a step of the engine and a line on your report. Before you sign, you get the names of the pod that would run your show.
[Name] Placeholder bio
Sets the targets on every program: runs the ICP workshop in days 1–5, signs off the guest criteria before a single invitation goes out, and leads the day-60 pipeline review.
[Name] Placeholder bio
Leads the producer bench and sets how many shows each producer carries. Your pod's producer is your day-to-day contact: runs the 15-minute pre-interview with every accepted guest, scores fit, writes the brief you read before recording, and sits in the producer chair on every call.
[Name] Placeholder bio
Sets the research method and the trigger events we watch. The researcher on your show builds your list from title, stage, funding, niche and trigger events: the first 300 names during warm-up, days 6–17, each with a reason to invite them now.
[Name] Placeholder bio
Sets the sending rules every program runs on. Your pod's deliverability specialist sets up separate invitation domains and 40, 80 or 150 mailboxes by tier, runs the warm-up and checks inbox health daily. Your main domain never sends an invitation.
[Name] Placeholder bio
Runs the desk and its closers. On Engine or Network programs with the Closing Desk, a senior closer takes qualified guest conversations from CRM handoff to signed: follow-up calls, proposals, negotiation support, a weekly deal review.
[Name] Placeholder bio
Sets the edit and clip standard across shows. Your editor cuts every episode and its clips: 3 per episode on Pilot, 5 plus quote cards on Engine and Network. Guests approve their clips before anything is posted.
Four people work your show every week. Strategy and the Closing Desk plug in at fixed points. One shared channel, one Friday report, one owner per step.
The researcher and the deliverability specialist run the top of the funnel: who gets invited, from which mailbox, at what daily volume. The producer and the editor run the bottom: who gets recorded, what the brief says, what ships and when.
On Pilot and Engine, your producer runs a small, fixed number of shows, so pre-interviews and briefs never queue behind a bigger client. On Network, the producer works on your program only.
You talk to the person doing the work. A question about a guest goes to the producer. A question about a mailbox goes to the deliverability specialist. Nobody relays it. How that compares with an agency retainer: why not an agency.
| step | pod owner | your part |
|---|---|---|
| 01 source | guest research | approve the guest criteria once; veto any name |
| 02 invite | deliverability + guest research | approve invitation sequences before day 18 |
| 03 qualify | producer | read the scored brief before recording |
| 04 record | producer, in the chair | host 30 minutes per guest |
| 05 convert | producer or Closing Desk | follow up from the handoff note |
| 06 compound | editor & clips | approve clips; ask guests for intros |
They decide what happens when a week goes sideways: a mailbox dips, a guest cancels, a clip needs legal.
Invitations go out under the host's name from separate, warmed domains. If a mailbox has a bad week, your company email doesn't.
Every accepted guest gets a 15-minute pre-interview first. Fit is scored before the host gives it 30 minutes.
Guests are invited because their view is worth publishing. They decide whether to keep talking after the recording.
The host reviews each episode, guests approve their clips, and regulated teams get a legal review step before publishing.
The guest is the audience. We report recorded guests, opportunities and revenue, in the same format in a good week and a bad one.
Domains, mailboxes, episodes, clips, the guest list and CRM data sit in your name. If you leave, all of it stays.
A steady-state week on an Engine program, from day 90 on. The host's part is about two hours, and half of it is on the record.
Last week's numbers, this week's recording slots, inbox health, and which accepted guests still need a date. Internal, 20 minutes.
Research adds guests from fresh trigger events: a funding round, a new VP, a public post. Invitations go out at a volume the mailboxes can hold.
The producer runs 15-minute pre-interviews and writes a one-page brief for every guest who qualifies.
Two 30-minute recordings back to back, producer in the chair. The editor starts the cut the same afternoon.
The weekly report goes out: invited, accepted, qualified, recorded, opportunities, signed. Handoff notes land in the CRM with a follow-up drafted for the host.
A producer can run only so many pre-interviews and briefs a week before quality slips. So the producer bench sets capacity, not the sales calendar. When it's full, new programs get the next start date.
Hiring. We look for former journalists, podcast producers and B2B researchers who like working to a scoreboard. Producer seats open first, because they set how many shows we can start each quarter.
new shows started per quarter, each with a named producer and 12 days of mailbox warm-up before the first invitation.
Advise B2B founders? Refer a host. 20% of first-12-months fees for every host who signs, paid monthly, no cap.
See the partner program →Apply with your ICP and ACV. A producer reads every application. If it's a fit, you get a guest forecast for your market within 72 hours of the fit call, and the names of the pod that would run your show.