All use cases

Money

Whop desks: one bot for acquisition, ads, ops metrics

Whop connected, then three jobs mashed into one agent for the screenshot.

Share

What hurt

Cicero (@cicerougc) says the Whop connector is not a party trick: one bot for acquisition, one for ads, one for ops watching MRR, churn, and LTV — assign one job per desk and delete the rest. If an agent cannot name its job in one sentence, it does not ship. Tip-only, crisp.

What to install or create

Connect Whop once. Split three desks. Delete agents that fail the one-sentence job test.

Bots

  • Whop acquisition

    Acquisition lane only. One-sentence job or delete.

  • Whop ads

    Ads lane only. Spend needs your yes.

  • Whop ops

    Watch MRR, churn, LTV. Report; do not silently change pricing.

Plugins

  • Whop

    Required

Routines

  • Weekday: ops desk metrics brief; quiet if unchanged.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/cicerougc/status/2099226914460242005.
  2. 2Connect Whop in Settings → Plugins.
  3. 3Create three bots: acquisition, ads, ops (MRR/churn/LTV) — one sentence each.
  4. 4Delete any leftover general helper that cannot pass that test.
  5. 5Gate ads spend and refunds; ops reports only by default.

Approval fence

Ads spend, refunds, and public posts stay behind your yes.

What to tweak

Steal one-job-per-desk. Connector access is not a license to mush roles.

Source

Cicero @cicerougc · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro