Product Spec — The Prospect Call System ($97)

Cole, 2026-08-11. Spec only — nothing built.

Name is open. Reid's primary is The Sales Conversation System; his alternate is The Prospect Call System if "sales" comes out. This spec uses the alternate as the working name because the free skill's own do-not-say list bars anything reading as sales training, and "prospects are not clients" is Kathryn's line. One word, her call. Folder slug follows whatever she picks.

The commitment this name makes

Kathryn's own POV: "you don't really have a system. You have a document." So the name is a promise with a test attached, and Reid flagged it before she took it:

Six stages. Each one ingests something the buyer already has and returns a finished artifact they would otherwise have had to make. If any stage returns advice, a template, or a worksheet to fill in, that stage fails the name and the product fails her own line. There is no version of this that ships as a guide.

The ladder it sits on

The pitch writes itself: you built the questions. That's one of six stages. This builds all six.

And this is why the free skill's output has to be an input. Stage 3 accepts the Question Set Builder's output directly. Someone who ran the free skill starts stage 3 already done — which is the moment the ladder becomes obvious rather than asserted.

The six stages, and what each one returns

Stage names are Kathryn's, verbatim from her email 2 copy. The artifact column is the commitment.

1 — Take the lead

"how you open so the call belongs to you"

• Ingests: their current booking page title, what they sell, call length.
• Returns: the renamed booking page, written, plus the opening frame — purpose, why they booked, who else decides — in their words, ready to read.
• Source: the 7/27 session, where the booking was renamed off the internal process onto the outcome.

2 — Set the stage

"why now, and who else decides"

• Ingests: their offer, what the prospect receives before booking, call length.
• Returns: the post-booking confirmation email, written and sendable — what the call covers, what to have ready, how long, what happens after. Short enough to read on a phone.

3 — Dig deeper

"the question bank, and the reflect-back that makes your recommendation theirs"

• Ingests: the Question Set Builder output, or a transcript, or questions typed from memory.
• Returns: the standard question set by call type, plus the feed-back lines that put their own words back in front of them.
• Note: the only stage with a free predecessor. Everyone else starts here cold; a free-skill user starts here finished.

4 — Cost of inaction

"what staying put costs them in their own dollars, and the first win that covers your fee"

• Ingests: their fee, what they fix, a typical client's numbers.
• Returns: the arithmetic in their own figures — the annual leak multiplied across three years — plus the named first win that covers the fee, with the sentence to say it.

5 — Name it

"your price as a range, said out loud, on the call"

• Ingests: their 4–5 most common scope combinations and what each has been billed at.
• Returns: the rough-range grid, plus the script for saying a range out loud, plus the ROI line, plus the three reactions and what to say to each.

6 — Close

"book the next call from the call. Never 'I'll send you a quote.'"

• Ingests: their calendar tool and typical decision timeline.
• Returns: three written pieces — the kickoff booking script for yes, the 15-minute decision-call invite for thinking, and the dated re-contact note for not now.

The assembly — the seventh output

One page carrying all six stages in order, in their language: the run-of-show for the next call. This is the thing they keep, and it is what makes six skills a system rather than six skills.

Merged in from the parallel spec, 2026-08-11

Another session specced this independently. Four things in theirs beat mine and are now binding here:

1. It is NOT per-prospect prep — and that boundary is a live product collision I missed. The DFY Claude Project (OTO2, 16 buyers) already preps the buyer for each individual call, one prospect at a time. This builds the standing conversation those calls run on. If that line is not in the build and in the copy, the $97 competes with something she already sells.

2. Nothing is assembled from the 52. If a stage could be produced by running a skill the buyer already owns, it comes out. That is a quality gate, not a preference — it is what stops the $97 reading as a repackage.

3. Completion is the main risk, and the build has to be sequenced for it. Nothing forces a self-serve buyer to finish, and an unfinished artifact generates refunds. So: each stage produces its file before the next begins, stages can run in separate sessions, the build states what it needs to resume, and someone who stops after two still holds two finished things. Target 45–60 minutes across as many sittings as they want. My spec had no completion mechanic at all.

4. Five artifacts, not six-plus-an-assembler. Artifact 1 — The Conversation, all six stages in their words — is the assembly. Cleaner than bolting a seventh output on the end, and it makes the spine the first thing they get rather than the last.

The five: The Conversation · The Question Set · The Objection Lines · The Range Grid · The Follow-Up. Each ships as its own file and each is usable without the other four. The six stage names below still hold — they are the structure inside artifact 1.

And one delivery trap worth more than it looks: the DFY Project's instructions tell Claude never to name skills, so a file dropped into that project gets absorbed. Buyers who own both must run this in a separate conversation. That goes on the delivery page.

Segmentation: suppress DFY Project owners or send them a variant. SLO buyers already know what a skill file does; free-only opt-ins have never bought anything. Handle in the send, not in the product.

One open decision of theirs is already answered by their own spec: required vs recommended free-skill input. Their Input section specifies a fallback, so it is recommended, with a fallback — required would block anyone who skipped it for no gain.

Build shape

Six skills plus an assembler, delivered in the OTO2 mold — a Notion delivery page with the skill files and setup, which is the pattern that already builds and delivers cleanly and the only $97-tier mold with buyers behind it.

Reuse, and what I have not verified. Stages 4, 5 and 6 map onto Kathryn's own concept briefs — the first win, the live number, the three doors — each of which already carries its mechanic and its cost formula. Stage 3 is the free skill, built. There are also 17 files in Engagements/Stevan Franeta/ on the Drive — a sales framework deck, a playbook, a script. I have not opened them. That is build step one, because it decides how much of stages 1, 2 and 5 already exists in draft.

Build order: 3 (exists) → 5 → 6 → 4 → 1 → 2 → assembler. Stages 5 and 6 first because they carry the sharpest pain and the most existing material.

Hard constraints

• No vertical. The source session is tax-flavored. Every trace comes out — no CPA, tax, returns, IRS, software names. make-paste-ready.py enforces this mechanically on copy.
• No client. Nothing identifiable about the source client in any shipped asset.
• Every stage returns an artifact. The name is the test. A stage that returns advice gets rebuilt or cut.
• Kathryn publishes. Nothing goes live without her.

Open

1. The name — Sales Conversation System or Prospect Call System. Blocks the folder slug, the files, and Sloane's copy.
2. Price confirmation at $97. The only $97-tier evidence we have is OTO2 converting 16 buyers. Thin, and it's the number she named.
3. Whether stage 3 ships inside the $97 as well, or whether buyers are expected to have the free skill. Recommendation: ship it inside, so the product is whole for someone who arrives cold.