VerbatimSample brief: the advisory we wrote for Verbatim itself, exactly as a customer receives it. Order yours
This is a real Verbatim Advisory, unedited, written for Verbatim itself from podcasts published in the weeks before it was written. Yours is built the same way for your business. How Advisory works

In plain English

This is the brief Verbatim Advisory wrote about Verbatim itself. It read what founders, investors and operators said on 900+ podcasts in the weeks before, matched it to what Verbatim sells, and turned it into next moves. Every quote in the brief links to the second it was said.

Buyers already feel the problem Verbatim solves. An investment CIO says AI summaries of research miss something 75% of the time and are completely wrong 10 to 15% of the time. An investor puts expert calls at $750 to $1,000 an hour, and up to $5,000 for an ex-CEO.

What worked for other businesses, with their numbers. Sell a one-time paid entry before the subscription: one founder found strangers pay $1,000 once far more easily than $2,000 to $2,500 a month. Put a short survey on the page after signup. Score a target list for buying signals: one sales leader cut outbound lists by 80%.

Eight new lanes, among them Verbatim inside the buyer's own AI tools, a monthly study published from the library, and a capped founding-member presale (150 spots sold in 48 hours).

Five traffic moves and a 30-day plan. A free flagship that drew 60,000 signups, guest spots that plug one free asset early in the episode, and a weekly live session (13 webinars, 232 enrolments).

The three moves it recommends first:

  1. Make the one-off brief the paid front door to the monthly brief, crediting the price on upgrade.
  2. Ask new free users five questions and offer them a brief that fits their answers.
  3. Publish a page on using Verbatim from inside an AI assistant, and a page for investors pricing it against expert calls.

How to read the rest. The first block and STEP 0 are the working record: which pages were checked, how far back the search went, and why a section is shorter than its target. When the library held no more evidence, the brief says so instead of padding. Signal A is buyer pain, Signal B is what worked, Opportunity is new lanes, Signal T is traffic, and the Build Agenda ends with ready-to-run build prompts for each move.

Verbatim Advisory for Verbatim

Verified: 2026-10-29, from https://verbatim.theartofservice.com, https://verbatim.theartofservice.com/advisory, https://verbatim.theartofservice.com/about and https://www.linkedin.com/in/gerardblokdyk (auth-walled). LinkedIn: URL only, auth-walled Data source: the Verbatim library, 900+ business and technology podcasts, searched 2026-10-29. Windows: Pain window = 60 days (default 30, auto-widened to 60). Mechanic window = 21 days (default 7, auto-widened 7 to 14 to 21). Opportunity searches ran at 30 days. Override from PERSON DETAILS: none. Signal A expansion: Rungs fired: 1, 2, 3 and 4. Offer sweep queries: 24 across Free, Pro, Team, One brief and Monthly brief. Adjacent-fit rows: 1 (A4, on the role and company test). Final count: 4, against a target of 5-8 and a hard floor of 3. Opportunity coverage: Pass C returned about 105 adjacent-lane atoms, of which 8 came from named operators with a number. The Opportunity section ships 8 rows against a target of 20-40, honest-sized. Signal T ships 5 rows against 15-30, also honest-sized. Operator density: under 5% of lane atoms were named first-hand operators. The library this fortnight is thin on operator voice in this lane, so the brief is short.

Every quote in this brief links to the podcast moment where it was said. If any link is broken or any attribution is wrong, we refund you.

STEP 0 - Anchor list (verified by WebFetch 2026-10-29)

Scope: Verbatim (verbatim.theartofservice.com) only, a product of The Art of Service. The wider The Art of Service catalogue is out of scope. The anchor below matches the Scope notes, so no frame conflict was found.

Currency: the site prices in US dollars. The FAQ states USD for Pro and Team. The Verbatim Advisory prices ($497, $297/month) carry no currency label on the page, so this brief treats them as USD (inferred, to confirm).

Positioning (verbatim, per URL)

Named ideal buyer (verbatim, per URL)

Offers (verbatim one-line description, price, source URL)

# Offer Verbatim description Price Source
O1 Free "For anyone who wants the week's best moments on a few topics." Monday brief on 3 topics; search the last 7 days; play every quote at the second; 10 searches a day. $0 home
O2 Pro "For founders, marketers and sellers building trust, audience and relationships in a market." Unlimited topics, your own words; watchlist of 25 names or phrases; next-morning alerts when they are said; search 30 days, export to CSV; "Another view" on contested claims. $29/month (USD) home
O3 Team "For teams who want living data in their own AI and one shared view of the market." 5 seats, shared watchlists; search the full archive; REST API and MCP: living data for your own AI; everything in Pro. $299/month (USD) home
O4 Verbatim Advisory, One brief "For a decision you are making now, a launch, or a first look at your market." Home describes Advisory as "a private brief matched to your offers, from $497." $497 /advisory, home
O5 Verbatim Advisory, Monthly brief "For businesses that want this month's pains, recipes and lanes every month." $297/month /advisory

Advisory deliverable components (verbatim, /advisory): "Pains your offers already solve", "Recipes that worked", "New lanes you have not opened", "Traffic recipes for your buyers", "Your build agenda", "A build prompt for every page", "Delivered in two business days". Order form: "A name, a website and a LinkedIn profile. Add your offers and anything to focus on or leave out. Two minutes."

Supporting surfaces (not priced offers): Topics (/topics, 24 topic pages, e.g. ai-agents, pricing, sales, marketing, customer-acquisition, content-and-media), Search (/search), How we quote (/how-we-quote), Takedown (/takedown).

Stated problems solved (verbatim)

Explicit absences

LinkedIn

