A staged, evidence-based rollout for the first OpenClaw marketing agent — promoting TeamCentral's closed-loop MCP wedge to consultants and operators.
Every blog post links to a TeamCentral-hosted artifact. Every demo video shows a real send-from-Claude. Every lead enrichment is performed via the product. The work itself is the proof.
The video's architecture is sound. We adopt the structure but tune every principle to TeamCentral's wedge.
| Rythic's principle | How we apply it |
|---|---|
| One agent, one job | Resist the super-agent temptation. Each sub-agent has a single output type. |
| Start with one, layer up | Phase 1 ships only two agents. Trust is earned. |
| Orchestrator on a frontier model | MarkyMark itself = orchestrator on Opus 4.6. Sub-agents can be smaller. |
| Voice training before scale | Week 0: collect 20+ of David's best LinkedIn posts, emails, Loom transcripts. |
| Trend × Pain overlap = gold | Same rule: Twitter trend × Reddit pain × TC feature = highest-priority slot. |
| Engagement Intel is underrated | We agree — but stay Tier 1 (human approval) longer than Rythic does. |
Rythic sells an indie-dev tool. We sell the action layer for Claude and ChatGPT. Different wedge, different moves.
Each recipe IS a working demo with a hosted artifact link. 365 pieces/year, ~10 min of David's time each. The wedge content engine.
Marky uses TeamCentral MCP for its own lead enrichment, follow-ups, and content distribution. Failures get caught internally; wins become case studies.
"Vanilla Claude (7 steps) vs. TeamCentral MCP (1 prompt)" is its own content lane. Visual catnip for the AI-ops audience.
Test four tribes in Week 1 — consultants, sales, AM, recruiters. Double down on whichever pulls. Start narrow: consultants managing clients.
Before any public push, prove the demo doesn't break. Then come the keys.
Before any public push, David sends every normal email via TeamCentral MCP for 7 days. The first public failure of the send-from-Claude demo is expensive — skeptics will try to break it.
Goal: catch every rough edge ourselves before strangers do.
Ship the smallest system that delivers a daily output David can review from his phone. Resist scope creep.
Opus 4.6. Coordinates sub-agents, handles exceptions, surfaces decisions to David through one Slack/Twilio channel — never noisier than that.
Scrapes r/consulting, r/SaaS, r/ChatGPTPro, r/ClaudeAI, LinkedIn comments, X. Ranks by TC-shape fit × engagement velocity. 3–5 opportunities/day, draft reply included.
One recipe/day demonstrating chat → draft → host → send. Real prospect scenario, one prompt, live artifact link, time-saved metric. The wedge in motion.
10 published MCP recipes + 20 Tier-1 engagement replies by end of Week 2. Measure click-through on the artifact links.
Three more agents. Ad posting moves to Tier 2 — guardrails, not free rein.
Daily JSON of what's hot in AI-ops, MCP, Claude/ChatGPT power-user space. Feeds the Recipe Generator and the Long-form Writer.
Weekly Tuesday publish. Takes the strongest Trend × Pain overlap and writes in David's voice. Bias toward comparison content and the Fathom Trojan-horse angle.
Article → LinkedIn + X thread + carousel + 60-sec video script + community distribution list. Every variant carries a TeamCentral shareable link as the CTA.
Ads go live within guardrails: budget cap, max 3/day, pre-approved themes.
1 blog/week + 5 X posts/day + 3 LinkedIn posts/week + ≥1 attributable signup.
Marky earns the right to optimize itself. Performance feeds back into next week's drafts.
Friday weekly report: Ahrefs, TC analytics, X/LinkedIn engagement, signups, attribution. Format: 3 wins, 3 misses, 1 recommendation. Foundation for Phase 4 ad reallocation.
5–10 concurrent A/B tests across post variants, ad creative, headlines, CTAs. Winners auto-feed the Writer + Repurposer. Losers killed within 48 hours.
Demonstrable week-over-week CTR or signup lift attributable to winning variants.
Full closed loop on ads and back-office. Public replies stay Tier 1 indefinitely until voice is bulletproof.
Every signup → LinkedIn lookup → TC Contact Directory cross-ref → personalized welcome drafted via TeamCentral MCP. Marky is the first power user.
Daily watch on Calendly, Jasper, Granola, Fireflies, Otter. Tactical response content when they ship — or stumble.
Reads Fathom transcripts via MCP. Extracts exact prospect phrases. Feeds verbatim into ad copy and landing pages. The killer pattern — language from buyers' mouths beats founder-voice every time.
Same skeleton, different organs. Three Marky-only agents have no Rythic equivalent.
| Rythic | Marky | Phase |
|---|---|---|
| Axis (orchestrator) | MarkyMark | 01 |
| Medium Research | Pain-Point Listener | 01 |
| Engagement Intel | (merged into Pain-Point Listener for v1) | 01 |
| Trend Intel | Trend Intel | 02 |
| Medium Writer | Long-form Writer | 02 |
| Content Repurposer | Repurposer | 02 |
| Tweet Gen | (rolled into Repurposer + Recipe Generator) | 02 |
| — new — | MCP Recipe Generator | 01 |
| — new — | Performance Reporter | 03 |
| — new — | Experiment Loop | 03 |
| — new — | Inbound Lead Enricher | 04 |
| — new — | Competitor Moves Desk | 04 |
| — new — | Customer-Conversation Miner | 04 |
Don't dilute the wedge. MCP closed-loop content gets half the production hours.
Fathom Trojan-horse angle · Founder Voice amplification (2–3 LinkedIn posts/week)
Autonomy expands on the back-office; public engagement stays human-in-loop for as long as it needs to.
Each is preventable, but only if we name it before it happens.
Confirm Phase 0 homework is on track, then I draft the three artifacts that unblock Week 1.