Fictional client show

Inside a client show:
Build Notes.

The show, host, guests and numbers are invented. The format is what we build.

Start the engine → See the pipeline math

show.meta / build_notesFictional example

formatinterview · 1 guest guestsVP Eng, CTO, platform cadenceweekly · 2×/wk from oct length~28 min edited run onEngine tier →

buttons go live with the client's feed · browse episodes ↓

cover / s013000×3000

art direction: the guest's world, not the product.

A B2B podcast show example, end to end.

Build Notes is a fictional B2B podcast show example: the show page, episode list, clips and guest nominations a client gets, plus how each episode feeds the sales pipeline.

show.promise

The promise, written for the guest.

A VP Engineering decides in one line whether this is worth half an hour.

// on the show page, verbatim

Engineering leaders on the systems they built, broke and would build again. Thirty minutes. No pitch.

Host: co-founder & CTO of the client

a Series A build-infrastructure company, ~40 people

Placeholder bio

[who's on]guest criteria

Buyers, by title

VP Eng, CTO or head of platform at Series B–D software companies, 150–1,500 people.

in: ICP spec → out: guest list

[guests get]per episode

A stage and five clips

A peer conversation and clips they approve.

in: 30 min → out: episode + 5 clips

[client gets]per guest

Discovery, on file

Priorities, pain and the buying committee, in their words.

in: episode → out: CRM notes

episodes · season_01

Eight aired. Twenty-four recorded.

Eight recordings a month, so releases go twice weekly from October. Guests get clips within a week and an air date within eight weeks.

8 of 8 episodes

newest first · guests anonymizedPlaceholder guests

08
platformsep 22
The migration we paused at 70%
VP Engineering · Series C logistics software · ~400 people

29:48 5 clips 2 cards
07
reliabilitysep 15
Audit logs before features
CTO · Series B healthtech · ~180 people

27:12 5 clips 3 cards
06
platform · featuredsep 8
Two deploys a day, in two big lumps
Head of Platform · Series B fintech infrastructure · ~250 people
Excerpt and CRM notes ↓

28:30 5 clips 1 card
05
teamssep 1
Hiring the second platform team
VP Engineering · Series D marketplace · ~900 people

28:02 5 clips 2 cards
04
reliabilityaug 25
On-call nobody dreads
Head of Platform · Series D B2B software · ~1,200 people

26:55 5 clips 2 cards
03
costaug 18
Boring databases, on purpose
CTO · Series B data tooling · ~220 people

25:47 5 clips 2 cards
02
costaug 11
The cloud bill, without a freeze
VP Engineering · Series C HR software · ~350 people

29:10 5 clips 3 cards
01
teamsaug 4
Measuring developer experience without surveys
CTO · Series B security company · ~300 people

24:36 5 clips 2 cards

featured · ep_06 · aired tue sep 8

Two deploys a day, in two big lumps.

No sales questions. By minute 23: priority, pain, failed fix, deadline and who signs.

Fictional transcript

recording / ep_06 · 30:00 raw · 28:30 airedHow the interview is built →

airedexcerpt · 08:40–13:55cut from the edit · 28:30–30:00

Episode 6 chapters and what each surfaced, plus the off-air cut
ch · time	on air	surfaces
01 · 00:00	Warm-up: why they're here	context
02 · 03:05	“Walk me through the next 12 months. What has to go right?”	priorities
03 · 08:40	“Where does that plan feel fragile?”	pain
04 · 13:20	“What did you try last year that you wouldn't try again?”	failed fixes
05 · 18:55	“If you could fix one thing before Q4, which would it be?”	urgency
06 · 22:30	“When a decision like that comes up, whose phone rings first?”	committee
07 · 25:10	Wrap: thanks and the air date	air date
cut · 28:30	Off air: “You mentioned test selection. Can I send you something on that?”	next step

transcript · 08:40–13:55 · excerptFictional transcript

host08:40

Where does that plan feel fragile?

guest08:44

The release train. On paper we deploy twice a day. In practice a flaky integration suite holds the queue for forty minutes, so people batch changes to dodge it. Two deploys a day, in two big lumps.

host13:20

What did you try last year that you wouldn't try again?

guest13:26

A CI rewrite owned by one person for a quarter. It worked for six weeks. Then he moved teams and nobody else could read the config.

crm.handoff / ep_06_guestExample data

What the host learned

Never published. Straight to the client's CRM.

priorityship smaller, more often, before a 40-engineer hiring push pain40-minute queue holds from a flaky integration suite triedone-person CI rewrite in 2025, abandoned urgencyfixed before Q4 planning locks committeehead of platform + VP Eng; CFO signs tools over $50k follow-uptest-selection benchmark sent, day +1 stageopportunity · call booked day +6

pre-interview fit score: 8 / 10 · owner: client AE

Five clips and a quote card, all guest-approved.

Fictional example

swipe for all 6 →

clip_01 · 0:489:16

Two deploys a day, in two big lumps.

✓ host + guest posted

clip_02 · 0:361:1

Nobody decided it. It just accreted.

✓ host posted

clip_03 · 0:529:16

One person owned the rewrite. Then he moved teams.

✓ guest posted

clip_04 · 0:4116:9

The queue is a tax every engineer pays twice a day.

✓ in the newsletter

clip_05 · 0:399:16

Fix the wait before you hire more people to wait in it.

✓ scheduled thu

card_01 · quote1:1

Forty minutes, twice a day, 120 engineers. Do that math once.

✓ guest posted

Per recorded guest: a brief, a producer, CRM notes and approved clips. Five on Engine, three on Pilot.

Start the engine → See pricing

guest.nominations

Know someone who belongs on the record?

step 1 · check
Against the guest criteria
Title, stage, team size, topic. Off-ICP names go to a separate list.
step 2 · invite
Under the host's name
From the show's own domain, never the client's.
step 3 · pre-interview
15 minutes with a producer
Scored before the host spends a minute.
step 4 · record
Half an hour with the host
The nominator gets a thank-you and the air date.

nominations so far: 4 · recorded: 2 Example data

why_each_block_exists

Every block here has a pipeline job.

Built for the next guest, not downloads.

[01]cover + promise

Answers the invite

Every invitation links here.

in: invitation click → out: accept

[02]episode list

Peers already said yes

A CTO accepts faster after eight peers did.

in: skim → out: trust

[03]chapters + transcript

Shows the format

Guests see it stays on their work.

in: doubt → out: prepared guest

[04]clips

Reach inside the ICP

Guests post clips. Peers watch.

in: 5 clips → out: peer reach

[05]nomination form

Refills the list

Past guests name their peers.

in: nomination → out: next guest

[06]crm notes · private

The part nobody sees

Never published. Read by the AE.

in: recording → out: opportunity

two objections, answered

“Legal will never approve this.”

Episodes are reviewed before publishing, guests approve their clips, and nothing airs without sign-off. More in the FAQ →

“None of us has hosted anything.”

Nobody needs to. It's a conversation with people you'd want to meet anyway. We write the brief and sit in the producer chair.

your show, your buyers as guests

Want a show like this one?

Tell us who you sell to. We send back a show concept, a guest profile and the pipeline math. Or browse the show network.

Start the engine → See the pipeline math

Inside a client show:Build Notes.

A B2B podcast show example, end to end.

The promise, written for the guest.

Buyers, by title

A stage and five clips

Discovery, on file

Eight aired. Twenty-four recorded.

The migration we paused at 70%

Audit logs before features

Two deploys a day, in two big lumps

Hiring the second platform team

On-call nobody dreads

Boring databases, on purpose

The cloud bill, without a freeze

Measuring developer experience without surveys

Two deploys a day, in two big lumps.

Transcript excerpt

What the host learned

Five clips and a quote card, all guest-approved.

Know someone who belongs on the record?

Against the guest criteria

Under the host's name

15 minutes with a producer

Half an hour with the host

Every block here has a pipeline job.

Answers the invite

Peers already said yes

Shows the format

Reach inside the ICP

Refills the list

The part nobody sees

Want a show like this one?

Inside a client show:
Build Notes.