Run marketing without headcount

Founder / solo operator / lean-team founder / agency owner · Assemble in ~15 min; first run in <2 min once installed.

GTMEdit flowon X◐ readiness 51

step 1ready

Orchestrate the agent colony

marketing-swarm14 alts

step 2ready

Positioning / GTM strategy

go-to-market-strategy2 alts

step 3ready

Produce content + conversion copy

marketing-strategist14 alts

step 4partial

Distribute via paid + channels

money-ads3 alts

step 5ready

Run outreach sequences with reply handling

outreach-sequencer8 alts

step 6connector

Report on funnel performance

⚡ GA4 / analytics

step 7ready

Sync state to CRM

geo-prospect4 alts

Did this recipe work for you?

What you get

▸A coordinated agent org (positioning → content → outreach → reporting)
▸Weekly output pack with approval gates
▸Persistent pipeline + content state

tools: inherits connectors of nested recipes

tokens: ~$10-30/week at steady cadence

≈ $40-120/mo tokens

What stays yours

· Work the approval gates (the org pauses for you by design)
· Weekly direction-setting (what to push, what to pause)

The problem

When I can't afford a full GTM team or a tool stack, I want a coordinated, installable colony of specialized agents (positioning → content → copy → distribution → outreach → reporting → CRM-sync) that hand off work with persistent state and approval gates, so I run an entire marketing operation solo while I sleep.

Readiness

Most of the pipeline genuinely assembles from the library: a marketing-swarm orchestrator plus solid/rich specialists for strategy, copy/content, outreach, and CRM-sync give you 5 ready legs. The real holes are the data/tool-bound ones — distribution needs live ad and channel accounts, and reporting needs live metrics piped in — plus the cybernetic glue (a shared memory store and a colony-wide scheduler) that no single skill provides. So it's a strong skeleton, but "runs my whole marketing org while I sleep" still requires bringing live integrations and wiring state+scheduling yourself.

Cybernetic layers

Memorybyo

No colony-wide persistent state store. 284 geo-prospect gives a CRM-lite file store for lead records, but cross-agent handoff state (who did what, approval-gate status, last-run cursors) must be brought — a shared DB or a structured file store the orchestrator reads/writes each run.

Background / schedulingpartial

530 outreach-sequencer ships its own daily cron loop, so the outreach arm runs unattended. But running the whole colony headcount-free while-you-sleep needs an external scheduler (cron / Claude Code routine) to wake the orchestrator and step the pipeline; only one arm is self-scheduling out of the box.

Harnessready

Claude Code. Invoke the orchestrator (482) as the entry skill; it dispatches the specialist skills via the Task/subagent mechanism, with approval gates as human-in-the-loop checkpoints between legs.

Click any step to see what fills it — and the ranked alternatives you can swap in.