Skill Tracer
Skills › Marketing Skills › marketing-loops › loop-orchestration.md

loop-orchestration.md

71 lines · skills/marketing-loops/references/loop-orchestration.md at 88c79f6

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Loop Orchestration & Rollout
2
3Loops aren't independent scripts — they compose into a marketing operating system. This reference covers how they fit together and the order to adopt them so you never build them all at once.
4

Loop Orchestration & Rollout

Loops aren't independent scripts — they compose into a marketing operating system. This reference covers how they fit together and the order to adopt them so you never build them all at once.

Raw lines 1 to 4
5## The system view
6
7Loops fall into four layers. Data flows down and learnings flow back up.
8
9```
10SENSING analytics-anomaly · tracking-QA · weekly-marketing-review
11 │ (detect what changed; trust the numbers first)
12 ▼
13DIAGNOSTIC per-stage watchers — onboarding drop-off, churn-signal,
14 ranking-drop, landing-page regression, ad-fatigue, …
15 │ (figure out what to do about it)
16 ▼
17ACTION staged drafts, nudges, outreach, budget moves
18 │ (mostly human-checkpointed)
19 ▼
20LEARNING experiment-backlog · campaign-postmortem · voice-of-customer
21 │ (capture what worked)
22 └──────────────► feeds back into SENSING & DIAGNOSTIC
23```
25Key connective tissue:
26- **weekly-marketing-review is the router.** It reads top-line metrics and dispatches each notable mover to the loop that owns it. It's the one loop that sees the whole board.
27- **tracking-QA + analytics-anomaly are the foundation.** Every other loop reads from analytics. If tracking is broken, every downstream loop acts on lies. These come first.
28- **experiment-backlog is the sink.** Hypotheses generated by many loops (signup-leak, pricing, onboarding, voice-of-customer) converge here, then hand off to `ab-testing`. Don't let each loop run its own tests.
29- **voice-of-customer is a source.** Customer language it mines feeds copy for ad-fatigue, lifecycle-email, landing-page, and pricing loops.
30- **campaign-postmortem closes the loop.** Its learnings become next quarter's hypotheses and plan inputs, and the ones that hold are proposed for the **Learnings** table in the product-marketing context doc, where every drafting skill reads them.
32Avoid duplicate ownership: when two loops could act on the same signal, one owns the action and the other just flags. (E.g., an at-risk account belongs to churn-signal, not expansion/upsell — never upsell an account that's churning.)

The system view

Loops fall into four layers. Data flows down and learnings flow back up.

SENSING        analytics-anomaly · tracking-QA · weekly-marketing-review
                  │  (detect what changed; trust the numbers first)
                  ▼
DIAGNOSTIC     per-stage watchers — onboarding drop-off, churn-signal,
               ranking-drop, landing-page regression, ad-fatigue, …
                  │  (figure out what to do about it)
                  ▼
ACTION         staged drafts, nudges, outreach, budget moves
                  │  (mostly human-checkpointed)
                  ▼
LEARNING       experiment-backlog · campaign-postmortem · voice-of-customer
                  │  (capture what worked)
                  └──────────────► feeds back into SENSING & DIAGNOSTIC

Key connective tissue:

  • weekly-marketing-review is the router. It reads top-line metrics and dispatches each notable mover to the loop that owns it. It's the one loop that sees the whole board.
  • tracking-QA + analytics-anomaly are the foundation. Every other loop reads from analytics. If tracking is broken, every downstream loop acts on lies. These come first.
  • experiment-backlog is the sink. Hypotheses generated by many loops (signup-leak, pricing, onboarding, voice-of-customer) converge here, then hand off to ab-testing. Don't let each loop run its own tests.
  • voice-of-customer is a source. Customer language it mines feeds copy for ad-fatigue, lifecycle-email, landing-page, and pricing loops.
  • campaign-postmortem closes the loop. Its learnings become next quarter's hypotheses and plan inputs, and the ones that hold are proposed for the Learnings table in the product-marketing context doc, where every drafting skill reads them.

Avoid duplicate ownership: when two loops could act on the same signal, one owns the action and the other just flags. (E.g., an at-risk account belongs to churn-signal, not expansion/upsell — never upsell an account that's churning.)

Raw lines 5 to 33
Starts an agent dispatches :26
Names a skill ab-testing :28
34## Rollout path (adopt in this order)
36Add a loop only when the loops before it are running and earning their keep. Each stage assumes the previous one is solid.
38**Stage 0 — Foundation (trust the data + see the board).**
39`tracking-QA`, `weekly-marketing-review`.
40You cannot run any loop responsibly on untrustworthy data or without a full-funnel pulse. This is non-negotiable and comes first.
42**Stage 1 — Plug the leaks (highest ROI, protects existing revenue).**
43`failed-payment/dunning`, `churn-signal`, `lifecycle-email-refresh`.
44Recovering customers you already have is cheaper than acquiring new ones. Dunning alone often pays for the whole system.
46**Stage 2 — Convert what you already get (fix the bucket before adding water).**
47`onboarding drop-off`, `signup-funnel-leak`, `trial-conversion`.
48More traffic into a leaky funnel is waste. Seal activation and conversion next.
50**Stage 3 — Grow the top (now scale acquisition).**
51`keyword-gap`, `content-repurposing`, `ad-fatigue`, `social-listening`, `analytics-anomaly`.
52With the bucket sealed, turn on demand generation and the safety-net anomaly watcher.
54**Stage 4 — Optimize monetization.**
55`pricing-page-experiment`, `paywall-optimization`, `PQL/upgrade-intent`, `expansion/upsell`.
56Once volume is healthy, tune revenue per user — judged on revenue quality, not conversion alone.
58**Stage 5 — Compounding & advocacy.**
59`referral-nudge`, `review-and-UGC-harvest`, `review-site-management`, `case-study-sourcing`, `partner-pipeline`, `brand-mention/reputation`, `experiment-backlog`, `campaign-postmortem`.
60The flywheel: happy customers and earned media that feed back into acquisition, plus the learning loops that make everything compound.
62The remaining catalog loops (content-decay, striking-distance push, AI-answer check, AI-answer accuracy audit, claim-drift, signal-sweep, reply-triage, cold-domain health, sequence-retro, internal-linking, programmatic-SEO quality, content-calendar refill, weekly ads-check, paid-search query-mining, retargeting-hygiene, landing-page regression, community-engagement, competitor-watch, backlink-prospecting, directory-submission, feature-adoption, lead-capture-asset, email-deliverability, voice-of-customer, agent-default check, niche-outlier, creator-scouting, launch-reaction) slot into the stage that matches their function as each channel becomes a priority.

Rollout path (adopt in this order)

Add a loop only when the loops before it are running and earning their keep. Each stage assumes the previous one is solid.

Stage 0 — Foundation (trust the data + see the board). tracking-QA, weekly-marketing-review. You cannot run any loop responsibly on untrustworthy data or without a full-funnel pulse. This is non-negotiable and comes first.

Stage 1 — Plug the leaks (highest ROI, protects existing revenue). failed-payment/dunning, churn-signal, lifecycle-email-refresh. Recovering customers you already have is cheaper than acquiring new ones. Dunning alone often pays for the whole system.

Stage 2 — Convert what you already get (fix the bucket before adding water). onboarding drop-off, signup-funnel-leak, trial-conversion. More traffic into a leaky funnel is waste. Seal activation and conversion next.

Stage 3 — Grow the top (now scale acquisition). keyword-gap, content-repurposing, ad-fatigue, social-listening, analytics-anomaly. With the bucket sealed, turn on demand generation and the safety-net anomaly watcher.

Stage 4 — Optimize monetization. pricing-page-experiment, paywall-optimization, PQL/upgrade-intent, expansion/upsell. Once volume is healthy, tune revenue per user — judged on revenue quality, not conversion alone.

Stage 5 — Compounding & advocacy. referral-nudge, review-and-UGC-harvest, review-site-management, case-study-sourcing, partner-pipeline, brand-mention/reputation, experiment-backlog, campaign-postmortem. The flywheel: happy customers and earned media that feed back into acquisition, plus the learning loops that make everything compound.

The remaining catalog loops (content-decay, striking-distance push, AI-answer check, AI-answer accuracy audit, claim-drift, signal-sweep, reply-triage, cold-domain health, sequence-retro, internal-linking, programmatic-SEO quality, content-calendar refill, weekly ads-check, paid-search query-mining, retargeting-hygiene, landing-page regression, community-engagement, competitor-watch, backlink-prospecting, directory-submission, feature-adoption, lead-capture-asset, email-deliverability, voice-of-customer, agent-default check, niche-outlier, creator-scouting, launch-reaction) slot into the stage that matches their function as each channel becomes a priority.

Raw lines 34 to 63
64## Rollout rules
66- **One at a time.** Prove a loop earns its keep (someone acts on its output, it moves its metric) before adding the next.
67- **Foundation before growth.** Acquisition loops before solid tracking + retention = pouring water into a leaky bucket.
68- **Cap the total.** If you're running more loops than you can review the output of, you have vanity loops. Retire the ones nobody acts on.
69- **Re-audit quarterly.** Recalibrate thresholds, kill dead loops, promote the ones that consistently drive action.
71For worked examples of several loops composed into one channel operator, see `seo-operator.md` and `outbound-operator.md`.

Rollout rules

  • One at a time. Prove a loop earns its keep (someone acts on its output, it moves its metric) before adding the next.
  • Foundation before growth. Acquisition loops before solid tracking + retention = pouring water into a leaky bucket.
  • Cap the total. If you're running more loops than you can review the output of, you have vanity loops. Retire the ones nobody acts on.
  • Re-audit quarterly. Recalibrate thresholds, kill dead loops, promote the ones that consistently drive action.

For worked examples of several loops composed into one channel operator, see seo-operator.md and outbound-operator.md.

Raw lines 64 to 71