PRD — Async Playbook: Self-Guided Market Intelligence Experience

Section 1

Overview

Core Principle

"The best lead magnet is a piece of the product itself."

The Async Playbook is a free, self-guided experience that lets prospects taste what the Mastery Monetization Lab delivers. Instead of a static PDF or a gated webinar replay, the playbook is an interactive working session. Prospects work through five structured exercises at their own pace and walk away with their own market intelligence document — built by them, using our methodology.

This is not a teaser. It is a genuine piece of the product. The exercises mirror the first 30 minutes of what our live system automates. The difference: in the live session, the AI does the work. In the playbook, the prospect does. That gap is the conversion lever.

Attribute	Detail
Product	Async Playbook (free lead magnet / taste-of-product)
Purpose	Let prospects experience the Mastery Lab methodology before applying. Self-paced. Output = their own market intelligence.
Distribution	Published as a live HC page at `ideas.asapai.net/playbook` (dogfooded)
Target Audience	Experts & consultants who saw the report or heard about us but are not ready to apply yet
Time to Complete	45-60 minutes
Exercises	5 structured exercises with guided prompts, frameworks, and quality gates
Primary Success Metric	40%+ of playbook completers click "Apply for Beta"
Content Type	HC page (`content_type: 'html'`), published via `hc-publish.js`

Why Not a PDF?

PDFs are dead weight. They sit in downloads folders. They don't track completion. They can't link to the live system. The playbook is a live page — progress is saved in localStorage, exercises are interactive, and the final CTA links directly to the assessment gate. The medium IS the message: we build things on the web, not in Word.

Section 2

User Journey

Entry Points

Report CTA

Inline callout in the Market Intelligence Report: "Read the playbook — build your own intelligence in 60 minutes."

Email Nurture

Day 2 of the 5-day email drip: "Before the live session, try building one yourself."

Direct Share

Shareable link from existing users, LinkedIn posts, or DM conversations.

Flow Sequence

Land on Page

→

Read Intro

→

Exercise 1

→

Exercise 2

→

Exercise 3

→

Exercise 4

→

Exercise 5

→

Summary

→

Apply CTA

Step-by-Step Breakdown

Step	User Action	System Behavior	Time Est.
`1`	Lands on playbook page from entry point	Check localStorage for saved progress; offer resume if found	—
`2`	Reads intro: what this is, what you will build, time commitment	Progress tracker initializes at 0/5	3 min
`3`	Exercise 1: Define Your ICP (guided prompts + template)	Expand section; save inputs to localStorage on blur	10 min
`4`	Exercise 2: Map Your Pain Points (5 questions, framework)	Pre-populate ICP name from E1; save progress	10 min
`5`	Exercise 3: Find Your Fishing Holes (guided research)	Reference ICP + pain points from E1+E2 in prompts	15 min
`6`	Exercise 4: Generate Content Hooks (turn pain into angles)	Pull pain points + fishing holes into hook formula template	10 min
`7`	Exercise 5: Draft Your First Outreach (message + personalization)	Combine all prior outputs into outreach template	10 min
`8`	Summary: Review what you built across all 5 exercises	Render combined output with copy-to-clipboard per section	2 min
`9`	CTA: "Want this done FOR you in 2 minutes?" → Apply for Beta	Track click event; link to assessment gate	—

No Login Required

The entire playbook works without authentication. All data stays in the browser via localStorage. This eliminates friction. We only ask for identity at the Apply step — by which point they have already invested 45+ minutes and have tangible output they want to keep.

Section 3

Exercise Design

Each exercise follows a consistent structure: Input (what the user provides), Framework (the methodology they apply), Output (the artifact they produce), and Quality Gate (the self-check question that validates their work). Quality gates are critical — they prevent users from producing low-quality outputs that would undermine their perception of the methodology.

Input

Three guided questions that progressively narrow the user's target market:

Q1: "What do you teach, coach, or consult on? Describe it in one sentence as if telling a stranger at a party."
Q2: "Who pays you right now? Describe your last 3 paying clients — their role, industry, and why they hired you."
Q3: "Who SHOULD be paying you? If you could clone your best client 10x, what do those people have in common?"

Framework: ICP Canvas

The user fills out a structured canvas with four quadrants:

Quadrant	Prompt	Example
Demographics	Role, company size, industry, revenue range, years of experience	"VP of Marketing at B2B SaaS, 50-200 employees, $5M-$50M ARR"
Psychographics	Values, frustrations, aspirations, self-identity	"Sees themselves as a builder. Frustrated by 'shiny object' culture."
Buying Triggers	Events that make them look for help NOW	"Just lost a key team member. Board is asking about pipeline."
Objections	Reasons they would NOT buy from you today	"I've been burned by consultants before. How is this different?"

