# Running Growth Experiments

> Reviews an Earth Care Network Growth Plan and turns its recommendations into armed, running automations. Use when someone wants a growth-plan checkup, asks what is confirmed versus open, wants to know what to work on next, or wants to automate their sales follow-up.

- Skill: `giving-back-studio/running-growth-experiments` (Agent Skill)
- Install (CLI): `npx skillmds@latest add giving-back-studio/running-growth-experiments`
- Raw SKILL.md: https://api.skillmd.com/api/skills/giving-back-studio/running-growth-experiments/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: Giving-Back-Studio (https://skillmd.com/u/giving-back-studio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/giving-back-studio/running-growth-experiments

---


# Running growth experiments

The Growth Plan is the living deliverable: **story → offer → icp → signals →
prospects → moves → automation_plan**. This skill audits it and closes the gaps.

## Audit

`get_growth_plan` returns the plan plus real metrics. Report plainly which
modules are confirmed, which are drafted but unconfirmed, and which are empty.
Do not describe an empty plan as a start — say it's empty.

The metrics block is the honest read on whether anything is working. Content
created but never approved is not content shipped; say that when it's true.

## Close gaps in order

Modules compound — an `automation_plan` is only as good as the `icp` under it.
Work the earliest open one first.

- `update_growth_plan_module` — draft or revise. Only some modules are draftable
  here, and the parameter differs: **`content`** (a string) for `story`/`icp`,
  **`payload`** for `targets`/`channel_bets`/`challenges`/`agentic_solutions`.
  `offer`, `signals`, `prospects`, `moves`, and `automation_plan` are confirm-only.
  There is no `value` parameter — sending one writes nothing.
- `confirm_growth_plan_module` — after the owner approves it. Accepts all seven.

If `icp` is thin, stop and use `refining-your-icp` rather than drafting a weak
one inline.

## Arm the automations

Confirming `automation_plan` returns 2-3 recommendations computed from that
business's own confirmed ICP, watchlists, and leads. **These are computed, not
authored — narrate what comes back, don't invent additions.**

`create_workflow_from_template` instantiates one as a **draft**. Templates
include `daily-lead-digest`, `signal-inbox-digest`, `daily-gtm-followups`,
`sales-inquiry-pipeline`, `sales-follow-up-3day`.

Say clearly: it is a draft, it does not run until they publish it, and nothing
sends without their approval. A person who believes automation is live when it
isn't will miss real leads.

Don't arm a template the plan didn't recommend. If they ask for one anyway,
that's their call — just say it isn't grounded in their data.

## Choosing what's next

When someone asks "what should I do?", answer from their data, not best
practice in general:

1. **No confirmed ICP** → that, before anything else.
2. **ICP confirmed, no watchlist** → arm monitoring; it compounds while they sleep.
3. **Signals arriving, none triaged** → triage; unread signals are worth nothing.
4. **Leads with no follow-up** → drafts; the pipeline leaks here.
5. **All of the above healthy** → then automate the repeated motion.

Name the one next action, not five. A person with five priorities has none.