LinkedIn not accessible for anchor (https://www.linkedin.com/in/gerardblokdyk returned HTTP 999, auth wall); profile text not provided.

Prior knowledge, not confirmed on site today

None supplied (Known offers field was blank).

STEP 2 - Library coverage (60-day pain window, 21-day mechanic window, ending 2026-10-29)

How to read the counts: semantic retrieval returns exactly k moments for every query, so the raw count is always the k requested. The useful number is the second one in each cell: how many returned moments were in Verbatim's lane, and how many of those were named-operator voice.

Pass A - lane coverage

Query (paraphrased) Raw atoms at pain window Raw atoms at mechanic window
Customers' words, out-of-date market research 50 at 30d (k=50); 4 in lane, 0 operator pains not run at 7d; 21d sweep below
AI-written content distrusted, content stopped working 50 at 30d (k=50); 3 in lane, 1 named operator pain not run at 7d
Tracking what competitors and customers say 50 at 30d (k=50); 3 in lane, 2 named operators not run at 7d
Launched an offer nobody bought 12 at 30d; 0 in lane -
Consulting pipeline dried up, unsure which offer 12 at 30d; 0 in lane -
AI agent wrong because of stale data 12 at 30d; 0 operator pains -
Expert-network call cost 12 at 60d; 2 in lane, 2 named -
Buying-signal alerts with a number - 15 at 7d; 0 in lane
Paid research brief sold - 15 at 7d; 1 in lane
Free tool or scorecard driving signups - 15 at 21d; 2 in lane
Webinar to demos - 12 at 21d; 5 in lane

Pass B - operator density: About 160 Pass A atoms were read. Roughly 12 were in Verbatim's lane, and 6 of those came from named operators speaking first-hand, which is under 5%. The library this fortnight is thin on operator voice in this lane, so the brief is short. Most lane-relevant moments come from vendors, agency hosts and consultants describing other people's problems. STEP 1 excludes those voices.

Auto-widen: Pains widened from 30 to 60 days (rung 3). The 60-day rerun of the expert-network, investor-research and buyer-understanding queries found no new qualifying pains. Every surviving Signal A atom falls inside 30 days. Mechanics widened from 7 to 14 to 21 days, because the 7-day sweeps returned one lane-relevant mechanic.

Pass C - adjacent-lane coverage for Opportunity:

Adjacent query Returned Lane-relevant, named operator
Annual or founding-member pricing 12 + 5 2
Licensing data or content to AI companies 12 0
Podcast-guest booking for clients 12 0
MCP and connectors for customer data 12 + 8 2
Expert calls replaced by AI interviews 12 + 5 1
Learning teams using podcasts 5 1
One-off paid analysis of a large corpus 15 1

Expected Opportunity volume: 8 rows, against a target of 20-40. The adjacent lanes are real, but most of those moments come from unnamed speakers or vendors.

Signal A - Pains that match a stated offer

What this block is for: This section shows buyer pain that justifies Verbatim's current ladder. Each row is a named operator in the podcast library (pain window widened to 60 days; every survivor falls inside 30) describing a specific unresolved problem that one of Verbatim's stated offers solves directly. Read it to see which pains in the market right now already fit what Verbatim sells: Free, Pro, Team, and the Verbatim Advisory One brief and Monthly brief. For each row, the HOW block shows how Verbatim would help if this operator signed up this week, and the Practical example walks through the engagement end to end. The Site + productize action and Claude Code prompt show what to add to verbatim.theartofservice.com so buyers searching for this pain find it. This section has 4 rows against a target of 5. Rungs 1 (offer sweep across all five offers), 2 (buyer widening to investors, analysts, coaches and agency founders) and 3 (pain window 30 to 60 days) all fired. Rung 4 admitted one adjacent-fit row (A4, tagged on the role and company test). The other rung 4 candidates were dropped for lack of a named role and company.

Signal A #1 - AI summaries of research that are completely wrong

#
A1
Operator (role, company)
Moez Kassam, CIO (billion-dollar investor, per episode title)
Show, date, time
The Pomp Podcast, 2026-10-21, 24:33
Verbatim quote
"We drop it into Claude or ChatGPT… 75% of the time there's something they missed or 10-15% they're completely wrong"
Reported cost
AI summaries of analyst reports miss a point 75% of the time and are completely wrong 10-15% of the time; he checks every one before trading
Matches offer
Pro
Why this offer
Pro lists "'Another view' on contested claims" and home says "play every quote at the second". Home names the problem: "Most market insight is someone's summary of someone else's summary."
Falsifiable tag
Medium: named role, speaker not voice-verified
**Listen link**
Listen at 24:33

HOW block

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack (WordPress, Webflow, Next.js, Astro or static) and its deploy path. Without repo access, ship a self-contained HTML page, a /ai-summary-wrong-check.md twin and an /llms.txt append.

2. CREATE PAGE at /ai-summary-wrong-check.
- H1: "Is the AI summary of your research wrong?"
- Direct answer (50-100 words): "Verbatim Pro, from Verbatim by The Art of Service, costs USD 29 per month. It lets investors and analysts check an AI summary against what operators actually said on 900+ business podcasts. Verbatim Pro adds Another view on contested claims, a watchlist of 25 names or phrases, next-morning alerts, 30 days of search and CSV export. Every quote plays at the exact second it was said."
- Symptom bullets: "the summary missed the point"; "the summary was completely wrong and nobody noticed"; "you cannot show where a claim came from"; "every competitor's AI read the same internet".
- Primary CTA "Check a claim free" to /login?next=/account%3Fwelcome%3D1. Secondary "Go Pro" to /checkout/pro.
- Proof: one Verbatim moment card that plays the quoted second, labelled with its claim and number ("10 to 15 percent completely wrong"). No speaker name in the page copy.
- FAQ, 6 pairs, each answer 40-80 words and naming Verbatim Pro: "Can I trust ChatGPT summaries of analyst reports?"; "How do I verify an AI summary against the source?"; "What is Another view?"; "How much is Verbatim Pro?"; "How many podcasts does Verbatim read?"; "Can I export the quotes?"
- Secondary section: "How to check an AI summary in four steps".
- Name the framework in body copy and caption it. Closing CTA repeats Go Pro.

3. FRAMEWORK. Build "The Source Second Check" (origin: invented, grounded in the anchor features play-at-the-second, Another view and watchlist). Components: Summary claim, Source second, Another view, Verdict. Form: a horizontal audio-waveform ruler with a claim card snapping onto one tick, and a second waveform beneath for Another view. On mobile, stack it vertically. Make it a hand-built inline SVG React component at components/frameworks/SourceSecondCheck.tsx with role="img", <title>, <desc>, real <text> labels readable at 375px, staged draw-in, hover one-liners and prefers-reduced-motion respected. No pyramids, lightbulbs, puzzle pieces, Venn diagrams, stock art, external images or statistics. Log the name, origin, components, idea, anchor basis and page in docs/frameworks-inventory.md.

4. STRUCTURED DATA (JSON-LD). Service: Verbatim Pro, provider Organization The Art of Service and Person Gerard Blokdyk, areaServed Worldwide, priceSpecification 29 USD per month, serviceType "podcast research subscription". Also FAQPage; Person with sameAs https://www.linkedin.com/in/gerardblokdyk; Organization with url, logo and sameAs; BreadcrumbList Home > Pricing > this page; speakable on the direct answer and FAQ answers; ImageObject for the framework (name, one-sentence description, creator Verbatim, encodingFormat image/svg+xml).

5. AEO FILES. Write /ai-summary-wrong-check.md with the H1, answer, bullets, FAQ and the framework idea. Append "- [Is the AI summary of your research wrong?](https://verbatim.theartofservice.com/ai-summary-wrong-check): check AI summaries against the second an operator said it" to /llms.txt, and to /llms-full.txt if it exists.

6. META. Title: "Verbatim Pro: check AI summaries at the source". Description, under 155 characters, naming Verbatim Pro, wrong summaries and quotes at the second. Robots: "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1". Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. Add OpenGraph tags and a summary_large_image card using the framework PNG, plus canonical and last-modified 2026-10-29.

7. LINKING. Inbound from /how-we-quote, /topics/investing and the home pricing section, with anchor text "check an AI summary against the source". Outbound to /how-we-quote and /topics/investing. Semantic breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Pro Source Second Check", sitemap lastmod 2026-10-29. Keep HTML under 100KB and the total page under 500KB. Lighthouse performance and accessibility at or above baseline.

9. PRODUCTIZE. In the existing checkout, add the entry name "Pro: Summary Check" routing to /checkout/pro with utm_content=summary-check. Keep the price at USD 29 per month. Add one line about Another view to the Pro welcome email.

10. LEADING INDICATOR. Weekly Search Console sessions on the slug. Weekly test queries in Perplexity, ChatGPT, Claude, Gemini and Google AI Overview for "how to verify an AI summary of analyst reports". ChatGPT referrals via UTM. A brand-mention tool tracking "Verbatim Pro". SVG render checks at 375px and desktop, with reduced motion on and off. Counts only.

Practical example

Signal A #2 - Expert-network calls at $750 to $5,000 an hour

#
A2
Operator (role, company)
Ben Isaac, Brizo Capital (episode guest)
Show, date, time
Yet Another Value Podcast, 2026-10-20, 18:53
Verbatim quote
"Expert networks, what's the going rate for an expert network? $750, $1,000 per hour. CEOs don't even do them, and ex-CEOs will charge $5,000 an hour sometimes."
Reported cost
$750-$1,000 an hour for an expert call, up to $5,000 an hour for an ex-CEO
Matches offer
Team
Why this offer
Team: "search the full archive; REST API and MCP: living data for your own AI". Home names "Investors and analysts" as a buyer.
Falsifiable tag
Medium: speaker taken from episode title, not voice-verified
**Listen link**
Listen at 18:53

HOW block

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /expert-call-alternative.md twin and an /llms.txt append.

2. CREATE PAGE at /expert-call-alternative.
- H1: "An alternative to $1,000-an-hour expert network calls"
- Direct answer (50-100 words): "Verbatim Team, from Verbatim by The Art of Service, costs USD 299 per month for 5 seats. It gives investors and analysts full-archive search of what CEOs, founders and operators said on 900+ business podcasts, with shared watchlists and REST API and MCP access so the moments flow into the team's own AI. Every quote plays at the second it was said."
- Symptom bullets: "expert calls cost $750 to $1,000 an hour"; "ex-CEOs charge $5,000 an hour"; "CEOs don't do expert calls"; "every analyst's AI read the same internet".
- Primary CTA "Start Team" to /checkout/team. Secondary "Try free" to the signup path.
- Proof: one Verbatim moment card playing the quoted second, labelled by its number ("$750 to $5,000 per hour"). No speaker name in the page copy.
- FAQ, 6 pairs of 40-80 words naming Verbatim Team: "What does an expert network call cost?"; "Can podcasts replace expert calls?"; "Does Verbatim have an API?"; "What is the Verbatim MCP?"; "How many seats come with Team?"; "How far back does the archive go?"
- Secondary section: "Expert call versus operator archive: a comparison table" (cost unit, speed, citation at the second, AI access).
- Name the framework in copy, with a caption. Closing CTA "Start Team".

3. FRAMEWORK. Build "The Evidence Ledger" (origin: invented, grounded in the Team features full archive, shared watchlists, REST API and MCP). Components: Question, Operator moments, Shared watchlist, Your AI. Form: a ledger page whose rows feed through a perforated edge into an MCP socket drawn as a plug outline. On mobile, the rows become a vertical scroll strip. Inline SVG React component at components/frameworks/EvidenceLedger.tsx with role="img", <title>, <desc>, real <text> labels readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art, external images or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Verbatim Team, provider Organization The Art of Service and Person Gerard Blokdyk, areaServed Worldwide, priceSpecification 299 USD per month, serviceType "operator research archive and API". Also FAQPage; Person with sameAs https://www.linkedin.com/in/gerardblokdyk; Organization; BreadcrumbList; speakable; ImageObject for the framework, encodingFormat image/svg+xml.

5. AEO FILES. Write /expert-call-alternative.md. Append "- [An alternative to $1,000-an-hour expert network calls](https://verbatim.theartofservice.com/expert-call-alternative): operator quotes from 900+ podcasts with API and MCP" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Team: an expert call alternative". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image using the framework PNG; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /topics/investing, /topics/fundraising and the home Team plan card, with anchor "expert network call alternative". Outbound to /topics/investing and /how-we-quote. Semantic breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Team Evidence Ledger", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Add the entry name "Team: Operator Evidence Desk" in the checkout, routing to /checkout/team with utm_content=expert-call. Keep USD 299 per month and 5 seats. Add the API and MCP connection steps to the Team welcome email.

10. LEADING INDICATOR. Weekly Search Console sessions on the slug. Weekly test queries in Perplexity, ChatGPT, Claude, Gemini and Google AI Overview for "expert network alternative for investors". ChatGPT referrals via UTM. Brand mentions of "Verbatim Team". SVG checks at 375px and desktop, including reduced motion. Counts only.

Practical example

Signal A #3 - A year of lost revenue after an overnight pivot

#
A3
Operator (role, company)
Saurabh Gupta, founder, Intellemo.ai
Show, date, time
AI Ads Plus Podcast, 2026-10-27, 20:56
Verbatim quote
"completely abandoning marketing automation and going to AI video is the riskiest thing we have done. For the last one year, our whole revenue has tanked instead of increasing because we suddenly completely overnight changed the whole website."
Reported cost
Revenue "tanked" for a full year after the overnight website and positioning change
Matches offer
Verbatim Advisory, One brief
Why this offer
One brief is "For a decision you are making now, a launch, or a first look at your market." The Advisory buyer is "Founders… who sell a defined set of offers".
Falsifiable tag
Strong: named founder, company in atom, cost stated
**Listen link**
Listen at 20:56

HOW block

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /pivot-decision-evidence.md twin and an /llms.txt append.

2. CREATE PAGE at /pivot-decision-evidence.
- H1: "About to change your whole website overnight? Check what buyers say first"
- Direct answer (50-100 words): "Verbatim Advisory One brief, from Verbatim by The Art of Service, costs USD 497. It is a private brief for founders making a decision now, such as a pivot, a launch or a repositioning. The brief lists the buyer pains your offers already solve, recipes that worked, new lanes, traffic recipes and a build agenda, all sourced from operators on 900+ podcasts. It is delivered in two business days."
- Symptom bullets: "changing the whole website overnight"; "abandoning what sells for a new bet"; "revenue tanked after the switch"; "no evidence of what buyers want right now".
- Primary CTA "Get one brief, $497" to /advisory/start?plan=once.
- Proof: one Verbatim moment card playing the quoted second, labelled "a year of revenue lost after an overnight switch". No speaker name in the page copy.
- FAQ, 6 pairs of 40-80 words naming Verbatim Advisory: "How do I know if a pivot will work?"; "What is in a Verbatim Advisory brief?"; "How long does it take?"; "What do you need from me?"; "Is it matched to my offers?"; "What does it cost?"
- Secondary section: "Signs you are about to pivot without evidence".
- Introduce the framework by name, with a caption. Closing CTA repeats the order link.

3. FRAMEWORK. Build "The Pivot Pressure Gauge" (origin: invented, grounded in the Advisory deliverables: pains your offers already solve, recipes that worked, new lanes, your build agenda). Components: Pains solved, Recipes, New lanes, Build agenda, read as four arcs around a needle marked "decide" or "wait". On mobile, render four stacked bars with the needle as a marker. Inline SVG React component at components/frameworks/PivotPressureGauge.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Verbatim Advisory One brief, provider Organization The Art of Service and Person Gerard Blokdyk, priceSpecification 497 USD, delivery two business days, serviceType "market evidence brief". HowTo with the steps order, intake and delivery. Also FAQPage; Person with sameAs https://www.linkedin.com/in/gerardblokdyk; Organization; BreadcrumbList; speakable; ImageObject for the framework, encodingFormat image/svg+xml.

5. AEO FILES. Write /pivot-decision-evidence.md. Append "- [About to change your whole website overnight?](https://verbatim.theartofservice.com/pivot-decision-evidence): a buyer-evidence brief before a pivot" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Pivot check: Verbatim Advisory One brief". Description under 155 characters. Robots with max-snippet:-1. Allow the nine AI crawlers: GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image with the framework PNG; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /advisory, /topics/founders and /topics/transformation, with anchor "check before you pivot". Outbound to /advisory and /topics/founders. Breadcrumb Home > Advisory > Pivot check.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Advisory Pivot Pressure Gauge", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. In the Advisory order system, add "One brief: Pivot Check" at USD 497, delivered in two business days, with a form field "the decision you are making now". Route the CTA to /advisory/start?plan=once&focus=pivot. Mirror the name in the confirmation email and invoice.

10. LEADING INDICATOR. Weekly Search Console sessions. Weekly AI-engine test queries for "should I pivot my business model evidence". ChatGPT referrals via UTM. Brand mentions of "Verbatim Advisory". Orders tagged focus=pivot. SVG render checks at 375px and desktop. Counts only.

Practical example

Signal A #4 - A founder back on sales calls to learn who they attract

#
A4
Operator (role, company)
Jasmine Star, founder speaking of her own sales team (host, The Jasmine Star Show)
Show, date, time
The Jasmine Star Show, 2026-10-15, 1:39
Verbatim quote
"I jumped in and I just became the stopgap... I was looking at this not just to be a stopgap in sales, I really wanted to drill down and deeply understand who we were attracting"
Reported cost
Two weeks of the founder's full sales calendar, taken to learn who the business was attracting
Matches offer
Verbatim Advisory, Monthly brief
Why this offer
Monthly brief is "For businesses that want this month's pains, recipes and lanes every month". Advisory promises "evidence of what buyers in their market are struggling with right now".
Falsifiable tag
Medium: verified speaker, company not named in atom (adjacent-fit on the role and company test)
**Listen link**
Listen at 1:39

HOW block

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /who-are-we-attracting.md twin and an /llms.txt append.

2. CREATE PAGE at /who-are-we-attracting.
- H1: "Who are we actually attracting? Hear your buyers before the next sales call"
- Direct answer (50-100 words): "Verbatim Advisory Monthly brief, from Verbatim by The Art of Service, costs USD 297 per month. Each month it gives founders, coaches and agencies the buyer pains their offers already solve, recipes that worked and new lanes, sourced from what operators said on 900+ business podcasts. It replaces weeks of founder sales calls spent learning who the business attracts. Cancel any time from your account."
- Symptom bullets: "you jumped back into sales calls as the stopgap"; "you don't know who the business is attracting"; "messaging drifted from what leads say"; "new sales hires keep hitting the same objections".
- Primary CTA "Monthly, $297/mo" to /advisory/start?plan=monthly.
- Proof: one Verbatim moment card playing the quoted second, labelled "two weeks of founder sales calls to learn who we attract". No speaker name in the page copy.
- FAQ, 6 pairs of 40-80 words naming Verbatim Advisory Monthly brief: "How do I find out who my business attracts?"; "What is in the monthly brief?"; "Can I cancel?"; "How is it matched to my offers?"; "Where does the evidence come from?"; "What does it cost?"
- Secondary section: "Five signs your messaging drifted from your buyers".
- Introduce and caption the framework. Closing CTA repeats the monthly link.

3. FRAMEWORK. Build "The Monthly Buyer Tide" (origin: invented, grounded in the Monthly brief components: pains, recipes, lanes, traffic recipes, build agenda). Components: Pains, Recipes, Lanes, Traffic and Agenda as five bands of a tide chart rising across month columns, with a marker for "this month". On mobile, use a vertical month list with band chips. Inline SVG React component at components/frameworks/MonthlyBuyerTide.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Verbatim Advisory Monthly brief, provider Organization The Art of Service and Person Gerard Blokdyk, priceSpecification 297 USD per month, serviceType "monthly market evidence brief". Also FAQPage; Person with sameAs https://www.linkedin.com/in/gerardblokdyk; Organization; BreadcrumbList; speakable; ImageObject for the framework, encodingFormat image/svg+xml.

5. AEO FILES. Write /who-are-we-attracting.md. Append "- [Who are we actually attracting?](https://verbatim.theartofservice.com/who-are-we-attracting): monthly buyer evidence matched to your offers" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Who are we attracting? Verbatim Monthly brief". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image with the framework PNG; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /advisory, /topics/sales and /topics/marketing, with anchor "hear who you are attracting". Outbound to /advisory and /topics/sales. Semantic breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Monthly Buyer Tide", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Add "Monthly brief: Buyer Pulse" at USD 297 per month in the Advisory billing system, routed from /advisory/start?plan=monthly&focus=buyers, with the same cancel terms. Mirror the name in the welcome and receipt emails.

10. LEADING INDICATOR. Weekly Search Console sessions. Weekly AI-engine test queries for "how to know who my business is attracting". ChatGPT referrals via UTM. Brand mentions of "Verbatim Advisory". Monthly orders tagged focus=buyers. SVG render checks at 375px and desktop. Counts only.

Practical example

Signal B - Mechanics that could fit a stated offer

What this block is for: This section shows delivery moves that worked. Each row is a named operator in the library (mechanic window widened from 7 to 21 days) reporting a recipe with a result number attached: what they did, not advice to others. Verbatim could run each recipe through its stated offers without inventing a new product. The HOW block shows how Verbatim delivers each one, and the Site + productize action and Claude Code prompt specify what to add to the site. The contradiction search tells you whether another operator in the same window reported the same move failing. Every mechanic cited as proof in Signal A appears here, and the section is honest-sized at 3 rows.

Signal B #1 - A one-time paid front end before the recurring offer

#
B1
Operator (role, company)
Corey Ganim, founder (AI assessment business, per episode)
Show, date, time
7-Figure Leap with Dustin Riechmann, 2026-10-20, 17:28
Verbatim recipe
"it's so much easier to get somebody to pay you $1,000 one time when they don't yet trust you versus $2,000-$2,500 a month"
Reported result
A $1,000 one-time assessment sold to strangers ahead of a $2,000-$2,500/month offer. The same episode reports 30-40 initial clients growing to 316 members.
Fits offer
Verbatim Advisory, One brief leading to Monthly brief
Why this offer
The ladder already exists: One brief at $497 "For a decision you are making now" and Monthly brief at $297/month "every month".
Contradiction search
No contradicting atom in 21 days. Corroborating: Simon, one-person agency, "I sell it at about $1,500 initially… if you end up going to a retainer, we will credit that inbox audit against the retainer" (The Side Hustle Show, 2026-10-15, 25:06)
Falsifiable tag
Strong: verified speaker, number in atom, second show (Build With AI, 2026-10-15) repeats the $1,000 assessment
**Listen link**
Listen at 17:28

HOW block

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /one-brief-then-monthly.md twin and an /llms.txt append.

2. CREATE PAGE at /one-brief-then-monthly.
- H1: "Not ready for a monthly retainer? Start with one brief"
- Direct answer (50-100 words): "Verbatim Advisory One brief, from Verbatim by The Art of Service, costs USD 497 and is delivered in two business days. It is a private brief matched to your offers: pains your offers already solve, recipes that worked, new lanes and a build agenda, every line linked to the podcast second it came from. If you move to the Monthly brief at USD 297 per month, the One brief is credited (terms to confirm)."
- Symptom bullets: "you don't trust a monthly commitment yet"; "you want proof before a retainer"; "you need one decision answered now"; "you want evidence, not opinion".
- Primary CTA "Get one brief, $497" to /advisory/start?plan=once. Secondary "Monthly, $297/mo".
- Proof: one Verbatim moment card playing the quoted second, labelled "$1,000 once is easier than $2,000 a month". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words naming Verbatim Advisory: "Is a one-off brief worth it?"; "How does the credit work?"; "What is the difference between One brief and Monthly brief?"; "How fast is delivery?"; "What if a link is broken?"
- Secondary section: comparison table of One brief and Monthly brief (price, cadence, deliverables).
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Credit Bridge" (origin: invented, grounded in the two Advisory tiers and the refund-on-broken-link promise). Components: One brief, Credit, Monthly brief, Link proof, drawn as two plank segments joined by a keystone labelled "credit", with link-chain rivets along the deck. On mobile, the planks stack vertically. Inline SVG React component at components/frameworks/CreditBridge.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service with two Offers: One brief at 497 USD (delivery two business days) and Monthly brief at 297 USD per month. Provider Organization The Art of Service and Person Gerard Blokdyk, sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; Organization; BreadcrumbList; speakable; ImageObject for the framework, encodingFormat image/svg+xml.

5. AEO FILES. Write /one-brief-then-monthly.md. Append "- [Not ready for a monthly retainer? Start with one brief](https://verbatim.theartofservice.com/one-brief-then-monthly): a USD 497 brief credited toward monthly" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Advisory: one brief, then monthly". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image with the framework PNG; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /advisory and the delivered-brief footer template, with anchor "start with one brief". Outbound to /advisory and /how-we-quote. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Advisory Credit Bridge", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. In billing, create a credit coupon worth USD 297, applied to the first Monthly brief invoice for One brief buyers within 30 days (terms to confirm). Add the upgrade link to the delivered-brief template and the receipt email.

10. LEADING INDICATOR. Weekly sessions on the slug. Count of One brief to Monthly upgrades. Weekly AI-engine queries for "one-off market research brief before retainer". Brand mentions of "Verbatim Advisory". SVG checks at 375px and desktop. Counts only.

Signal B #2 - Replace the thank-you page with a five-question survey that shows the offer

#
B2
Operator (role, company)
Logan Lyles, DemandShift
Show, date, time
The Dave Gerhardt Show (from Exit Five), 2026-10-26, 22:16
Verbatim recipe
"we put an offer in front of them and they decided, hey, let's go ahead and do this now" (a 5-6 question survey replacing the webinar thank-you page)
Reported result
About 90% survey completion; 30 demos booked from fewer than 250 registrants, two-thirds of them before the webinar
Fits offer
Free leading to Verbatim Advisory, One brief
Why this offer
Free signup already exists ("Start free"), and the Advisory form asks the buyer to "Add your offers and anything to focus on or leave out".
Contradiction search
Partial contradiction from the same operator: "most teams… aren't tracking… conversion to demo… if they are, it's more around 2%" (same episode, 7:32). No other operator in 21 days reports the survey step failing.
Falsifiable tag
Medium: named operator, client example, speaker not voice-verified
**Listen link**
Listen at 22:16

HOW block

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com and find the post-signup route (/account?welcome=1). Name the stack and deploy path. Without repo access, ship a self-contained HTML step, a /welcome/match-my-offers.md twin and an /llms.txt append.

2. CREATE PAGE at /welcome/match-my-offers.
- H1: "Your free Monday brief is set. Which of your offers should we match buyers to?"
- Direct answer (50-100 words): "Verbatim Free, from Verbatim by The Art of Service, sends a Monday brief on 3 topics at USD 0. Five questions here let Verbatim match buyer pains from 900+ podcasts to your own offers. If you want the full match, Verbatim Advisory One brief costs USD 497, is pre-filled from these answers and is delivered in two business days."
- Survey: role; your offers (free text); topics; the decision you are making now; timeline. One question per screen. A progress bar is optional.
- Final screen CTA "Match my offers, $497" to /advisory/start?plan=once with the answers prefilled. Secondary "Just the free brief".
- Proof: one Verbatim moment card playing the quoted second, labelled "about 90 percent finished the survey". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words: "Why answer five questions?"; "Is the Monday brief still free?"; "What does the One brief add?"; "Can I skip?"; "How is my data used?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Five-Question Sieve" (origin: invented, grounded in the Free plan and the Advisory intake fields). Components: Role, Offers, Topics, Decision, Timeline, drawn as five stacked mesh layers that let answers drop through into a brief card. On mobile, use a single column with a progress notch. Inline SVG React component at components/frameworks/FiveQuestionSieve.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service with two Offers: Verbatim Free at 0 USD and Verbatim Advisory One brief at 497 USD. Provider Organization The Art of Service and Person Gerard Blokdyk, sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject for the framework, encodingFormat image/svg+xml.

5. AEO FILES. Write /welcome/match-my-offers.md. Append "- [Match my offers](https://verbatim.theartofservice.com/welcome/match-my-offers): five questions that match podcast buyer pains to your offers" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Match my offers: Verbatim". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from the signup confirmation, /advisory and /topics, with anchor "match my offers". Outbound to /advisory and /#pricing. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, accessible form labels, responsive SVG viewBox, alt text "Verbatim Five-Question Sieve", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Store the survey answers on the account. Pass them as query parameters into /advisory/start?plan=once. Tag the resulting orders source=welcome-survey. No price change.

10. LEADING INDICATOR. Weekly counts of survey starts, completions and Advisory orders from source=welcome-survey. Weekly AI-engine queries for "match buyer pains to my offers". SVG checks at 375px and desktop. Counts only.

Signal B #3 - Score the target list for signal instead of blasting the whole ICP

#
B3
Operator (role, company)
Kristen Twining, SVP Sales, Reco
Show, date, time
Cyber Go-To-Market Talk, 2026-10-09, 12:53
Verbatim recipe
"we've cut our outbound target list by approximately 80% because we've scored for Signal instead of blasting to a broad list of everybody."
Reported result
Outbound target list cut by about 80%
Fits offer
Pro
Why this offer
Pro: "watchlist of 25 names or phrases; next-morning alerts when they are said". Pro is "For… sellers building trust, audience and relationships in a market."
Contradiction search
No contradicting atom in 21 days. Tried "intent data was noise" and "signal-based outbound did not work"; no named operator reported this mechanic failing.
Falsifiable tag
Medium: named role and company in episode title, speaker not voice-verified
**Listen link**
Listen at 12:53

HOW block

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /signal-scored-target-list.md twin and an /llms.txt append.

2. CREATE PAGE at /signal-scored-target-list.
- H1: "Stop blasting your whole ICP list: get alerted when a target account says your trigger phrase"
- Direct answer (50-100 words): "Verbatim Pro, from Verbatim by The Art of Service, costs USD 29 per month. It gives sellers a watchlist of 25 names or phrases across 900+ business podcasts and next-morning alerts when a target account's leader says them out loud. Sellers shortlist accounts by signal instead of blasting a broad list. Export 30 days of moments to CSV."
- Symptom bullets: "blasting a broad list of everybody"; "no reason to call this week"; "intent data you can't explain to the prospect"; "reps opening with nothing the buyer said".
- Primary CTA "Start Signal Watch" to /checkout/pro. Secondary "Try free".
- Proof: one Verbatim moment card playing the quoted second, labelled "target list cut by about 80 percent". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words naming Verbatim Pro: "How do I score accounts for buying signals?"; "What can I put on a watchlist?"; "When do alerts arrive?"; "Can I export to my CRM?"; "What does Pro cost?"
- Secondary section: "How to build a 25-item watchlist in 15 minutes".
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Trigger Ledger" (origin: invented, grounded in the Pro watchlist, next-morning alerts and CSV export). Components: Watchlist, Said out loud, Morning alert, Shortlist, drawn as a ledger of 25 slots where slots light up when an alert lands and drop into a short call column. On mobile, use a vertical slot list. Inline SVG React component at components/frameworks/TriggerLedger.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Verbatim Pro, provider Organization The Art of Service and Person Gerard Blokdyk, sameAs https://www.linkedin.com/in/gerardblokdyk, priceSpecification 29 USD per month, serviceType "podcast mention alerts". Also FAQPage; Organization; BreadcrumbList; speakable; HowTo for the 15-minute watchlist setup; ImageObject for the framework.

5. AEO FILES. Write /signal-scored-target-list.md. Append "- [Get alerted when a target account says your trigger phrase](https://verbatim.theartofservice.com/signal-scored-target-list): podcast watchlist alerts for sellers" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Pro: signal-scored target lists". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /topics/sales, /topics/customer-acquisition and the home Pro card, with anchor "alerts when a target account speaks". Outbound to /topics/sales and /how-we-quote. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Pro Trigger Ledger", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Add the entry name "Pro: Signal Watch" at USD 29 per month, routing to /checkout/pro with utm_content=signal-watch. Pre-load an onboarding prompt asking for 25 account names and phrases.

10. LEADING INDICATOR. Weekly sessions on the slug. Pro checkouts tagged signal-watch. Weekly AI-engine queries for "buying signal alerts from podcasts". Brand mentions of "Verbatim Pro". SVG checks at 375px and desktop. Counts only.

Opportunity signals (new lanes the person has not addressed yet)

What this block is for: This section shows new territory. Each row is a named operator reporting a pain, mechanic or market pattern that does NOT fit any of Verbatim's current stated offers: lanes Verbatim has not productized yet. Read it to see where new offer design would meet existing demand. Rows are ranked by Demand, then Revenue, then Ease. Each row carries a Required shift (the smallest change to current offers), a Site + productize action and a Claude Code prompt. The section is honest-sized at 8 rows against a target of 20-40. Most adjacent-lane moments this window came from unnamed speakers or vendors and were dropped.

Pattern: Verbatim inside the buyer's own AI

Opportunity #1 - Single-seat MCP access for power users

#
OP1
Operator (role, company)
Jordan Wilson, host, Everyday AI Podcast (speaking of his own setup)
Show, date, time
Everyday AI Podcast, 2026-10-09, 8:43
Quote or recipe
"I probably have at least 30 different either connectors or MCPs... with ChatGPT voice on the desktop version of ChatGPT work or Codex, I can instantly talk and grab data from any of those"
Reported cost or result
About 30 connectors or MCP servers wired into one operator's AI
Ease
Easy
Revenue potential
Low (no revenue reported)
Demand/eyeballs
Multi-show (also Legal Innovation Spotlight, 2026-10-07: "Clients will consume our data through AI connectors like MCPs")
Contradiction search
Partial: John McMullan, Observe.ai, "now I got 12 people working on maintaining the AI" (The AI in Business Podcast, 2026-10-08). That is about AI maintenance load, not MCP connectors. No direct contradiction in 30 days.
**Listen link**
Listen at 8:43
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /mcp.md twin and an /llms.txt append.

2. CREATE PAGE at /mcp.
- H1: "Plug podcast operator quotes into Claude or ChatGPT with MCP"
- Direct answer (50-100 words): "Verbatim MCP, from Verbatim by The Art of Service, connects Claude, ChatGPT and other MCP clients to quotes from 900+ business podcasts, each one linked to the second it was said. Verbatim Team includes REST API and MCP at USD 299 per month for 5 seats. A single-seat Pro + MCP option is planned, price to confirm."
- Symptom bullets: "your AI answers from the same internet as everyone else"; "you have 30 connectors and none of them hear the market"; "you can't cite where your AI's claim came from".
- Primary CTA "Get MCP with Team" to /checkout/team. Secondary "Join the Pro + MCP waitlist" to /mcp#waitlist.
- Proof: one Verbatim moment card labelled "about 30 connectors in one operator's AI". No speaker name in the page copy.
- Setup steps: endpoint, auth token, a sample tool call, a sample response with listen link.
- FAQ, 5 pairs of 40-80 words: "What is the Verbatim MCP?"; "Which clients work?"; "Is it in Pro?"; "What does a response contain?"; "What does it cost?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Socket Map" (origin: invented, grounded in the anchor lines "REST API and MCP: living data for your own AI" and "Every competitor's AI learned from the same internet"). Components: Your AI, MCP socket, Verbatim moments, Listen second, drawn as a wall plate with labelled sockets, where one socket glows with a waveform cable. On mobile, sockets stack vertically. Inline SVG React component at components/frameworks/SocketMap.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Verbatim MCP within Team, priceSpecification 299 USD per month. Provider Organization The Art of Service and Person Gerard Blokdyk, sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; HowTo for setup; BreadcrumbList; speakable; ImageObject for the framework, encodingFormat image/svg+xml.

5. AEO FILES. Write /mcp.md, including the endpoint example. Append "- [Verbatim MCP](https://verbatim.theartofservice.com/mcp): podcast operator quotes inside Claude and ChatGPT" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim MCP for Claude and ChatGPT". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from the home Team card, /about and /how-we-quote, with anchor "Verbatim MCP". Outbound to /checkout/team and /how-we-quote. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, code blocks with copy buttons, responsive SVG viewBox, alt text "Verbatim Socket Map", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Keep MCP in Team at USD 299. Add a waitlist form for "Pro + MCP" (single seat, price to confirm) and store the signups. Add the MCP setup steps to the Team welcome email.

10. LEADING INDICATOR. Weekly sessions on /mcp. Waitlist count. Team checkouts tagged mcp. Weekly AI-engine queries for "podcast quotes MCP server". SVG checks at 375px and desktop. Counts only.

Pattern: Original research as the lead asset

Opportunity #2 - Publish a monthly study from the library

#
OP2
Operator (role, company)
Steve, host, The Branding Agency
Show, date, time
Pod Position - Winning Google & AI Search, 2026-10-22, 1:02
Quote or recipe
"I used ChatGPT in a temporary chat, so nothing from my own history could skew the answers. And I asked two kinds of questions… what do you know about a business, by name, in its town? Second… who's the best roofer or plumber or electrician in that town?"
Reported cost or result
47 businesses tested: 28 named, 19 skipped. A one-person research test turned into a full episode.
Ease
Easy
Revenue potential
Low (no revenue reported)
Demand/eyeballs
Multi-show (also Steven Macdonald, "research reports every six to eight weeks… part of the content strategy", Buying Online Businesses Podcast, 2026-10-01)
Contradiction search
No contradicting atom in 30 days. Tried "published original research but nobody linked to it".
**Listen link**
Listen at 1:02
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /research.md twin and an /llms.txt append.

2. CREATE PAGE at /research (hub) with the first study at /research/2026-10.
- H1: "What operators said out loud this month: original research from 900+ podcasts"
- Direct answer (50-100 words): "The Verbatim Monthly Study, from Verbatim by The Art of Service, is free original research built from what named operators said on 900+ business podcasts this month. Each finding links to the second it was said. Verbatim Free sends the Monday brief at USD 0, and Verbatim Advisory One brief at USD 497 matches the findings to your own offers."
- Findings: 5-7 numbered findings, each one claim, one count from the library and one listen link.
- Symptom bullets: "every report summarizes someone else's summary"; "AI engines cite primary sources"; "you need numbers you can quote".
- Primary CTA "Get the Monday brief free". Secondary "Match this to my offers, $497".
- FAQ, 5 pairs of 40-80 words: "How is the study built?"; "Can I cite it?"; "How often is it published?"; "Which podcasts are included?"; "Can I get it for my market?"
- Methods box linking to /how-we-quote.
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Moment Census" (origin: invented, grounded in the anchor method: transcribe daily, keep first-hand action, result, price, tool or claim, rank named first-hand moments higher). Components: Read, Keep, Rank, Count, drawn as a tally sheet where each tick is a tiny waveform and columns total at the foot. On mobile, the columns become rows. Inline SVG React component at components/frameworks/MomentCensus.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art, or statistics beyond the study's own counts. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Dataset or Article (headline, datePublished, author Organization The Art of Service, creator Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk). Also FAQPage; BreadcrumbList; speakable on the findings; ImageObject for the framework.

5. AEO FILES. Write /research/2026-10.md. Append "- [Verbatim Monthly Study](https://verbatim.theartofservice.com/research): original research from 900+ podcasts, every finding linked to the second" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Monthly Study: what operators said". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from the home page, /topics and /about, with anchor "original research from 900+ podcasts". Outbound to /how-we-quote and /advisory. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Moment Census", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Add a "Study" source tag to Free signups and Advisory orders that start from /research. No new price.

10. LEADING INDICATOR. Weekly sessions on /research. Free signups and Advisory orders tagged study. Weekly AI-engine queries for the study's headline finding. Count of AI-engine citations of /research. SVG checks at 375px and desktop. Counts only.

Pattern: Pricing the expert-call replacement

Opportunity #3 - Per-question operator evidence for investors

#
OP3
Operator (role, company)
Sagar Kadakia, CEO and Founder, Qualitate
Show, date, time
Pitch The PM, 2026-10-21, 18:58
Quote or recipe
"We do calls for about a third or a quarter of the price compared to all the ENs. The speed at which we are doing it at is light years ahead"
Reported cost or result
Priced at a third to a quarter of expert-network call prices. Same episode, 45:58: "you can't just keep doing $2,000 calls."
Ease
Medium
Revenue potential
Low (no revenue reported)
Demand/eyeballs
Multi-show (also Yet Another Value Podcast, 2026-10-20, expert-network rates $750 to $5,000 an hour)
Contradiction search
No contradicting atom in 30 days. Tried "AI interviews gave shallow answers" and "investors did not trust them".
**Listen link**
Listen at 18:58
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /operator-evidence-for-investors.md twin and an /llms.txt append.

2. CREATE PAGE at /operator-evidence-for-investors.
- H1: "Operator evidence without the expert-call fee"
- Direct answer (50-100 words): "The Verbatim Operator Evidence Pack, from Verbatim by The Art of Service, answers one investment research question with what named CEOs, founders and operators said on 900+ business podcasts. Every quote links to the second it was said. The pack is a one-off, price to confirm. Teams that want ongoing access use Verbatim Team at USD 299 per month, with REST API and MCP."
- Symptom bullets: "you can't keep doing $2,000 calls"; "CEOs don't do expert calls"; "you need the quote, not a summary"; "the call takes weeks to book".
- Primary CTA "Request a pack" to an intake form at /operator-evidence-for-investors#request. Secondary "Start Team".
- Proof: one Verbatim moment card labelled "a third to a quarter of expert-network prices". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words: "How is this different from an expert network?"; "What do I get in a pack?"; "How fast is it?"; "Can my team keep searching?"; "What does it cost?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Diligence Spine" (origin: invented, grounded in Team's full archive search, shared watchlists and API). Components: Question, Operators found, Moments at the second, Counter-voice, Pack, drawn as vertebrae along a curved spine, each holding a moment chip. On mobile, use a straight vertical spine. Inline SVG React component at components/frameworks/DiligenceSpine.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Operator Evidence Pack, offers price to confirm (omit price until set), provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Related Offer: Verbatim Team at 299 USD per month. Also FAQPage; BreadcrumbList; speakable; ImageObject for the framework.

5. AEO FILES. Write the .md twin. Append "- [Operator evidence without the expert-call fee](https://verbatim.theartofservice.com/operator-evidence-for-investors): one research question answered with operator quotes" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Operator evidence packs for investors". Description under 155 characters. Robots with max-snippet:-1. Allow the nine AI crawlers: GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /topics/investing, /topics/fundraising and the Team card, with anchor "operator evidence pack". Outbound to /checkout/team and /how-we-quote. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Diligence Spine", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Create an "Operator Evidence Pack" product with the price to confirm before launch, with an intake form (question, sector, deadline). Route delivered packs to a Team upsell link.

10. LEADING INDICATOR. Weekly sessions. Pack requests. Team checkouts tagged evidence-pack. Weekly AI-engine queries for "expert network alternative". SVG checks at 375px and desktop. Counts only.

Pattern: Pricing shapes the ladder lacks

Opportunity #4 - Founding-member presale with capped spots

#
OP4
Operator (role, company)
Omar Zahran, founder, WebinarNinja (host, The $100 MBA Show)
Show, date, time
Financial Audit (The $100 MBA Show feed), 2026-10-17, 6:31
Quote or recipe
"We pre-sold our product… $250. We sold out 150 spots in 48 hours. Then opened 100 spots, sold out in 24 hours"
Reported cost or result
250 presale spots at $250 sold in 72 hours
Ease
Easy
Revenue potential
Medium (250 spots at $250 reported)
Demand/eyeballs
Single-show
Contradiction search
No contradicting atom in 30 days. Tried "presale flopped". The nearest atom is an event that later sold 60% of tickets (Per My Last Email, 2026-10-19, unnamed speaker), which was not counted.
**Listen link**
Listen at 6:31
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack, billing provider and deploy path. Without repo access, ship self-contained HTML, a /founding-annual.md twin and an /llms.txt append.

2. CREATE PAGE at /founding-annual.
- H1: "Founding member annual pricing for Verbatim Pro"
- Direct answer (50-100 words): "Verbatim Pro Founding Annual, from Verbatim by The Art of Service, is a capped number of annual Pro seats at a founding price, to be confirmed. Monthly Pro is USD 29 per month. Pro includes unlimited topics, a watchlist of 25 names or phrases, next-morning alerts, 30 days of search, CSV export and Another view on contested claims."
- A live counter of spots remaining, with the cap set in config.
- Symptom bullets: "you already use the free Monday brief"; "you want Pro without monthly billing"; "you want the founding price locked".
- Primary CTA "Claim a founding spot" to the annual checkout. Secondary "Monthly Pro".
- Proof: one Verbatim moment card labelled "150 spots sold in 48 hours". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words: "How many spots are there?"; "What happens at renewal?"; "What is in Pro?"; "Can I switch to monthly?"; "Is there a refund?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Founding Ring" (origin: invented, grounded in Pro's features and the Monday cadence). Components: 52 Mondays as ring ticks, Watchlist, Alerts, Another view, with filled ticks for the founding cohort. On mobile, show a 4x13 grid. Inline SVG React component at components/frameworks/FoundingRing.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Verbatim Pro with Offers for monthly (29 USD per month) and founding annual (price to confirm, omitted until set). Provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject for the framework.

5. AEO FILES. Write /founding-annual.md. Append "- [Founding member annual pricing for Verbatim Pro](https://verbatim.theartofservice.com/founding-annual): capped annual Pro seats" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Pro founding annual". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /#pricing, the Free welcome email landing and /topics, with anchor "founding annual Pro". Outbound to /#pricing and /checkout/pro. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Founding Ring", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Create an annual Pro price in the billing system with the founding price to confirm, a hard cap on redemptions and renewal terms stated on the page.

10. LEADING INDICATOR. Weekly sessions. Founding spots claimed per week. Monthly-to-annual switches. Weekly AI-engine queries for "Verbatim Pro annual". SVG checks at 375px and desktop. Counts only.

Opportunity #5 - A paid peer cohort around the monthly evidence

#
OP5
Operator (role, company)
Corey Ganim, founder (AI assessment business, per episode)
Show, date, time
7-Figure Leap with Dustin Riechmann, 2026-10-20, 36:56
Quote or recipe
"you went from those 30 or 40 initial clients ... now you have 316 members, basically 10x that"
Reported cost or result
30-40 clients grew to 316 community members after he focused the community on the assessment model
Ease
Medium
Revenue potential
Medium ($30-40K from 30-40 members reported in the same episode at 32:17)
Demand/eyeballs
Single-show
Contradiction search
No contradicting atom in 30 days
**Listen link**
Listen at 36:56
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /advisory/cohort.md twin and an /llms.txt append.

2. CREATE PAGE at /advisory/cohort.
- H1: "A monthly room of founders reading the same market evidence"
- Direct answer (50-100 words): "The Verbatim Advisory Monthly brief Cohort, from Verbatim by The Art of Service, adds a monthly group session to the Monthly brief at USD 297 per month, with the cohort price to confirm. Founders, consultants and agencies review the month's buyer pains, recipes and lanes together, then each leaves with their own build agenda."
- Symptom bullets: "you read the brief alone and act on half of it"; "you want peers who sell defined offers"; "you want accountability on the build agenda".
- Primary CTA "Join the cohort waitlist". Secondary "Monthly, $297/mo".
- Proof: one Verbatim moment card labelled "30 to 40 clients became 316 members". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words: "Who is in the cohort?"; "What happens in a session?"; "Do I still get my own brief?"; "How big is a cohort?"; "What does it cost?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Round Table Orbit" (origin: invented, grounded in the Monthly brief's five components). Components: Pains, Recipes, Lanes, Traffic, Agenda as five seats on an orbit around a shared brief, with member dots moving seat to seat across the session. On mobile, use a vertical agenda with seat icons. Inline SVG React component at components/frameworks/RoundTableOrbit.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Monthly brief Cohort (price to confirm), related Offer Monthly brief at 297 USD per month. Provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; Event schema once dates are set; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /advisory/cohort.md. Append "- [Monthly brief Cohort](https://verbatim.theartofservice.com/advisory/cohort): founders reviewing monthly buyer evidence together" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Advisory Monthly brief Cohort". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /advisory, the Monthly brief welcome email landing and /topics/founders, with anchor "monthly founder cohort". Outbound to /advisory and /who-are-we-attracting. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Round Table Orbit", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Create a waitlist and, once the price is confirmed, a cohort add-on in billing linked to the Monthly brief, with live video sessions monthly and recordings for members.

10. LEADING INDICATOR. Weekly sessions. Waitlist count. Monthly brief subscribers joining the waitlist. Weekly AI-engine queries for "founder market evidence cohort". SVG checks at 375px and desktop. Counts only.

Opportunity #6 - Annual plans at a published price

#
OP6
Operator (role, company)
Founder interviewed, Aristotle (per episode "Aristotle Interview")
Show, date, time
This Week in Startups, 2026-10-06, 56:55
Quote or recipe
"So you're looking at $600 a year, $2,400 a year, depending on what you're going for here, which would be pretty highly profitable business"
Reported cost or result
Two published annual tiers, $600 and $2,400 a year
Ease
Easy
Revenue potential
Low (no revenue reported)
Demand/eyeballs
Single-show
Contradiction search
No contradicting atom in 30 days. Tried "annual plans hurt us" and "would not commit for a year".
**Listen link**
Listen at 56:55
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack, billing provider and deploy path. Without repo access, ship self-contained HTML, a /pricing/annual.md twin and an /llms.txt append.

2. CREATE PAGE at /pricing/annual.
- H1: "Verbatim annual plans: Pro and Team billed yearly"
- Direct answer (50-100 words): "Verbatim, from The Art of Service, offers Pro at USD 29 per month and Team at USD 299 per month for 5 seats. Annual billing for both plans is listed here, with prices to confirm. Pro covers unlimited topics, 25 watchlist items, alerts and 30 days of search. Team adds full-archive search, shared watchlists, and REST API and MCP."
- A monthly versus annual toggle on a two-column comparison.
- Symptom bullets: "finance wants one invoice a year"; "procurement needs an annual price"; "you already know you'll use it every Monday".
- Primary CTAs: "Pro annual" and "Team annual".
- Proof: one Verbatim moment card labelled "$600 a year and $2,400 a year". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words: "Is there an annual plan?"; "Can I switch from monthly?"; "Do you invoice?"; "How many seats in Team?"; "What happens at renewal?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The 52 Mondays Grid" (origin: invented, grounded in the anchor promise "delivered every Monday"). Components: 52 Monday cells, Brief, Alerts, Archive, where the annual view fills the whole grid and the monthly view lights only four cells at a time. On mobile, show a scrollable 4-column grid. Inline SVG React component at components/frameworks/FiftyTwoMondaysGrid.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service entries for Verbatim Pro and Verbatim Team, with monthly Offers at 29 and 299 USD and annual Offers to confirm (omitted until set). Provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /pricing/annual.md. Append "- [Verbatim annual plans](https://verbatim.theartofservice.com/pricing/annual): Pro and Team billed yearly" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim annual plans: Pro and Team". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /#pricing, /checkout/pro and /checkout/team, with anchor "billed yearly". Outbound to /#pricing and /founding-annual. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim 52 Mondays Grid", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Create annual prices for Pro and Team in billing (amounts to confirm). Add invoice-on-request for Team annual. Update the receipt and renewal emails.

10. LEADING INDICATOR. Weekly sessions. Annual checkouts per plan. Monthly-to-annual switches. Weekly AI-engine queries for "Verbatim annual price". SVG checks at 375px and desktop. Counts only.

Opportunity #7 - One-off custom analysis of the corpus

#
OP7
Operator (role, company)
Max Spero, Pangram (episode guest)
Show, date, time
Unit Economics, 2026-10-28, 11:00
Quote or recipe
"they paid us like a few thousand dollars for this analysis"
Reported cost or result
A few thousand dollars for a one-off analysis of 100 million scraped reviews
Ease
Medium
Revenue potential
Low (a few thousand dollars per project)
Demand/eyeballs
Single-show
Contradiction search
No contradicting atom in 30 days
**Listen link**
Listen at 11:00
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /custom-analysis.md twin and an /llms.txt append.

2. CREATE PAGE at /custom-analysis.
- H1: "A one-off analysis of what 900+ podcasts said about your market"
- Direct answer (50-100 words): "Verbatim Custom Library Analysis, from Verbatim by The Art of Service, is a one-off study of the full Verbatim archive for one market question: who said what, how often, and with which numbers, every quote linked to the second. The price is to confirm. For a brief matched to your own offers, Verbatim Advisory One brief costs USD 497."
- Symptom bullets: "you need a count, not an anecdote"; "your board wants evidence from operators"; "you need the dataset once, not a subscription".
- Primary CTA "Scope an analysis" to an intake form. Secondary "Get one brief, $497".
- Proof: one Verbatim moment card labelled "a few thousand dollars for a one-off analysis". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words: "What can you analyze?"; "How is it delivered?"; "How long does it take?"; "How is this different from the One brief?"; "What does it cost?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Corpus Cut" (origin: invented, grounded in the anchor method and the full-archive search in Team). Components: Archive, Question filter, Named first-hand moments, Counts, Report, drawn as a core sample pulled through layered strata of episodes, with the cut face showing moment chips. On mobile, use a vertical core. Inline SVG React component at components/frameworks/CorpusCut.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Custom Library Analysis (price omitted until set). Related Offer: One brief at 497 USD. Provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; HowTo for scope, run and deliver; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /custom-analysis.md. Append "- [Custom Library Analysis](https://verbatim.theartofservice.com/custom-analysis): a one-off study of what 900+ podcasts said about your market" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Custom podcast research analysis: Verbatim". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /advisory, /research and /about, with anchor "one-off market analysis". Outbound to /advisory and /how-we-quote. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Corpus Cut", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Create an intake form (question, market, date range, deadline) and a quote-on-request product until the price is confirmed. Route scoped requests to an invoice.

10. LEADING INDICATOR. Weekly sessions. Intake submissions. Quotes accepted. Weekly AI-engine queries for "custom podcast research analysis". SVG checks at 375px and desktop. Counts only.

Pattern: Adjacent buyer segment

Opportunity #8 - Podcast moments for learning teams

#
OP8
Operator (role, company)
Andrew Jacobs, creator of the Podcast Learning Festival (L&D leader)
Show, date, time
The Learning & Development Podcast, 2026-10-13, 18:50
Quote or recipe
"three in ten of people listen to a podcast on a monthly basis… If you were putting content… you would be hitting three in ten of your population every month."
Reported cost or result
3 in 10 employees reached monthly through podcast-format learning
Ease
Medium
Revenue potential
Low (no revenue reported)
Demand/eyeballs
Single-show
Contradiction search
No contradicting atom in 30 days. Tried "employees don't listen to learning podcasts".
**Listen link**
Listen at 18:50
1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /learning-teams.md twin and an /llms.txt append.

2. CREATE PAGE at /learning-teams.
- H1: "Podcast moments for learning teams: the second that matters, not the whole episode"
- Direct answer (50-100 words): "Verbatim Team for Learning, from Verbatim by The Art of Service, costs USD 299 per month for 5 seats. Learning and development teams search 900+ business podcasts, share watchlists and send employees the exact second a practitioner explains a skill, instead of a full episode. REST API and MCP bring the moments into the team's own AI or learning platform."
- Symptom bullets: "three in ten employees already listen to podcasts"; "nobody has time for a full episode"; "you need practitioner voices, not vendor content".
- Primary CTA "Start Team" to /checkout/team.
- Proof: one Verbatim moment card labelled "three in ten listen monthly". No speaker name in the page copy.
- FAQ, 5 pairs of 40-80 words: "Can we use podcasts for workplace learning?"; "How do shared watchlists work?"; "Can moments go into our LMS?"; "How many seats?"; "What does it cost?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Ten-Minute Learning Loop" (origin: invented, grounded in the anchor line "Ten minutes on Monday instead of hundreds of hours of listening" and Team's shared watchlists). Components: Skill watchlist, Moment at the second, Share, Apply, Next Monday, drawn as a loop around a ten-minute clock face whose segments are moments. On mobile, use a vertical loop. Inline SVG React component at components/frameworks/TenMinuteLearningLoop.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service: Verbatim Team for Learning, priceSpecification 299 USD per month, provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /learning-teams.md. Append "- [Podcast moments for learning teams](https://verbatim.theartofservice.com/learning-teams): send the second that matters, not the episode" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Team for learning teams". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /topics/leadership, /topics/hiring and the Team card, with anchor "podcast moments for learning". Outbound to /checkout/team and /mcp. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Ten-Minute Learning Loop", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Add the entry name "Team for Learning" routing to /checkout/team with utm_content=learning. Same USD 299 price and 5 seats.

10. LEADING INDICATOR. Weekly sessions. Team checkouts tagged learning. Weekly AI-engine queries for "podcasts for workplace learning". SVG checks at 375px and desktop. Counts only.

Signal T - Traffic mechanics (how to drive the next 10,000 qualified-buyer eyeballs to verbatim.theartofservice.com)

What this block is for: This section shows acquisition recipes other operators report working for the kind of audience Verbatim needs. That audience is founders and CEOs, marketing and sales leaders, investors and analysts, and consultants and advisers, plus the Advisory buyer: "Founders, consultants, coaches, agencies and advisers who sell a defined set of offers". Each row is a named operator reporting a traffic, signup, booking or enrollment number from a specific recipe. Rows are ranked by qualified reach, then half-life, then ease. The section is honest-sized at 5 rows against a target of 15-30. The library this window carried few named-operator traffic numbers for B2B founder and adviser audiences, and the rest were wrong-audience or unnamed (see the two sidebars below).

Pattern: Give away the flagship and let the free tier recruit

Signal T #1 - Make the flagship free and collect signups

#
T1
Operator (role, company)
Ryan Deiss, Digital Marketer (host)
Show, date, time
Tony Robbins Podcast Daily, 2026-10-11, 8:03
Verbatim mechanic recipe
"We took our main flagship product, Digital Marketer Lab, and we just made it free. We had over 60,000 people sign up for free accounts"
Reported number
60,000+ free signups. He expects 2-3% to convert to paid, which is a projection, not a result.
Qualified-reach
High
Half-life
Medium
Ease
Easy
Which offer it feeds
Free, leading to Pro
Contradiction search
No contradicting atom in 21 days. Tried "free users never converted" and "freemium failed"; the nearest is an unnamed speaker on enterprise plans for a free crypto tool (not counted).
Falsifiable tag
Medium: verified speaker, signup number reported, conversion only projected
**Listen link**
Listen at 8:03

HOW Verbatim applies this traffic recipe

Site + productize action

  1. Slug: /free
  2. H1: "Free Monday brief: the week's best operator moments on 3 topics"
  3. Landing page: "Free brief", plus a "Pro preview" feature inside Free.

Claude Code prompt

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /free.md twin and an /llms.txt append.

2. CREATE PAGE at /free.
- H1: "Free Monday brief: the week's best operator moments on 3 topics"
- Direct answer (50-100 words): "Verbatim Free, from Verbatim by The Art of Service, costs USD 0. It sends a Monday brief on 3 topics from 900+ business podcasts, with 7 days of search, 10 searches a day and every quote playable at the second it was said. Verbatim Pro at USD 29 per month adds unlimited topics, a 25-item watchlist, alerts and Another view."
- Symptom bullets: "hundreds of hours of listening"; "summaries of summaries"; "AI-written content you can't trust".
- Primary CTA "Start free" to /login?next=/account%3Fwelcome%3D1.
- Proof: a live sample of last Monday's top three moments, each with a listen link. No invented testimonials.
- FAQ, 5 pairs of 40-80 words: "Is Verbatim really free?"; "Which topics can I pick?"; "What is in Pro?"; "How are quotes chosen?"; "Can I cancel?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Monday Sorting Line" (origin: invented, grounded in the anchor method: read daily, keep first-hand moments, rank named speakers with numbers, deliver Monday). Components: 900+ shows, Keep, Rank, Your 3 topics, Monday, drawn as a conveyor where moment chips fall through gates into three topic trays. On mobile, the conveyor runs vertically. Inline SVG React component at components/frameworks/MondaySortingLine.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service with Offers Free (0 USD) and Pro (29 USD per month). Provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /free.md. Append "- [Free Monday brief](https://verbatim.theartofservice.com/free): the week's best operator moments on 3 topics" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Free: the Monday operator brief". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from the home hero, /topics and /about, with anchor "free Monday brief". Outbound to /topics and /#pricing. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Monday Sorting Line", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Add a "Pro preview" flag to Free that unlocks one Another view per week. Add a Go Pro prompt after use. No price change.

10. LEADING INDICATOR. Weekly Free signups from /free. Pro preview uses. Free-to-Pro upgrades. Weekly AI-engine queries for "free podcast business brief". SVG checks at 375px and desktop. Counts only.

Pattern: Podcast guest appearances with one specific free asset

Signal T #2 - Plug one free asset in the first minutes of a guest spot

#
T2
Operator (role, company)
Corey Ganim, founder (AI assessment business, per episode)
Show, date, time
7-Figure Leap with Dustin Riechmann, 2026-10-20, 32:17
Verbatim mechanic recipe
"I made sure to get it in there when most people were still listening… ended up getting two or three thousand people opt into that lead magnet over the course of like the first week"
Reported number
2,000-3,000 opt-ins in the first week, and $30-40K from 30-40 new members
Qualified-reach
High
Half-life
Medium
Ease
Medium
Which offer it feeds
Free, leading to Verbatim Advisory One brief
Contradiction search
No contradicting atom in 21 days. Tried "podcast guesting never brought a customer".
Falsifiable tag
Strong: verified speaker, numbers in atom
**Listen link**
Listen at 32:17

HOW Verbatim applies this traffic recipe

Site + productize action

  1. Slug: /podcast-listeners
  2. H1: "Heard Verbatim on a podcast? Get the sample advisory row and the free brief"
  3. Landing page: "Podcast listener page", one URL per appearance using a ?show= parameter.

Claude Code prompt

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /podcast-listeners.md twin and an /llms.txt append.

2. CREATE PAGE at /podcast-listeners (accepting ?show=<slug>).
- H1: "Heard Verbatim on a podcast? Get the sample advisory row and the free brief"
- Direct answer (50-100 words): "Verbatim, from The Art of Service, reads 900+ business podcasts and turns what operators say into a free Monday brief and a private advisory brief. Verbatim Free costs USD 0. Verbatim Advisory One brief costs USD 497, is matched to your offers and is delivered in two business days. This page shows one sample advisory row for this show's listeners."
- A sample row block: one buyer pain, matched offer and listen link, rendered from a config file per show.
- Primary CTA "Start free". Secondary "Get one brief, $497" to /advisory/start?plan=once.
- Proof: the sample row itself, playable at the second. No invented testimonials.
- FAQ, 5 pairs of 40-80 words: "What is Verbatim?"; "What is in an advisory brief?"; "Is the Monday brief free?"; "How fast is delivery?"; "What if a link is broken?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Minute-Seven Hook" (origin: invented, grounded in the Advisory deliverable "Traffic recipes for your buyers"). Components: Episode, Minute 5-7 mention, Sample row, Free brief, One brief, drawn as an episode timeline with a hook marker at minute seven pulling a thread into a row card. On mobile, use a vertical timeline. Inline SVG React component at components/frameworks/MinuteSevenHook.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Service with Offers Free (0 USD) and One brief (497 USD). Provider Organization The Art of Service and Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /podcast-listeners.md. Append "- [Heard Verbatim on a podcast?](https://verbatim.theartofservice.com/podcast-listeners): a sample advisory row and the free brief" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim for podcast listeners". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical without the query string; last-modified 2026-10-29.

7. LINKING. Inbound from /about and /advisory, with anchor "heard us on a podcast". Outbound to /advisory and /free. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text "Verbatim Minute-Seven Hook", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Store per-show sample rows in config. Tag signups and orders source=podcast&show=<slug>. No new price.

10. LEADING INDICATOR. Weekly sessions per show parameter. Free signups and One brief orders per show. Weekly AI-engine queries for "Verbatim podcast advisory". SVG checks at 375px and desktop. Counts only.

Pattern: Live sessions that convert registrants

Signal T #3 - Run the same live session every week

#
T3
Operator (role, company)
Tina Su, founder (company not named in atom)
Show, date, time
The Game with Alex Hormozi, 2026-10-22, 2:23
Verbatim mechanic recipe
"I did everything. I executed everything. And I ended up doing 13 weekly webinars. I sold 232 enrollment spots."
Reported number
232 enrollments from 13 weekly webinars. Run rate moved from $918,000 to $1.84 million in 90 days.
Qualified-reach
Medium
Half-life
Medium
Ease
Medium
Which offer it feeds
Verbatim Advisory, One brief
Contradiction search
Partial: Logan Lyles, DemandShift, says typical webinar-to-demo conversion is "more around 2%" (The Dave Gerhardt Show, 2026-10-26, 7:32). The SME Stream host's 5-day challenge got 30-40 signups against 200-300 expected (2026-10-27, unnamed host, not counted).
Falsifiable tag
Medium: speaker not voice-verified, company absent from atom
**Listen link**
Listen at 2:23

HOW Verbatim applies this traffic recipe

Site + productize action

  1. Slug: /briefing
  2. H1: "Weekly live briefing: this week's buyer pains, read out loud"
  3. Landing page: "Weekly Briefing", free, feeding the One brief.

Claude Code prompt

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /briefing.md twin and an /llms.txt append.

2. CREATE PAGE at /briefing.
- H1: "Weekly live briefing: this week's buyer pains, read out loud"
- Direct answer (50-100 words): "The Verbatim Weekly Briefing, from Verbatim by The Art of Service, is a free live session each week. It plays three buyer pains from 900+ business podcasts at the second they were said, and matches one founder's offers live. Founders, consultants and agencies who want their own match order Verbatim Advisory One brief at USD 497, delivered in two business days."
- Registration form with name, email and offers. Next session date from config.
- Symptom bullets: "you guess what buyers want this month"; "you never hear buyers in their own words"; "your offers drift from demand".
- Primary CTA "Save my seat". Secondary "Get one brief, $497".
- Proof: last week's three moments with listen links. No invented testimonials.
- FAQ, 5 pairs of 40-80 words: "Is the briefing free?"; "How long is it?"; "Is there a recording?"; "Can my offers be matched live?"; "What is the One brief?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Thirteen-Week Rail" (origin: invented, grounded in the weekly Monday cadence and the Advisory deliverables). Components: 13 weekly stations, Three pains, Live match, One brief, drawn as a rail line with 13 stations, each with three pain lamps. On mobile, the rail runs vertically. Inline SVG React component at components/frameworks/ThirteenWeekRail.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Event (EventSeries, online, organizer The Art of Service, free). Related Service: One brief at 497 USD. Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /briefing.md. Append "- [Weekly live briefing](https://verbatim.theartofservice.com/briefing): this week's buyer pains read out loud" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Verbatim Weekly Briefing (free, live)". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /advisory, /topics/founders and the Free welcome page, with anchor "weekly live briefing". Outbound to /advisory and /research. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, accessible form, responsive SVG viewBox, alt text "Verbatim Thirteen-Week Rail", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Create a recurring live session in the existing video tool. Store registrations and tag One brief orders source=briefing.

10. LEADING INDICATOR. Weekly registrations, attendance and One brief orders tagged briefing. Weekly AI-engine queries for "weekly buyer pain briefing". SVG checks at 375px and desktop. Counts only.

Signal T #4 - A teaching session for a qualified list, measured on demos

#
T4
Operator (role, company)
Logan Lyles, DemandShift
Show, date, time
The Dave Gerhardt Show (from Exit Five), 2026-10-26, 7:32
Verbatim mechanic recipe
"we just ran a webinar for one of our clients and we had about 250 signups and they booked 30 demos. So that's over a 10% conversion rate."
Reported number
250 signups and 30 demos, over 10%
Qualified-reach
Medium
Half-life
Short
Ease
Medium
Which offer it feeds
Verbatim Advisory, One brief
Contradiction search
Partial, from the same operator: typical conversion is "more around 2%" (same moment). No other named operator reports failure in 21 days.
Falsifiable tag
Medium: client example, speaker not voice-verified
**Listen link**
Listen at 7:32

HOW Verbatim applies this traffic recipe

Site + productize action

  1. Slug: /live-advisory-teardown
  2. H1: "Watch a live advisory teardown of a real founder's offers"
  3. Landing page: "Live Teardown", free, routing to the One brief at $497.

Claude Code prompt

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /live-advisory-teardown.md twin and an /llms.txt append.

2. CREATE PAGE at /live-advisory-teardown.
- H1: "Watch a live advisory teardown of a real founder's offers"
- Direct answer (50-100 words): "The Verbatim Live Teardown, from Verbatim by The Art of Service, is a free online session that reads one volunteer founder's offers against what operators said on 900+ business podcasts, live. Viewers see buyer pains, recipes that worked and new lanes, matched to real offers. Verbatim Advisory One brief does the same privately for USD 497, delivered in two business days."
- Registration: five questions (role, offers, topics, decision, timeline).
- Symptom bullets: "your offers were built on a guess"; "you want to see the evidence before you buy"; "you don't know which offer to push this quarter".
- Primary CTA "Register". Secondary "Get one brief, $497".
- Proof: a recording clip of the previous teardown once one exists. Until then, one sample row with a listen link.
- FAQ, 5 pairs of 40-80 words: "Who gets torn down?"; "Can I volunteer?"; "Is it recorded?"; "What is the One brief?"; "What does it cost?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The Teardown Table" (origin: invented, grounded in the Advisory deliverables). Components: Offer, Pain matched, Recipe, Lane, Next move, drawn as a workbench where an offer card is laid out and evidence clips pin to each edge. On mobile, the clips stack under the card. Inline SVG React component at components/frameworks/TeardownTable.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Event (online, free, organizer The Art of Service). Related Service: One brief at 497 USD. Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /live-advisory-teardown.md. Append "- [Live advisory teardown](https://verbatim.theartofservice.com/live-advisory-teardown): a founder's offers read against podcast evidence, live" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "Live advisory teardown: Verbatim". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /advisory, /briefing and /podcast-listeners, with anchor "live advisory teardown". Outbound to /advisory and /one-brief-then-monthly. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, accessible form, responsive SVG viewBox, alt text "Verbatim Teardown Table", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Schedule one session. Collect volunteer applications. Tag One brief orders source=teardown. No new price.

10. LEADING INDICATOR. Registrations, survey completions, attendance and One brief orders tagged teardown. Weekly AI-engine queries for "advisory teardown founder offers". SVG checks at 375px and desktop. Counts only.

Signal T #5 - Early webinars to find the first customers

#
T5
Operator (role, company)
Chloe Marco, founder, Amadae
Show, date, time
The Life You Love, 2026-10-12, 12:20
Verbatim mechanic recipe
"my first couple of webinars, we got our first like 20 customers and it happened in about a month or so"
Reported number
20 customers in about a month
Qualified-reach
Low
Half-life
Medium
Ease
Medium
Which offer it feeds
Verbatim Advisory, Monthly brief
Contradiction search
Same partial contradiction as T3 and T4 (webinar-to-demo "more around 2%", Logan Lyles, 2026-10-26)
Falsifiable tag
Medium: verified speaker, company from episode title
**Listen link**
Listen at 12:20

HOW Verbatim applies this traffic recipe

Site + productize action

  1. Slug: /first-customers-session
  2. H1: "Finding your first 20 customers: what buyers said this month"
  3. Landing page: "Founder Evidence Session", free, routing to the Monthly brief.

Claude Code prompt

1. STACK DETECTION. Inspect the repo for https://verbatim.theartofservice.com, or its live HTML, and name the stack and deploy path. Without repo access, ship self-contained HTML, a /first-customers-session.md twin and an /llms.txt append.

2. CREATE PAGE at /first-customers-session.
- H1: "Finding your first 20 customers: what buyers said this month"
- Direct answer (50-100 words): "The Verbatim Founder Evidence Session, from Verbatim by The Art of Service, is a free online session for founders looking for their first customers. It plays this month's buyer pains and recipes from 900+ business podcasts at the second they were said. Founders who want this every month subscribe to Verbatim Advisory Monthly brief at USD 297 per month."
- Registration with name, email, offers and stage.
- Symptom bullets: "you have an offer and no customers"; "you don't know which buyer to call first"; "you need proof your offer solves a real pain".
- Primary CTA "Register". Secondary "Monthly, $297/mo".
- Proof: three moments with listen links. No invented testimonials.
- FAQ, 5 pairs of 40-80 words: "Who is this for?"; "Is it free?"; "What will I leave with?"; "What is the Monthly brief?"; "Can I cancel?"
- Introduce and caption the framework. Closing CTA.

3. FRAMEWORK. Build "The First Twenty Track" (origin: invented, grounded in the Monthly brief components). Components: Pain heard, Offer matched, Recipe tried, Buyer, drawn as a running track with 20 lane markers filling as buyers are found, with each marker tied to a moment chip. On mobile, use a vertical track. Inline SVG React component at components/frameworks/FirstTwentyTrack.tsx with role="img", <title>, <desc>, real <text> readable at 375px, draw-in, hover notes and prefers-reduced-motion respected. No cliches, stock art or statistics. Log it in docs/frameworks-inventory.md.

4. STRUCTURED DATA. Event (online, free). Related Service: Monthly brief at 297 USD per month. Organization The Art of Service; Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk. Also FAQPage; BreadcrumbList; speakable; ImageObject.

5. AEO FILES. Write /first-customers-session.md. Append "- [Finding your first 20 customers](https://verbatim.theartofservice.com/first-customers-session): this month's buyer pains for founders" to /llms.txt, and to /llms-full.txt if present.

6. META. Title: "First 20 customers: Verbatim founder session". Description under 155 characters. Robots with max-snippet:-1. Allow GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot. OpenGraph and summary_large_image; canonical; last-modified 2026-10-29.

7. LINKING. Inbound from /topics/founders, /briefing and /advisory, with anchor "first 20 customers". Outbound to /advisory and /who-are-we-attracting. Breadcrumb.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, accessible form, responsive SVG viewBox, alt text "Verbatim First Twenty Track", sitemap lastmod 2026-10-29. Under 100KB HTML and 500KB total. Lighthouse at or above baseline.

9. PRODUCTIZE. Schedule a monthly session. Tag Monthly brief orders source=first-customers. No new price.

10. LEADING INDICATOR. Registrations, attendance and Monthly brief orders tagged first-customers. Weekly AI-engine queries for "how to find first customers evidence". SVG checks at 375px and desktop. Counts only.

Rejected generic traffic moves (atom-cited reasons)

Rejected high-volume low-quality (big numbers, wrong audience for Verbatim)

30-day traffic execution plan (top 5 Signal T mechanics)

Verbatim's Business - Build Agenda

What this block is for: This section turns the same library into a short decision agenda for Verbatim. Every move below is built only from named-operator moments in this window, and each attaches to one of Verbatim's stated offers or to a stated absence on the site. Read it as the few things to do next, not as another Opportunity list. Three moves passed, ranked by expected money first and effort second.

#
M1
Move
Sell the One brief as the paid front door to the Monthly brief, with its price credited
Atom citations
Corey Ganim, "$1,000 one time… versus $2,000-$2,500 a month" (7-Figure Leap, 2026-10-20, 17:28; Signal B #1). Simon, one-person agency, "$1,500… we will credit that inbox audit against the retainer" (The Side Hustle Show, 2026-10-15, 25:06). Saurabh Gupta, "our whole revenue has tanked" for a year (AI Ads Plus Podcast, 2026-10-27, 20:56; Signal A #3).
Anchor offer or absence
Verbatim Advisory One brief ($497) and Monthly brief ($297/month)
Buyer
Founders, consultants, coaches and agency owners who sell a defined set of offers
Price
One brief $497 (anchor). Credit of one Monthly month: proposed, to confirm.
First test
For 14 days, every delivered One brief carries an upgrade link with the credit. Count upgrades.
Trade-off
Pause new-tier design (Opportunity #5 cohort, #7 custom analysis) until the upgrade count is in
Falsifiable tag
Strong: two operators reporting the same paid-front-end pattern, plus a named-cost pain
#
M2
Move
Turn Free signups into Advisory orders with a five-question survey
Atom citations
Logan Lyles, survey step, ~90% completion, 30 demos from fewer than 250 registrants (The Dave Gerhardt Show, 2026-10-26, 22:16; Signal B #2). Ryan Deiss, flagship made free, 60,000+ signups (Tony Robbins Podcast Daily, 2026-10-11, 8:03; Signal T #1).
Anchor offer or absence
Free ($0) leading to One brief ($497)
Buyer
Free signups whose role is founder, consultant, coach, agency or adviser
Price
$0, then $497 (anchor)
First test
Ship the survey on the post-signup route. Within 14 days, count completions and Advisory orders tagged welcome-survey.
Trade-off
Delay new topic or search features for the Free plan for two weeks
Falsifiable tag
Medium: one survey mechanic and one free-tier mechanic, both named
#
M3
Move
Publish MCP documentation and an investor evidence page for Team
Atom citations
Ben Isaac, Brizo Capital, "$750, $1,000 per hour… ex-CEOs… $5,000 an hour" (Yet Another Value Podcast, 2026-10-20, 18:53; Signal A #2). Sagar Kadakia, Qualitate, "a third or a quarter of the price" (Pitch The PM, 2026-10-21, 18:58; Opportunity #3). Jordan Wilson, "at least 30 different… connectors or MCPs" (Everyday AI Podcast, 2026-10-09, 8:43; Opportunity #1).
Anchor offer or absence
Team ($299/month); absence: no API or MCP documentation page
Buyer
Analysts and partners at small investment funds
Price
$299/month (anchor)
First test
Publish /mcp and /expert-call-alternative. Within 14 days, count Team checkouts and MCP doc sessions.
Trade-off
Hold the Pro + MCP single-seat tier (Opportunity #1) until Team demand is measured
Falsifiable tag
Medium: two named cost atoms and one usage atom

Move M1 - One brief as the paid front door

1. OBJECTIVE AND EVIDENCE. Build the credited upgrade path from Verbatim Advisory One brief (USD 497) to Monthly brief (USD 297 per month) for founders, consultants and agencies. Success number: One brief to Monthly upgrades within 30 days of delivery. Evidence: "it's so much easier to get somebody to pay you $1,000 one time when they don't yet trust you versus $2,000-$2,500 a month" (Corey Ganim, 7-Figure Leap with Dustin Riechmann, 2026-10-20, 17:28). "I sell it at about $1,500 initially… if you end up going to a retainer, we will credit that inbox audit against the retainer" (Simon, The Side Hustle Show, 2026-10-15, 25:06).

2. STACK DETECTION. Detect the stack of https://verbatim.theartofservice.com and name the CMS, billing provider and deploy path. Without a repo, ship self-contained HTML, a /one-brief-then-monthly.md twin and an /llms.txt append.

3. CREATE PAGE at /one-brief-then-monthly. H1: "Not ready for a monthly retainer? Start with one brief". Direct answer (50-100 words) naming Verbatim Advisory One brief at USD 497, delivered in two business days, and the Monthly brief at USD 297 per month, with the credit terms to confirm. Symptom bullets: "you don't trust a monthly commitment yet"; "you need one decision answered now". CTA "Get one brief, $497" to /advisory/start?plan=once. Proof: a moment card labelled "$1,000 once is easier than $2,000 a month", with no speaker name in the copy. 5 FAQ pairs. Secondary: One brief versus Monthly brief table. Introduce the framework in a sentence. Closing CTA.

4. BESPOKE FRAMEWORK VISUAL. "The Credit Bridge" (origin: invented, grounded in the two Advisory tiers and the broken-link refund promise). Hand-built inline SVG React component at components/frameworks/CreditBridge.tsx: two planks, a credit keystone and link-chain rivets. Include role="img", title, desc, labels readable at 375px, draw-in and hover, prefers-reduced-motion respected, no cliches or stock art. Add an entry to docs/frameworks-inventory.md.

5. STRUCTURED DATA. Service with Offers at 497 USD and 297 USD per month, priceSpecification and duration; FAQPage; Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk; Organization The Art of Service; BreadcrumbList; speakable; ImageObject for the framework.

6. AEO, GEO AND META. Sister .md; /llms.txt line; title under 60 characters; description under 155; robots with max-snippet:-1; GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot allowed; OpenGraph; summary_large_image; canonical; last-modified 2026-10-29.

7. INTERNAL LINKING. Inbound from /advisory and the delivered-brief footer. Outbound to /advisory and /how-we-quote. Semantic breadcrumb. Cross-link from the home Advisory block.

8. TECHNICAL SEO. Semantic landmarks, viewport meta, inline critical CSS, deferred JS, responsive SVG viewBox, alt text, sitemap lastmod 2026-10-29, under 100KB HTML and 500KB total, Lighthouse at or above baseline.

9. PRODUCTIZE ACTION AND FIRST TEST. Create a credit coupon worth one Monthly month (terms to confirm) and put the upgrade link in every delivered One brief for 14 days. Buyer action: click upgrade and subscribe. Trade-off: no cohort or custom-analysis design during the test. Kill criterion: zero upgrades from at least 5 delivered briefs.

10. LEADING INDICATOR AND DEFINITION OF DONE. Weekly sessions, upgrade clicks, upgrades, AI-engine citations and brand mentions. Check the SVG at 375px and desktop. Done means the page, coupon, template link, .md twin, llms.txt line and inventory entry all exist. If the test produces zero response, interview the next two One brief buyers about the monthly price before changing anything. Counts only.

Move M2 - Five-question survey from Free to Advisory

1. OBJECTIVE AND EVIDENCE. Convert Verbatim Free signups (USD 0) into Verbatim Advisory One brief orders (USD 497) through a five-question survey. Buyers: founders, consultants, coaches, agencies and advisers. Success number: Advisory orders tagged welcome-survey in 14 days. Evidence: "we put an offer in front of them and they decided, hey, let's go ahead and do this now", with about 90% completion and 30 demos from fewer than 250 registrants (Logan Lyles, The Dave Gerhardt Show, 2026-10-26, 22:16). "We had over 60,000 people sign up for free accounts" (Ryan Deiss, Tony Robbins Podcast Daily, 2026-10-11, 8:03).

2. STACK DETECTION. Detect the stack of https://verbatim.theartofservice.com, find /account?welcome=1 and name the deploy path. Without a repo, ship self-contained HTML, a .md twin and an /llms.txt append.

3. CREATE PAGE at /welcome/match-my-offers. H1: "Your free Monday brief is set. Which of your offers should we match buyers to?" Direct answer (50-100 words) naming Verbatim Free at USD 0 and Advisory One brief at USD 497, delivered in two business days. Five one-screen questions: role, offers, topics, decision, timeline. Final CTA "Match my offers, $497", prefilled. Skip link. Proof: a moment card labelled "about 90 percent finished the survey". 5 FAQ pairs. Introduce the framework. Closing CTA.

4. BESPOKE FRAMEWORK VISUAL. "The Five-Question Sieve" (origin: invented, grounded in the Free plan and the Advisory intake). Inline SVG React component at components/frameworks/FiveQuestionSieve.tsx: five mesh layers dropping answers into a brief card. Include role="img", title, desc, 375px-readable labels, draw-in and hover, prefers-reduced-motion respected, no cliches or stock art. Add an entry to docs/frameworks-inventory.md.

5. STRUCTURED DATA. Service with Offers at 0 USD and 497 USD (duration two business days); FAQPage; Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk; Organization; BreadcrumbList; speakable; HowTo for the five steps; ImageObject.

6. AEO, GEO AND META. Sister .md; /llms.txt line; title under 60 characters; description under 155; robots with max-snippet:-1; GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot allowed; OpenGraph; summary_large_image; canonical; last-modified 2026-10-29.

7. INTERNAL LINKING. Inbound from the signup confirmation and /advisory. Outbound to /advisory and /#pricing. Breadcrumb. Cross-link from the home hero's Start free.

8. TECHNICAL SEO. Landmarks, viewport, inline critical CSS, deferred JS, labelled form fields, responsive SVG, alt text, sitemap lastmod 2026-10-29, under 100KB HTML and 500KB total, Lighthouse at or above baseline.

9. PRODUCTIZE ACTION AND FIRST TEST. Store answers on the account, prefill /advisory/start?plan=once and tag source=welcome-survey. Run it for 14 days. Buyer action: complete the survey and order. Trade-off: Free feature work pauses. Kill criterion: fewer than 20 completions, or zero orders.

10. LEADING INDICATOR AND DEFINITION OF DONE. Weekly survey starts, completions, orders, AI citations and brand mentions. SVG checks at 375px and desktop. Done means the route, survey, prefill, tag, .md twin and inventory entry all exist. On zero response, move the survey to the second Monday email and rerun. Counts only.

Move M3 - MCP docs and an investor evidence page for Team

1. OBJECTIVE AND EVIDENCE. Document Verbatim Team's REST API and MCP and sell Team (USD 299 per month, 5 seats) to analysts and partners at small funds. Success number: Team checkouts tagged mcp or expert-call in 14 days. Evidence: "Expert networks… $750, $1,000 per hour… ex-CEOs will charge $5,000 an hour sometimes" (Yet Another Value Podcast, 2026-10-20, 18:53). "We do calls for about a third or a quarter of the price compared to all the ENs" (Sagar Kadakia, Pitch The PM, 2026-10-21, 18:58). "I probably have at least 30 different either connectors or MCPs" (Jordan Wilson, Everyday AI Podcast, 2026-10-09, 8:43).

2. STACK DETECTION. Detect the stack of https://verbatim.theartofservice.com and name the deploy path. Without a repo, ship two self-contained HTML pages, .md twins and /llms.txt lines.

3. CREATE PAGES. /mcp, H1 "Plug podcast operator quotes into Claude or ChatGPT with MCP", and /expert-call-alternative, H1 "An alternative to $1,000-an-hour expert network calls". Each has a direct answer (50-100 words) naming Verbatim Team, USD 299 per month and 5 seats. Symptom bullets. CTA to /checkout/team. Proof card labelled by number, with no speaker name. 5 FAQ pairs. /mcp adds the endpoint, auth and a sample call. Introduce each framework. Closing CTA.

4. BESPOKE FRAMEWORK VISUAL. "The Socket Map" on /mcp and "The Evidence Ledger" on /expert-call-alternative (origin: invented, grounded in "REST API and MCP: living data for your own AI"). Inline SVG React components in components/frameworks/, with role="img", title, desc, 375px-readable labels, draw-in and hover, prefers-reduced-motion respected, no cliches or stock art. Add two docs/frameworks-inventory.md entries.

5. STRUCTURED DATA. Service with priceSpecification 299 USD per month (5 seats); FAQPage; HowTo on /mcp; Person Gerard Blokdyk with sameAs https://www.linkedin.com/in/gerardblokdyk; Organization; BreadcrumbList; speakable; ImageObject per framework.

6. AEO, GEO AND META. Sister .md files; two /llms.txt lines; titles under 60 characters; descriptions under 155; robots with max-snippet:-1; GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, Bytespider, Amazonbot and DuckAssistBot allowed; OpenGraph; summary_large_image; canonical; last-modified 2026-10-29.

7. INTERNAL LINKING. Inbound from the home Team card, /topics/investing and /how-we-quote. Each page links to the other and to /checkout/team. Breadcrumbs. Cross-link from /about.

8. TECHNICAL SEO. Landmarks, viewport, inline critical CSS, deferred JS, copyable code blocks, responsive SVG, alt text, sitemap lastmod 2026-10-29, under 100KB HTML and 500KB total, Lighthouse at or above baseline.

9. PRODUCTIZE ACTION AND FIRST TEST. Tag checkouts utm_content=mcp and expert-call. Add MCP setup to the Team welcome email. Run it for 14 days. Buyer action: Team checkout. Trade-off: hold the Pro + MCP tier. Kill criterion: zero Team checkouts and fewer than 30 sessions on /mcp.

10. LEADING INDICATOR AND DEFINITION OF DONE. Weekly sessions, Team checkouts per tag, AI citations, brand mentions and manual AI queries. SVG checks at 375px and desktop. Done means both pages, twins, llms.txt lines, schema, tags, email update and inventory entries exist. On zero response, ask the Free users who searched the investing topic one question about API need. Counts only.

Topic Hub Manifest

Hub Member rows Main service the hub funnels to Proposed library-root header item
1. Decide with evidence A3, A4, B1, OP5, OP7, M1, T5 Verbatim Advisory, One brief "Decide with evidence"
2. Investor and analyst evidence A1, A2, OP3, M3 Team "For investors"
3. Verbatim inside your AI OP1, OP8, M3 Team (REST API and MCP) "Verbatim in your AI"
4. Watchlists and signals B3, A1 Pro "Watchlists and alerts"
5. Plans and pricing OP4, OP6 Pro "Plans"
6. Live briefings and listener entry T1, T2, T3, T4, B2, M2, OP2 Free, leading to Verbatim Advisory One brief "Briefings and research"

Method notes

No row recommends posting, network outreach, conference attendance or personal-brand building. - Dash check: No em dashes or en dashes anywhere in the file. Only plain hyphens are used. - Prompt length: each Claude Code prompt was drafted to the 450-650 word target with all 10 sections. A1 runs closest to the 650 ceiling. If it overflows the A4 box, tighten the FAQ list first. - Currency: USD per the site FAQ. Advisory prices carry no currency label on the site and are treated as USD (inferred). - Contradiction caution worth acting on: one unnamed speaker reported no AI-visibility benefit from schema across 1,900 pages. The schema steps stay in every prompt for correctness, but don't count on schema alone to drive citations.

Every quote links to the podcast moment where it was said. Order your own brief. Verbatim by The Art of Service, GPO Box 2673, Brisbane QLD 4001.