Content Blueprint: Consulting Practice SOP Manual

Page Structure Overview

Target total per page: ~250-350 words. This is an operating manual, not a guide. If it bloats past 350 words, it fails the 9 PM test.

Database-only properties (NOT rendered in page body):

• Category — database property for filtering/browsing
• Skills Referenced — multi_select for filtering; skills appear in-context in procedure steps
• Practice Stage — multi_select for filtering
• Time to Complete — appears in Quick Reference callout, not as a separate section

Section Details

Section 1: SOP Title

Type: heading_1 Word count: — Variable dependencies: Name Content rules:

• Use the SOP Name exactly as it appears in the database
• No subtitle or tagline — just the name Format:
• Heading 1, plain text

Section 2: Quick Reference

Type: callout with 📋 emoji Word count: — Variable dependencies: Frequency, Time to Complete, Trigger (generated from entry context) Content rules:

• Three fields on a single line, pipe-separated: Frequency, Time, Trigger
• Trigger is a specific description of what initiates this SOP — either time-based ("Every Monday morning, before email") or event-based ("When a signed contract is received")
• Trigger language must be concrete and actionable — not "when appropriate" or "as needed"
• Trigger text comes from the entry list in product-idea.md Format:
• Bold labels: Frequency: Weekly | Time: 30 min | Trigger: [specific trigger]
• All on one line inside the callout Example: > 📋 Frequency: Weekly | Time: 30 min | Trigger: Every Monday morning, before email

Section 3: Purpose

Type: paragraph Word count: 40-80 Variable dependencies: Name, Category Content rules:

• Opens with the problem this SOP prevents OR the outcome it ensures — not both
• Written in second person ("you")
• Names the specific consequence of NOT running this SOP — make the stakes real
• No generic "this SOP helps you..." openers. Start with the operational reality.
• Do NOT cite specific statistics, frequencies, or percentages. Use directional language. Format:
• Single paragraph, no bullets
• No bold or italic

Section 4: Prerequisites

Type: heading2 ("Prerequisites") + bulletedlist Word count: 30-60 (2-5 bullet items) Variable dependencies: Skills Referenced, Category Content rules:

• List what must be true or ready BEFORE starting this SOP
• Include tool references (tool-agnostic): "Your pipeline tracker (CRM, spreadsheet, or equivalent)"
• Include strategic skill output dependencies where applicable: "Your current Ideal Client Profile (output from the Ideal Client Profile Refiner skill)" — framed as an existing artifact to open, NOT a skill to re-run
• Include any prior SOP completions required: "SOP complete: Weekly Pipeline Review (if running this SOP on Monday)"
• Keep items concrete and checkable — the buyer should be able to scan this list and know in 10 seconds whether they're ready to start Format:
• Heading 2: "Prerequisites"
• Bulleted list, 2-5 items
• Tool references in parentheses: "(CRM, spreadsheet, or equivalent)"
• Skill output references with the skill name: "(output from the [Skill Name] skill)"

Section 5: Procedure

Type: heading2 ("Procedure") + numberedlist Word count: 150-250 (5-8 steps, each 20-40 words) Variable dependencies: Skills Referenced, Frequency, Category Content rules:

• Numbered steps, each starting with an action verb
• Skill calls are precise: "Run the [exact Skill Name] skill with [specific inputs described]." Use the exact canonical skill name from the 52-skill library. Describe the input the buyer should provide.
• Buyer's tools are vague: "Open your pipeline tracker," "Check your calendar," "Review your project folder" — never prescribe a specific platform
• Decision points where the path forks: "If [condition], [action]." Format as a sub-bullet or parenthetical within the step.
• Maximum 8 steps. If the procedure needs more, it should be split into two SOPs.
• Steps should flow naturally — each step's output feeds the next step's input
• Strategic skills referenced in the entry's multi_select that are NOT called in-line should appear in Prerequisites instead (see Section 4 rules)
• Cross-SOP references: When one SOP naturally leads to or depends on another, reference it by name: "If pipeline depth is below target, trigger the Cold Outreach Batch SOP." Format:
• Heading 2: "Procedure"
• Numbered list
• Skill names in bold: "Run the Weekly Pipeline Review skill"
• Decision points as sub-text within the step

Section 6: Expected Outcome

Type: heading_2 ("Expected Outcome") + paragraph Word count: 30-60 Variable dependencies: Name, Category Content rules:

• Describes what "done" looks like as a completed state, not a process description
• Written as a list of concrete artifacts or conditions: "You'll have [X], [Y], and [Z]"
• Every outcome must be verifiable — the buyer should be able to look at their work and confirm the SOP is complete
• No aspirational language. No "you'll feel more confident." Only observable outputs. Format:
• Heading 2: "Expected Outcome"
• Single paragraph
• Items separated by commas or listed with "and"

Section 7: Common Mistakes

Type: callout with ⚠️ emoji Word count: 60-120 Variable dependencies: Category, Name Content rules:

• 1-3 specific mistakes consultants make with this SOP — not generic errors
• Each mistake names the behavior AND the consequence: "[What they do wrong] — [what happens as a result]"
• Written in the expert's direct voice — this is where the perspective comes through strongest
• Focus on mistakes specific to solo consultants, not team/enterprise errors
• No "don't forget to..." platitudes. Real operational failures. Format:
• Callout block with ⚠️ emoji
• Bold opener: "Common mistakes:" followed by the items
• Each mistake as a separate line within the callout, prefixed with dash
• Mistake behavior in bold, consequence in plain text

