Advocacy should be run by agents, not account managers
The best playbooks admit the truth: manual ops work at 5 creators, strain at 50, and are impossible at 500. Their answer is to hire a Social Operator and stand up a Discord. Ours is to hand the grind to agents.
Pluto's advocacy layer is an early-access pilot build on VYG's live data layer and attribution. Where this playbook says Pluto does something, read: the pilot is built to.
Read the two most operationally honest creator playbooks in circulation and you find the same confession, written twice. The first describes a new hire it calls the Social Operator — a person who lives in creator culture, translates briefs into "creator gold," spots trends early, and balances freedom against conversion. It states the scaling law plainly: "Manual processes work at 5 creators. They break at 50. Impossible at 500." The second describes the machine that Social Operator is supposed to run — a retainer ambassador army held together by weekly owner meetings, individual Discord channels per creator, 50/50 payout verification in the platform backend, and a Notion bible of what to say and what not to. Its author is candid about why the incumbents leave this to you: "most agencies won't touch it because the ROI isn't there for them."
That is the whole game, stated against interest. The advantage these programs sell is not software. It is labor — a human account manager, or a small department of them, doing coordination work that does not scale linearly with the roster. The incumbent tools sit underneath that labor and bill for the seat. When they get to the part where the work actually breaks, the recommendation is always the same: hire another operator.
Pluto's position is the inverse. The coordination work is real, but it is protocol work, not relationship work — recruit, vet, brief, pay, and police, each a defined transition with defined inputs and a policy that governs it. Anything that is protocol work can be run by an agent. So Pluto runs it with agents, over an open MCP interface, inside guardrails you set. The human stops being the advantage and becomes what it always was: the cost.
Walk the program stage by stage and the difference is not "faster." It is a different substrate.
Recruit
Today, recruitment is an outreach bot spraying thousands of DMs a day filtered by niche, gender, follower count, and GMV — then a human sorting the replies, vetting video quality, and chasing the ones worth chasing. The founder records a 30-second video and drops a Drive link so it feels personal. It is personal-at-scale theater, and it works until the volume of replies exceeds the operator's hours.
A Pluto recruit agent starts from a different signal. It reaches for the advocate already inside the post-purchase SMS conversation — a customer who has bought, is satisfied, and is one consented reply away from enrolling. The agent handles the ask, the consent capture, and the handle collection as a conversation, not a campaign. There is no reply queue to drain because the roster is grown from people who already raised their hand, ranked by revenue they can actually be shown to drive rather than followers they claim.
Vet
Manual vetting is a green-flag checklist a person runs by eye: video quality, real GMV, already sells for competitors. It is judgment, and judgment is exactly the thing that does not clone across 500 applicants. So it degrades — the operator gets looser as the inbox gets deeper.
A vet agent applies the same criteria as a rule, uniformly, at any volume, and it does not get tired at applicant 400. Fit, prior performance, and category signal are evaluated identically for the first advocate and the five-hundredth. The judgment is encoded once, in policy, and then held constant — which is the one thing a human operator structurally cannot promise.
Brief
The Notion "creator bible" is the incumbent's honest attempt to automate a person: distill the A/B learnings, the hooks that work this month, the angles, the things not to say, and have your best creator record a walkthrough because peers trust peers. It is a static document that a human must keep current and re-explain per creator.
A brief agent treats that bible as live context. It briefs each advocate in native language, tuned to what is converting now, without a person rewriting the same guidance for the fortieth partner. The brief is not a PDF someone maintains; it is generated against current performance every time, per advocate, at no marginal human cost.
Pay
The retainer model runs on 50/50 payouts — 50% up front, 50% after a human verifies delivery in the platform backend, prorated if the creator came up short. Multiply that by twenty retained creators producing fifteen to thirty videos a month each and payout verification alone becomes a job.
| Ops stage | Manual today | Agent-run on Pluto |
|---|---|---|
| Recruit | Outreach bot + human reply-sorting | Agent enrolls the consented post-purchase advocate in-conversation |
| Vet | Operator's eye, degrades with volume | Criteria applied as policy, uniform at any scale |
| Brief | Static Notion bible, re-explained per creator | Live brief generated against current performance, per advocate |
| Pay | Manual 50/50 verification in the backend | Payout-within-policy against verified, attributed delivery |
| Fraud-flag | Guessing ROI; spot-checking for fakes | Deterministic attribution; anomalies flagged automatically |
A payout agent settles within the policy you define, against delivery that has already been verified and attributed deterministically — not estimated, not eyeballed. The prorate logic, the delivery threshold, the commission tier: all rules the agent enforces so a person does not spend their week reconciling backends.
Fraud-flag
This is the stage the manual model handles worst, because it is the stage where the incumbents have no ground truth. Their measurement chapter is a tour of workarounds — EMV, halo surveys, media-mix guesses — which means fraud detection is also a guess. You cannot flag a fake conversion when you never had a real one to compare it against.
Pluto's fraud-flag agent stands on the same deterministic attribution that runs the rest of the program: the click-to-order path is the record, so an anomaly against it is a signal, not a
See the full agent program — every stage, every guardrail
The complete walkthrough of recruit → vet → brief → pay → fraud-flag as agent transitions, plus the policy surface you control. Free. No case studies we can't prove.