Skip to content

JasonColapietro/suede-creator-skills / skills/suede-marketing-plan

suede-marketing-plan

Verified

Suede Marketing Planning Skills: a scored tactic shortlist or a full AARRR operating plan with a 90-day plan, 12-month roadmap, and measurement. Use when asked "what should we try next" or for a marketing plan grounded in budget, capacity, and evidence. NOT FOR: channel execution, contested bets (suede-marketing-council), recurring loops (suede-marketing-loops), or positioning alone (suede-product-marketing).

references/plan-template.md

View on GitHub
# Plan Template: The 13-Section Structure

The canonical template for every marketing plan generated by this skill. Each section has a purpose, a structure, and inline prompts for what to draft.

The Quietude plan (see `references/example-quietude.md`) is the canonical reference implementation.

---

## Title block

```markdown
# {Client}: Marketing Plan {plan_version}

**Prepared by:** {Author / fCMO name}
**For:** {Founders / leadership team}
**Date:** YYYY-MM-DD
**Status:** Draft {plan_version}: for team review
```

---

## Section 1: Executive summary

**Purpose:** Lift-and-share. A founder should be able to paste this into a board update or investor email without editing.

**Length:** 400–700 words. Tight.

**Structure:**
1. **One-sentence frame.** What does this plan optimize for? Not "more revenue": something specific to this client at this stage.
2. **Three big bets, ranked by leverage.** Each is a paragraph. Bet = a high-conviction thesis about where the team should focus capital and attention.
3. **What twelve months looks like, plausibly.** Bullet list. The plausible outcome state at end of plan horizon. Investor-readable.
4. **90-day priorities.** Numbered list. The six (give or take) moves that ship in the first quarter.

**Voice notes:**
- Match the client's voice
- Direct, founder-readable, no marketing-speak
- Use names and numbers (specific channels, specific metrics), not abstractions
- Tradeoffs named explicitly when they matter

---

## Section 2: Strategic frame

**Purpose:** Distill positioning, ICP, business-model logic, and brand voice into a single page that any team member or new hire can read to orient.

**Length:** 800–1500 words.

**Structure:**

### What {Company} is, in one sentence
Pulled from positioning doc / seed deck / founder language.