Output

A filled ICP profile (text block) that the user can copy and reuse. This output feeds into all subsequent exercises as the anchor reference.

◆ Quality Gate: "Can you name 3 specific, real people who match this profile? If not, your ICP is too abstract. Go back and make it concrete."

Input

Five pain-mining questions from the T2 Pain Archaeologist methodology. These are designed to move the user past surface-level problems into root causes and emotional weight:

Q1: "What is the thing your ICP complains about publicly — on LinkedIn, in forums, in Slack groups?"
Q2: "What is the thing they would only admit to a trusted peer over drinks?"
Q3: "What is the gap between where they are and where they told their boss they'd be by Q3?"
Q4: "What have they already tried that didn't work? What did that failure cost them?"
Q5: "If they could snap their fingers and fix ONE thing tomorrow, what would it be and why?"

Framework: Pain Hierarchy

Users map each pain point across three layers:

Surface Pain

What they say out loud. Observable symptoms. "We need more leads."

Root Pain

The underlying cause. System failures. "Our positioning is wrong — leads don't understand what we do."

Dream State

Where they want to be. Emotional aspiration. "People come to us. We choose our clients."

Output

5 pain points ranked by urgency, each with surface/root/dream-state layers filled in. The ranking forces prioritization — you cannot address 5 pain points at once in outreach.

◆ Quality Gate: "Would someone screenshot this pain point and send it to a friend saying 'this is SO me'? If the language is too generic or corporate, rewrite it in the voice of a real person venting."

Input

The ICP profile from Exercise 1. Users take their demographics and psychographics and go hunting for specific places where these people congregate online.

Framework: 3-Channel Strategy

Every ICP has at least three digital habitats. Users find one of each:

Channel	What to Find	Research Prompt
LinkedIn	Groups, hashtags, or specific creators whose comment sections are full of your ICP	"Search LinkedIn for [ICP role] + [pain keyword]. Find a post with 50+ comments where your ICP is venting."
Niche Community	Reddit subs, Slack groups, Discord servers, Facebook groups, paid communities	"Search Reddit/Google for [industry] + [community/forum/group]. Find one with 1,000+ members and recent activity."
Content Platform	YouTube channels, podcasts, newsletters where your ICP consumes content	"Search YouTube for [ICP topic] + [pain keyword]. Find a video with comments from your ICP asking questions."

Output

3 fishing holes with specific URLs, group names, or channel links. Each one must include:

The platform and exact location (URL preferred)
Approximate audience size or activity level
Why this fishing hole matches the ICP (1 sentence)

◆ Quality Gate: "Can you see 10+ people matching your ICP who have been active in this fishing hole in the last 7 days? If not, the fishing hole is dead water. Find a live one."

Input

Pain points from Exercise 2 (ranked) + Fishing holes from Exercise 3 (3 channels). Users combine these inputs using a formula to generate hooks that stop the scroll.

Framework: Hook Formula

Hook = [Agitation] + [Counter-intuitive Insight] + [Implied Solution]

Example breakdown:

Agitation: "Most consultants spend 80% of their time looking for clients and 20% serving them."
Counter-intuitive: "The ones who flip that ratio didn't get better at sales — they got better at being found."
Implied solution: "Here's the 3-part system I used to make that switch in 14 days."

Output

8 content hooks — 2 per format type:

