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/growth-patterns.md

View on GitHub
# Growth Patterns: Evidence-Driven Scenarios

Growth rarely follows a smooth forecast. Use patterns to organize hypotheses,
not to assign a company to a universal ARR phase or promise a timeline.

## Evidence First

Before selecting a pattern, record dated evidence for:

- acquisition volume, mix, cost, and saturation;
- activation and time-to-value;
- cohort retention and expansion;
- sales, onboarding, support, and product capacity;
- gross margin, cash, and approved exposure;
- market or product changes that could create a discontinuity.

If the evidence is missing, say `unknown` and propose the smallest measurement
or bounded test that resolves it.

## Pattern 1: Linear

A comparable unit is added at a roughly steady rate over a bounded period.

Use only when:

- the cohort and measurement window are explicit;
- variance is visible rather than hidden by a rolling average;
- capacity is sufficient for the implied volume.

Treat continuation as a hypothesis. Set a review date and stop condition.

## Pattern 2: Step Function

A discrete change: such as a launch, segment, product capability, or distribution
agreement: may shift the baseline.

Document:

- the intervention and causal hypothesis;
- the pre-change baseline;
- the decision window and confounders;
- the capacity needed if the baseline changes.

Do not label ordinary variance as a step function.

## Pattern 3: Layered Curves

Channel, product, and market initiatives can mature at different times. The plan
may prepare a second bounded test before the first plateaus, but it must not
assume every new curve compounds.

| Layer | Evidence to read | Constraint to name |
|---|---|---|
| Channel | marginal reach, CAC, conversion, saturation | creative, audience, budget |
| Product | activation, retention, expansion, support load | engineering and service capacity |
| Market | segment demand, sales cycle, win/loss, localization | fit, compliance, operations |

## Selecting the Planning Scenario

Build low, base, and high cases from the client's evidence. For each:

- name assumptions and sources;
- show capacity and cash constraints;
- define owner, review date, and stop conditions;
- separate approved work from conditional unlocks.

Funding stage and ARR may be descriptive context, but neither determines the
binding constraint, channel, hiring plan, growth multiple, or north-star metric.

## How This Informs the Plan

| Section | What to include |
|---|---|
| **3 (Current state)** | Dated evidence, observed pattern, uncertainty, and current constraint. |
| **4–8 (AARRR)** | Stage-specific evidence and the smallest intervention tied to the current constraint. |
| **9 (90-day roadmap)** | Approved tests and measurement checkpoints. |
| **10 (outlook)** | Low/base/high scenarios and conditional decisions, not a promised curve. |
| **13 (measurement)** | Metrics selected from the business model and current decision. |

External benchmarks belong only in a separate context box with current source,
cohort definition, and comparability limits.
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