Content Generation Constraints (Global)

1. Word count ceiling: ~250-350 words per SOP. This is the 9 PM test. The expert profile says: "Trigger, Steps, Skill, Outcome. That's it." If a generated SOP exceeds 350 words, it has padding that needs to be cut.

1. Tool-agnostic, skill-precise. Buyer's tools are generic ("your CRM", "your calendar"). Skill calls are exact ("Run the Proposal Builder skill with the prospect's requirements as input").

1. Strategic skills are dependencies. When a recurring SOP references a strategic skill (Ideal Client Profile Refiner, Annual Plan Builder, Offer Suite Designer, Exit Readiness Assessment, etc.), frame it as a prerequisite: "Open your current [output name]." Do not instruct the buyer to re-run the strategic skill at the recurring frequency.

1. No hallucinated statistics. No specific numbers, percentages, or frequencies unless they come directly from the entry's variable data. Use directional language: "most consultants," "significantly," "consistently."

1. Cross-SOP references. When one SOP naturally leads to or depends on another, reference it by name: "If pipeline depth is below target, trigger the Cold Outreach Batch SOP." This builds the system feeling — SOPs connect to each other, not just to skills.

1. Dollar signs. Escape as \$ in all Notion content.

1. No padding. Every sentence must carry information. If a step can be said in 20 words, don't use 40.

1. Database-only properties. Category, Skills Referenced (multi_select), Practice Stage, and Time to Complete are database properties for filtering. They do NOT appear as separate sections in the page body. Time to Complete appears only inside the Quick Reference callout. Skills appear only in-context within procedure steps.

Canonical Skill Reference

The 52 Claude Skills that SOPs may reference. All skill names must match exactly.

Business Development: Diagnostic Call Prep, Weekly Pipeline Review, Referral Ask Builder, Follow-Up Sequence Writer, Cold Outreach Personalizer, Strategic Partnership Pitch Proposals & Pricing: Proposal Builder, Change Order Builder, Pricing Review Analyzer, SOW Generator, Value Justification Brief, Retainer Renewal Pitch, Competitive Positioning Brief Client Onboarding: Client Onboarding Welcome Sequence, Engagement Kickoff Agenda, Expectation-Setting Script, Client Intake Questionnaire Builder, Stakeholder Map Builder, Quick-Win Identifier Client Delivery & Prep: Session Prep Brief, Deliverable Draft Builder, Progress Update Builder, Client Presentation Prep Client Communication: Scope Creep Response, Session Recap Writer, Action Item Tracker, Milestone Celebration Note, Re-Engagement Email Writer, Late Payment Follow-Up, Difficult Conversation Prep, Fee Increase Announcement, Project Pause Communication, Engagement Closure Summary Content & Visibility: Speaking Proposal Writer, Thought Leadership Post Writer, Case Study Builder, LinkedIn Profile Optimizer, Speaking Talk Outline Builder, Newsletter Issue Writer, Content Repurposer Operations & Admin: Capacity Planner, SOP Writer, Meeting Agenda Builder, Quarterly Business Review Prep, Client Profitability Analyzer, Process Bottleneck Identifier Practice Strategy: Annual Plan Builder, Offer Suite Designer, Ideal Client Profile Refiner, Revenue Goal Reverse Engineer, Exit Readiness Assessment, Quarterly Reflection Debrief

Trigger Reference (from product-idea.md)

Each SOP's trigger text for the Quick Reference callout:

Sample Skeleton: Weekly Pipeline Review

Weekly Pipeline Review

📋 Frequency: Weekly | Time: 30 min | Trigger: Every Monday morning, before email

Without a recurring pipeline review, you deliver brilliantly for current clients while your pipeline drains. This SOP keeps your opportunities visible, your follow-ups current, and your quarterly revenue target honest.

Prerequisites

• Your pipeline tracker (CRM, spreadsheet, or equivalent) with current opportunity data
• Last week's business development activity (calls made, proposals sent, meetings held)
• Your quarterly revenue target (output from the Revenue Goal Reverse Engineer skill, or your own number)

Procedure

1. Open your pipeline tracker and scan all active opportunities.
2. Run the Weekly Pipeline Review skill with last week's activity as input.
3. Review the skill output — it flags stalled opportunities and compares pipeline depth to your quarterly revenue target.
4. If pipeline depth is below target, prioritize business development this week. Run the Capacity Planner skill to identify which days have capacity for outreach.
5. If pipeline depth is on target, update next actions on each active opportunity.
6. For any opportunity stalled 7+ days with no response, trigger the Follow-Up Sequence Activation SOP.
7. Log your weekly pipeline count and move the top 3 priority actions to your weekly plan.

Expected Outcome

An updated pipeline with next actions on every active opportunity, a clear read on whether you're tracking to quarterly revenue, and — if you're not — a specific list of what to do about it this week.

⚠️ Common mistakes:

— Only reviewing when pipeline feels thin. By the time it feels thin, you're 6-8 weeks from a revenue gap. The whole point is reviewing when you're busy.

— Updating the tracker without running the skill. Your gut says the pipeline is fine. The skill checks the math. Those are different things.