The Proof Gap Briefing — Recording Script (v3)

~20 minutes · Interactive HTML + voiceover · Screen-recorded walkthrough

How to use this. Word-for-word script. The briefing is a screen-recorded walkthrough of an interactive HTML piece — same format as the thought leadership interactives (proof-gap article, subtract/add article) but designed for the recording. You scroll, click to trigger reveals, and narrate over the experience.

[SCROLL] = scroll to next section. [CLICK] = trigger an interactive element. [REVEAL] = something appears/builds on screen. [PAUSE] = hold on the current visual.

The interactive is designed so you control the pacing. Nothing auto-advances. Every reveal waits for your click or scroll.

Section 1 — The Pattern

0:00–3:00

[SCROLL to hero section. Dark background. Title: "The Proof Gap Briefing." Subtitle fades in: "What came out when I extracted case studies from someone who said he didn't have any." Advisory OS logo in nav.]

I've been asking practice owners the same question for the last few weeks.

"How many client outcomes from the past year could you turn into a case study?"

Most people say one. Maybe two. A few say zero — their work is too complex, too confidential, too routine. The results are just what they do.

Then I ask four different questions.

[SCROLL to the four questions. They appear as a stacked list — each one fades in or builds as you scroll. Gold left border on each.]

"In the past twelve months — has a client renewed without you having to sell it?"

[REVEAL — first question appears]

"Has someone referred a prospect to you without being asked?"

[REVEAL — second question appears]

"Have you helped a client avoid a mistake they didn't see coming?"

[REVEAL — third question appears]

"Has a client's situation changed meaningfully because of your work?"

[REVEAL — fourth question appears]

And they start counting. Three. Four. Sometimes more.

The outcomes exist. They've always existed. The problem isn't results.

[SCROLL to transition line. Large, centered: "The problem is what happens before anyone finds out about them."]

Section 2 — The Prospect's Path

3:00–8:00 · This is where the interactive earns its place.