### The category we're claiming
Is the company creating a new category, redefining an existing one, or competing in a defined category? Name it. State the category-defining frame in 2–3 sentences. Reference the source (founder's words, ICP doc, etc.).

### Who we're for (ICP, distilled)
Demographics / firmographics + stated problem vs. real problem + what they're actually buying. Tight, 4–6 bullets.

### The business model logic
How does the company make money? What's the customer-acquisition unit economics theory? What's the compounding channel thesis (if any)? Pulled from seed deck / financial model / founder narrative.

### Brand voice (the non-negotiable)
If the client has documented voice rules, list them. YES / NO vocabulary. CTA rules. Tone. Core method (initiatory, explanatory, narrative, etc.). Every other section of the plan must respect these.

**Voice notes:**
- This section is the most "lift from existing materials", don't invent positioning. Surface what's there.
- If positioning is unclear or contradicted across materials, flag it in Section 13's open decisions.

---

## Section 3: Current state

**Purpose:** Anchor the plan in reality. What's the team, budget, in-flight work, and stuck work *today*?

**Length:** 1000–2000 words.

**Structure:**

### Team composition (marketing surface area)
Table of every person with marketing surface area:

| Person | Role | Marketing surface area |
|---|---|---|

Be honest about gaps. For each uncovered capability, record the outcome, present
owner and capacity, evidence of durable workload, access and risk, options
(reassign, defer, automate, contractor, agency, or employee), decision owner,
maximum exposure, and review date. Do not infer a hire, title, or vendor from
company size, funding, or hire order; use `references/team-and-agency-model.md`.

### Marketing budget (current)
- Paid acquisition: $X/mo
- Tooling stack: list with estimated cost
- Retainers / fCMO: list
- Headcount: list
- Blended CAC: $X (must include salaries, content costs, tools, retainers, not just paid spend; see `references/budget-planning.md` for the calculation)
- Current spend as % of ARR: X% (record for context; do not compare with an
  unsourced universal range)

State which capabilities are current, approved tests, conditional unlocks, or
deferred (see `references/funding-stage-unlocks.md`). The 90-day plan includes
only current work and explicitly approved tests.

### Phase of SaaS growth
Name the observed pattern and current constraint from dated acquisition,
activation, retention, capacity, cash, and market evidence (see
`references/growth-patterns.md`). Section 10 presents conditional low/base/high
scenarios and review checkpoints.

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

| Asset | Status | Marketing leverage |
|---|---|---|

This is where past launches, PR moments, content pillars, certifications, notable users get acknowledged. **Critical**: don't write a plan that ignores work the team is proud of.

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

| Item | Status | Blocker |
|---|---|---|

Be honest about blockers. Where the blocker is "no time" or "no decision," that goes to Section 13's open decisions.

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

| Issue | Cost of inaction | Action |
|---|---|---|

Stuck things are the most leverage-positive places to focus the first weeks of the 90-day plan.

### Audit rubric snapshot
17-section scored snapshot using the embedded current-state rubric. See `references/current-state-rubric.md` for the full rubric and scoring guides.

If a prior scored audit exists, paste those scores in. Otherwise score from available materials and note "scored from materials" under the heading.

| # | Section | Score | Note |
|---|---|---|---|
| 1 | Positioning | 0–5 | |
| 2 | Customer research | 0–5 | |
| ... | ... | ... | ... |
| 17 | Internationalization | 0–5 | |

**Total: X / 85 (Y%).** Note the *shape* of strength and weakness: that shape is the gap the rest of the plan closes.

**Voice notes:**
- Honest > polished. If the client's metrics are bad, name them. Founders read past sugar-coating.

---

## Section 4: Acquisition

**Purpose:** Answer "how do strangers become aware of us?" Map every channel: current state, planned moves, skipped (with reason).

**Length:** 1000–1800 words.

**Structure:**

### Current state
Brief. What's working today, what's not, what the data shows about channel mix.

### The plan
Numbered "Moves." Each move is a paragraph describing the evidence, hypothesis,
owner, specific work, exposure, review date, and stop conditions. Build the
move set from client evidence rather than an archetype menu. Candidate questions:

- Is there measured search demand and an accessible site surface?
- Does a verified marketplace or store listing matter to the current funnel?
- Which audience channels show comparable reach and qualified action?
- Is there a source-backed credibility event worth amplifying?
- Do events, partnerships, commerce, or sales enablement address the measured
  constraint?
- Is a paid test justified by audience, economics, tracking, creative capacity,
  explicit approval, and an affordable downside?

### 90-day acquisition moves
Week-by-week breakdown of the ships in the first quarter.

### 12-month acquisition outlook
Quarter-by-quarter outcome state (Q1 / Q2 / Q3 / Q4).

### Skills + tools
- **Skills:** list relevant public Suede skills (`suede-seo-audit`, `suede-programmatic-seo`, `suede-ads`, `suede-social`, `suede-competitors`, etc.)
- **MCPs / APIs:** list connections (Ahrefs API, GA4 MCP, Typefully MCP, Stripe MCP for LTV math, etc.)

---

## Section 5: Activation

**Purpose:** Answer "once someone tries us, do they have an experience that converts?"

**Length:** 800–1500 words.

**Structure:** Same as Acquisition (Current state / The plan / 90-day / 12-month / Skills + tools).

**Common moves:**
- Bedrock fixes (broken signup, broken onboarding gates, etc.)
- Onboarding tests / rebuild (often the most leveraged move at this stage)
- App Store listing rewrite (cross-references to Acquisition)
- Lifecycle Flow ship order (when to ship onboarding emails vs. hold for product stability)
- Paywall + pricing review (often Activation × Revenue)

### Skills + tools
`suede-onboarding`, `suede-paywalls`, `suede-copy`, `suede-site-alchemy`, `suede-ab-testing`, etc.

---

## Section 6: Retention

**Purpose:** Answer "once someone converts, do they stay and deepen?"

**Length:** 800–1500 words.

**Structure:** Same as above.

**Common moves:**
- Lifecycle email flows (post-purchase, lapsed user, win-back)
- Subscription / preference centers
- Churn reconciliation (often metric definitions don't match across surfaces)
- Hardware → software activation paths (for hybrid businesses)
- Annual plan default tests (cross-references to Revenue)

### Skills + tools
`suede-emails`, `suede-churn-prevention`, `suede-copy`, `suede-paywalls`, etc.

---

## Section 7: Referral

**Purpose:** Answer "do retained users bring more users, and at what cost?"

**Length:** 500–1200 words.

**Structure:** Same as above.

**Common moves:**
- Ambassador / affiliate pilot only after inbound fit, rights/disclosures,
  economics, owner capacity, tracking, maximum exposure, approval, review, and
  stop conditions are verified
- Share-after-value moments built into product
- Founder amplification (founder as referrer-zero)
- Long-game expert / Guides / certified-host network
- Gifting flows (for consumer / hardware)

### Skills + tools
`suede-referrals`, `suede-social`, `suede-emails` (for ambassador lifecycle), `suede-copy`, etc.

---

## Section 8: Revenue

**Purpose:** Answer "what do we charge, who pays, and how does it compound?"

**Length:** 500–1200 words.

**Structure:** Same as above.

**Common moves:**
- Pricing audit (what's actually charged today vs. listed?)
- Annual plan default tests
- Hardware → software bundling formalization (for hybrid businesses)
- Storefront / commerce page optimization
- B2B case studies + sales material
- Long-term value pools (data licensing, enterprise expansion): flagged not executed in 12-month plan

### Unit economics
Required table:

| Metric | Value | Note |
|---|---|---|
| ARPC (avg monthly revenue per customer) | $X | Pulled from Stripe / billing |
| Blended CAC | $X | Includes all marketing costs, not just paid |
| Retention / churn input | X% | Definition, cohort, window, source, as-of date |
| LTV range | $X–$Y | Finance-approved model, margin treatment, horizon, source assumptions |
| LTV / CAC range | X–Y | Compared with the company's approved hurdle and payback constraint; no universal threshold |

These feed the sensitivity model in Section 10. If any input is unknown, label
the output `unverified assumption`, show low/base/high cases, and list the
missing decision in Section 13. Do not use a reciprocal-churn shortcut when
cohort retention, gross margin, or a finance-approved LTV definition is absent.

### Skills + tools
`suede-pricing`, `suede-paywalls`, `suede-sales-enablement`, `suede-revops`, `suede-ab-testing`, etc.

---

## Section 9: 90-day roadmap

**Purpose:** The tactical execution layer. Every move ships within a named week, with an owner.

**Length:** Tables, not prose. Should fit on one printed page if possible.

**Structure:** Four 2–3-week sprints:

### Weeks 1–2: Unblock
Highest-confidence, lowest-cost changes. Removing things that are broken.

| Move | Stage | Owner |
|---|---|---|

### Weeks 3–4: Foundation
Pillar/foundational work. Domain consolidation. First content. First flows shipping. First tests live.

### Weeks 5–8: Velocity
Compounding work begins. Content cadence. Repeat tests. Channel scaling.

### Weeks 9–12: Compound
Second-order moves. Layered tactics. 90-day review prep.

---

## Section 10: 12-month outlook

**Purpose:** Quarterly decision checkpoints with conditional capability
unlocks anchored in dated evidence, resource capacity, approval, and an
explicitly testable growth-pattern hypothesis.

**Length:** Four sub-sections, one per quarter. ~250–400 words each. Plus a short framing paragraph at the top naming the budget method and growth pattern.

### Framing (top of Section 10)

State explicitly:
- **Scenario method used.** Capacity-based or goal-based sensitivity model.
  See `references/budget-planning.md`; show source dates, low/base/high
  assumptions, approval state, and limitations.
- **Maximum approved exposure**, downside stop, owner, and review date.
- **Resulting outcome range.** A decision scenario, not a guarantee.
- **Growth pattern hypothesis.** Linear, step-function, or layered S-curves,
  chosen from current evidence and revisited at the review date.

### Structure (per quarter)

#### Q{N}: Months {X}–{Y}

**Verified resource state:** {current evidence, capacity, cash/runway boundary,
owner, and approval as of date}

**Conditional unlocks:** {condition → capability}, including decision owner,
maximum exposure, review date, and pause/stop conditions. A financing event may
be one condition but never supplies the spend, hire, vendor, channel, or target.

**Focus:** One-sentence focus theme for the quarter.

**Outcomes by end of Q{N}:**
- Bulleted outcome list (5–8 items)

**KPI decision rules:** 3–5 source-backed ranges or thresholds. For each, name
baseline/cohort/date, low/base/high assumption, owner, review date, and action
on hit/miss. Do not invent a number to fill the template.

**Channel/Product/Market S-curve position:** Which curves are growing, which are plateauing, which is the next one being staged for this quarter (see `growth-patterns.md`: layering principle).

---

## Section 11: Marketing operations stack

**Purpose:** Show how approved work runs through accountable owners, present
capacity, authorized manual or tool-assisted workflows, review gates, and
fallbacks. Do not imply that tooling replaces staffing or expertise.

**Length:** Tables + brief explanation.

**Structure:**

### The thesis
1–2 paragraphs explaining how the public Suede skill pack and verified integrations make approved workflows more repeatable. Do not claim headcount equivalence, guaranteed throughput, or replacement of channel ownership and human review.

### Skills mapped to AARRR stages

| Stage | Primary skills | Supporting skills |
|---|---|---|
| Acquisition | (list) | (list) |
| Activation | (list) | (list) |
| Retention | (list) | (list) |
| Referral | (list) | (list) |
| Revenue | (list) | (list) |
| Cross-cutting | (list) | (list) |

### MCPs / APIs mapped to stages

| Stage | Existing connections | fCMO tooling layer |
|---|---|---|

### A concrete example
Pick one verified operational moment that shows how the stack was used. Name the source artifact, owner, review gate, and observed result; do not infer causality or broader performance from the event.

### Capability unlocks by verified resource state

| Capability | Current evidence/owner | Constraint | Unlock condition | Approval / maximum exposure | Review / stop |
|---|---|---|---|---|---|
| (workflow) | (source, date, owner, capacity) | (specific gap) | (verified condition) | (decision owner and ceiling) | (date and rule) |

### Team and agency model (RACI)

Use `references/team-and-agency-model.md` to compare current ownership,
reassignment, deferral, automation, contractor, agency, and employee options
against actual duration, capacity, access, risk, cost, and handoff needs.

| Function | Owned by (internal strategic role) | Executed by (IC / contractor / agency) |
|---|---|---|
| Growth marketing (demand engine) | | |
| Product marketing (story engine) | | |
| Content marketing (trust engine) | | |

If a function lacks an accountable owner, add a bounded ownership decision to
Section 9. Do not assume the answer is a hire or vendor. Record evidence
required, options, decision owner, maximum exposure, approval, review date, and
the interim safe state. Pull conditions from
`references/funding-stage-unlocks.md`.

---

## Section 12: Tactical idea bank

**Purpose:** Cross-reference all 142 ideas from `references/tactic-library.md` against AARRR stages, with client-specific status.

**Length:** Long: tables can easily total 150+ rows.

**Structure:**

### Intro paragraph
Explain the cross-reference: Sections 4–8 prescribe what's *being done*. This section maps what's *possible*.

### Status legend

- **Current**: already active with a verified owner and evidence
- **Approved test**: bounded test with exact approval, exposure, and stop rules
- **Conditional**: only after named evidence, capacity, approval, and review gates
- **Deferred**: intentionally held pending a named decision or resource
- **Skip / off-brand**: incompatible with brand voice or business model

### 12.1 Acquisition ideas

By status (Current / Approved test / Conditional / Deferred / Skip), tables of
relevant tactic-library entries by number.

| # | Idea | Client note |
|---|---|---|

### 12.2 Activation ideas
### 12.3 Retention ideas
### 12.4 Referral ideas
### 12.5 Revenue ideas
### 12.6 Cross-cutting / brand foundation ideas

### Idea-bank summary
- Counts per AARRR stage
- Counts skipped, with rationale
- What the plan covers as a % of the available tactical surface area
- What this proves about the client's stage

Use `references/idea-cross-reference.md` as the source-of-truth mapping. Apply
client-specific filters during draft. Timing comes from fit, evidence, owner
capacity, dependencies, authorization, and stop conditions: not a round label.

---

## Section 13: Measurement, RACI, open decisions, appendix

**Purpose:** Operational close. Define how the plan gets measured, who owns what, what's still TBD, and where to find the deeper docs.

**Structure:**

### Measurement: the metrics that matter

**North star (proposed):** One metric that captures the business-model thesis. For Quietude it was blended-LTV-to-blended-CAC; for a B2B SaaS it might be NRR × NPS; for a marketplace, take-rate × monthly transacting users. Make it specific to the company.

**Leading indicators by AARRR stage:** Table:

| Stage | Leading indicators |
|---|---|
| Acquisition | ... |
| Activation | ... |
| Retention | ... |
| Referral | ... |
| Revenue | ... |

**Review cadence:**
- Weekly: who syncs with whom, on what
- Monthly: who reviews what
- Quarterly: plan recalibration trigger

### RACI

| Domain | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|

Common domains: strategic plan, brand voice, app/product implementation, lifecycle, SEO content, App Store, founder-led social, events, ambassadors, B2B sales, pricing, investor narrative, future hires.

### Open decisions blocking the plan

Ranked by impact. Each is: name + impact + what's blocked.

1. (highest impact) ...
2. ...
8. (lowest impact) ...

### Appendix: deep-dive links

**Published in this repo / shared with team:** {relative paths to docs in the shared repo}

**Founder-authored strategic context** (internal knowledge base): {names of docs the team has access to outside the plan repo}

**fCMO working drafts** (not yet published): {names + how to access from author}

---

## Closing line

```markdown
*{Client} Marketing Plan {plan_version}. Prepared by {Author}, {Date}. For team review and discussion.*
```

---

## Per-section heuristics for "is this section done?"

- **Section 1**: A non-Quietude reader could understand the company's growth thesis from this alone.
- **Section 2**: Brand voice rules are explicit enough that any new copywriter could follow them.
- **Section 3**: All "in-flight" items have an owner and a blocker named.
- **Sections 4–8**: Each move names an owner, evidence source, execution method,
  review gate, and fallback. Name a public Suede skill or authorized tool only
  when actually available; a manual workflow is valid.
- **Section 9**: Every row has an owner.
- **Section 10**: Each quarter names source-backed scenarios, resource
  conditions, accountable approval, review date, and pause/stop rules.
- **Section 11**: At least one evidence-backed operational example shows how the stack was used without overstating causality.
- **Section 12**: Skip list has rationale, not just absence.
- **Section 13**: North-star is specific to this company (not generic "ARR growth").
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall