Product Definition: Consulting Practice SOP Manual

Core Definition

Type: SOP (Standard Operating Procedure) Niche: Independent consulting practice operations ICP: Solo consultants running \$500K-\$2M practices who already own the 52 Claude Skills. They need the recurring rhythms that turn AI skills from a one-time experiment into a practice operating system. Value Proposition: 40 standard operating procedures that turn your Claude Skills into a practice operating system. SOPs define the rhythm. Skills do the work inside each rhythm. Together, they run the practice. Target Size: 40 SOPs across 8 operational categories Price: \$29-35 (OTO1 — first upsell after \$7 tripwire checkout)

Fixed Structure (every SOP page)

1. SOP Title — Action-oriented name (e.g., "Run Weekly Pipeline Review," not "Pipeline Review SOP")
2. Category — Which operational area (select property)
3. Frequency — How often this runs (select property)
4. Time to Complete — Honest estimate including skill run time (select property)
5. Trigger — What initiates this SOP — time-based ("Every Monday before email") or event-based ("When a prospect says yes"). Research confirms this is the #1 differentiator vs. every competitor — no existing SOP product tells solo consultants WHEN to run each procedure.
6. Purpose — Why this procedure exists (the problem it prevents or the outcome it ensures)
7. Prerequisites — What you need before starting (data, access, prior SOPs completed)
8. Step-by-Step Procedure — Numbered steps with specific actions, including decision points where the path forks
9. Skills Referenced — Which Claude Skills are called within this SOP, by name (e.g., "Step 3: Run the Session Prep Brief skill with these inputs"). Genuinely unique — no competitor links SOPs to AI skills.
10. Expected Outcome — What done looks like, written as a completed state (e.g., "Pipeline is current, all prospects have a next action, weekly deal count logged")
11. Common Mistakes — What goes wrong when consultants skip steps or shortcut the process. Research confirms this is high-value for solo operators with no colleagues to catch errors.

Variables

Entry List (Full 40 SOPs)

Business Development (5 SOPs)

Proposals & Pricing (5 SOPs)

Client Onboarding (5 SOPs)

Client Delivery & Prep (5 SOPs)

Client Communication (5 SOPs)

Content & Visibility (5 SOPs)

Operations & Admin (5 SOPs)

Practice Strategy (5 SOPs)

Frequency Distribution

Skill Coverage

All 52 Claude Skills appear at least once across the 40 SOPs. 15 skills appear in 2+ SOPs (workhorses: Action Item Tracker in 4, Client Profitability Analyzer in 4, Progress Update Builder in 3).

Delivery Mode

Recommended: page — With ~40 entries across 8 categories, each averages ~5 entries. Page mode gives clean category sections on the homepage with direct links to each SOP. (Can be overridden in Phase 8.)

Cross-Sell Integration

• Every SOP references specific Claude Skills by name — "Step 3: Run the Session Prep Brief skill with these inputs"
• The two products form a complete system: SOPs (when to do it) → Skills (AI does the work)
• Intro section makes the relationship explicit: "This manual assumes you have the 52 Claude Skills"
• SOPs create natural demand for PBOS — once the buyer is running weekly rhythms, they'll want the Practice Command Center and community support

Strategic Notes

OTO Timing (for copy/marketing phases)

Buyer purchased 52 skills 30 seconds ago, hasn't opened one. OTO page copy must anchor on the CIB experience they already had during the tripwire flow — not skills they haven't run. Frame: "You've seen what one skill does for call prep. This manual tells you when to run all 52 — so your whole practice runs that way."

PBOS Ascension

SOP Manual manufactures PBOS demand. Once someone is running weekly SOPs with the skills, the gap PBOS fills (diagnostic, personalization, community) becomes obvious.

Content Generation Note (for Phase 4 blueprint)

SOP 4 (Cold Outreach Batch): Ideal Client Profile Refiner is a strategic tool, not a weekly execution. Blueprint must specify it as a prerequisite dependency ("Step 1: Open your current Ideal Client Profile output"), not a step that runs inside the weekly procedure. Same pattern applies to any strategic skill referenced in a recurring SOP — the skill output is a dependency, not an in-line step.

Domain Research Summary

• No competitor links SOPs to AI skills — genuinely unique in the market
• 40 SOPs is well-calibrated — existing products either overwhelm (50-60 per category) or underwhelm (10 total)
• Trigger + Frequency is the highest-value differentiator — no existing SOP product tells solo consultants WHEN to run procedures
• Common Mistakes field is critical for solos — high-value for operators with no colleagues to catch errors
• Existing products are built for teams, not solos — org charts, job descriptions, new hire onboarding are dead weight