[This section shows the viewer their prospect's evaluation experience through interactive elements they watch you navigate. This is the visual concept that the article doesn't cover — the prospect's path before the phone rings.]

[SCROLL to section header: "Before They Call You." Subhead: "What your prospect does before you know they exist."]

I want to show you something most practice owners have never actually looked at.

This is what happens before a prospect picks up the phone. Before they book a call. Before they ever talk to you.

Someone mentions your name. Or they find you in a search. Or a colleague says "you should talk to this person."

And the first thing they do — before anything else — is look you up.

[SCROLL to the Evaluation Path — a horizontal journey visualization. Five stages that build left to right as you scroll or click. Each stage is a card or node that appears one at a time.]

[CLICK — Stage 1 appears: "Someone mentions your name."]

It starts with a referral. Or a search result. Or a name in a conversation. They have your name and nothing else.

[CLICK — Stage 2 appears: "They find your website."]

They go to your site. They scan the homepage. Services. About. Maybe a blog.

[CLICK — Stage 3 appears: "They look for proof."]

And then they look for one thing. Whether you've done this before, for someone like them, and what happened.

They're not checking your credentials. They already know you're qualified — whoever referred them told them that, or they wouldn't be on your site. They're looking for evidence. A specific outcome. A situation that sounds like theirs.

[CLICK — Stage 4 appears. The path FORKS into two branches.]

[REVEAL — Left branch (gold): "Finds proof." Right branch (dimmed): "Finds nothing."]

And this is where the path splits.

[CLICK — Left branch expands: "Shows up ready to move. The call is confirmation, not evaluation."]

If they find it — a documented outcome, a case study, a specific result that matches their situation — they show up to the first call differently. They're not interviewing you. They've already decided. The call is confirmation.

[CLICK — Right branch expands: "Calls guarded. Comparison shops. Or doesn't call at all."]

If they don't find it — and most practices have nothing there — they either call with their guard up, treating it like a comparison shop... or they don't call at all. They go back to whoever referred them and say "yeah, I looked at their site, but I couldn't really tell what they do differently."

[PAUSE]

That moment — that evaluation moment — is happening right now for practices watching this.

[SCROLL to "The Invisible No" section. A single statement, large, centered, stark.]

["You hear every yes. You hear some no's. You never hear: 'I looked, couldn't find proof, and moved on.'"]

I call this the invisible no. You hear every yes — those become clients. You hear some no's — the ones who get on a call and don't move forward. But you never hear from the ones who looked, didn't find what they needed, and quietly moved on.

That's the proof gap. Not a content gap. Not a marketing gap. A proof gap — the space between outcomes you've already created and a prospect's ability to find them before they decide whether to call.

[PAUSE]

I wrote about this earlier this week. The article gives you the framework. But the framework doesn't show you what it actually looks like when someone sits down to close this gap — and discovers they can't do it themselves.

One practice. One extraction conversation. What I found that the owner had been sitting on for years.

Section 3 — The Extraction

8:00–16:00 · The story, supported by interactive elements.

[This section tells the extraction story. The interactives support the narrative — a practice profile that sets the scene, a reveal mechanic for the "what he said vs. what came out" contrast, and the three layers building one at a time. Specifics live in the voice. The interactive shows the pattern.]

[SCROLL to section header: "What Extraction Actually Looks Like"]

[SCROLL to Practice Profile — four columns or cards: "Practice: Operations Consultant" / "Revenue: Healthy range" / "Clients: Growing" / "Documented case studies:" and the fourth card is face-down or hidden.]

[CLICK — fourth card reveals: "Zero." In red.]

The practice owner is an operations consultant. Revenue in a healthy range. Growing client base. Gets referrals. Good work, consistently.

Zero documented case studies. Nothing on the website. Nothing he could hand to a prospect before a call.

When I asked why, same answer I always hear:

[SCROLL to quote block: "My results are just what we do. There's nothing dramatic enough to write up."]

[PAUSE]

Thirty-minute conversation. No prep. I could have sent a form — fill in the blanks, what was the situation, what did you do, what changed. I would not have gotten a fraction of what came out. When you type, you filter. You summarize. You skip what feels obvious. When you talk it through with someone asking the right follow-up questions, the real story surfaces.

[SCROLL to the First Question section. The question displayed large, in gold italic: "Tell me about a client who came to you in a situation that felt stuck or unsustainable."]

I started where I always start.

He described a client — a growing services firm, about fifteen people. The founder was working sixty-hour weeks, buried in every project, approving every decision. They were turning away work because the founder was the bottleneck. Revenue had been flat for two years even though demand was there.

If he'd written his own case study, it would have stopped at: "Client was overworked. We streamlined some processes." That's what he thought the story was.

Then I asked: "What changed after you implemented the new structure?"

[SCROLL to a toggle/reveal element. Two states: "What he said" (visible) and "What actually happened" (hidden). The visible state shows a short, flat summary: "Helped a client restructure their operations. Freed up the founder's time. Improved their workflow." Dimmed, stone-colored. Plain.]

[CLICK — toggles to "What actually happened." The flat summary transforms into the real picture: founder went from 60 to 35 hours/week, firm took on $200K in new projects within the quarter, hired two senior people without the founder involved in day-to-day, and built a delivery model that didn't require the founder on every engagement. Gold-accented. The visual transformation should feel like watching the real story emerge from behind the surface version.]

The founder went from sixty-hour weeks to thirty-five. The firm took on $200,000 in new projects within one quarter — work they'd been turning away for two years. They hired two senior people and the founder wasn't involved in day-to-day delivery for the first time since starting the business.

When I showed him the full picture, he said: "Well, yeah — but that's just what we do."

That sentence. That's the proof gap in action.

[SCROLL to Three Layers section. Header: "Three versions of the same engagement." Three rows that build one at a time — each clicking or scrolling to reveal.]

Three layers came out of that one extraction.

[CLICK — Surface layer appears. Stone/dimmed. Label: "Surface." Description: "What the owner would write. Accurate. Flat."]

The surface story — what the owner would have written himself. "Helped a client streamline their operations." Accurate. Completely flat. A prospect reads it and thinks "okay, they do that."

[CLICK — Real layer appears below. White/cream. Label: "Real." Description: "What emerges with follow-up questions. Numbers. Actions. Before and after."]

The real story — specific numbers, specific actions, a clear before-and-after. Sixty-hour weeks to thirty-five. Two years of flat revenue to $200K in new work within a quarter. A founder who couldn't take a day off to a delivery model that runs without them. This layer only comes out with follow-up questions the owner wouldn't ask himself.

[CLICK — Prospect layer appears below. Gold. Label: "Prospect." Description: "What makes someone pick up the phone. Starts where the client started."]

The prospect story — the version that starts where the client started. Buried in every project. Working sixty hours. Turning away business because there wasn't enough of them to go around. Knowing the business could grow but unable to let go of the work long enough to build the infrastructure. A prospect in that situation reads this and thinks: "that's where I am right now."

[PAUSE — all three layers visible]

Same engagement. Three versions. The practice owner would have written version one and stopped.

[SCROLL to Second Case Study section. Transition text: "12 minutes left in the conversation."]

We had about twelve minutes left. I asked: "Different client — different situation, similar level of outcome?"

A second case study fell out immediately. Different client, different industry. This consultant had been brought in to help a professional services firm that was losing proposals. Win rate had dropped below twenty percent. They were competing on price in every pitch.

He rebuilt their scoping process and proposal structure. Within six months, win rate went from under twenty percent to over fifty. Average project size increased by forty percent because they stopped discounting to compete. Annual impact: roughly $300,000 in additional revenue from the same number of proposals.

[SCROLL to a similar toggle element for the second case study. Same mechanic — surface version visible, click to reveal what actually happened.]

[CLICK — reveals the real outcome beneath the surface description.]

When I asked about this client, the first version was "we improved their sales process and helped them win more work." The $300,000 came out four questions later.

[SCROLL to the summary. Large centered numbers that build: "30 minutes" → "2 case studies" → "~$500K combined impact." Each appears with a beat.]

[REVEAL — "30 minutes."]

Thirty minutes.

[REVEAL — "2 case studies."]

Two case studies.

[REVEAL — "~$500K in combined client impact."]

Combined impact for those two clients: roughly half a million dollars. One from unlocking capacity. One from winning work they were already pitching.

[REVEAL — Below the numbers, in stone: "From someone who said he didn't have any."]

[PAUSE]

Section 3B — Why You Can't Do This Yourself

16:00–19:00

[This section closes the gap. The interactive shows what the owner missed — and why. The "what he skipped" items work as click-to-expand elements. Brief label visible, detail revealed on click.]

[SCROLL to section: "What He Skipped." Three collapsed items visible by title only.]

If you're watching this, you're probably thinking: I could do that. I know my client outcomes. I could sit down and write them up.

Here's what I want you to notice about what just happened.

At every point in that extraction, the real story came out because of a question the owner wouldn't have asked himself.

[CLICK — first item expands: "The emotional starting point." Detail: "He started with the process changes. A prospect needs to start with the person — what the founder was dealing with, what they couldn't do."]

He skipped the emotional starting point. He started with the operational changes. A prospect needs to start with the person — the sixty-hour weeks, turning away business, unable to take a day off.

[CLICK — second item expands: "The compounding outcome." Detail: "The ongoing capacity and revenue were afterthoughts. To a prospect, recurring impact is the headline."]

He skipped the compounding outcome. The ongoing capacity was an afterthought to him — just the natural result of better systems. To a prospect, "$200K in new work within a quarter" is the headline.

[CLICK — third item expands: "The specificity." Detail: "'Streamlined their operations' vs. a number a prospect remembers next week."]

He skipped the specificity. "Streamlined their operations" versus "sixty-hour weeks to thirty-five, $200K in new projects within one quarter." One of those a prospect remembers. The other disappears.

[SCROLL to his reaction. Quote block with gold border:]

["I never would have framed it that way. That's... that's actually what happened, I just never thought to lead with it."]

And when the finished case studies landed — the anonymized versions, structured and ready to deploy — he saw his own work through a prospect's eyes for the first time.

[SCROLL to the distinction. Two lines, maybe a toggle or contrast visual:]

["A credential tells a prospect you're qualified." / "Proof tells them you've done this before, with someone like them, and here's what happened."]

A credential tells a prospect you're qualified. Proof tells them you've done this before, with someone like them, and here's what happened.

[PAUSE]

Section 4 — The Close

19:00–22:00

[SCROLL to the Decision Fork callback. The same evaluation path visualization from Section 2 appears again — but now with an addition. The right-side path ("Finds nothing") has a subtle indicator: "Most practices are here." The left-side path ("Finds proof") now feels like a destination, not an abstraction.]

Remember this?

Right now, for most practices watching this — the right side is where your prospects land. They look you up. They find credentials, a services page, maybe some testimonials. But they don't find proof.

Some of them call anyway. Some don't. And the ones who don't — you never hear about it.

The outcomes that would close that gap are already in your head. They've been there for years. You just described them as "what we do" and never wrote them down.

[SCROLL to the two paths. Two interactive cards — click to expand details.]

Two ways to act on this.

[CLICK — Left card expands (gold/highlighted): "Case Study Build."]

[REVEAL — Details build as a list, each appearing with a beat:]

[REVEAL — "✓ 30-minute extraction interview"] [REVEAL — "✓ Two written versions — named and anonymized"] [REVEAL — "✓ Branded HTML page matching your current site"] [REVEAL — "✓ Loom walkthrough of the finished asset"] [REVEAL — "$497. Done within the week."]

If you already know which outcome you'd start with — you just need someone to extract it. That's the case study build. Thirty minutes on a call. I pull the story out, structure it, write both versions — one with the client named for when you have permission, one anonymized so you can publish it tomorrow. I build it as a branded page that matches your site, and I record a Loom walkthrough so you see exactly how to use it and where it fits in your prospect's path.

$497. Finished within the week.

[CLICK — Right card expands: "Systems Diagnostic."]

[REVEAL — Details: "60 min. Full practice review. Find the binding constraint. The proof gap might be first — or it might be third."]

If you're not sure where to start — or you're realizing the proof gap is one piece of a bigger operational picture — that's the Systems Diagnostic. Sixty minutes. Your practice, your constraints. I find the binding constraint. The proof gap might be first. Or it might be third — behind a delivery bottleneck or a sales process. The diagnostic tells you which.

[SCROLL to Calendly section. Clean, centered. "Your best proof is already there." Link prominent. "Limited spots each month."]

The link is below this video. Limited spots each month — that's math, not marketing.

Your best proof is already there. It just needs to be where your prospects can find it.

[PAUSE — hold 3 seconds. End.]

Production Notes

Format: Screen-recorded walkthrough of an interactive HTML piece + voiceover. Same production method as walking through any of the thought leadership interactives, but this one is designed for the recording format — pacing, reveals, and visual beats timed to narration.

Recording workflow: Open the HTML in Chrome full-screen. Screen record + audio. Scroll and click through the interactive as you narrate. Each interactive element waits for your input — nothing auto-advances. You control the pacing completely. The browser window at 16:9 is your frame.

Case details — COMPOSITED: The extraction story is composited from real client work. The practice type, industry, specific situations, and all numbers have been changed. The pattern — surface story vs. real story, what the owner skipped, the three layers — is exact. No one from any real engagement would recognize themselves.

• Practice type: Operations consultant (changed from original)
• Case 1: Founder bottleneck → 60hr to 35hr weeks, $200K new work in one quarter, delivery model rebuilt
• Case 2: Proposal win rate → under 20% to over 50%, average project size up 40%, ~$300K additional annual revenue
• Combined impact: ~$500K
• All quotes are composited/generalized

Interactive elements that earn their place:

What's different from the published proof-gap article:

• The article covers the framework: what the proof gap is, the comparison problem, the trust tax.
• The briefing covers the extraction: what actually happens when you try to close the gap. The prospect's evaluation path (new — not in the article), the extraction story, and why self-extraction fails.
• The flip cards in the article show "What You Show / What They Think." The interactive elements in the briefing show the extraction process — surface → real transformation, three layers building, what got skipped.
• No content overlap. Someone who read the article gets a completely different experience.

What stays in the voice only (not on screen):

• All specific case narrative details — situations, interview dynamics, what questions were asked, what came out.
• His reactions, the "just what we do" moment.
• The emotional texture — tone, pacing, emphasis.
• The numbers appear on screen in the toggle reveals and summary builds, but the story around them is voice only.

What appears on screen:

• The practice profile (type, revenue range, client base, zero case studies)
• The surface version vs. real version (toggle)
• The three layers (Surface / Real / Prospect) — labels and brief descriptions
• The summary numbers (30 min, 2 case studies, ~$500K impact)
• The "What He Skipped" labels (emotional starting point, compounding outcome, specificity)
• The evaluation path and decision fork
• The offer details (deliverables list, pricing)

Design notes for the HTML build:

• Dark theme (charcoal/gold AOS palette) — different from the light-theme published articles. This is a briefing, not a blog post. It should feel exclusive.
• Larger type than the articles. This will be viewed as a video, often on smaller screens. Everything needs to read on a phone screen watching a recording.
• Interactive elements should have clear visual state changes — the viewer needs to see something happen even in a compressed video format.
• Smooth scroll behavior. No jarring jumps between sections.
• The evaluation path in Section 2 is the signature visual. Spend design time here. This is the equivalent of the Subtract/Add deck's ranked lists — the thing the viewer remembers.

Aspect ratio: The HTML is a responsive scrollable page (same as all thought leadership interactives). When screen-recorded in a full-screen Chrome window, it captures at the screen's native resolution — 16:9 on standard displays. No fixed canvas needed.

Calendly: calendly.com/kathryn-brown/systems-diagnostic

Complete Case Study Build offer:

• 30-minute extraction interview
• Two written versions — named and anonymized
• Branded HTML page matching current site
• Loom walkthrough of the finished asset
• $497
• Delivered within the week