Core: The Sync Tax Recovery Agent — a single AI conversation that takes their meeting list and builds everything needed to eliminate information transfer meetings. Classified, costed, replaced, scripted, and sequenced.
Video: Screen-recorded walkthrough of Kathryn using the agent on a real meeting list — showing classification, CEO Memo output, and what Monday looks like after.
Companions (3):
Context: They've read the sync tax article, possibly run the free Meeting Audit, and decided $27 is worth it for the deployment tools. They're already problem-aware. They don't need more convincing — they need the system.
Checkout page copy (key frame): "You already know meetings are the problem. This builds the replacement."
Post-purchase redirect: Thank You page (not a generic confirmation — a designed experience).
Purpose: Orient them. Reduce post-purchase anxiety. Give them one clear next step.
"Your Sync Tax Recovery System is ready. Everything is below — and it's also in your inbox."
"Start with the video. It's 12 minutes. You'll see the agent in action on a real meeting list — classification, cost calculation, and the CEO Memo system being built in real time. Then open the agent and run it on your own meetings."
Video (embedded or linked) — positioned as Step 1
The Sync Tax Recovery Agent — link to ChatGPT/Claude project
Meeting Benchmark (PDF or HTML)
Resistant Team Member Scripts (PDF or HTML)
Async Failure Diagnostic — link to ChatGPT/Claude project
No upsell on the Thank You page. No order bump. No "wait — one more thing." They just paid. Give them what they bought. The bridge to the Systems Diagnostic happens inside the agent (Phase 5), not here.
Purpose: Backup access. Repeat the one instruction. Create a bookmark they'll come back to.
Subject line: "Your Sync Tax Recovery System — start here"
Body structure:
No drip sequence. No "Day 2" email. No "have you started yet?" nudge. One email, all access, one instruction. If they need a follow-up, it's because they didn't deploy — and that's what the Async Failure Diagnostic is for.
Purpose: Show them it works. Reduce friction before they open the agent. Build confidence that this isn't a prompt they'll struggle with — it's a conversation that walks them through it.
Format: Screen recording of Kathryn using the agent. Not a talking-head explainer. Not a course module. A live demonstration — the agent running on a real (anonymized) meeting list.
What they see (in order):
Kathryn pastes a firm's meeting list into the agent. They see how the input works — what to include, how to format it, what "good enough" looks like.
The agent classifies each meeting as IT, CW, or SPLIT. Kathryn pauses to explain one classification — why the team meeting is 70% IT despite feeling collaborative. This is the "aha" moment.
The sync tax number appears. Kathryn doesn't react with hype. She reads it, references the benchmark ("this is typical for a firm this size"), and moves on. The math does the work.
The agent builds the full CEO Memo system — memo structure, AI project instructions, delivery protocol. Kathryn highlights that it's customized to the firm's specific meetings, not a template. They see the paste-ready AI instructions.
The agent writes the team communication. Kathryn reads it and points out the resistance-handling language — "This is what makes the change stick."
The agent offers to stop after the CEO Memo ("Deploy this Friday. If it holds, come back for the rest."). Kathryn explains why this matters: "One meeting replaced and holding is worth more than five planned and never started."
Target length: 10–15 minutes. No padding. Every minute shows the agent producing output.
The video is the highest-value element in the product. It's what converts a $27 buyer into someone who actually runs the agent. Without it, a meaningful percentage will save the link and never open it. With it, they see it work and think "I can do that in 15 minutes."
Purpose: The deployment. This is the product. Everything else supports this moment.
What they do:
Time to first result: 15–20 minutes from opening the agent to having a fully built CEO Memo system with paste-ready instructions.
The critical moment: When they see their own sync tax number and the CEO Memo customized for their specific meetings — that's when the $27 feels like a steal. They're holding something that would take a consultant 2–3 hours to build.
Purpose: Handle the three things that stall deployment after the agent does its job.
When they use it: Before running the agent (to see where their firm falls) or after (to validate their sync tax number against industry data).
What it contains: Sourced data from HBR, Asana, Microsoft, SPI Research, AICPA. Four ICP firm profiles with rate breakdowns and sync tax calculations. The anonymized case study proof point.
Why it matters: It turns "I think meetings are a problem" into "the data confirms my meetings are a problem — and here's what firms my size are spending." Removes self-doubt before they deploy.
When they use it: After sending the kill script, when someone pushes back.
What it contains: Five resistance patterns by role — the specific objection each role raises and the exact language to address it. Partner/owner ("I need to see everyone's face"), manager ("my updates won't get read"), senior staff ("I need direct access to you"), admin ("this is more work"), new hire ("I don't know what's expected").
Why it matters: The kill script handles 80% of the change. The scripts handle the 20% that pushes back. Without this, the first objection from a team member can kill the deployment.
When they use it: If they've tried async before and it didn't stick — or if their first deployment starts to slip.
What it contains: AI-powered diagnostic that asks what they tried, what happened, and why it failed. Identifies the structural gap (no ownership, no format, no deadline, no guardrails) and tells them exactly what was missing.
Why it matters: Most of this ICP has tried some version of "let's do this by email instead." It failed — not because async doesn't work, but because they tried to make a meeting disappear without building the replacement infrastructure. The diagnostic shows them why it failed and what the agent builds differently.
Purpose: Pattern reveal — not a pitch. After they've recovered hours, the agent surfaces what becomes visible once the calendar opens up.
What the agent says (Phase 5): "You've recovered approximately [X] hours per week. Here's what firm owners in your position typically discover..." — then the three categories: operational processes, decision infrastructure, visibility systems.
The offer: Free 60-minute Systems Diagnostic at advisoryos.ai — the same constraint diagnosis applied to their entire operation.
Why it works: By this point they've experienced the methodology. They've seen the diagnosis reveal a pattern they couldn't see. They've held the output. The bridge isn't "buy more." It's "the thing you just felt? That applies to your whole business." The ones who are ready will book. The ones who aren't will deploy the CEO Memo and come back later.
The bridge lives inside the agent, not in a separate email or page. It appears at the natural completion point — when the work is done and the hours are recovered. No follow-up email sequence pushes toward it. No countdown. No urgency. Pattern recognition is the only sales mechanism.
| Moment | What Happens | Time |
|---|---|---|
| Purchase | Checkout completes | T+0 |
| Thank You Page | Access delivered, one instruction given | T+0 |
| Welcome Email | Backup access, "what to have ready" | T+0 |
| Video | Watch the agent work on a real meeting list | T+5 min |
| Agent — meeting list entered | Input their meetings, rates, tools | T+20 min |
| Agent — classification + cost | See the sync tax number | T+30 min |
| Agent — CEO Memo built | Customized memo system with paste-ready AI instructions | T+40 min |
| Agent — kill script | Team communication ready to send | T+45 min |
| First deploy | Friday: record brain dump, post memo | Next Friday |
| Monday shift | Meeting starts at discussion, not download | Following Monday |
The LTO truth: Completion rate drives next purchase. A buyer who deploys the CEO Memo and sees their Monday meeting change is 10x more likely to book the Systems Diagnostic than one who saved the link and never opened it.
What drives completion in this product:
| Asset | Status | Notes |
|---|---|---|
| Sync Tax Recovery Agent (system prompt) | Done | sync-tax-recovery-agent-v1.md — needs testing + refinement |
| Meeting Benchmark (companion) | Done | sync-tax-meeting-benchmark.html — sourced, 4 ICP profiles |
| Video walkthrough | Kathryn produces | Screen recording of Kathryn running the agent. 10–15 min. |
| Resistant Team Member Scripts | To build | 5 patterns by role, standalone PDF or HTML |
| Async Failure Diagnostic (agent) | To build | Separate agent prompt — diagnoses why prior async attempts failed |
| Thank You page | To build | Depends on platform (Kajabi, Gumroad, etc.) |
| Welcome email | To build | One email, all access, one instruction |
| Checkout page copy | To build | Sales page or checkout page — depends on funnel architecture |
| Agent deployment | To build | Create the ChatGPT Project (or Claude Project) from system prompt |
Single agent, not four GPTs. The user's original draft had four separate GPT tools. Merged into one conversation because: (a) switching between tools is friction, (b) context is lost between tools, (c) one conversation maintains continuity from classification through deployment. The phase management handles the sequencing internally.
CEO Memo as the core first deployment, not a bonus. The original draft treated the Monday Meeting Replacement Template as Bonus 5. Moved it to the center of the product because it's the proven deployment — 6+ months holding, client self-enhanced by week 4. The product should lead with the strongest asset, not bury it.
Video first, agent second. LTO completion data consistently shows that seeing someone use the tool before using it yourself doubles completion rates. The video isn't supplementary — it's the activation mechanism.
No drip sequence. This ICP doesn't respond to "Day 3: Have you started?" emails. They're busy practice owners. They'll use it when they use it. The product is designed for same-session completion — watch the video, run the agent, deploy Friday. If they don't do it same-session, a nudge email won't change that. The Async Failure Diagnostic handles the "I tried and it didn't work" case.
"Do one thing" exit in the agent. The agent explicitly offers to stop after the CEO Memo build. This is deliberate: one system deployed and holding is worth more than five planned and never started. The buyer who deploys one thing and sees it work will come back for the rest — or book the Systems Diagnostic. The buyer who gets overwhelmed by five changes at once deploys zero.
Bridge inside the agent, not in email. The pattern reveal happens at the natural completion point — when they've done the work and can see what opens up. An email trying to "bridge" them to the diagnostic two weeks later has no context. The agent has full context — their meetings, their cost, their recovered hours. That's when the pattern lands.
Removed Bonus 4 (Uncaptured Revenue Identifier). The original draft included a 5-tab spreadsheet for identifying revenue left on the table. Cut because: (a) it shifts from sync tax (meetings) to revenue optimization (different problem), (b) it requires manual data entry the agent doesn't produce, (c) it dilutes the product's single-outcome promise. The sync tax product recovers calendar hours. Revenue is what they do with those hours — that's the Systems Diagnostic conversation.