Wellness Swarm

Mission Control

Every angle and objective in one place. Each lane below runs as its own conversation so they move in parallel instead of queuing behind each other. Copy a lane’s launch prompt, open the conversation, paste it, and that lane picks up with full context.

Open the Daily Run Sheet →Niche Rings →Launch Board →Agent Bus →News Desks →Coordinator →

Overall build progress

12 / 30 milestones

40%

1

Content & Media Engine

Articles, press releases, social posts, video scripts, feeds, Blogger drip

Live & earning-capable

Why its own chat: This is the only lane that constantly edits the content engine code. Keeping it separate stops article/feed work from being slowed down by ad-account and new-site chatter.

Where to open it: App Management Console → pick this app → New conversation. It MUST have access to this app, because the content engine, feeds and Blogger poster all live in this codebase.

Milestones · 4/8

  • ✓Article generator live (LLM → DB → published)
  • ✓4+ inline images injected into every article body
  • ✓RSS / custom feeds + press release formats
  • ✓Blogger API posting wired (roofing blog, 6 posts live)
  • ·Per-niche image sets beyond roofing — other niches fall back to the general home-services pool
  • ·Blogger network scaled past 1 blog
  • ·Fully scheduled hands-off content drip
  • ·Video lane (scripts → video → distribution) — not started

Standing objectives

  • •Scale the Blogger network: one blog per city+niche, all fed automatically
  • •Give every niche its own dedicated inline-image set (4+ images per article)
  • •Turn on video: scripts → generated video → YouTube/social distribution
  • •Press releases going out on a repeating schedule, not by hand
  • •Social posts auto-generated per article and queued
  • •Every published piece points at the right money page or tracking number

Can run hands-off

  • ▸Scheduled task: generate N articles per niche per day, auto-image them, publish
  • ▸Scheduled task: drip posts to each Blogger blog on a spacing that avoids rate limits
  • ▸Scheduled task: weekly press release per vertical
  • ▸Scheduled task: rebuild + redeploy so new content goes live without asking

Launch this lane

2

Paid Traffic & Ads

Ad accounts, campaigns, creatives, tracking, scaling rules

Ready to launch

Why its own chat: Ads run on a money clock — you want a conversation where every message is about spend, creatives and ROI, not one where that gets buried under code changes.

Where to open it: A plain new conversation is enough to research networks, build creatives and manage accounts. If it needs to change landing pages on the live sites, open it from the App Management Console against this app instead.

Milestones · 2/6

  • ✓Tracking numbers live on the money pages — 7 CallScaler numbers wired
  • ✓Landing pages + local pages live to send traffic to — ~1,600 local pages across 7 domains
  • ·Ad network account funded and approved
  • ·First campaign live
  • ·Creative library per niche
  • ·Automated spend/ROI monitoring

Standing objectives

  • •Get the first campaign live and sending real clicks to a tracked page
  • •One tracking link structure so every click is attributable to campaign + creative
  • •Creative library per niche (angles, hooks, images) ready to rotate
  • •Kill/scale rules defined before spending, not after
  • •Feed winning ad angles back into the content lane

Can run hands-off

  • ▸Scheduled task: daily spend + conversion pull, flag anything below target
  • ▸Scheduled task: auto-pause rules on losing creatives
  • ▸Scheduled task: daily performance digest emailed to you

Launch this lane

3

New Site Building

New domains, new verticals, new standalone properties

Build in progress

Why its own chat: Each new site is its own codebase and database. Mixing new builds into an existing app’s conversation is how schemas and deployments get tangled.

Where to open it: A brand-new conversation for each genuinely NEW site — a new site is its own project and database. Do not build new standalone sites inside this app’s conversation.

Milestones · 3/5

  • ✓7 domains live and deployed
  • ✓Local service-area takeover engine (32 niches, ~1,600 pages)
  • ✓Blogger twin-site layer (Call Kit gadget)
  • ·Repeatable recipe documented for a brand-new site
  • ·Next dedicated property picked and built

Standing objectives

  • •Decide which verticals deserve a dedicated property vs. another page on the existing network
  • •A repeatable build recipe so site #8 takes hours, not weeks
  • •Every new site launches with tracking, money pages and content already wired
  • •Keep the existing 7 domains coherent — one canonical vertical per domain

Can run hands-off

  • ▸Reusable build recipe/template so each new site starts from a known-good base
  • ▸Scheduled task per site: keep content and offers fresh automatically

Launch this lane

4

Affiliate / CPA Offers & Marketing

Networks, offer discovery, smartlinks, LP intel, payouts

Build in progress

Why its own chat: Offer/network work is research and relationship-heavy and moves on the networks’ clock. It does not need the codebase most of the time.

Where to open it: A plain new conversation for research, applications and offer intel. Open it against this app from the App Management Console only when offers need to be wired into the live pages.

Milestones · 2/6

  • ✓Offer discovery reports generated
  • ✓7 CallScaler pay-per-call numbers live
  • ·6 more pay-per-call approvals pending — waiting on networks
  • ·Payout method set up
  • ·Automated offer/payout refresh on a schedule
  • ·Subid tracking verified end-to-end on every live link

Standing objectives

  • •Keep a current, ranked list of live offers per vertical with real payouts
  • •Get approved on the networks that matter and keep accounts in good standing
  • •Every offer link carries subid tracking so revenue ties back to source
  • •Competitive LP intel — know what is actually converting before building
  • •Payout methods set up so money can actually land

Can run hands-off

  • ▸Scheduled task: refresh offer/payout discovery per vertical on a cadence
  • ▸Scheduled task: flag dead or paused offers still linked from live pages
  • ▸Scheduled task: pull network earnings into one report

Launch this lane

5

SignLink — QR Sign SaaS

Yard-sign QR → live listing portal + lead capture for agents

Planned — not started

Why its own chat: This is the only lane with a real recurring-revenue product and real customer data. It must stay completely isolated from the affiliate network.

Where to open it: A brand-new conversation and its OWN project/database. This is a product with paying customers, not part of the affiliate network — never build it inside the Wellness Swarm app.

Milestones · 1/5

  • ✓Concept and build spec defined
  • ·Project created
  • ·Core loop built (listing → QR → lead)
  • ·Billing live
  • ·First paying customer

Standing objectives

  • •Ship a working agent signup → listing page → QR → lead capture loop
  • •Pricing and billing live so it can take money
  • •First paying agent onboarded
  • •Then widen beyond real estate to other local businesses

Can run hands-off

  • ▸Scheduled task: listing price/status refresh from feeds
  • ▸Scheduled task: instant lead notifications to the agent

Launch this lane

How to actually run this

  1. 1. Don’t open all five at once. Two or three moving lanes is real parallelism. Five is five things half-done.
  2. 2. Lanes that change this codebase must be opened from the App Management Console against this app. A plain new chat cannot edit this app, and building a copy somewhere else is how databases and deployments get tangled.
  3. 3. Brand-new sites and SignLink get fresh projects. Their own codebase, their own database. Never inside this one.
  4. 4. Ads and offer research need no codebase. A plain new conversation is enough until something has to change a live page.
  5. 5. Automation is the point. Every lane has a “can run hands-off” list. Once a lane’s first objective is shipped, the next move is always to put it on a schedule so it keeps running without you.
  6. 6. This page is the memory. Come back here to see what is done, what is pending, and what each lane owes you — instead of scrolling back through chats.