Marketing Plan

You are an expert marketing strategist operating at fCMO (fractional CMO) level. Your job is to produce a comprehensive, executable 12-month marketing plan for a specific client or company, structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to their actual budget, team, stage, and capabilities, and cross-referenced with the full marketing-ideas library and the embedded 17-section current-state audit rubric.

The deliverable is a single Notion-paste-ready markdown document — the kind of strategy artifact a fractional CMO would present to founders. It must be specific to the client (not generic), exhaustive (covers every tactical surface area, not just what's prescribed), and operationally honest (reflects what their team can actually execute with their current stack and headcount).

When to use

Invoke this skill when:

• A user is starting a new client engagement as a fractional CMO or marketing consultant
• A founder needs a 12-month marketing roadmap they can share with their team or investors
• A team wants to consolidate scattered marketing work (SEO research, brand voice docs, audit findings, onboarding analyses) into a single coherent plan
• The user explicitly asks for a "marketing plan," "growth plan," "GTM plan," "fCMO plan," "AARRR plan," or "90-day + 12-month marketing roadmap"
• An existing scored audit (from any prior current-state assessment) needs to be sequenced into an action plan

Do not use when the user wants a tactical execution document for a single channel (use the channel-specific skill instead — emails, ads, seo-audit, onboarding, etc.), or when the user just wants marketing ideas without commitment to a plan (use marketing-ideas).

How this skill is invoked

/marketing-plan {client-name-or-domain}

Examples:

• /marketing-plan quietude.app
• /marketing-plan acme-saas
• /marketing-plan (will prompt for client name)

On invocation, the skill reads ~/marketing-plans/{client-slug}/progress.md and resumes based on the state machine documented in references/methodology.md Step 1.1.2 (fresh → INIT → REVIEW → FINALIZE → finalized). Finalized plans are never silently overwritten — the user is asked whether to revise as v{N+1}, start fresh, or re-open a section.

The three phases

The full workflow lives in references/methodology.md. Quick summary:

Phase 1 — INIT (research + intake)

Read all available materials about the client. Pull data from any wired tools (Ahrefs, GA4 MCP, Stripe MCP, etc.). Conduct structured intake covering: client overview, ICP, current funnel state, funding state, team composition, marketing budget, channels currently active, what's already been done, what's in-flight, what's stuck, tooling stack. Save to research.md.

Use the embedded 17-section current-state rubric (references/current-state-rubric.md) as your scoring lens for Section 3 — score each section 0–5 against available materials.

Phase 2 — REVIEW (walk through each of 13 sections interactively)

Present each section's draft in chat. For each section you can:

• Approve as-is ("good," "next")
• Adjust ("change X to Y")
• Add observations ("also mention Z")
• Expand ("go deeper on this")

Save each confirmed section to the progress file as you go. The skill is resumable — if interrupted, run /marketing-plan client-name again to pick up at the next unfinished section.

Phase 3 — FINALIZE (compile + verify + publish)

Compile all 13 sections into final_plan.md. Run a verification pass: confirm cross-references (marketing-ideas idea numbers, related skills, MCP integrations) are accurate; check for machine-specific paths that shouldn't ship; ensure the brand voice matches what was captured in the strategic frame.

Optionally offer to publish to a shared GitHub repo (e.g., {client-org}/{client-context}/marketing/plan.md) if the user wants to share it with the team.

The 13-section plan structure

Full template lives in references/plan-template.md. The structure:

1. Executive summary — 3 big bets, 90-day priorities, 12-month outcome. Written so it can be lifted into an investor or board update.
2. Strategic frame — Category claim, ICP distilled, business-model logic, brand voice non-negotiables.
3. Current state — Team, budget, what's done, what's in-flight, what's stuck. Scored against the embedded 17-section current-state rubric (references/current-state-rubric.md).
4. Acquisition — How strangers become aware. Channels current + planned + skipped, 90-day and 12-month moves, skills + tools.
5. Activation — How a new user has an experience that converts. Onboarding, first session, App Store / signup, paywall, lifecycle setup.
6. Retention — How a converted user stays and deepens. Lifecycle flows, churn prevention, win-back, support-as-marketing.
7. Referral — How retained users bring more users. Ambassador / affiliate / Guides / WOM mechanics.
8. Revenue — Pricing, packaging, upsells, bundles, hardware-to-software, B2B ACV.
9. 90-day roadmap — Weeks 1–2 (Unblock), 3–4 (Foundation), 5–8 (Velocity), 9–12 (Compound). AARRR-tagged, owner-assigned.
10. 12-month outlook — Quarterly milestones tied to funding-stage capability unlocks.
11. Marketing operations stack — Marketing skills + MCP/API integrations mapped to each AARRR stage. Capability unlocks by funding stage.
12. Tactical idea bank — All 139 ideas from marketing-ideas cross-referenced to AARRR + client-specific status (Now / Q2 / Q3+ / Q4+ / Skip).
13. Measurement, RACI, open decisions, appendix — North-star metric, leading indicators by stage, RACI table, blocking decisions, links to deeper docs.

The AARRR framing

AARRR replaces the older "channels and tactics" approach because it forces every recommendation to be funnel-stage-tagged, which makes the plan executable in priority order.

Full primer in references/aarrr-framework.md. Quick rule:

• Acquisition = strangers → aware (top of funnel)
• Activation = aware → first valued experience (signup, onboarding, first session)
• Retention = repeat users (lifecycle, churn prevention, deepening engagement)
• Referral = retained users → bring more users (programs, viral mechanics)
• Revenue = monetization (pricing, upsells, bundles, ACV expansion)

Brand and content are cross-cutting, not their own AARRR stage — they serve every stage.

The current-state rubric

The plan's "Current State" section scores the client against the embedded 17-section rubric. Full rubric in references/current-state-rubric.md — it's the source of truth, not a derivative of any external skill.

If the user already has a separately scored audit, ingest those scores directly into Section 3. Otherwise, score from available materials using the rubric as your lens — mark "scored from materials" in the section header so the team can push back where they have better data.

Cross-references — skills this plan integrates with

1. marketing-ideas — 139 proven marketing tactics. Section 12 of the plan cross-references every one to AARRR + client status. Detail in references/idea-cross-reference.md.
2. product-marketing — Sets up the foundational .agents/product-marketing.md context file (positioning, ICP, voice). Read this first; Section 2 (Strategic frame) builds on it.
3. AARRR-stage-specific skills — onboarding, signup, emails, referrals, pricing, etc. The "Marketing operations stack" (Section 11) maps these to AARRR stages.

The plan is opinionated about which skills serve which stages. Full mapping in references/ops-stack-mapping.md.

The marketing operations stack

This is the differentiator of an fCMO-style plan vs. a generic marketing plan. The plan doesn't just say what to do — it says what skills and tooling execute it.

A small team + an fCMO + the marketing-skills library + MCP integrations can output the work of a 15–20-person traditional marketing org. The plan must show this stack explicitly, AARRR-stage by AARRR-stage.

Full mapping in references/ops-stack-mapping.md.

Funding-stage capability unlocks

Every plan must include explicit "what changes when funding closes / when budget unlocks" reasoning. This makes the plan investor-friendly (founders mid-raise see what they're buying) and operationally honest (we're not pretending the team can spend $50K/mo on paid before the round closes).

Standard tiers in references/funding-stage-unlocks.md:

• Pre-seed / bootstrapped — $0–$2K/mo total marketing spend; organic only
• Seed close — $5–$15K/mo paid test budget; first marketing hire
• Seed deployment — $20–$50K/mo paid; second marketing hire
• Series A — $50–$150K/mo paid; performance + content + designer; international consideration
• Series B+ — $150K+/mo paid; brand campaigns; PR firm; full-stack marketing org

Use these as anchors. Adjust for category (consumer apps and ecommerce can spend more; deep-tech B2B may spend less).

Setting the budget scientifically

The funding-stage anchors above tell you what's in the ballpark. To set the actual number defensibly, use one of two methods (full detail in references/budget-planning.md):

1. Revenue-Based (5–40% of ARR) — start from comfortable spend, forecast resulting revenue. Best when historical CAC data exists.
2. Goal-Based — reverse-engineer the budget from the revenue target. Formula: [(New ARR / (ARPC × 12)) × CAC] / annual retention rate. Best for fundraising or when the goal is fixed.

Always add 10–20% experimental budget on top — CAC is the main dependency, and the experimental layer is what funds the next-channel investment before the current one plateaus.

For VC-backed Series A+ clients, anchor the 12-month outlook against the 3-3-2-2-2 rule (3× in years 1–2, 2× in years 3–7 from $1M ARR).

Growth patterns — the real shape of SaaS growth

Pitch decks show hockey sticks. Real growth is a series of S-curves with plateaus between them. Full framework in references/growth-patterns.md. Key implications for the plan:

• Phase identification — $0–10K ARR (grueling), $10K–100K (treacherous middle), $100K–1M (acceleration). Section 3 names the current phase; Section 10 sequences the next.
• Linear vs step-function — most healthy SaaS growth is linear (predictable additions per month) punctuated by step-functions (enterprise tier launch, new segment, channel breakthrough). The plan should describe both honestly — not promise exponential.
• S-curve layering — Channel × Product × Market. Start the next S-curve while the current one is still growing. Riding any single S-curve to its ceiling before investing in the next produces multi-month plateaus.

Team and agency model

Strategy lives in-house. Execution can — and often should — be outsourced. Full framework in references/team-and-agency-model.md. Three implications for every plan:

1. First hire is a strategist, not a tactician. Look for a π-shaped marketer (two deep skill sets) — common high-leverage combos: Product Marketing + Growth Marketing, Product Marketing + Content Marketing, Growth Marketing + Content Marketing.
2. Title conservatively. First marketing hire is almost always Manager or Lead, not VP or CMO. Inflated titles paint the org into a corner when you scale.
3. Use contractors and small niche agencies for execution. Most pre-Series-A companies should rely on individual contractors for nearly all outsourced work; deepen agency relationships as the company moves into Growth Stage and Scale Stage.

What every plan must customize

A generic plan is a failed plan. Every plan must explicitly customize for:

1. Current marketing budget — exact $/mo, broken down by line (paid, tools, headcount, retainers). Plus blended CAC (must include salaries, content costs, tools, retainers — not just paid ad spend) and current %-of-ARR allocation.
2. Unit economics — ARPC, annual retention rate, LTV. These feed the budget math in Section 8 and Section 10.
3. Team composition and surface area — every person who touches marketing, with what they own. Identify whether the strategic owner (if there is one) is π-shaped, T-shaped, or tactical-only.
4. What the client is currently doing — by channel, with status (working / not / TBD).
5. What they've already done that should be acknowledged — past launches, PR moments, content, partnerships. Don't write a plan that ignores work they're proud of.
6. Phase of SaaS growth — $0–10K ARR / $10K–100K / $100K–1M / $1M+. Each phase has its own binding constraint.
7. Future funding milestones — when the next round closes, what budget tier that unlocks, and which capability comes online (first hire, paid channels, agency relationship).
8. The marketing skills mapped to specific moves — every move in the AARRR sections names the skill that executes it.
9. The API/MCP/tool connections that enable execution — every move names the tooling that makes it doable without hiring.

If you can't confirm any of these in INIT, list them in Section 13's "Open decisions" — never gloss over them. CAC unknown is the highest-impact open decision — every revenue projection depends on it.

Common client-type variations

Plan structure stays consistent. What changes:

• B2B SaaS — Acquisition leans on SEO + content + outbound + LinkedIn. Activation = signup + product trial. Retention = product engagement + CSM motion. Referral = customer advocacy. Revenue = expansion / NRR.
• D2C consumer app — Acquisition leans on App Store + paid social + influencer + PR. Activation = onboarding + first session + paywall. Retention = lifecycle email + push. Referral = sharing mechanics. Revenue = subscription + upsell.
• Hardware-led — Acquisition leans on PR + retail + Amazon + Shopify SEO. Activation = unboxing + setup + first use. Retention = software companion + community. Referral = gifting + reviews. Revenue = blended LTV hardware + accessories + subscription.
• Marketplace — Activation has two sides (supply + demand). Retention is repeat transaction frequency. Revenue is take-rate × GMV.
• Developer tool — Acquisition leans on technical content + DevRel + documentation SEO. Activation = first build / first integration. Retention = depth of integration. Referral = team adoption.

Detail in references/client-types.md.

Quality bar

What separates a good plan from a generic one:

Good plan signals:

• Every move names the AARRR stage it serves
• Every recommendation is anchored in real client data (their actual budget, their actual team, their actual current channels)
• The 90-day roadmap has owners, not just actions
• The funding-stage section explains what changes when the next round closes
• The ops stack section names specific skills + MCPs per move
• The idea bank shows what we're not doing and why (skipped ideas with rationale)
• The exec summary can stand alone — could be lifted into an investor update
• Open decisions are explicit, not glossed over

Failure modes to avoid:

• Listing tactics without sequencing
• Recommending things the team can't execute at current size
• Pretending paid budget exists before the round closes
• Glossing over uncomfortable metrics (e.g., churn) instead of naming them as open decisions
• Generic language ("build a community," "improve SEO") without specific moves
• Ignoring brand voice — every plan section must respect the client's voice rules
• Padding the plan with skills/ideas the client doesn't actually need
• Not acknowledging work the team has already done

Output format

The final deliverable is a single markdown file: ~/marketing-plans/{client-slug}/final_plan.md.

Headers (## 1. Executive summary, etc.) are H2 for clean Notion paste. Tables for any structured comparison (RACI, idea bank, ops stack). Status legend for the idea bank. Internal references to other sections use §N (e.g., "see §5 for Activation detail").

Length expectation: ~8,000–12,000 words for a comprehensive plan. Shorter is fine if the client is early-stage with limited surface area; longer is fine if the client has years of history to acknowledge.

File layout per plan

~/marketing-plans/
└── {client-slug}/
    ├── materials/         # Client-provided files (decks, audit output, brand-voice doc, etc.)
    ├── research.md        # Research record written during INIT
    ├── progress.md        # State machine — phase, current_section, approved artifacts, plan_version
    ├── sections/
    │   ├── 01.md          # Each approved section saved as a canonical artifact
    │   └── ...            # Zero-padded so they sort in order
    └── final_plan.md      # Compiled deliverable (FINALIZE output)

The full schema for progress.md and the resumption decision tree live in references/methodology.md Steps 1.1.1 and 1.1.2.

Related skills

• product-marketing — Run first. Captures positioning, ICP, voice in .agents/product-marketing.md so every section of the plan references the same foundation.
• marketing-ideas — Source of the 139 tactics in Section 12.
• customer-research — Deepens the ICP and voice-of-customer inputs that feed Section 2 (Strategic frame).
• onboarding — Deep work on Section 5 (Activation).
• emails — Deep work on Section 6 (Retention) + onboarding emails in Section 5.
• referrals — Deep work on Section 7 (Referral).
• pricing — Deep work on Section 8 (Revenue).
• seo-audit / ai-seo / programmatic-seo — Deep work on the SEO portion of Section 4 (Acquisition).
• ads / ad-creative — Deep work on the paid portion of Section 4 once budget unlocks.
• launch — Deep work on launch moments inside Section 4 / Section 9.

Task-specific questions (used during INIT)

The full intake questionnaire lives in references/methodology.md. The most important questions:

1. Funding state — What round are you in? How much raised so far? Burn? Runway? Upcoming rounds and timing?
2. Team — Who are all the people who touch marketing? What does each own? Where are the gaps?
3. Budget — What's the current monthly marketing spend, broken down by paid acquisition, tools, retainers, headcount? What budget unlocks when the next round closes?
4. Current channels — What's working today? What's not? What have you not tried yet?
5. Already done — What past campaigns / launches / content / PR moments should this plan acknowledge?
6. In-flight — What's drafted but not shipped? What's blocking each item?
7. Tooling stack — What's wired? Customer.io / Mailchimp / Resend? Shopify / Stripe / App Store Connect? GA4 / Mixpanel / Amplitude? GitHub / Notion / Figma?
8. Beta or GA? — If product is in beta, what's the GA timeline? Throttling? What gates exist?
9. The most important thing to fix this quarter — founder's read.
10. The most important thing to ignore this quarter — what looks important but isn't.

How exhaustive should the plan be?

Default to comprehensive. Founders share a plan with their team and investors; brevity here is false economy. A 10,000-word plan with the right structure is more useful than a 3,000-word plan that misses the ops stack or the idea bank.

That said: don't pad. Every section should be dense, not bloated. If a section has nothing to say, write that explicitly — "Q4+ — long-game / not in scope for this 12-month plan" is honest and useful.

A note on tone

This plan is written for founders who are sharp, busy, and skeptical of marketing-speak. Write like a thoughtful colleague, not a deck-slide-writer. No jargon for jargon's sake. Direct claims, named tradeoffs, explicit assumptions. When unsure, name the open question rather than guessing.

The exec summary should be short enough to read in 60 seconds. The rest should reward deep reading.

---

Supporting file: evals/evals.json

{
  "skill_name": "marketing-plan",
  "evals": [
    {
      "id": 1,
      "prompt": "I'm starting a fractional CMO engagement with a Series A B2B SaaS doing $2M ARR, 12-person team with 1 marketer, $20K/month marketing budget. They want a marketing plan we can share with the team and the board. Build it.",
      "expected_output": "Should check for product-marketing.md first. Should ask for client name or use a slug. Should walk through three-phase workflow (INIT → REVIEW → FINALIZE), starting with intake covering funding state, team, budget, channels, what's done, in-flight, tooling stack. Should produce a 13-section AARRR-structured plan: executive summary, strategic frame, current state (scored against the embedded 17-section rubric), Acquisition, Activation, Retention, Referral, Revenue, 90-day roadmap with owner-assigned moves, 12-month outlook with funding-stage capability unlocks, marketing operations stack mapping skills + MCPs to AARRR stages, tactical idea bank cross-referencing all 139 marketing-ideas to AARRR + client-specific status, measurement framework with north-star + leading indicators + RACI + open decisions. Should be ~8–12K words, Notion-paste-ready. Should be specific to the client (their budget, team, channels), not generic.",
      "assertions": [
        "Checks for product-marketing.md",
        "Asks for client name or uses a slug",
        "Walks through INIT phase with structured intake",
        "Produces 13-section plan structured by AARRR",
        "Section 3 scores against the embedded 17-section rubric",
        "Section 9 (90-day roadmap) has owner-assigned moves, not just actions",
        "Section 10 names funding-stage capability unlocks explicitly",
        "Section 11 maps marketing skills + MCPs to each AARRR stage",
        "Section 12 cross-references all 139 marketing-ideas with client-specific status",
        "Output is Notion-paste-ready markdown",
        "Plan is specific to the client (their budget, team, current channels), not generic"
      ],
      "files": []
    },
    {
      "id": 2,
      "prompt": "We're pre-seed bootstrapped, $0 paid marketing budget, 4-person team building a D2C consumer app. Founder wants a 90-day plan + 12-month roadmap they can show investors during the upcoming raise. The product is in beta.",
      "expected_output": "Should recognize Tier 1 funding profile (pre-seed) and skip paid acquisition recommendations until budget unlocks. Should lean Acquisition heavy on organic + lifecycle + ambassador moves. Should explicitly map what unlocks when seed closes (paid test budget $5–15K/mo, first marketing hire, etc.). Should respect that the product is in beta and account for activation/throttling gates. Should include the AARRR diagnostic — likely binding constraint at this stage is Activation (onboarding) and Referral. Plan must be investor-friendly: exec summary can be lifted into an update.",
      "assertions": [
        "Recognizes pre-seed tier and uses Tier 1 budget profile",
        "Skips paid acquisition recommendations until budget unlocks",
        "Leans Acquisition on organic + lifecycle + ambassador",
        "Names what unlocks when seed closes",
        "Accounts for product being in beta",
        "Identifies binding-constraint AARRR stage (likely Activation or Referral)",
        "Executive summary can be lifted into an investor update",
        "Plan is operationally honest — doesn't pretend paid budget exists"
      ],
      "files": []
    },
    {
      "id": 3,
      "prompt": "we have an audit already done — can you take that and turn it into a real plan",
      "expected_output": "Should ask for the audit output (file path or paste). Should recognize that current-state scoring already exists and ingest it directly into Section 3 — don't re-score. Should note scoring date in case material has shifted since. Should proceed with full 13-section plan generation using audit findings to inform 90-day roadmap and AARRR sections (gaps from audit become moves in the plan).",
      "assertions": [
        "Asks for the audit output",
        "Ingests prior audit scoring directly into Section 3",
        "Does not re-score what's already been scored",
        "Notes the scoring date and flags any shifted material",
        "Uses audit gaps to inform 90-day roadmap and AARRR section moves",
        "Still produces a full 13-section plan, not just Section 3"
      ],
      "files": []
    },
    {
      "id": 4,
      "prompt": "/marketing-plan acme-saas — pick up where we left off",
      "expected_output": "Should read ~/marketing-plans/acme-saas/progress.md to determine state machine phase. Should resume from the next unfinished section in REVIEW phase, or transition to FINALIZE if all sections approved. Should NOT silently restart from scratch. If progress.md is missing or shows 'finalized', should ask: revise as v{N+1}, start fresh, or re-open a section.",
      "assertions": [
        "Reads ~/marketing-plans/acme-saas/progress.md",
        "Resumes from next unfinished section based on state machine",
        "Does not silently restart from scratch",
        "Handles finalized state by asking user how to proceed (revise / fresh / re-open)",
        "Saves each newly confirmed section to the progress file"
      ],
      "files": []
    },
    {
      "id": 5,
      "prompt": "I need a plan for a hybrid hardware+software wellness company. They sell a physical product and a subscription app. Series A, $100K/month marketing budget, 8-person team including a marketing lead.",
      "expected_output": "Should recognize hybrid hardware+software archetype and consult references/client-types.md for archetype-specific emphases. Acquisition leans PR + retail + Amazon + Shopify SEO + paid. Activation = unboxing + setup + first session + paywall. Retention = lifecycle + community. Referral = gifting + reviews. Revenue = blended LTV (hardware + subscription + accessories). Should recognize Series A tier and recommend appropriate paid spend. Should include cross-cutting brand + customer-research moves. Idea bank should skip ideas that conflict with premium positioning or hardware constraints.",
      "assertions": [
        "Recognizes hybrid hardware+software archetype",
        "Acquisition leans on PR, retail, Amazon, Shopify SEO, paid",
        "Activation covers unboxing, setup, first session, paywall",
        "Retention covers lifecycle, community",
        "Referral covers gifting, reviews",
        "Revenue covers blended LTV with hardware + subscription + accessories",
        "Recognizes Series A tier in budget recommendations",
        "Idea bank skips ideas that conflict with brand fit, with explicit rationale"
      ],
      "files": []
    },
    {
      "id": 6,
      "prompt": "Just give me a quick marketing plan. Don't make it long.",
      "expected_output": "Should resist defaulting to a short plan. Should explain that a marketing-plan is the comprehensive fCMO-deliverable artifact (~10K words) and that for a single-channel quick plan, the channel-specific skill is the right tool (emails, ads, seo-audit, etc.). Should offer alternatives: (a) full marketing-plan as designed, or (b) point to a specific skill for the user's actual need. Should NOT silently produce a stripped-down 3K-word plan that misses the ops stack or the idea bank.",
      "assertions": [
        "Resists short-plan request and explains why",
        "Names marketing-plan as the comprehensive fCMO artifact",
        "Recommends channel-specific skills for single-channel quick plans",
        "Offers alternatives clearly",
        "Does not silently produce a stripped-down plan"
      ],
      "files": []
    }
  ]
}

---

Supporting file: references/aarrr-framework.md

AARRR Framework — Primer for Plan Sequencing

AARRR (Dave McClure's "pirate metrics") is the spine of every plan produced by this skill. This doc is the primer + the decision rules for when each stage gets prioritized.

The five stages

Signup boundary rule. Signup intent (a stranger landing on the signup page) is Acquisition. Signup completion and everything after (first key action, trial-to-paid) is Activation. Apply this rule consistently across all docs and the plan template.

Why AARRR for plan sequencing

Three reasons.

1. Funnel-stage tagging forces prioritization. Without AARRR, marketing plans become channel-organized ("here's the SEO plan, here's the social plan, here's the paid plan"). Channels can address multiple stages; tagging by stage instead asks the more useful question: what stage of the funnel is the binding constraint right now?

2. Fix the leak before pouring water in. The Activation/Retention question ("does the funnel convert at acceptable rates given exposure?") is usually higher leverage than the Acquisition question ("how do we get more exposure?"). AARRR sequencing surfaces this naturally.

3. The Revenue / Referral conversation is honest. Most marketing plans bury monetization under "growth" and treat referral as wishful thinking. AARRR forces explicit treatment of both.

Brand and content — not a stage, cross-cutting

A common mistake: making "Brand" or "Content" the sixth bucket. They're not — they serve every stage.

• Brand voice governs every piece of copy across every stage
• Content feeds Acquisition (SEO, social), Activation (onboarding copy), Retention (email lifecycle), Referral (ambassador talking points), Revenue (pricing pages, sales material)

In the plan, brand/content shows up as the strategic frame (Section 2) and cross-cutting in Section 11's ops stack — never as its own AARRR section.

Diagnosing the binding constraint — which AARRR stage is highest leverage?

For every client, one or two AARRR stages will be the binding constraint. The plan sequences moves there first.

Decision rules:

If you don't have any users → start with Acquisition

• Pre-launch / day-0 / waitlist stage
• No funnel data exists
• Leverage = building the first 100 users

If you have users but they bounce → start with Activation

• Signups happen but activation rate is low
• App Store conversion is poor
• Onboarding completion is broken
• Day 1 → paid rate is much lower than Day 30 → paid (means product converts given time but onboarding doesn't bridge to it)
• Leverage = bridging signup to first felt value

If activation works but users churn → start with Retention

• Month 1 retention is below category norms
• Activated users stop using within 7–14 days
• LTV is short
• Leverage = lifecycle, deepening engagement, churn prevention

If retention is strong but growth is slow → start with Referral / Revenue

• Retained users love the product but don't share
• Inbound referrals come in unstructured
• Pricing hasn't been pressure-tested
• ARPU is low for the value delivered
• Leverage = WOM mechanics + pricing optimization (these often cluster)

If everything works at small scale → start with Acquisition (scaling)

• Funnel is healthy
• Question is just "more"
• This is the "post-fit" scaling problem

Stage-by-stage strategic patterns

Acquisition

The diagnostic question: Where is the gap between TAM-level awareness and current funnel volume? What channels are saturated by competitors vs. open?

Common Acquisition moves:

• SEO content strategy (organic compounding)
• Founder-led channels (LinkedIn, X, Substack for B2B; Instagram/TikTok for D2C)
• Paid acquisition (when budget unlocks)
• App Store / Play Store / marketplace listing optimization
• PR and credibility-anchor amplification
• Events (live, webinar, conference speaking)
• Partnerships (newsletter swaps, integration co-marketing, reseller / agency partners)
• Hardware / commerce surface (Shopify SEO + Amazon for hybrid businesses)
• B2B sales support (case studies, partner pages, vertical content)

Sequencing principle: Build the organic compound first (SEO + founder-led + content + PR amplification + ambassadors). Only layer paid on top of a working organic baseline. Premature paid amplifies what's broken.

Activation

The diagnostic question: Where in the user's first session do they decide "this works for me" or "this doesn't"? What stops them from reaching that moment?

Common Activation moves:

• Bedrock fixes (broken gates, broken signup steps, broken paywall)
• Onboarding tests / rebuild (often the most leveraged single move)
• App Store listing rewrite (the threshold to the trial)
• Lifecycle Flow ship order (when to ship onboarding emails)
• Paywall structure + trial length
• Free → paid bridge (in-app upsells, soft paywalls)

Sequencing principle: Get to first felt value as fast as possible. Everything that adds friction between "user opens app" and "user has the experience that converts them" is a candidate to cut.

Retention

The diagnostic question: Why do users churn? What would have made them stay? What's the "second moment of value" after the first one?

Common Retention moves:

• Lifecycle email flows: onboarding, lapsed user re-engagement, post-purchase, win-back
• Subscription / preference centers
• Churn reconciliation (often metric definitions don't match across surfaces)
• Hardware → software activation paths (for hybrid businesses)
• Annual plan defaults / pricing structure (cross-cuts Revenue)
• Support as marketing (high-touch moments that drive stories)
• Community + practitioner networks

Sequencing principle: Ship lifecycle flows in the order their content is most stable. Hardware post-purchase flows ship first (they don't reference in-app screens that might change). Onboarding emails ship last (they reference UI that might change). Win-back is a quarterly campaign, not a one-time flow.

Referral

The diagnostic question: Is there inbound referral interest that isn't being captured? What's the share-after-value moment that's natural to the product?

Common Referral moves:

• Ambassador / affiliate program (start with inbound interest, not cold recruitment)
• Share-after-value moments built into the product (reflection prompts, milestone celebrations)
• Founder amplification (founder as referrer-zero)
• Long-game expert / Guides / certified-host networks (for category-creating businesses)
• Gifting flows (consumer / hardware)
• Two-sided referrals (reward both referrer and referred)

Sequencing principle: Lead with whoever is already raising their hand. If there are 5 inbound ambassadors, launch with those 5 — don't wait for a "complete program." Iterate based on what they tell you.

Revenue

The diagnostic question: Is the company underpricing? Underpackaging? Missing an upsell? What's the "right" price discipline given LTV and brand voice?

Common Revenue moves:

• Pricing audit (what's actually charged today vs. listed?)
• Annual plan defaults
• Hardware → software bundling formalization
• Storefront / commerce page optimization
• B2B case studies + sales material
• Long-term value pool flags (data, expansion, enterprise) — flagged not executed

Sequencing principle: Run the pricing audit before testing changes. Surprisingly often, the "implied" pricing on the dashboard doesn't match the listed price — discounts, trials, or plan mix distorts the read. Surface the ground truth first.

How to assign a move to a stage

Some moves clearly belong to one stage. Others span. The rule:

Assign to the stage where the move's primary measurable impact lands.

Examples:

• "Rewrite App Store listing in voice" — spans Acquisition (organic discovery) and Activation (threshold to trial). Primary impact = Activation (trial conversion rate). Assign to Activation, mention crossover.
• "Eye mask Shopify page rewrite" — spans Acquisition (organic search for sleep mask) and Revenue (sale conversion). Primary impact = Revenue (transaction). Assign to Revenue, mention crossover.
• "Alex's LinkedIn cadence" — Acquisition (top of funnel for D2C subscribers).
• "Customer.io Flow 6 (eye mask post-purchase)" — Retention (deepens hardware buyer engagement) with crossover to Activation (hardware → app premium activation path).

When in doubt: where would removing this move hurt the most? Assign there.

When the AARRR breakdown isn't equal

For most clients, the plan won't have equal volume across stages. That's fine — and worth surfacing as a diagnostic.

• Heavy Acquisition section = client has product-market fit but top-of-funnel is the bottleneck. Common for early-stage with strong retention metrics.
• Heavy Activation section = client has traffic but conversion is broken. Often beta-stage products.
• Heavy Retention section = client has churn problem. Often mid-stage products that scaled past PMF without lifecycle infrastructure.
• Heavy Referral section = client has loyalty but no WOM mechanics. Often consumer products with passionate users.
• Heavy Revenue section = client is underpricing or missing monetization layers. Common for tools transitioning from free to paid.

If a plan ends up evenly distributed across all five stages, the diagnostic was probably weak — re-examine the funnel state intake to find where the binding constraint is.

A note on the order of presentation

Always present AARRR in order (Acquisition → Activation → Retention → Referral → Revenue) regardless of priority order.

This is for the reader's mental model. Founders expect the funnel to flow top-to-bottom. If Retention is the most-leveraged stage but you lead with Retention, the reader has to context-switch.

To signal priority, use the executive summary (Section 1) — name the biggest bets there. The AARRR breakdown then walks the funnel in order, with the most leverage-positive section being the longest and most-detailed.

---

Supporting file: references/budget-planning.md

Budget Planning — Scientific Methods for Setting the Marketing Budget

The problem with most SaaS marketing budgets is that they're pulled out of thin air — a number that hopefully doesn't constrain growth too much, but doesn't anchor in customer-acquisition economics either. The result: when someone asks "why this number?" there's no answer.

Two scientific methods solve this. Use one (not both) in Section 8 (Revenue) and Section 10 (12-month outlook) of every plan.

Excerpted and adapted from Founding Marketing by Corey Haines.

Method 1 — Revenue-Based (5–40% of annual revenue)

Direction: budget → revenue goal.

You start with what the company can comfortably spend on marketing, then forecast what revenue that spend can plausibly generate.

The ranges

For reference: public SaaS companies routinely report sales-and-marketing spend between 20% and 55% of revenue (Zoom historically ran between 20% and 55% across years).

The math (Conservative example)

Business at $1M ARR, 5% allocation:

• Annual marketing budget: $50,000
• Blended CAC: $100 → can acquire 500 new customers
• ARPC: $50/mo → adds $300K to ARR
• Account for 15% annual churn → 85% × $300K = +$255K net new ARR
• End-of-year goal: $1.255M ARR

The math (Aggressive example)

Business at $1M ARR, 40% allocation:

• Annual marketing budget: $400,000
• Blended CAC: $100 → can acquire 4,000 new customers
• ARPC: $50/mo → adds $2.4M to ARR
• End-of-year goal: $3.4M ARR

Two keys to making this method work

1. Know your blended CAC (see "Calculating CAC" below)
2. Match the allocation percentage to your actual ambition. A founder running 5% allocation while telling the board they expect to triple revenue is showing two incompatible signals.

Method 2 — Goal-Based (reverse-engineered from the revenue target)

Direction: revenue goal → budget.

You start with the revenue goal and work backward through the unit economics to derive the budget required to hit it. Best for:

• Companies just starting up (no historical CAC baseline yet, working from first principles)
• Companies anticipating outside capital (need to defend the ask)
• Companies using revenue-based financing (Pipe, Capchase, Founderpath)

The formula

Marketing budget = [(New ARR / (ARPC × 12)) × CAC] / annual retention rate

Worked example: $1M ARR → $2M ARR

Step 1 — How much new ARR per customer? ARPC × 12 = $50 × 12 = $600 ARR per new customer

Step 2 — How many new customers do we need? $1,000,000 / $600 = 1,667 new customers

Step 3 — What's the raw acquisition cost? 1,667 × $100 CAC = $166,700

Step 4 — Account for churn (15% annual = 85% retention) $166,700 / 0.85 = $196,118 (round to $200K)

When someone asks how you got to the budget, walk them through the four steps. It's defensible.

Why this formula and not something simpler

The four steps each correspond to a real economic reality:

• Step 1 converts MRR-language into the ARR-language a board talks in
• Step 2 names the customer count, which is what the funnel actually has to deliver
• Step 3 anchors the budget in the cost of acquisition
• Step 4 acknowledges that churned customers don't count toward net new ARR, so the budget needs to cover the gap

Required buffer

Always add 10–20% as "experimental budget" on top of the formula output. CAC is the main dependency; if CAC comes in 50% higher than estimated, the cascading effect is missing the revenue goal. It is much cheaper to overestimate CAC than to underestimate it.

The experimental budget also funds the experiments that find your next channel before your current one plateaus (see growth-patterns.md — channel S-curves).

The VC growth path (3-3-2-2-2 rule)

Once a company has crossed $1M ARR and taken a Series A, the implicit benchmark VCs expect is:

That's the 3-3-2-2-2 rule. Useful when:

• The plan needs to map 12-month and 36-month milestones to VC expectations
• The founder is mid-raise and the board needs to see a plausible path to the next round
• Section 10 (12-month outlook) needs anchoring against an industry benchmark, not just internal ambition

Most companies miss it. That's fine. Knowing the benchmark gives the team a defensible reason to either match it or explicitly choose not to.

Calculating CAC (blended, not paid-only)

If there's no historical CAC, use a baseline: one year of revenue from the smallest paid plan. Deploy the budget, capture actual CAC data, replace the baseline with the measured number for the next planning cycle.

For an established CAC calculation, CAC must be blended. Include:

• Marketing salaries (full loaded cost, not just base)
• Advertising spend
• Marketing tech stack costs
• Content production costs (writers, designers, video editors)
• Agency / contractor retainers
• SDR / BDR salaries if doing outbound
• Tools (CRM, marketing automation, analytics)

Then divide by the number of new customers acquired in the period. That blended number is the one to use in either budgeting method.

The mistake to avoid: calculating CAC from paid ad spend alone. A company that "doesn't run ads" still has a CAC — it's just hidden in the content team, the founder's time, the SEO contractor, the conference booth.

The reality check on forecasting

This whole framework derives a budget and a revenue goal — not a 12-month month-by-month forecast accurate to the dollar.

Unless the company is publicly traded, all forecasts are educated guesses. No startup under $100M ARR reliably hits forecasts to the month. The honest framing for the plan:

• The annual goal is a defensible direction-of-travel
• The budget is the resource commitment that makes the goal plausible
• The 90-day roadmap (Section 9) is what's actionable now
• Month-to-month variance is expected; quarterly review is when the plan adjusts

What's actionable: how to deploy the budget, what concrete moves to execute, what to adjust when real data comes in.

What's not actionable: trying to forecast traffic, pipeline, retention curves, conversion rates, and channel mix all down to the decimal point and expecting that forecast to hold. Founders who over-engineer the forecast tend to spend the plan period explaining variance instead of executing.

Rule for the plan: the budget number is honest. The annual goal is honest. The month-by-month projection is illustrative.

How this flows into the plan

When to choose which method

• Method 1 (Revenue-Based) when the company has historical CAC data, a profit/burn posture, and the question is "given our posture, what's a plausible goal."
• Method 2 (Goal-Based) when the company has a specific goal (board mandate, VC milestone, fundraise target) and the question is "what budget do we need to hit it."

For most plans in the seed-to-Series-A range, Method 2 is more useful — it forces the conversation about whether the goal is funded.

---

Supporting file: references/client-types.md

Client Types — Variations by Business Model

The 13-section plan structure stays consistent across client types. What changes is the content emphasis within each section. This doc names the dominant patterns by client archetype.

Archetype 1 — B2B SaaS

Core characteristics

• Subscription revenue
• Often higher ACV ($1K–$100K+ per year)
• Sales-assisted or self-serve depending on tier
• Buyer often different from user (champion vs. end-user)

AARRR emphasis

Acquisition heavy:

• SEO is the dominant top-of-funnel motion (people search for solutions)
• Content marketing (blog, knowledge base, comparison pages) drives MQLs
• LinkedIn for both organic founder presence and paid
• Outbound (cold email + LinkedIn) often complements inbound
• Events (conferences, webinars) for high-ACV products

Activation:

• Signup → trial → first key action (PLG products)
• Trial → demo → POC (sales-led products)
• Empty states matter — guide users to first value action

Retention:

• Product engagement metrics (DAU, feature adoption)
• Customer success motion (CSM team for higher ACV)
• Lifecycle emails focused on feature discovery, value moments

Referral:

• Customer advocacy programs
• Partner / integration co-marketing
• G2 / Capterra reviews
• Champion-to-buyer expansion

Revenue:

• Expansion / NRR is often the biggest growth lever
• Tier upgrades, seat expansion, usage-based add-ons

Skills emphasis

• cold-email, programmatic-seo, competitors, seo-audit, ai-seo
• ads weighted toward LinkedIn + Google
• emails for trial nurture + lifecycle
• pricing for tier optimization

Tier-1 budget priority

• SEO + content > everything else
• Founder-led LinkedIn channel
• Customer.io / Mailchimp for nurture
• HARO + investor backchannel for PR

---

Archetype 2 — D2C Consumer App (Subscription)

Core characteristics

• Lower ACV ($5–$30/mo typically)
• High volume, lower margin per user
• App Store / Play Store as the primary acquisition surface
• Lifecycle email + push for retention
• Often paid-acquisition-driven once budget unlocks

AARRR emphasis

Acquisition:

• App Store Optimization (ASO) is the highest-leverage non-site asset
• Paid social (Meta, TikTok) often dominant once budget exists
• Apple Search Ads for high-intent App Store traffic
• Influencer + content creators
• PR + endorsements

Activation:

• Onboarding is the dominant activation surface
• Time-to-value must be minutes, not hours
• Paywall structure + trial length critical

Retention:

• Lifecycle email + push
• In-app reminders (carefully — overuse = churn)
• Subscription preference center
• Win-back campaigns

Referral:

• Built-in sharing (share-a-month flow)
• Two-sided referrals
• Influencer / creator ambassadors

Revenue:

• Annual plan default is the biggest single move (compresses MRR but improves LTV)
• Tier optimization (Free → Premium → Premium+)
• In-app upsells

Skills emphasis

• onboarding, paywalls, emails
• ads, ad-creative (heavy creative iteration)
• referrals
• pricing for annual default + tier consolidation

Tier-1 budget priority

• ASO first (highest organic leverage)
• Onboarding rebuild
• Lifecycle email shipping
• Founder-led social if founder is on-camera

---

Archetype 3 — Hybrid Hardware + Software

Core characteristics

• Physical product + software companion (e.g., Quietude's eye mask + app)
• Hardware as a distribution wedge (lower price, easier first purchase)
• Software as the LTV (recurring revenue)
• Blended CAC across both surfaces

AARRR emphasis

Acquisition:

• Shopify storefront SEO (hardware product pages target consumer search)
• Amazon listing (high-discovery, takes margin)
• PR amplification (hardware is photogenic — high-profile influencer endorsements move volume)
• Paid social for hardware (Meta + Instagram, eye-catching creative)

Activation:

• Two activations to track: hardware unboxing experience + software signup
• Hardware → software activation flow is the bridge
• Concierge setup for high-value hardware buyers

Retention:

• Hardware post-purchase lifecycle (different from app onboarding)
• Software companion drives stickiness
• Community / practitioner network around hardware

Referral:

• Hardware gifting flows (high WOM for physical products)
• Eye-catching hardware drives organic social sharing
• Reviews on Shopify + Amazon

Revenue:

• Blended LTV math is critical (hardware margin + software recurring)
• Bundle strategy (hardware buy → free Premium for X months)
• Annual plan default for software

Skills emphasis

• seo-audit for Shopify product pages
• emails for both hardware post-purchase and software lifecycle
• referrals with gifting layer
• pricing for blended-bundle math
• ads with creative-heavy Meta presence

Tier-1 budget priority

• Shopify product page optimization
• Hardware post-purchase lifecycle ship
• Bundle strategy formalization
• Hardware → app activation audit

---

Archetype 4 — Marketplace

Core characteristics

• Two-sided product (supply + demand)
• Network effects matter
• Liquidity is the critical early metric
• Take-rate × GMV is the revenue model

AARRR emphasis

Acquisition:

• Two funnels — supply and demand
• Supply often acquired through outbound / partnership / cold email
• Demand often acquired through SEO / paid / content
• City-by-city programmatic SEO common

Activation:

• Supply activation: first listing posted, first response sent
• Demand activation: first purchase / first match / first transaction
• Both sides need their own onboarding

Retention:

• Repeat transaction frequency
• Supply utilization (% of listings active)
• Demand habit (DAU / MAU)

Referral:

• Supply → supply (refer other providers)
• Demand → demand (refer other buyers)
• Cross-side referrals are weaker

Revenue:

• Take-rate optimization
• Premium tier (better matching, lower fees)
• Lead-gen vs. transaction-fee monetization

Skills emphasis

• programmatic-seo for city pages, vertical pages
• cold-email for supply-side recruitment
• referrals for both sides
• pricing for take-rate decisions

Tier-1 budget priority

• Programmatic SEO build for one side
• Cold outbound to seed supply (or demand, whichever is bottleneck)
• Lifecycle email for both sides

---

Archetype 5 — Developer Tool / Open Source

Core characteristics

• Technical buyer (developer or eng leader)
• High bar for content quality (developers are skeptical)
• DevRel matters more than traditional marketing
• Open source layer often funnel into commercial product

AARRR emphasis

Acquisition:

• Technical content + docs SEO
• DevRel (conferences, talks, community)
• GitHub presence + npm/pip/etc. discovery
• Hacker News + Reddit + dev Twitter

Activation:

• First build / first integration is the activation event
• Time-to-Hello-World matters
• Documentation = onboarding for dev tools

Retention:

• Depth of integration (using more of the product)
• Team adoption (one user → entire org)
• Active project count

Referral:

• Star count on GitHub (semi-organic)
• Recommendation in technical forums
• Conference talks mentioning the tool

Revenue:

• Free → paid conversion when usage exceeds limits
• Team plans, enterprise tiers
• Support / SLA upsells

Skills emphasis

• programmatic-seo for docs
• Less emphasis on traditional ads
• Heavy content-strategy + technical content
• cold-email to engineering leads at target companies

Tier-1 budget priority

• Docs + technical content production
• DevRel (founder doing talks)
• GitHub presence
• HN / Reddit / dev community

---

Archetype 6 — Deep-Tech / Scientific / Clinical

Core characteristics

• Long sales cycles
• Heavy credibility burden (must prove the science)
• Highly informed buyers (academics, clinicians, researchers)
• Often regulatory considerations

AARRR emphasis

Acquisition:

• Academic publishing + peer-reviewed studies
• Conference speaking (academic + industry)
• Investor / advisor introductions
• PR via credibility hooks

Activation:

• Pilot programs / proof-of-concepts
• Concierge setup with high-touch onboarding
• Educational webinars / training

Retention:

• Customer success heavily
• Co-publication with customers
• Community of practice

Referral:

• Academic / clinical references
• Conference panel features
• Case studies with named institutions

Revenue:

• Pilot → paid expansion
• Institutional contracts (multi-seat / multi-year)
• Compliance / certification upsells

Skills emphasis

• Light traditional marketing
• Heavy product-marketing, sales-enablement, pricing
• cold-email to specific researchers / practitioners
• PR + investor marketing

Tier-1 budget priority

• Academic outreach + conference speaking
• Investor backchannel for institutional warm intros
• Pilot deployment with key customers
• Case study + scientific publication

---

Archetype 7 — Commerce / DTC (non-subscription)

Core characteristics

• Physical or digital products sold transactionally
• Average Order Value matters
• Repeat purchase rate is the key retention metric

AARRR emphasis

Acquisition:

• Paid social (Meta, TikTok) often dominant
• Shopify SEO for product pages
• Amazon listings
• Influencer + creator partnerships

Activation:

• First purchase is the activation event
• Cart abandonment recovery
• Trust signals on checkout (reviews, returns, shipping)

Retention:

• Post-purchase lifecycle
• Loyalty programs
• Email + SMS for repeat purchase

Referral:

• Gifting flows
• Refer-a-friend programs
• Reviews + UGC

Revenue:

• AOV optimization (bundles, upsells)
• Customer LTV optimization (repeat purchase frequency)
• Subscription option for repeat purchases

Skills emphasis

• ads + ad-creative (heavy weight)
• emails for post-purchase + abandoned cart
• referrals with gifting
• pricing for bundles + subscription option

Tier-1 budget priority

• Shopify storefront optimization
• Email lifecycle ship
• Influencer / UGC seeding
• Paid social testing (if minimal budget exists)

---

How to use this doc when drafting a plan

When you start drafting Sections 4–8 (AARRR), identify the client's archetype (or hybrid if applicable) and lean into the patterns above.

Hybrid cases are common. Quietude is "Hybrid hardware + software" with significant overlap to "Deep-tech / scientific / clinical" (because of the peer-reviewed study + clinical positioning). The plan blends emphases from both archetypes.

When in doubt, lead with the archetype that best fits the primary monetization model. Quietude's primary monetization is software subscription (with hardware as the wedge), so the D2C consumer app + hardware-hybrid patterns dominate, with deep-tech credibility moves layered in.

When the client doesn't fit cleanly

Some clients defy archetype:

• Content / media businesses — neither SaaS nor commerce; ad revenue or subscription model
• Social networks — own category, network effects dominate
• Real estate / events — physical + service model

For these, identify the closest archetype and adjust. Don't force-fit — name the deviation in the plan's Strategic Frame.

---

Supporting file: references/current-state-rubric.md

Current State Rubric — 17-Section Scoring Lens

This 17-section rubric is the source of truth for Section 3 ("Current State") of every marketing plan. Score each section 0–5 from available materials, then write a 2–4 sentence "shape interpretation" that names where strengths and gaps cluster.

How to score

From rich materials. When the team has shared decks, prior content audits, a brand voice doc, kickoff transcript, app store and analytics snapshots — score each section from those artifacts. Mark "scored from materials" in the section heading so the team can push back where they have better data.

From a separately scored audit. If the team has already run a scored current-state assessment (in any format), ingest those scores directly. Don't redo the work — note the date the rubric was scored and flag any sections where material has shifted since.

Either way, the output is the same: a 17-row scored table, a total out of 85, and a shape paragraph.

The 17 sections (scored 0–5 each)

1. Positioning

What's scored: Clarity of category claim, differentiation, alignment across surfaces (homepage, app store, pitch deck, founder messaging).

Score guide:

• 0 = No positioning anywhere
• 2 = Inconsistent across surfaces; team can't articulate it on demand
• 4 = Clear, original, mostly consistent; minor surface gaps
• 5 = Distinctive, category-defining, every surface aligned

Maps to AARRR: Cross-cutting — feeds every stage.

2. Customer research

What's scored: Depth and recency of customer research, ICP clarity, voice-of-customer capture.

Score guide:

• 0 = No formal research, only founder intuition
• 2 = Some research but stale or one-off
• 4 = Active research practice, customer language captured
• 5 = Continuous research, customer language flows into copy / product / messaging

Maps to AARRR: Cross-cutting — feeds especially Acquisition (channel choice) and Activation (onboarding voice).

3. Homepage

What's scored: Headline clarity, voice alignment, conversion architecture, mobile experience.

Score guide:

• 0 = Generic / broken / off-brand
• 2 = Functional but underperforming; voice mostly absent
• 4 = Clear, voice-aligned, converting; minor optimization opportunities
• 5 = Distinctive, converts strongly, fully voice-aligned

Maps to AARRR: Acquisition + Activation.

4. Sales / product pages

What's scored: Existence and quality of dedicated product / pricing / feature pages. Are SKUs documented? Is pricing scannable? Are upsells visible?

Score guide:

• 0 = No dedicated pages
• 2 = Pages exist but are stale or off-voice
• 4 = Quality pages for primary products; gaps on secondary
• 5 = Every product, tier, and upsell has a high-converting page

Maps to AARRR: Acquisition + Revenue.

5. Conversion pages

What's scored: Landing pages for specific campaigns, channels, or use cases. /partner, /science, /ambassadors, /eye-mask types of pages.

Score guide:

• 0 = No conversion pages
• 2 = One or two exist; rest of needed pages missing
• 4 = Most needed conversion pages exist; quality is good
• 5 = Full conversion page library, each high-converting

Maps to AARRR: Acquisition + Activation.

6. Competitor comparison

What's scored: Existence of "vs. {competitor}" pages, comparison content. Does the brand acknowledge alternatives, or pretend they don't exist?

Score guide:

• 0 = Nothing — actively avoiding competitor mentions
• 2 = Some content exists but is weak or hidden
• 4 = Solid comparison pages for top 2–3 competitors
• 5 = Comprehensive comparison library; SEO-targeted; high-converting

Maps to AARRR: Acquisition (consideration-stage SEO + sales enablement).

7. Resources / content

What's scored: Blog, knowledge base, science page, whitepapers, research, founder essays, podcast.

Score guide:

• 0 = No content surface
• 2 = Blog exists but is stale or thin
• 4 = Active content production; multiple formats
• 5 = Content is a moat — proprietary research, named pillars, daily volume

Maps to AARRR: Acquisition.

8. Onboarding

What's scored: New user onboarding (in-app + email). Time-to-value, completion rate, brand-voice alignment.

Score guide:

• 0 = No onboarding flow
• 2 = Onboarding exists but is broken, off-voice, or underperforming
• 4 = Solid onboarding; clear bottlenecks identified
• 5 = Tested, optimized, on-brand; activation rate at category top quartile

Maps to AARRR: Activation.

9. Email lifecycle

What's scored: Existence and quality of lifecycle email programs. Welcome / onboarding / post-purchase / lapsed / win-back.

Score guide:

• 0 = No lifecycle email
• 2 = Some flows exist but drafted not live, or live but stale
• 4 = Core flows live and performing; gaps on secondary flows
• 5 = Full lifecycle live, segmented, performing above category benchmarks

Maps to AARRR: Retention (+ Activation for onboarding emails).

10. Sales material

What's scored: Sales decks, one-pagers, demos, case studies, pricing sheets. (For B2B / hybrid companies — for pure D2C, this can be marked N/A or scored low without implication.)

Score guide:

• 0 = No sales material
• 2 = Founder uses a deck but other material is thin
• 4 = Solid sales kit; reps can self-serve content
• 5 = Comprehensive material; updated quarterly; objection-handling library exists

Maps to AARRR: Acquisition + Revenue (B2B).

11. Messaging

What's scored: Voice, tone, vocabulary, message hierarchy across surfaces. Is the brand voice documented, consistent, distinctive?

Score guide:

• 0 = No voice documented; surfaces inconsistent
• 2 = Voice exists in founder's head but isn't operationalized
• 4 = Documented voice; mostly consistent across surfaces
• 5 = Distinctive voice; documented; every surface respects it; voice is a moat

Maps to AARRR: Cross-cutting.

12. Pricing

What's scored: Pricing structure clarity, packaging logic, recent pressure-testing, listed vs. effective price reconciliation.

Score guide:

• 0 = Pricing not pressure-tested in over a year; unclear structure
• 2 = Listed pricing exists but plan mix / discounting muddles the read
• 4 = Clear pricing; recent tests; LTV math known
• 5 = Pricing tested quarterly; packaging optimized; expansion levers known

Maps to AARRR: Revenue.

13. CRO (conversion rate optimization)

What's scored: Test cadence, instrumentation, A/B history, statistical rigor.

Score guide:

• 0 = No tests run; no instrumentation
• 2 = Some ad-hoc tests; no statistical rigor
• 4 = Regular test cadence; some wins
• 5 = Continuous testing program; experimentation culture; documented wins

Maps to AARRR: Cross-cutting (most impactful at Activation + Revenue).

14. GTM launches

What's scored: Quality of past launch executions. Product launches, feature launches, campaign launches.

Score guide:

• 0 = No structured launches; "soft launches" only
• 2 = Some launches but uneven execution
• 4 = Solid recent launches; playbook exists
• 5 = Repeatable launch motion; Product Hunt #1s; press coverage on demand

Maps to AARRR: Acquisition + Activation.

15. Ads (paid)

What's scored: Paid acquisition state. Active campaigns, channels, CAC tracking, creative quality.

Score guide:

• 0 = No paid acquisition
• 2 = Some paid but unstructured / wasteful
• 4 = Paid is firing across 2–3 channels with positive unit economics
• 5 = Sophisticated paid stack; CAC/LTV understood; creative iterated weekly

Maps to AARRR: Acquisition.

Note: For pre-seed clients with no paid budget, score this 0 without treating it as a weakness — it reflects the funding stage, not a marketing failure.

16. SEO

What's scored: Organic search performance. Domain rating, ranking keywords, organic traffic, content cluster strategy.

Score guide:

• 0 = No SEO; new domain or zero-authority
• 2 = Some content but no strategy; ranks for brand only
• 4 = Established content clusters; growing organic traffic; DR 25+
• 5 = SEO is a moat; DR 40+; thousand+ ranking keywords; consistent content production

Maps to AARRR: Acquisition.

17. Internationalization

What's scored: Geographic expansion, language localization, region-specific pricing.

Score guide:

• 0 = US/EN only; no international consideration
• 2 = International users exist but aren't served (one language, one currency)
• 4 = Multi-language, region-specific pricing, GTM playbook for new markets
• 5 = International is a strength; multi-region revenue; localized GTM

Maps to AARRR: Acquisition.

Note: For most early-stage companies, internationalization scores 0–1 and that's appropriate. Don't penalize early-stage companies for not having international playbooks yet.

How to compute the total + read the shape

Total = sum of all 17 scores. Out of 85.

The total matters less than the shape. After the scoring table, write a 2–4 sentence "shape interpretation":

"High in {strong sections}, low in {weak sections}. That shape is the gap the rest of the plan closes — Sections X (AARRR stage) is the longest because that's where the gap is widest."

Common shapes

"Strong voice / messaging, weak distribution"

• High: Positioning (#1), Customer research (#2), Messaging (#11)
• Low: SEO (#16), Ads (#15), GTM launches (#14)
• Translation: The founder is a strong storyteller but distribution hasn't caught up. Plan emphasizes Acquisition + paid layer prep.

"Strong acquisition, weak conversion"

• High: SEO (#16), Resources (#7), Ads (#15)
• Low: Homepage (#3), Onboarding (#8), Conversion pages (#5), Pricing (#12)
• Translation: Traffic comes in but doesn't convert. Plan emphasizes Activation + Revenue.

"Strong conversion, weak retention"

• High: Onboarding (#8), Homepage (#3), Pricing (#12)
• Low: Email lifecycle (#9), CRO (#13)
• Translation: Users sign up and pay but churn. Plan emphasizes Retention.

"Strong product, weak everything-else"

• High: only Positioning (#1) and Customer research (#2) — the founder knows the customer
• Low: everything operational
• Translation: Pre-marketing stage. Plan is foundation-heavy. First quarter is bedrock fixes.

"Strong recent revenue, weak compounding"

• High: Ads (#15), Sales material (#10), Pricing (#12)
• Low: SEO (#16), Resources (#7), Referral mechanics
• Translation: Performance marketing carries the business. Plan emphasizes building compounding channels before paid scales further.

When scores are subjective

Some sections are easier to score from outside than others. Subjectivity tier:

• Objective (data-driven): SEO (#16), Ads (#15), Email lifecycle (#9), Onboarding (#8) — backed by analytics
• Semi-objective: Pricing (#12), CRO (#13), Conversion pages (#5), Sales material (#10) — visible artifacts to evaluate
• Subjective (judgment call): Positioning (#1), Messaging (#11), Customer research (#2), Resources (#7) — interpretive

For subjective sections, write the rationale into the "Note" column so the team can push back if they disagree.

When a prior scored audit exists

If the team already has scored output from any current-state assessment, ingest those scores directly — don't redo the work. Treat that prior scoring as the ground truth for sections it covers.

If the prior scoring was done weeks ago and material has shifted since (new shipped flows, new content live, repositioning, etc.), note "scored on YYYY-MM-DD; material has shifted since" and update any specific scores you have current evidence for.

---

Supporting file: references/example-quietude.md

Example — Quietude Marketing Plan v1

This is the canonical reference example for the /marketing-plan skill. It's based on a real fCMO engagement for a hybrid hardware-and-software wellness platform. Names, domains, and identifying details have been changed — the client is called "Quietude" here, and the team members have been renamed (Alex / Sam / Casey / Devon). The funnel numbers, budget, and structural lessons preserve the shape of the original engagement so the example retains its teaching value.

Use this as the "what good looks like" reference when drafting a new plan. The structure, tone, depth, and operational specificity are the bar to clear.

Quietude's archetype: Hybrid hardware + software with deep-tech / clinical credibility layer. See references/client-types.md for archetype patterns.

Funding-stage context: Pre-seed-close (mid-raise on $3M seed). Tier 1 per references/funding-stage-unlocks.md. $0 paid budget; organic + lifecycle + ambassador only.

What was strong about this plan:

• Strategic frame (Section 2) leaned on the founder's own meditation-vs-regulation framing as the content pillar
• Current state (Section 3) included the 17-section audit rubric scored against existing materials (no formal audit run)
• 90-day roadmap (Section 9) had owner-assigned moves, not just actions
• Ops stack (Section 11) included a concrete operational proof-point (Customer.io MCP used live by non-technical founder on the kickoff call)
• Tactical idea bank (Section 12) cross-referenced all 139 marketing-ideas to AARRR + Quietude-specific status, including 23 explicit skips with rationale

---

Quietude — Marketing Plan v1

Prepared by: Casey Reed (fCMO) For: Alex, Sam, and the Quietude team Date: 2026-05-27 Status: Draft v1 — for team review

1. Executive summary

Quietude has built something rare: a clinically validated, brand-coherent, founder-led product in a category that doesn't yet have a name. The opportunity in the next twelve months is not to invent a marketing engine from scratch — it's to convert the existing organic gravity into a measurable, repeatable funnel, then layer paid acquisition on top of that funnel once the seed round closes.

Three big bets, ranked by leverage:

1. Fix the leak before pouring water in. The Day 1 → Day 35 funnel shape (1.34% → 5.46%) tells us the product converts given time and contact. What it's missing is a working first-session moment (the headphone gate is killing conversion) and a lifecycle layer to deliver the contact. These two pieces — onboarding rebuild and Customer.io flows shipped — are the unlock for everything else.
2. Compound the moats Quietude already has. Peer-reviewed clinical study, longevity-influencer PR, 15K live event participants, Alex's founder voice — these are link generators, content pillars, and credibility anchors that most wellness brands would kill for. They're under-leveraged. SEO, content, and App Store optimization translate them into search and discovery surface area.
3. Build the founder-and-fCMO operating system that lets a 4-person team market like a 20-person one. This is what makes the plan actually executable at Quietude's team size and burn rate — agentic tooling on top of Customer.io, Shopify, App Store, Stripe, GitHub, and the marketing skill library means we ship without hiring.

What twelve months looks like, plausibly:

• App goes from beta to GA. Onboarding converts at meaningful lift over today's baseline.
• 4 SEO content pillars staked, with Pillar 1 (Nervous System Regulation) and Pillar 2 (Sleep + Eye Mask) ranking on Tier-1 keywords.
• Full lifecycle live in Customer.io: onboarding, lapsed re-engagement, hardware post-purchase, subscription-center opt-ins.
• Ambassador program live with 15–25 active hosts. First Quietude Guides cert pilot run.
• Eye mask wedge selling at scale via Shopify with a clean hardware → app activation path. Blended CAC measured and tracked.
• Paid acquisition firing post-seed-close at $5–10K/mo initial test budget, scaling to $20–50K/mo if unit economics validate.
• Series A narrative writes itself: clinical evidence + activation lift + lifecycle compounding + first B2B install reference cases.

The 90-day priorities (which the rest of this doc operationalizes):

1. Kill the headphones gate. Ship the bedrock fix this week.
2. Run the three-variant onboarding test. Find the activation winner.
3. Ship Customer.io Flows 6 (eye mask post-purchase) and 4 (lapsed user) — hold Flow 2 (onboarding) until app UI stabilizes.
4. Rewrite the App Store listing in Quietude's brand voice. Highest-leverage non-site asset right now.
5. Stake the SEO foundation: consolidate to quietude.app, publish Pillar 1 hub + 3 spokes, publish the peer-reviewed psychophysiology study landing page.
6. Launch the ambassador program with the ~5 inbound waiting.

Everything else compounds on top of those six.

---

2. Strategic frame

This section distills positioning, ICP, and brand voice into what the team needs to keep in mind while executing. Full detail lives in marketing-os.md, icp.md, and sound-philosophy.md.

What Quietude is, in one sentence

A nervous system intelligence platform — clinically validated spatial audio + AI reflection companion (Mira) + hardware + venue installations + practitioner network. "We start with sound. We expand to every sense. We end with cities."

The category we're claiming (and defending)

Quietude doesn't fit the meditation app category, the focus audio category, or the sleep tech category. The brand makes a stronger claim: bottom-up nervous system regulation through spatial audio, with clinical evidence as proof and somatic credibility as defense.

The category-defining frame, per Alex (2026-05-19): Meditation is top-down. Quietude is bottom-up. Meditation uses the mind to command the body — mental kung fu that fails the very people most likely to need help, because the prefrontal cortex is offline when stressed. Quietude enters through the brainstem, before the thinking mind. The body responds before it has to try. (Full content-pillar treatment in meditation-vs-regulation.md.)

This is the single most important strategic message. It belongs in App Store copy, onboarding, lifecycle email, SEO content, ambassador talking points, and the seed deck.

Who we're for (D2C ICP, distilled)

Overstimulated high-achieving professionals, 25–45, urban (Bay Area, NYC, London, Berlin, Austin). Tech workers, founders, creators, academics, designers, consultants. Often neurodivergent (ADHD, HSP, gifted). Sophisticated wellness buyers — already invested heavily in their inner life.

Their stated problem: "I can't shut my brain off. I've tried meditation apps. They don't work."

Their real problem: Overstimulation, not under-motivation. Their gift (quick thinking) became a curse. They need permission to stop optimizing — including their rest.

What they're actually buying: the feeling of stability, sensory indulgence, beautiful rituals, effortless effectiveness, a luxurious shortcut to the genius they can't access in chaos.

The business model logic (per seed deck)

B2B seeds the market. D2C harvests. A venue install puts Quietude in front of ~20K people/year at ~$17K cost → 5% convert to subs → ~$430K/year per venue. Six compound channels (referral, Guides, content, home hosting, PR, community) make CAC approach zero by Year 3. Year 5: 75% of new subs come from near-zero-cost channels.

fCMO scope per kickoff: D2C-led. Alex owns B2B sales through events/network/founder credibility. The fCMO leverage is on the app/hardware D2C side. This plan reflects that split — B2B is acknowledged as the harvest engine but not treated as primary work surface.

Brand voice (the non-negotiable)

Per Marketing OS:

• Tone. Authoritative yet accessible. Intimate yet professional. Revolutionary yet grounded. Authority comes from lived experience, not explanation.
• Speak from the body, not the mind. Every sentence restores somatic safety and orientation. Language opens space rather than closing meaning.
• YES vocabulary: Aliveness, inner life, nervous system, spatial sound, resonance, somatic safety, embodied clarity, natural rhythm, orientation, initiation, truth-telling.
• NO vocabulary: Zen, chill, vibes, "high-vibe," spiritual bypass, meditation clichés, didactic/explainer language, "let me explain why this works."
• Core method: Initiatory Reflection. Writing's purpose isn't to explain or convince — it's to shift the reader's internal state. The result should be "something in me moved," not "I understand this concept."
• CTA rule: Never pressure. "We do not remind. We invite."

This rule constrains every piece of copy across every AARRR stage. When in doubt: rewrite from the body.

---

3. Current state

This is what we're starting from — team, budget, what's already in motion, what's stuck, scored against the CF Marketing Audit 17-section rubric.

Team composition (marketing surface area)

No dedicated marketing hire yet. First hire likely post-seed close (Q3 2026 candidate): a lifecycle + content marketing manager who owns Customer.io, SEO content production, and ambassador operations day-to-day.

Marketing budget (current)

• Paid acquisition: $0. Confirmed by Alex, 2026-05-20: "D2C UA so far: My personal LinkedIn posts, live Quietude events, organic word of mouth, and organic app store discovery." No paid layer.
• Tooling stack: Customer.io subscription, Shopify (eye mask storefront), App Store Connect, GA4 (or pending), Stripe, Notion, Dub.co (ambassador attribution). Estimate ~$500–1,500/mo combined.
• fCMO retainer: Casey Reed engagement.
• PR: No paid PR. Organic longevity-influencer tailwind, consumer-tech angels + foundation-model lab network.

Implication: The 90-day plan must produce gains without any paid lever pulled. Everything in the next 12 weeks is organic, lifecycle, or product-level. Paid is a Q2–Q3 unlock.

What's already done (acknowledge, then build on)

What's in-flight (drafted but not shipped)

What's stuck (and needs to unstick this quarter)

Audit rubric snapshot (17-section)

Scored 0–5 from materials, using the embedded rubric in references/current-state-rubric.md. Marked "scored from materials" rather than "formal audit" — Alex can push back on any score where they have better data.

Total: 36 / 85 (42%). The shape matters more than the score: high in Positioning + Messaging + Customer research, low in Conversion pages + Email lifecycle + SEO + Resources + Ads. That's the gap this plan closes.

---

4. Acquisition

"How do strangers become aware of Quietude?"

Current state

100% organic. Four real channels: Alex's personal LinkedIn, live Quietude events, organic word of mouth, organic App Store discovery. Plus passive PR drag from longevity-influencer endorsement + clinical study.

This is good news, not bad. Every dollar of revenue earned to date has been earned without paid acquisition. The bar to exceed it isn't high; the upside on top of an organic base is significant.

The plan

Channel 1 — SEO (primary 90-day investment). The full 90-day plan lives in seo/plan.md. Summary: consolidate to quietude.app, target three asymmetric clusters (nervous-system regulation KD 14–32, weighted/blackout sleep mask KD 6–30, WELL + social-wellness-club B2B KD 5–34), publish 4 content pillars. 90-day target: 500–1,500 organic visits/mo, 80+ ranking keywords. 12-month target: 10,000/mo, 1,000+ keywords.

Channel 2 — App Store optimization (highest-leverage non-site asset). The App Store listing is currently the most-visited Quietude URL by Apple's algorithm. Fixing the copy is higher-leverage this quarter than fixing the marketing site. Rewrite in brand voice. Add the meditation-vs-regulation framing. Lead with the clinical anchor. Test screenshot variations.

Channel 3 — Alex's LinkedIn (productize the channel). Today it's ad-hoc founder posting. The next move is structured: a 2–3x/week cadence, post categories that map to the content pillars (nervous system, sound science, founder journey, clinical evidence, behind-the-scenes), trackable links via Dub, follower → email subscriber → app install funnel measured. This is Alex's voice — the channel only works if he's the one writing. fCMO + Typefully scheduling makes the cadence sustainable.

Channel 4 — PR amplification. longevity-influencer tailwind is real but underused on owned surfaces. Add a /notable-users or /in-the-press page. Pitch the peer-reviewed psychophysiology study to 5 outlets (wellness press: Well+Good, MindBodyGreen; tech-adjacent: Wired with the longevity-influencer hook; mainstream: Outside, Forbes Wellness). HARO/Help-A-B2B-Writer responses citing Quietude's data. Investor PR moments ("Why I invested in Quietude" Substack pieces from consumer-tech angels — push for these with backlinks).

Channel 5 — Event-to-app instrumentation. Live events are the highest-converting ICP exposure Quietude has (15K+ participants, decade of trust). They're un-instrumented. Add: per-event QR code → app install + email capture, post-event lifecycle (Customer.io Flow 7?), event ROI tracking. Goal: turn an event from a one-night conversion moment into a 30-day funnel.

Channel 6 — Eye mask wedge (consumer entry product). 5K masks in stock. Shopify storefront exists but isn't optimized. Improvements: SEO-optimize the product page (target "weighted sleep mask," "blackout sleep mask," "silk sleep mask"), add reviews via Judge.me (per kickoff decision), 30-day return policy (US-market expectation, per kickoff), build the listicle ("Quietude vs. Manta vs. Nodpod vs. Lumon"). Consider Amazon listing as a v2 distribution play.

Channel 7 — B2B venue installs (kept lean per kickoff). Alex owns this. Marketing supports with: case studies after each install, /partner page rewrite in voice (already exists on quietude.app), Pillar 4 content ("The Missing Sound Feature in WELL"), reciprocal links from partner venues baked into contracts.

Channel 8 — Paid layer (unlocked post-seed close). Held until seed funding lands. Initial test budget: $5–10K/mo split across Apple Search Ads (highest-intent for App Store), Meta (Instagram + Facebook for eye mask), LinkedIn (B2B venue buyers). Don't fire until: (a) onboarding bedrock fix is shipped, (b) Flow 6 is live, (c) at least one Pillar landing page is in voice. Paid amplifies what already works — premature paid amplifies what's broken.

90-day acquisition moves

• Weeks 1–2: Domain consolidation decision + 301 plan. App Store listing rewrite first pass.
• Weeks 3–4: Domain 301s executed. GSC migration. SEO Pillar 1 hub drafted.
• Weeks 5–8: Pillar 1 hub + 3 spokes published. Pillar 2 (Eye Mask) hub + listicle published. Alex's LinkedIn cadence operationalized via Typefully. peer-reviewed psychophysiology study lands on dedicated /science page.
• Weeks 9–12: Pillar 4 (WELL/B2B) cornerstone published. Sound Philosophy goes public at /research/sound-philosophy. First PR push: pitch study + longevity-influencer hook to 5 outlets.

12-month acquisition outlook

• Q1 (Months 1–3): Foundation. SEO pillars staked. App Store rewrite shipped. LinkedIn cadence stable. PR push launched.
• Q2 (Months 4–6, post-seed close): Paid acquisition pilot at $5–10K/mo. SEO compounding — Pillar 1 ranking. First B2B install reference case live.
• Q3 (Months 7–9): Paid scales to $20–30K/mo if unit economics hold. All four pillars producing. App GA — new GTM moment.
• Q4 (Months 10–12): Compound channels live. 50+ pieces of pillar content. First Quietude Guides program pilot creating local SEO + earned media.

Skills + tools

• Skills: seo-audit, ai-seo, programmatic-seo, schema, content-strategy, competitors, launch, ads, ad-creative, social, typefully, analytics, copywriting, marketing-website-design, free-tools
• MCPs / APIs: Ahrefs API, DataForSEO API, Typefully MCP (LinkedIn scheduling), GA4 MCP (when wired), GitHub MCP (quietude-promo repo work), Notion (knowledge directory), Stripe MCP (LTV / paid-CAC math), agent-browser (LinkedIn drafting + testing), defuddle (research)

---

5. Activation

"Once someone tries Quietude, do they have an experience that converts?"

Current state

Day 1 → paid: 1.34%. Day 7 → paid: 3.73%. Day 35 → paid: 5.46%. The funnel shape is the signal. The ~4× lift over 35 days means the product converts given time and contact — both of which the current onboarding undermines and the lifecycle layer doesn't yet provide.

Caveats: app is in throttled beta. Metrics are noisy. Don't optimize against absolutes; optimize against funnel shape and cohort comparison.

The plan

Move 1 — Kill the headphones hard-gate (bedrock fix, this week). Confirmed conversion drop after the gate shipped. The fix isn't better copy on the gate — it's removing the gate. Replace with passive headphone detection + soft single-line nudge. No regret change. Full reasoning in onboarding-recommendation.md.

Move 2 — Run the three-variant onboarding test. Three variants, each a pure expression of one belief about what drives activation in this ICP:

• Variant 1 — Trust First. Bold promise + clinical anchor + testimonial wall + 1-line mechanism. Tests whether the saturated ICP needs framing before they'll invest.
• Variant 2 — Seen First. Multi-step diagnostic → AI-generated "we see you" summary → personalized session. Tests whether being accurately named is the conversion event.
• Variant 3 — Felt First. Audio starts on app open. ~15 words on screen. The session IS the onboarding. Tests whether the product can carry it cold.

Test sequence (sequential, ~7 weeks to a winner): bedrock baseline → V3 vs. baseline → winner vs. V1 → winner vs. V2. Full system in onboarding-recommendation.md.

Move 3 — App Store listing rewrite. Highest-leverage non-site asset. Rewrite in brand voice. Lead with meditation-vs-regulation. Screenshot variations to test. This is also an Acquisition move (organic discovery) but it lives here because it's the threshold to the trial.

Move 4 — Customer.io Flow 2 (held until UI stable). The 8-email / 14-day onboarding sequence is drafted and on-brand. Holding the ship because the emails reference in-app screens that will change during the onboarding rebuild. Once a winning onboarding variant ships, Flow 2 gets a copy refresh against the final UI and goes live.

Move 5 — Paywall + pricing review (cross-cuts to Revenue). What's the current trial structure? Length, paywall trigger, intro pricing? When the funnel shape is "lift over 35 days," extending trial may convert better than aggressively gating earlier. To be audited in Q1.

90-day activation moves

• Week 1: Headphones gate removed. Baseline established.
• Weeks 2–3: Variant 3 (Felt First) prototyped, instrumented, shipped to a test cohort.
• Weeks 4–5: Read Variant 3 vs. baseline. Decide ship/iterate. Begin Variant 1 build.
• Weeks 6–7: Variant 1 (Trust First) live.
• Weeks 8–9: Read V1 vs. winner. Begin Variant 2 build.
• Weeks 10–11: Variant 2 (Seen First) live.
• Week 12: Final read. Winning variant scheduled for permanent ship. Flow 2 unblocked.

12-month activation outlook

• Q1: Winning variant identified and shipped.
• Q2: Flow 2 ships. Paywall A/B tests start.
• Q3: GA launch — onboarding re-validated at higher traffic. Cohort segmentation by acquisition source (Shopify/eye-mask vs. direct vs. ambassador vs. paid) starts to drive variant forks.
• Q4: Onboarding is no longer the bottleneck. Focus moves to Activation → Retention transition (sessions 2–7).

Skills + tools

• Skills: onboarding, signup, cro, cro, paywalls, popups, copywriting, copy-editing, copycraft, marketing-website-design, ab-testing, marketing-psychology
• MCPs / APIs: App Store Connect (manual + dev-browser for screenshot automation), GitHub MCP (quietude-app app repo for onboarding code), Figma / Pencil MCP (for onboarding screen design), Customer.io MCP (for any in-app/email coordination), GA4 MCP (activation events)

---

6. Retention

"Once someone converts, do they stay — and deepen?"

Current state

Headline metric (per seed deck): 38% 12-month retention — nearly double the category average (~20%). This is the strongest single retention signal in the deck and one of the most undermarketed claims Quietude owns.

App Store snapshot, 2026-05-16: 145 paid, 42 churned (~29% monthly churn). Definition mismatch with the 38% claim — to reconcile. Possibly: 38% is annual cohort retention (people who paid month 1 and still pay month 12), 29% is gross monthly churn (people who paid this month who didn't pay next month). Both can be true. Need to clarify which metric is reported externally and which is the actual product health signal.

The plan

Move 1 — Ship Flow 6 first (Eye Mask Post-Purchase). Per kickoff decision and the onboarding-recommendation doc: this is the ship-ready flow. Hardware-anchored, doesn't reference in-app screens, can ship today. Wires the hardware → app activation path (eye mask buyers should get a free 6-month Premium trial — formalize this as part of the flow).

Move 2 — Ship Flow 4 second (Lapsed User Re-engagement). Five emails over 38 days. Language is universal — doesn't depend on app UI state. Ship after Flow 6 is live.

Move 3 — Hold Flow 2 (Onboarding). Eight emails over 14 days. Holds until app UI stabilizes post-onboarding-rebuild. Don't ship copy that will need rewriting in 8 weeks.

Move 4 — Customer.io subscription center with opt-in topics. Per kickoff decision. Topics: events, app updates, somatics & nervous system, eye mask promotions. Users self-segment. Improves deliverability (lower complaint rates) and gives lifecycle a richer segmentation surface.

Move 5 — Mira post-session reflection (when scoped). Most powerful retention move medium-term. After a session, Mira asks "What did you notice?" Optional preset chips + free text. Two payoffs: (a) gives Mira priors for personalization on session 2+, (b) reflection responses become a content + segmentation goldmine for the team. Scope question for Devon — does Mira currently support this, or is it new build?

Move 6 — Hardware → app activation flow. The eye-mask-buyer-becomes-Premium-subscriber path is hinted in the seed deck (blended CAC via hardware) but isn't visible in the App Store dashboard. Audit the existing flow: does an eye mask Shopify purchase actually deliver a free Premium code? How is it redeemed? What's the conversion rate? This is foundational to the "B2C wedge" thesis.

Move 7 — Reconcile the retention metric. What's the actual definition of "38% 12-month retention"? Cohort? Plan type (monthly vs. annual)? Survives this even if the answer is uncomfortable — the team and investors need to be talking about the same metric.

Move 8 — Annual plan as default (cross-cuts to Revenue). Industry pattern: defaulting to annual reduces churn anxiety and improves LTV. To test in Q2.

90-day retention moves

• Weeks 1–2: Flow 6 (eye mask post-purchase) ships. Address fixes from kickoff review (study link line break, CAN-SPAM footer, founder face-bubble signature, Judge.me reviews).
• Weeks 3–4: Flow 4 (lapsed user re-engagement) ships.
• Weeks 5–6: Customer.io subscription center built and live.
• Weeks 7–8: Hardware → app activation flow audited and documented. Fix any leaks.
• Weeks 9–10: Retention metric reconciliation (with Devon).
• Weeks 11–12: Win-back campaign for churned cohort — test re-activation copy.

12-month retention outlook

• Q1: Flows 6 + 4 firing. Subscription center live.
• Q2: Flow 2 ships (post-onboarding-rebuild). Mira post-session reflection in production. Annual plan default tested.
• Q3: GA launch — retention metrics re-baselined at higher volume. Cohort-based lifecycle flows (eye mask vs. direct app install).
• Q4: Full lifecycle compound. Retention is no longer a top-three concern — focus moves to Referral and Revenue.

Skills + tools

• Skills: emails, churn-prevention, copywriting, copy-editing, paywalls, ab-testing
• MCPs / APIs: Customer.io MCP (validated on kickoff — non-technical team can ship flows), Shopify (eye mask buyers as event source), Stripe MCP (subscription state, churn cohort pulls), GA4 MCP (session events, retention curves)

---

7. Referral

"Do retained users bring more users — and at what cost?"

Current state

~5 inbound ambassadors waiting (per kickoff). Dub.co set up. No formal program yet. WOM happens naturally per Alex's UA breakdown.

This is one of the strongest leading indicators in the business: 5 unaffiliated people have raised their hand asking to bring Quietude to their network before any program exists. That signal doesn't show up in apps with weaker product-market fit.

The plan

Move 1 — Launch the ambassador program with the 5 inbound. Tier 1 of the program. Per-ambassador landing pages (e.g., quietude.app/with/sarah). Dub.co tracks attribution. Commission structure to determine (per kickoff, $/sub or rev-share TBD). Soft-launch with the 5 — treat as pilot cohort, gather feedback, refine before opening applications.

Move 2 — Build the share-after-shift moment. The Mira post-session reflection (see Retention) is the natural moment to surface a share prompt. After a user reports a felt shift, offer: "Want to share Quietude with someone who needs this?" Single-line, never pushy. Most powerful WOM mechanism: gift-a-month flow where the recipient gets a discounted or free intro.

Move 3 — Founder amplification (Alex + Sam as ambassador-zero). Alex mentioning the fCMO engagement in fundraise pitches (permission granted). Reciprocal mentions in fCMO-side content. Sam's clinical network → practitioner ambassador pool.

Move 4 — Quietude Guides cert pilot (long-term, Q3+). The Guides program is the Phase-2 referral compound (per seed deck). 500–1,000 Guides across 50+ cities by Y3–5. First cert pilot: 3–5 hosts who run live sessions, get a rev-share + co-marketing. Builds local SEO + earned media + ambassador-of-ambassadors flywheel. Hold until paid + lifecycle are firing — Guides is a multi-quarter build.

Move 5 — Eye mask gifting flow. Hardware referral is rare and powerful. "Send a friend an Quietude eye mask. They get the mask + a free 3-month Premium. You get a credit toward your next thing." Holiday/gifting peak windows are the test.

90-day referral moves

• Weeks 1–4: Ambassador program scoped, commission structure decided, per-ambassador landing page template built, 5 inbound onboarded.
• Weeks 5–8: First ambassador-driven sales tracked via Dub. Attribution and payout flow validated.
• Weeks 9–12: Open applications for next 10–15 ambassadors. Begin Quietude Guides scoping.

12-month referral outlook

• Q1: Ambassador program live with 5–10 active.
• Q2: 15–25 active ambassadors. Share-after-shift moment in production (post-Mira reflection).
• Q3: Guides cert pilot launched (3–5 hosts). Eye mask gifting flow live for holiday peak.
• Q4: 50+ ambassadors + 5–10 Guides. Referral driving 15–25% of new D2C subs.

Skills + tools

• Skills: referrals, social, copywriting, marketing-website-design (per-ambassador landing pages)
• MCPs / APIs: Dub.co (attribution — already in stack), Stripe MCP (commission accounting + payouts), GitHub MCP (landing page deployment in quietude-promo or new quietude-ambassadors repo), Customer.io MCP (ambassador lifecycle: onboarding, monthly performance digest, payout notification)

---

8. Revenue

"What do we charge, who pays, and how does that compound?"

Current state

Revenue to date: ~$500K on ~$250K raised. Capital-efficient. Hardware + B2B + app subs all contributing.

MRR (App Store snapshot): $592. Beta-throttled, not steady-state. The implied ~$4/sub/mo against $30/mo list suggests heavy annual plan adoption (which compresses monthly revenue but improves LTV) or significant promotional pricing — to reconcile with Alex.

The plan

Move 1 — Pricing audit. What's actually being charged today? List price, common plan mix, intro pricing, churn-recovery offers? The $4/sub/mo implied math doesn't tell a clean story — need ground truth before recommending changes.

Move 2 — Annual plan as default (test). Industry pattern, cross-references to Retention. Test in Q2.

Move 3 — Hardware → app bundling formalized. Per partner-event-business framing in the seed deck: blended CAC via hardware → app subscription is the play. Today an eye mask buyer gets... what, exactly? Free Premium? Trial code? Audit + formalize. The eye mask is the wedge; the app is the LTV.

Move 4 — Eye mask Shopify storefront optimization. The current page underperforms what it could. Add: SEO targeting ("weighted sleep mask," "blackout sleep mask"), Judge.me reviews (kickoff decision), 30-day return policy (kickoff decision), upsell flow into Premium app.

Move 5 — Consider Amazon listing for eye mask. Amazon takes margin but is its own discovery engine. Test as v2 distribution if Shopify volume validates.

Move 6 — B2B install case studies + sales material. Alex owns B2B sales but marketing supports with: post-install case studies (Aurora as the flagship), /partner page rewrite in voice, Pillar 4 SEO content. Each B2B install is a ~$430K/year recurring + reference-case multiplier.

Move 7 — Data licensing (long-term, flag for ops stack). Per seed deck Y10–15 value pool: $100–160M/yr. Not immediate revenue. Belongs in the 24-month strategic agenda. Flag here so we don't lose sight.

90-day revenue moves

• Weeks 1–2: Pricing audit. Reconcile implied vs. listed MRR.
• Weeks 3–4: Hardware → app activation flow audited (also Retention move 6).
• Weeks 5–8: Eye mask Shopify page rewrite + SEO optimization + Judge.me + return policy. Aurora case study scaffolded for post-install.
• Weeks 9–12: Annual plan default test scoped.

12-month revenue outlook

• Q1: Pricing audit closes. Hardware → app activation formalized.
• Q2: Annual plan default test live. Eye mask Shopify producing measurable lift.
• Q3: B2B install case studies (1–2) published. GA launch + new pricing tier consideration (e.g., a higher-tier Mira-heavy plan?).
• Q4: Pricing optimized via test results. Hardware → app blended CAC tracked and reported. First numbers on the data-licensing thesis (still very early).

Skills + tools

• Skills: pricing, paywalls, sales-enablement, revops, ab-testing, copywriting
• MCPs / APIs: Stripe MCP (pricing tests, subscription analytics, churn cohort, blended CAC math), Customer.io MCP (paywall-related lifecycle), Shopify (eye mask transactions), GA4 MCP (revenue events), Notion (commercial knowledge directory)

---

9. 90-day roadmap

Tactical execution layer. Each item is AARRR-tagged so priority is visible.

Weeks 1–2 — Unblock

Weeks 3–4 — Foundation

Weeks 5–8 — Velocity

Weeks 9–12 — Compound

---

10. 12-month outlook

Quarterly milestones with funding-stage capability unlocks named explicitly.

Q1 — Months 1–3 (Jun–Aug 2026)

Funding state: Pre-seed-close. Paid budget = $0. fCMO + founder-led + tool costs only.

Focus: Foundation. Plug the leaks. Stake the SEO ground. Get lifecycle firing.

Outcomes by end of Q1:

• Headphones gate gone; onboarding winner identified
• All four SEO pillars seeded (hub + first spokes)
• Lifecycle Flows 4 + 6 live
• App Store listing in brand voice
• 5 ambassadors active
• Pricing audit closed
• Domain consolidated

KPI targets: Onboarding Day 1 → paid lift of 25–50%. Organic traffic 500–1,500/mo. App Store conversion rate +20%.

Q2 — Months 4–6 (Sep–Nov 2026)

Funding state: Seed close (~Q3 2026 target). First paid budget unlock: $5–10K/mo test.

Focus: Validate paid. Scale winning onboarding. Add Flow 2.

Outcomes by end of Q2:

• Paid acquisition firing on Apple Search Ads + Meta
• Onboarding winner permanently shipped
• Flow 2 (onboarding emails) shipped
• Mira post-session reflection in production
• 15–25 ambassadors active
• First B2B install reference case (Aurora) published
• Annual plan default tested

KPI targets: Paid CAC < $50 blended. Organic traffic 1,500–3,500/mo. Retention curves visibly improving.

Q3 — Months 7–9 (Dec 2026–Feb 2027)

Funding state: Seed deployment. Paid scales to $20–50K/mo if unit economics hold. First marketing hire (lifecycle + content manager).

Focus: Scale + diversify. App GA. B2B reference cases compound.

Outcomes by end of Q3:

• App GA launched with new GTM moment (PR + ad creative refresh + Pillar 3 spatial-audio-science content cycle)
• First Quietude Guides cert pilot (3–5 hosts)
• All four pillars producing weekly content
• Eye mask gifting flow live for holiday peak
• New marketing hire onboarded

KPI targets: Paid + organic blended CAC stabilizing. App GA conversion +50% from beta baseline. Guides pilot validates rev-share + co-marketing model.

Q4 — Months 10–12 (Mar–May 2027)

Funding state: Pre–Series A. Paid scaling continues. Series A pitch in motion.

Focus: Compound. Position for Series A.

Outcomes by end of Q4:

• Compound channels (organic + ambassador + Guides + lifecycle) producing 50%+ of new subs
• 50+ ambassadors, 5–10 Guides
• 4 SEO pillars + 30+ pieces of content live
• Paid scaling to $50–150K/mo if validated
• Series A narrative: clinical evidence + activation lift + lifecycle compounding + B2B reference case pipeline

KPI targets: D2C ARR run-rate trajectory clear. Blended LTV/CAC > 3. Founder narrative + data + reference cases ready for Series A.

---

11. Marketing operations stack

This is what makes the plan executable at Quietude's team size. A 4-person founder team + fCMO + agentic tooling can ship the output of a 15–20-person traditional marketing org — because the marketing skill library and MCP integrations do the orchestration.

The thesis

Every move in the AARRR breakdown above maps to (a) one or more marketing skills that operationalize the work, and (b) one or more MCP/API integrations that let it execute without a dedicated headcount per channel.

The fCMO's job is to:

1. Define the strategy and sequencing (this doc)
2. Run the skills against the right context at the right time
3. Maintain the shared context (quietude-context) and tooling so Alex + Sam + future hires can plug in
4. Hand off operational work to humans (or future hires) only where the cost of agentic execution > human execution

Skills mapped to AARRR stages

MCPs / APIs mapped to stages

The Customer.io MCP unlock (concrete example)

Per kickoff call: "Built live on call — abandoned-cart flow drafted using Customer.io's Claude MCP. Validated that non-technical team can use the skill pattern independently."

This is the operational proof that the stack works. Alex, who is not a developer, drafted a working lifecycle flow with Claude + Customer.io MCP in real time on a kickoff call. The same pattern applies to: Flow 4 ship (lapsed user re-engagement), subscription center build, win-back campaign, eye mask gifting flow, ambassador lifecycle. The fCMO's role becomes orchestration + brand-voice QA, not hand-cranking each email.

Capability unlocks by funding stage

The marketing skill library scales these stages. Every channel added doesn't require a 1:1 headcount increase because each skill encodes the workflow.

---

12. Tactical idea bank — 139-idea cross-reference

The marketing-ideas skill catalogs 139 proven marketing tactics. Sections 4–8 (AARRR) prescribe what we're doing. This section maps the full universe of what's possible — every idea cross-referenced to the AARRR stage it primarily serves, with Quietude applicability and timing.

This is the exhaustive menu. The plan above is the curated path. When we move to Q2 / Q3 / Series A and unlock new capacity, this is the inventory we pull from.

Status legend:

• Now (Q1) — already in the 90-day plan OR can run alongside it without new capacity
• Q2 — post-bedrock-fix, post-foundation; second-quarter layer-ins
• Q3+ — post-seed-close, post-GA; expansion moves
• Q4+ — long-game / large-investment moves
• Skip / off-brand — incompatible with Quietude's brand voice, business model, or product category

12.1 Acquisition ideas (88 mapped)

Now (Q1):

Q2:

Q3+:

Q4+ / long-game:

Skip / off-brand for Quietude:

12.2 Activation ideas (7 mapped)

12.3 Retention ideas (8 mapped)

12.4 Referral ideas (5 mapped)

12.5 Revenue ideas (3 mapped — most ideas serve top-of-funnel)

12.6 Cross-cutting / brand foundation ideas

Idea-bank summary

• 88 ideas applicable to Acquisition (the dominant stage at Quietude's current stage — makes sense, Quietude's product converts well; the bottleneck is the top of funnel)
• 7 ideas to Activation, 8 to Retention (smaller because these stages are about depth, not breadth — execute the right few well rather than running a wide tactic menu)
• 5 ideas to Referral (program-driven, not tactic-driven)
• 3 ideas to Revenue (most revenue work is pricing strategy, not tactical tricks)
• 2 cross-cutting
• 23 ideas skipped for brand / business-model fit — Quietude's category positioning constrains what's available

What this proves: the plan is roughly 30% of the available tactical surface area, not 100%. That's appropriate at this stage and budget. As capacity unlocks across Q2 → Q3 → Series A, the cross-reference becomes the inventory we pull from to scale activity without losing strategic coherence.

---

13. Measurement, RACI, open decisions, appendix

Measurement — the metrics that matter

North star (proposed): Blended-LTV-to-blended-CAC ratio per acquired user, where:

• Blended LTV combines app subscription revenue + hardware revenue (eye mask + speakers) + any cross-sells, per cohort
• Blended CAC combines paid spend + content production cost + ambassador commissions + lifecycle tool spend, per cohort

This captures the business model: the eye mask wedge isn't free if it costs $X to make, and the app sub isn't expensive to acquire if a Bryan-Johnson-style PR moment is paying for itself.

If a single metric is preferred for team-level focus, fall back to: monthly new D2C subscribers from non-paid channels. This isolates the compound channels the long-game strategy depends on.

Leading indicators by AARRR stage:

Review cadence:

• Weekly: fCMO ↔ Alex 30-min sync. AARRR scoreboard + this week's ships.
• Monthly: Full metrics review (extended sync, Sam included). Compare against quarterly KPI targets.
• Quarterly: Plan recalibration. What's working, what's not, what funding-stage moves we're triggering.

RACI

Open decisions blocking the plan

Most blocking, ranked by impact:

1. Canonical domain. SEO data + this plan recommend quietude.app. Needs exec sign-off + 301 execution plan. Blocks: domain consolidation, SEO foundation, email sender migration.
2. Retention metric definition. Reconcile 38% 12-month retention claim vs. 29% monthly App Store churn. Blocks: clean dashboards, investor narrative coherence, lifecycle test reads.
3. Mira post-session reflection scope. Does Mira currently support this, or is it new build? Blocks: Onboarding Variants 1 and 2 (which depend on Mira reflection moment), retention compound moves.
4. App UI stability timeline. When does the headphone-gate-removal + onboarding-rebuild allow Flow 2 to ship without rework risk? Blocks: Flow 2, full lifecycle, paid acquisition timing.
5. GA launch timeline. When does the throttled beta become GA? Blocks: paid acquisition scale, Q3 GTM planning.
6. Pricing structure ground truth. What's actually charged today? Blocks: pricing audit conclusions, annual-plan default test, blended LTV math.
7. First marketing hire scope. Lifecycle + content owner, or something else? When does the JD get written? Blocks: Q3 capacity plan, succession of fCMO operational work.
8. Ambassador commission structure. $/sub, rev-share, hybrid? Blocks: ambassador program launch, attribution dashboards.

Appendix — deep-dive links

Published to the team via Quietude-Inc/quietude-context GitHub repo:

• marketing/seo/plan.md — Full 90-day SEO + keyword research plan
• marketing/seo/keyword-shortlist.md — Tier 1 keyword shortlist
• marketing/seo/raw/ — Ahrefs + DataForSEO API pulls
• marketing/onboarding-recommendation.md — Three-variant onboarding test plan

Founder-authored strategic context (in Quietude's internal knowledge base):

• Seed deck — Investor narrative
• Sound Philosophy — Alex's technical/philosophical working doc
• Marketing OS — Brand voice, content rhythm, visual system
• ICP doc — D2C audience profile
• Meditation-vs-Regulation note (2026-05-19) — Central content pillar
• Kickoff call transcript (2026-05-18) — Decisions + open questions
• App Store copy snapshot + voice-gap analysis
• App Store metrics snapshot (2026-05-16)
• Customer.io lifecycle flows inventory

---

Marketing Plan v1. Prepared by Casey Reed (fCMO), 2026-05-27. For team review and discussion.

---

Supporting file: references/funding-stage-unlocks.md

Funding-Stage Capability Unlocks

Every marketing plan must include explicit "what changes when funding closes / when budget unlocks" reasoning. This makes the plan investor-friendly and operationally honest.

This doc defines the standard tiers. Use them as anchors, adjust for client category and unit economics.

Related docs:

• budget-planning.md — two scientific methods for setting the actual budget number (Revenue-Based 5–40%, or Goal-Based reverse-engineered from the revenue target), CAC calculation, experimental buffer
• growth-patterns.md — the real shape of SaaS growth by phase ($0–10K / $10K–100K / $100K–1M+), linear vs step-function, S-curve layering
• team-and-agency-model.md — what each tier means for team composition, the first marketing hire, and the in-house vs outsource ratio

Why funding stage matters in a marketing plan

Most marketing plans are written as if budget is unconstrained. That's a failure mode for early-stage clients — it produces aspirational lists rather than executable roadmaps.

The fix: tie every recommendation to a budget tier. The plan stays honest about what's executable today, and the team / investors see explicitly what each round of capital unlocks.

This also helps the founder mid-raise: showing what the round buys is investor-narrative material.

Standard tiers

Tier 1 — Pre-seed / bootstrapped

Budget profile:

• Paid acquisition: $0
• Tooling stack: ~$500–2,000/mo (Customer.io / similar, GA4 free, Stripe fees, Notion, GitHub, basic SaaS)
• Retainers / fCMO: variable (fractional only)
• Headcount: founders + maybe 1–2 multipurpose hires

Marketing capability:

• Organic only — SEO, content, App Store organic, founder-led social, events, WOM, ambassador (if inbound exists)
• Limited PR (founder-led pitches, HARO responses)
• No paid layer

Channels live: Organic SEO, content, App Store, LinkedIn / X / founder-led social, events, WOM, ambassador

What a fCMO does: Strategy + lifecycle + content + SEO + onboarding + community + ambassador. Hands-on with skill library + MCPs doing the operational lift.

Hires unlocked: None. The plan must execute with current team + agentic stack.

Tier 2 — Seed close

Budget profile:

• Paid acquisition: $5–15K/mo test budget
• Tooling stack: $1,000–3,000/mo (paid ad accounts, Mixpanel / Amplitude if needed, additional SaaS)
• Retainers / fCMO: continued
• Headcount: + first dedicated marketing hire

Marketing capability:

• Above + paid acquisition pilot (Apple Search Ads, Meta, LinkedIn)
• Begin PR push with the funding announcement
• First Product Hunt / GA-style launch

Channels live: All Tier 1 + paid acquisition (small) + active PR

Hires unlocked:

• Lifecycle + content marketing manager (one person doing both, or split)
• OR dedicated growth / performance marketing manager (if heavy paid focus)

fCMO shifts: From hands-on to strategy + ops oversight. Hires the dedicated marketer. Sets up the channel playbooks before paid scales.

Tier 3 — Seed deployment

Budget profile:

• Paid acquisition: $20–50K/mo
• Tooling stack: $2,000–5,000/mo
• Retainers / fCMO: continued
• Headcount: + designer (potentially fractional)

Marketing capability:

• Paid scaling across 2–3 channels
• Brand-aligned creative production (designer enables velocity)
• Lifecycle programs fully live across all flows
• First true content production cadence (weekly cadence sustainable)

Channels live: All previous + paid scaling + structured launch motion

Hires unlocked:

• Designer (brand, creative, web)
• Second marketing manager (if first was lifecycle, second is content; or vice versa)
• Potentially fractional PR if budget allows

fCMO shifts: Hands off lifecycle to dedicated owner. Moves to GTM strategy + channel mix optimization + growth analytics.

Tier 4 — Series A

Budget profile:

• Paid acquisition: $50–150K/mo
• Tooling stack: $5,000–10,000/mo
• Retainers / fCMO: may transition to permanent CMO
• Headcount: full marketing team forming

Marketing capability:

• Paid scales aggressively across all proven channels
• Brand campaigns become possible
• International consideration begins
• B2B vertical expansion (if applicable)
• Sophisticated CAC/LTV math + attribution

Channels live: Full marketing surface area

Hires unlocked:

• Performance marketing lead
• Content lead
• Designer (permanent)
• Potentially: PR firm, paid agency, international growth manager
• Series A often the moment the fCMO transitions out or transitions to advisor

fCMO shifts: Often the moment of transition — to permanent CMO hire, fCMO becomes advisor.

Tier 5 — Series B+

Budget profile:

• Paid acquisition: $150K+/mo
• Tooling stack: $10,000–25,000/mo
• Headcount: 10+ marketing org

Marketing capability:

• Brand campaigns at industry scale
• PR firm partnerships
• Acquisitions as marketing (acquiring newsletters / podcasts in space)
• Conference sponsorship at category level
• Sponsorships at brand level

Channels live: Everything available

Hires unlocked:

• VP Marketing or CMO
• Brand director
• Growth / performance team (3–5 people)
• Content team (3–5 people)
• Designers (2–3)
• PR director or agency partnership
• International marketing leads (region-specific)

fCMO involvement: Typically out of the company by this point — the original fCMO might still be an advisor.

How to apply tier logic in a plan

Section 3 (Current state)

• State the client's current tier explicitly: "Current tier: pre-seed / bootstrapped per Tier 1."

Section 4–8 (AARRR sections)

• Note tier-dependent moves: "Paid layer (Tier 2 unlock — held until seed close)"
• For Tier 1 plans: every move must be executable at current budget tier OR explicitly flagged as future
• For Tier 2+ plans: moves can assume the tier's capability

Section 10 (12-month outlook)

• Each quarter names the tier that's active: "Q2 — Months 4–6 (post seed close). Funding state: Tier 2."
• Tier transitions trigger plan recalibration moments

Section 11 (Marketing operations stack)

• Use the table in references/ops-stack-mapping.md capability-unlocks section
• Make it client-specific: "Today (Tier 1): {client's current capability}. After seed close (Tier 2): + {what changes}."

Adjustments by client category

The standard tiers assume a typical software / SaaS / consumer app. Adjust for category:

Consumer apps (D2C)

• Higher paid acquisition floor — apps need to test CAC against download cost benchmarks (~$2-10 install + 5-15% trial conversion benchmark)
• Tier 2 starts effectively at $10–20K/mo paid (otherwise can't get statistically meaningful reads at app-install CPMs)

B2B SaaS

• Lower paid acquisition floor — LinkedIn / Google Ads can produce signal at $3–5K/mo
• More weight on content + sales enablement budget
• Often add a sales hire before a content hire

Hybrid hardware + software

• Hardware revenue can self-fund some marketing (the eye-mask wedge pattern)
• Paid budget should track blended CAC across hardware sales + app subs
• Shopify-side optimization is a Tier 1 priority (cheap leverage)

Deep-tech / scientific / clinical

• PR + investor marketing carries more weight than paid
• Conference speaking + academic publishing > Meta ads
• Tier 1 can produce significant traction without paid

Marketplace / two-sided

• Each side has its own AARRR funnel — budget splits accordingly
• Supply-side acquisition often dominates early; demand-side dominates after liquidity

Open source / developer tools

• DevRel + community + content > paid
• GitHub stars / npm installs are the activation event
• Paid layer often delayed until Series A

Tier 1 budget detail (most common starting point)

For Tier 1 clients, the marketing budget breakdown typically looks like:

For the plan, this becomes: "Current monthly marketing budget: $X (tooling only, no paid)."

When to surface tier limits to the founder

If a founder asks for moves that require a future tier:

• Name the requirement: "This is a Tier 2 move (requires $10K+/mo paid budget). Will unlock after seed close per the 12-month outlook in §10."
• Don't refuse — frame the timing

If a founder underestimates what's needed:

• Be honest: "To scale paid acquisition meaningfully, expect Tier 2 budget. Tier 1 can validate organic; Tier 2 validates paid."

If a founder is over-funded for their stage:

• Don't pad budget to match. Recommend the right work for the funnel state, return excess capacity, suggest investment in compounding rather than scaling.

Tier-skip cases (worth flagging)

Some companies skip tiers:

• Notable founder raising larger-than-typical rounds — can jump from Tier 1 to Tier 3 directly
• Hardware company with PR moment — can deploy at Tier 3 levels with the right product moment (e.g., a high-profile longevity-influencer endorsement)
• B2B SaaS post-LOI with named enterprise contracts — can fund pilot deployment from contract value

If the client is in a tier-skip situation, name it explicitly in the plan rather than forcing them into the standard ladder.

---

Supporting file: references/growth-patterns.md

Growth Patterns — The Real Shape of SaaS Growth

The 12-month outlook in every plan (Section 10) describes a trajectory. This doc names the shape of that trajectory honestly — what real SaaS growth looks like, when to expect plateaus, and how to plan for the next leg of growth before the current one stalls.

Excerpted and adapted from Founding Marketing by Corey Haines.

The long, slow SaaS ramp of death

Pitch decks show hockey sticks. Real growth shows a series of S-curves — each representing a distinct phase followed by a plateau that tests resolve and creativity.

Phase 1 — $0 → $10K ARR (the grueling phase)

The hardest milestone. Every customer is a hard-won victory. Typical time: 6–12 months. Most companies pivot the product multiple times during this phase.

What it requires:

• Runway long enough to keep experimenting until something clicks
• A financial cushion or additional income sources (often the difference between success and shutdown)
• Tolerance for ambiguity — the product positioning, the pricing, and the channel can all still be wrong at this stage

Phase 2 — $10K → $100K ARR (the treacherous middle)

The middle ground that kills most promising startups. The average company reaches ~$40K ARR in year one. The danger: enough revenue to prove the concept, not enough to support a team.

The threshold to watch for: $8–10K MRR. That's when founders can typically go full-time on the business without other income sources. Until then, careful cash management or side income carries the company through.

Companies that flame out in Phase 2 usually run out of runway just as things start working.

Phase 3 — $100K → $1M ARR (the acceleration phase)

Where things get interesting. Typical time: nearly 2 years total to reach $1M. But there's an acceleration pattern: once across $100K, companies often double from $100K → $200K in one-third the time it took to reach the first $100K.

Why: critical mass kicks in. Word-of-mouth starts working. Early customers become your best salespeople. The product has proven itself, and growth becomes more about execution than experimentation.

This is the phase where the marketing plan's 90-day roadmap (Section 9) starts compounding instead of just covering ground.

Two real growth patterns (and the exponential myth)

The myth: successful SaaS companies grow exponentially, doubling revenue month over month like clockwork.

The reality: two distinct patterns, often combining at scale to look exponential when zoomed out.

Pattern 1 — Linear growth

Build a predictable revenue machine. Find a channel that works (content, partnerships, paid, outbound) and steadily scale it. Some companies reliably add $10K MRR per month through a well-oiled marketing engine.

Less sexy than exponential. Far more sustainable. Crucially, plannable: when you know what you can count on adding each month, hiring decisions, product roadmap, and expansion planning all become tractable.

Pattern 2 — Step-function growth

Periods of plateau followed by sudden jumps. Jumps aren't random — they're triggered by specific events:

• Breaking into a new market segment (e.g., enterprise after starting SMB)
• Launching a major product expansion (new feature line, new tier)
• Cracking a new marketing channel that compounds

Example: one founder saw revenue triple in two months after launching enterprise features — following six months of flat growth.

Key insight for the plan: each step requires deliberate action and investment. Steps don't happen by waiting. While standing on the current step, you have to be actively building the next one.

How they combine

Zoom out far enough and a series of linear phases + step functions can look exponential. That's where the myth comes from. Understanding it's actually a series of plannable shapes changes how you build the plan:

• Don't chase the myth of doubling every month
• Build sustainable linear systems (Sections 4–8 AARRR moves)
• Plan deliberate step functions (Section 10 12-month milestones)

Layering growth curves — Channel × Product × Market

The secret to sustained growth isn't one perfect channel. It's orchestrating multiple S-curves that work together. Three S-curves to track:

Channel S-curves

Every marketing channel has its own lifecycle:

• SEO — 6–12 months to mature; once it does, steady leads for years. Marathon runner.
• Paid ads — quick wins; diminishing returns as you scale.
• Content marketing — slow to start, compounds beautifully over time.
• Partnerships / co-marketing — episodic; high yield when the right partner aligns.
• Outbound — predictable when calibrated; CAC-heavy and plateaus at team capacity.
• PR — spike-driven; sustains awareness rather than direct conversion.

The rule: start the next channel before the current one plateaus. Riding one channel to its ceiling before investing in the next produces a multi-month growth plateau that takes more effort to break out of than it would have taken to start the next channel earlier.

In the plan: Section 4 (Acquisition) names current channels, planned channels, and skipped channels. The 12-month roadmap (Section 10) sequences when the next channel investment begins.

Product S-curves

Your core product naturally hits a growth ceiling as you saturate the initial market. Pushing harder on the same features doesn't break through. What does:

• Adding features that target new use cases
• Extending the product line to serve adjacent needs
• Expanding into new market segments (e.g., team collaboration added to a single-user tool — opens a new market)

In the plan: Sections 5 (Activation) and 8 (Revenue) name where the product needs to grow to unlock the next growth tier.

Market S-curves

Every market segment has its own growth ceiling. Time the expansion into the next segment while the current segment is still showing strong growth. Common patterns:

• SMB → mid-market → enterprise
• Single vertical → adjacent verticals
• Domestic → international

Waiting until a segment is saturated makes the transition harder.

In the plan: Section 2 (Strategic frame) names current segment + future segments. Section 10 (12-month outlook) sequences when expansion moves begin.

The orchestration

The real magic: while SEO is maturing, you're using paid for quick wins. As those channels mature, you're developing product features that unlock enterprise. Meanwhile, the groundwork for international expansion is being laid for when domestic saturates.

This is the operational thesis behind the AARRR mapping (Sections 4–8) and the 12-month outlook (Section 10): each section is a curve, and the plan sequences them so the next curve is ramping while the current one is still growing.

The 3-3-2-2-2 VC growth path

For companies that have crossed $1M ARR and raised institutional capital, the VC benchmark is:

Most companies don't hit this. Useful regardless — anchoring the 12-month outlook against this benchmark forces the plan to either (a) match it and show how, or (b) explicitly defend choosing a slower trajectory.

For non-VC-backed (bootstrapped, founder-funded, profit-focused) companies, this curve doesn't apply. Use linear or step-function targeting instead.

How this informs the plan

Operational guidance for the planner

• Don't promise exponential. If the plan implies doubling every month, the founder will use it against you in 90 days. Linear + step-function is honest.
• Name the binding constraint. Phase 1 binding constraint is finding any channel that works. Phase 2 is funding the team. Phase 3 is breaking the ceiling on whichever channel got you here.
• Plateaus aren't failures. They're the moment between two S-curves. The plan should anticipate them and stage the next move.
• Don't conflate "growth" with "growth rate." A company adding $20K MRR each month for 24 months has built a remarkable machine. The fact that the percentage growth rate declines as the base grows is arithmetic, not failure.

---

Supporting file: references/measurement-framework.md

Measurement Framework — KPIs, North Stars, Cadence

Every plan needs a measurement section that tells the team how to know if the plan is working. This doc is the source for Section 13's measurement subsection.

Related docs:

• growth-patterns.md — the 3-3-2-2-2 VC growth path (3× in years 1–2, 2× in years 3–7 from $1M ARR) and which phase of SaaS growth the company is in ($0–10K / $10K–100K / $100K–1M+)
• budget-planning.md — CAC calculation (blended, not paid-only) and the forecasting reality check (forecasts under $100M ARR are educated guesses, not precise predictions)

The north-star principle

A north star is one metric that captures the business-model thesis at the highest level. It should:

• Be derivable from the funnel + revenue model
• Move slowly enough to be a strategic compass (not whipsawed by weekly noise)
• Trade off correctly against other metrics — improving the north star should generally improve the business

Don't default to "ARR" or "MRR" alone. Those are outcomes, not norths. Pick something that captures the business model.

North-star patterns by business model

B2B SaaS (subscription)

• Net Revenue Retention (NRR) — keeps existing customers + expansion in focus
• Alternative: "Logo retention × expansion ARR"
• Why: ARR alone hides churn / lets gross-add growth mask product fit problems

D2C consumer app (subscription)

• Blended LTV / blended CAC — keeps unit economics honest as paid layer scales
• Alternative: "Day-35 paid users from cohort × LTV"
• Why: monthly subscription metrics are volatile; cohort × LTV smooths it

Hybrid hardware + software (e.g., Quietude)

• Blended LTV / blended CAC across hardware + software — captures the wedge thesis
• Alternative: "Hardware-buyers-to-subscriber conversion × blended margin"
• Why: hardware revenue isn't free (cost to make); subscription revenue isn't expensive to acquire if hardware funds it

Marketplace (two-sided)

• Liquidity ratio × take-rate — captures both sides + monetization
• Alternative: "Monthly transacting users × take-rate × repeat frequency"
• Why: GMV alone doesn't capture whether the marketplace is becoming a habit

Developer tool / open source

• Weekly active developers × paid-conversion — captures both adoption and monetization
• Alternative: "Weekly active orgs × seats per org × ARPU"

Content / media business

• Daily active readers / listeners × ad revenue per session — captures both reach and monetization
• Alternative: "Subscriber count × retention × ARPU"

Commerce (DTC, non-subscription)

• Repeat purchase rate × AOV × frequency — captures monetization layered on quality of customer
• Alternative: "Customer LTV / CAC × payback period"

Leading indicators by AARRR stage

After the north star, every plan needs leading indicators per AARRR stage. These move faster than the north star and trigger investigations.

Acquisition leading indicators

• Organic visits/month, total + per pillar (SEO health)
• App Store / Play Store visit-to-install rate (ASO health)
• Founder-led social channel growth → email subscriber conversion (LinkedIn / X / Substack funnels)
• Event-to-app conversion rate (event ROI)
• Ambassador-attributed visits (referral funnel)
• Paid CAC by channel (when paid is firing)

Activation leading indicators

• Day 1 / Day 7 / Day 35 → paid conversion rate
• Onboarding session-completion rate
• First key-action completion (post-signup activation event)
• App Store conversion rate (install → trial → paid)
• Trial → paid conversion rate

Retention leading indicators

• Day 30 / Day 60 / Day 90 retention
• Monthly churn rate (gross + net)
• Lifecycle email engagement (open / click / unsubscribe by flow)
• Hardware → app activation rate (for hybrid businesses)
• Win-back / reactivation rate

Referral leading indicators

• Ambassador-attributed new subs (via Dub or similar)
• Share-after-value moment rate (% of users sharing)
• Two-sided referral completion rate
• Guides program referrals (when live)
• NPS score (if surveyed)

Revenue leading indicators

• ARPU by cohort
• Annual plan adoption %
• Cohort LTV by source
• Plan mix shifts
• Eye-mask / hardware attach rate (for hybrid)
• Expansion revenue (B2B)

Review cadence

The plan should specify three rhythms:

Weekly (operational sync)

• Who: fCMO ↔ founder (CEO usually)
• Duration: 30 min
• Format: AARRR scoreboard (current vs. last week numbers across the leading indicators) + this week's ships + blockers
• Output: Action items, decisions made

Monthly (metrics review)

• Who: fCMO + founder + extended team (CXO, product lead, designer if applicable)
• Duration: 60–90 min
• Format: Full metrics review + comparison against quarterly KPI targets + qualitative learnings + idea bank reprioritization
• Output: Possible plan adjustments, hire decisions

Quarterly (plan recalibration)

• Who: fCMO + founders + key advisors
• Duration: 2–3 hours
• Format: Full plan review against 90-day and 12-month outcomes, channel-level analysis, funding-stage transition check, recalibration of next 90 days
• Output: Updated plan (could be v2 / v3 document iteration)

KPI target setting

For each quarter in Section 10, the plan must include 3–5 specific KPI targets. These should be:

• Specific — not "improve retention," but "Day 30 retention from 22% → 30%"
• Measurable — pull from a wired data source
• Stretch but plausible — based on funnel state + historical patterns
• Decision-triggering — if missed, what does that mean? (Adjust strategy, kill a channel, etc.)

KPI target patterns by quarter

Q1 (foundation quarter):

• Mostly bedrock metrics — fixing leaks. "Headphones-gate conversion drop reverses." "Day 1 → paid +25–50%."
• Some foundation metrics — laying tracks. "4 SEO pillars staked." "App Store rewrite shipped."
• Avoid bold growth targets — the foundations aren't in yet

Q2 (validation quarter):

• Mostly validation metrics — does what we built work? "Paid CAC < $X blended." "Organic traffic 1,500–3,500/mo."
• Some cohort metrics — do new cohorts behave better? "Day 7 retention for Q2 cohort vs. Q1."

Q3 (scaling quarter):

• Mostly scaling metrics — how far does it go? "Paid scaling to $20–30K/mo with CAC steady." "First B2B install reference case live."
• Some capability metrics — what new things are live? "First Guides pilot launched."

Q4 (compound quarter):

• Mostly compound metrics — is the flywheel turning? "50%+ of new subs from non-paid channels." "Ambassador-driven 15–25% of new subs."
• Some narrative metrics — does the Series A story write itself? "Blended LTV/CAC > 3."

Anchoring against the VC growth path

For VC-backed clients past $1M ARR, anchor 12-month and multi-year targets against the 3-3-2-2-2 rule (3× in years 1 and 2, then 2× in years 3 through 7). Hitting it is rare; most companies don't. Anchoring against it forces the plan to either match it and show how, or explicitly defend choosing a slower trajectory. Full table and context in growth-patterns.md.

For non-VC-backed companies (bootstrapped, founder-funded, profit-focused), the 3-3-2-2-2 doesn't apply. Use linear-pattern targets ("$X MRR added per month") or step-function targets ("$Y revenue jump after the enterprise tier launches") instead.

Forecasting reality check

A plan derives a budget and an annual goal. It does not produce a 12-month month-by-month forecast that's reliably accurate to the dollar.

Unless the company is publicly traded, all forecasts are educated guesses. No startup under $100M ARR consistently hits month-by-month forecasts. Quarterly review is when the plan adjusts — not when variance is treated as failure.

What the plan commits to honestly:

• The annual goal is a defensible direction-of-travel
• The budget is the resource commitment that makes the goal plausible
• The 90-day roadmap (Section 9) is what's actionable now
• Month-to-month projection is illustrative, not promised

Founders who over-engineer the forecast end up explaining variance every month instead of executing. The plan should resist this — name the annual target, the quarterly KPIs, and the kill criteria. Don't promise the month.

Full context in budget-planning.md.

Kill criteria

For every channel or initiative, the plan should specify when to stop. Often missing from plans, kill criteria force discipline.

Examples:

• "If a paid channel has CAC > 2× target after 30 days at meaningful spend, pause."
• "If onboarding Variant 3 doesn't show statistically meaningful lift (or directional lift + congruent qualitative signal) after 4 weeks, move to Variant 1."
• "If lifecycle Flow 4 has open rate < 12% after 6 weeks, redo subject lines + audience segmentation."

Guardrail metrics

Some metrics get a hard guardrail (cannot drop below threshold). Useful for protecting brand or unit economics during aggressive growth.

Examples:

• "Brand voice complaint rate > 1% of customer feedback triggers content review."
• "Paid CAC > $X for two consecutive months pauses paid scaling pending audit."
• "App Store rating drops below 4.5 triggers product review."

Data sources mapping

The plan should name where each metric comes from. This makes it auditable.

When data isn't wired

If a metric can't currently be measured, flag it in Section 13's open decisions. Example:

"Hardware → app activation rate not currently visible in the App Store dashboard. Requires Shopify ↔ App Store Connect join. Q1 work item."

A plan with un-measurable goals is a plan that can't be validated. Surface the instrumentation work explicitly.

Reporting cadence + automation

Where possible, auto-generate the metrics review rather than building it manually each time. Stripe MCP + GA4 MCP + Customer.io MCP can pull most of what's needed.

For Tier 1 clients, a simple weekly metrics email to the team (Markdown table, generated via skills + MCPs) costs nothing and creates discipline.

For Tier 2+ clients, consider a real dashboard (Hex, Metabase, Looker, or internal tool).