Format	Where It's Used	Hook Count
Post	LinkedIn feed, community post, tweet thread	2
Comment	Reply to a creator or community thread (adds value, doesn't pitch)	2
DM Opener	LinkedIn DM, community direct message	2
Loom Script	60-second async video, personal and specific	2

◆ Quality Gate: "Would YOU stop scrolling if you saw this hook in your feed? If it sounds like every other LinkedIn post, it's not a hook — it's wallpaper. Rewrite with a sharper agitation or a more surprising insight."

Input

Users select three ingredients from their previous exercises:

One fishing hole from Exercise 3 (the most active one)
One content hook from Exercise 4 (the DM opener they liked best)
One specific person they identified during Exercise 3 research (a real human, not a persona)

Framework: The Warm Open

The outreach message follows a three-part structure that feels like a conversation, not a pitch:

1

Acknowledge their content. Reference something specific they said, posted, or commented. This proves you are a real person who actually read their stuff. Not "I saw your profile." Something like "Your comment on [X's post] about [topic] really resonated — especially the part about [specific detail]."

2

Add value. Share an insight, resource, or perspective that is useful to them regardless of whether they ever respond. This is not a lead-in to a pitch. It is genuine value. "I put together a [framework/guide/analysis] on [topic] that addresses exactly what you were describing. Happy to share if it's useful."

3

Soft ask. Close with a low-commitment question that opens a conversation. Not "Can we hop on a call?" but rather "Curious — have you tried [approach]? I've seen it work well for people in [their situation]."

Output

1 ready-to-send DM or message, personalized to a real person, using the Warm Open framework. The user can copy this directly and send it today.

◆ Quality Gate: "Does this feel like a real person talking, not a template? Read it out loud. If it sounds like a sales email, strip out the corporate language and rewrite it as if you're texting a colleague you respect."

Exercise Outputs Are Cumulative

Each exercise builds on the previous ones. The ICP (E1) feeds into Pain Points (E2), which feed into Fishing Holes (E3), which feed into Hooks (E4), which feed into Outreach (E5). By the end, the user has a complete market intelligence document — not five disconnected worksheets. This cumulative structure mirrors the live session experience and makes the "automation" CTA more compelling.

Section 4

Technical Implementation

Architecture Overview

Aspect	Implementation
Format	Single-page HC page with collapsible exercise sections. No SPA framework — vanilla HTML/CSS/JS for maximum portability and zero build step.
Content Type	`content_type: 'html'` — served via the standard NowPage catch-all route
Publishing	Published via `hc-publish.js` to `ideas.asapai.net/playbook`
Authentication	None required. All exercises work without login. Identity captured only at Apply CTA.
Data Persistence	`localStorage` with key prefix `playbook_`. Save on input blur. Resume on page load.
Template Source	New template, but follows existing HC page patterns (hc-metadata, hc-instructions, hc-context-public)

Interactive Features

Expandable Sections

Each exercise is collapsible. Only the current exercise is expanded by default. Previous exercises show a collapsed summary with a green checkmark when complete. Next exercises are locked (greyed out) until the current one passes its quality gate.

Copy-to-Clipboard

Every exercise output has a "Copy" button that copies the structured text to clipboard. The Summary section has a "Copy All" that generates a formatted document with all 5 exercise outputs concatenated.

Progress Tracker

Fixed progress bar at the top showing X/5 exercises complete. Updates in real-time. Changes color from grey to gold as exercises are completed. Shows estimated time remaining.

Print/Export

CSS @media print styles for saving as PDF. Removes interactive elements, expands all sections, adds page breaks between exercises. Also: a "Download as PDF" button using window.print().

localStorage Schema

{
  "playbook_version": "1.0",
  "playbook_started_at": "2026-02-25T10:00:00Z",
  "playbook_last_saved": "2026-02-25T10:45:00Z",
  "playbook_e1_icp": { "q1": "...", "q2": "...", "q3": "...", "canvas": {...} },
  "playbook_e2_pain": { "points": [...], "ranked": [...] },
  "playbook_e3_holes": { "linkedin": {...}, "community": {...}, "content": {...} },
  "playbook_e4_hooks": { "posts": [...], "comments": [...], "dms": [...], "looms": [...] },
  "playbook_e5_outreach": { "target_person": "...", "message": "..." },
  "playbook_progress": { "completed": [1, 2, 3], "current": 4 }
}

Performance Requirements

Metric	Target	Notes
First Contentful Paint	< 1.5s	Single HTML file, no external JS dependencies beyond fonts
Total Page Weight	< 150KB	HTML + inline CSS + inline JS (gzipped)
Works Offline	Partial	After first load, exercises work offline (localStorage). Fonts may fall back to system.
Mobile Responsive	Required	All exercises must be usable on mobile. Research prompts (E3) may suggest switching to desktop.
Accessibility	WCAG 2.1 AA	Proper heading hierarchy, form labels, keyboard navigation, focus indicators

Section 5

CTA Strategy

In-Exercise Callouts (Subtle)

After each exercise, a small callout appears below the quality gate:

Want this automated? In the live session, you don't fill this out. You just talk for 3 minutes and the AI builds your ICP profile in real-time. See how it works →

These callouts vary per exercise, always comparing the manual effort to the automated version. They should feel informative, not pushy. The goal is to plant the seed, not to close.

End-of-Playbook CTA (Strong)

The final section delivers a direct comparison that makes the value proposition undeniable:

You just spent 60 minutes doing what our system does in 2.

In the live session, you don't fill anything out. You just talk. And it appears — ICP, pain points, fishing holes, hooks, and outreach — all generated, formatted, and ready to use.

Apply for Beta

Join the 5-Day Email Course

CTA Destinations

CTA	Destination	Purpose
Primary	Assessment gate form (P2 dependency)	Qualify the lead. Collect name, email, expertise area. Route to sales page if qualified.
Secondary	Email course signup	Capture leads not ready to apply. 5-day drip that deepens engagement and re-surfaces the Apply CTA.
In-Exercise	"See how it works" → preview/demo page	Shows the automated version of the exercise they just completed manually. Builds desire without hard selling.

Anti-Pattern: Do Not Gate the Exercises

The temptation will be to ask for an email before Exercise 3 or 4. Do not do this. The entire point is that the prospect invests 45+ minutes of effort and builds real outputs. That investment IS the conversion mechanism. Gating midway breaks the flow, reduces completion rates, and undermines the core principle. The only identity capture point is the Apply CTA at the very end.

Section 6

Dogfooding Requirements

The Async Playbook is not just a product feature — it is a demonstration of the system itself. Every decision about how it is built, published, and served must reinforce the message: we use our own tools for everything.

Published as an HC Page

The playbook MUST be published via hc-publish.js to ideas.asapai.net/playbook. It must have proper hc-metadata, hc-instructions, and hc-context-public blocks. Any AI agent that fetches this URL should be able to understand what the page is and how it fits into the registry.

References the HC Standard

The playbook should include a small "Powered by" footer note mentioning HC and NowPage. The page itself is evidence that the publishing system works — but we should make that explicit for prospects who are curious about the tech.

Shows the System Working

At the end of the playbook (before the CTA), include a preview of what the live session report looks like. Link to a real, live example report on the registry. This lets the prospect see the actual output quality and compare it to their manual effort.

Registered in the Meta-Registry

The playbook page should be registered in the appropriate registry with --registry auto. This ensures that any AI agent walking the registry can discover the playbook and recommend it to prospects.

Live Example Report

The playbook should include a link to a real Market Intelligence Report generated by the live system. This is the "before and after" — the prospect sees their manual output (what they just built in 60 minutes) next to the automated output (what takes 2 minutes). The contrast is the conversion lever. If no live report exists yet, create a demo report using the system and publish it before the playbook goes live.

Section 7

Success Metrics

35%+

Completion Rate

Reach Exercise 5

40%+

Apply Conversion

Of completers click Apply

45m

Median Time

Target completion time

2x

Quality Signal

Completers vs non-completers

Measurement Plan

Metric	Target	How Measured	Why It Matters
Completion Rate	35%+ reach E5	localStorage progress state polled on page unload; send beacon to analytics endpoint	Validates that the exercises are engaging enough to hold attention for 45+ minutes. Below 35% means exercises are too hard, too boring, or too long.
Exercise Drop-off	Track per-exercise	Progress events on exercise start/complete. Build a funnel chart: E1 → E2 → E3 → E4 → E5	Identifies which exercise is the bottleneck. If 60% drop at E3, the research step is too hard and needs simplification.
Apply Conversion	40%+ of completers	Click event on Apply CTA, compared to completion count	The north star metric. If completers don't click Apply, the CTA copy or value comparison is not landing.
Time to Complete	Median 45 min	`playbook_started_at` vs final exercise completion timestamp	If median is 30 min, exercises are too easy (outputs will be shallow). If 90+ min, it's too long and we lose people to life.
Shareability	Track referrals	UTM parameters on shared URLs; count unique visitors from non-standard referrers	Organic sharing = best signal that the playbook delivers real value. If no one shares it, the output quality is not high enough.
Quality Signal	2x higher scores	Compare assessment gate scores of playbook-completers vs cold applicants	Validates that the playbook is an effective qualification tool, not just lead gen. Completers should demonstrate higher understanding of their market.

Funnel Targets

1,000
Page Views

→

600
Start E1 (60%)

→

450
Complete E2 (75%)

→

350
Complete E4 (78%)

→

210
Complete E5 (60%)

→

84
Apply (40%)

Illustrative funnel: 1,000 visitors → 84 applications (8.4% overall conversion)

Section 8

Build Priority & Dependencies

Dependency Graph

The Async Playbook depends on three upstream deliverables. It can be partially built in parallel, but the CTA integration requires P2 and P3 to be complete.

TMPL1: Report Template

→

P2: Assessment Gate

→

P3: Sales Page

→

P4: Async Playbook

Dependency	Status	Blocks	Notes
`TMPL1` Report Template	Pending	Live example report link in Section 6 (Dogfooding)	Need at least one demo report published to link from the playbook's "preview" section.
`P2` Assessment Gate	Pending	Primary CTA destination ("Apply for Beta")	The Apply button currently has no destination. Can stub with a Typeform or similar as interim.
`P3` Sales Page	Pending	Post-assessment redirect, "See how it works" links	Users who pass the assessment need a place to land that explains pricing and enrollment.

Build Order

Phase A

Exercises 1-2 (Core Value)
Build the ICP Canvas and Pain Hierarchy exercises. These deliver standalone value even without the later exercises. Can ship as a "mini playbook" if needed for early testing. No external dependencies.

Phase B

Exercises 3-5 (Research + Output)
Add the research-heavy Fishing Holes exercise, the creative Hooks exercise, and the Outreach draft. These require the cumulative data from E1-E2. Exercise 5 may be cut for MVP if timeline is tight.

Phase C

CTA Integration + Dogfooding
Wire up the Apply CTA to the assessment gate (P2). Add the live report preview (requires TMPL1). Publish as HC page. Register in meta-registry. Full dogfooding validation.

Phase D

Analytics + Iteration
Add progress tracking beacons, funnel analytics, and the exercise drop-off dashboard. Run first cohort (50+ visitors). Iterate based on drop-off data. Tune exercise difficulty and CTA copy.

MVP Scope

MVP = Exercises 1-4 + Final CTA

Exercise 5 (Draft Outreach) can be skipped for v1 if needed. Exercises 1-4 produce a complete market intelligence document: ICP, pain points, fishing holes, and content hooks. That is enough to demonstrate the methodology and drive Apply conversions. Exercise 5 adds outreach readiness but is not essential for the core value proposition.

Timeline Estimate

Phase	Effort	Prerequisites	Output
A	1 session (3-4 hours)	None	Exercises 1-2 functional, localStorage saving, progress tracker
B	1 session (3-4 hours)	Phase A complete	Full 5-exercise playbook, all quality gates, copy-to-clipboard
C	1 session (2-3 hours)	TMPL1 + P2 ready	CTA wired, live report linked, HC published, registry updated
D	Ongoing	50+ visitor data	Analytics dashboard, iteration log, v1.1 improvements

Single-Session Build Feasibility

The entire playbook (Phases A + B) can be built in a single working session once the dependencies are ready. The page is vanilla HTML with inline CSS/JS — no build step, no framework, no deployment pipeline. Write the file, run hc-publish.js, verify the live URL. This is the NowPage advantage: publishing is a one-liner, not a sprint.

Appendix

Exercise Summary Matrix

Quick reference for all 5 exercises with their inputs, frameworks, outputs, quality gates, and time estimates.

Ex.	Name	Input	Framework	Output	Quality Gate	Time
`E1`	Define Your ICP	3 guided questions	ICP Canvas (4 quadrants)	Filled ICP profile	"Name 3 specific real people"	10m
`E2`	Map Pain Points	5 pain-mining questions	Pain Hierarchy (3 layers)	5 ranked pain points	"Would someone screenshot this?"	10m
`E3`	Find Fishing Holes	ICP profile from E1	3-Channel Strategy	3 fishing holes with URLs	"10+ active ICP in last 7 days?"	15m
`E4`	Content Hooks	E2 pain + E3 holes	Hook Formula (3-part)	8 hooks (2 per format)	"Would YOU stop scrolling?"	10m
`E5`	Draft Outreach	1 hole + 1 hook + 1 person	The Warm Open (3-step)	1 ready-to-send message	"Does this feel like a real person?"	10m

Overview

Core Principle

User Journey

Entry Points

Report CTA

Email Nurture

Direct Share

Flow Sequence

Step-by-Step Breakdown

Exercise Design

Define Your ICP

Map Your Pain Points

Surface Pain

Root Pain

Dream State

Find Your Fishing Holes

Generate Content Hooks

Draft Your First Outreach

Technical Implementation

Architecture Overview

Interactive Features

Expandable Sections

Copy-to-Clipboard

Progress Tracker

Print/Export

localStorage Schema

Performance Requirements

CTA Strategy

In-Exercise Callouts (Subtle)

End-of-Playbook CTA (Strong)

You just spent 60 minutes doing what our system does in 2.

CTA Destinations

Dogfooding Requirements

Published as an HC Page

References the HC Standard

Shows the System Working

Registered in the Meta-Registry

Success Metrics

Measurement Plan

Funnel Targets

Build Priority & Dependencies

Dependency Graph

Build Order

MVP Scope

MVP = Exercises 1-4 + Final CTA

Timeline Estimate

Exercise Summary Matrix