Campaign management
The operational side of a campaign: schedules, approvals, deliverables and payments, tracked stage by stage.
We don't run campaigns on email threads, we run them on one record everyone can see
Campaign management is the unglamorous discipline that determines whether a good idea survives contact with reality. It is schedules, approvals, deliverables and payments, and it is where most creator work quietly goes wrong: a deliverable slips, an approval is verbal, a payment is late, and trust erodes. We run campaigns stage by stage, with each state change recorded, so that at any moment everyone can see what has been delivered, what has been approved and what is owed.
How we work
The operational surface has grown more complex, not less. A single campaign now spans organic posts, their paid amplification through Spark Ads and Partnership Ads, disclosure obligations that vary by market, and measurement that has to be reconciled across platforms that each report differently. We hold all of it in one place. Approvals are logged against the person who gave them, deliverables are tracked against the brief, and the paid-media layer is managed alongside the organic work rather than in a separate silo that no one reconciles until it is too late.
- Each stage has an owner, a date and a definition of done.
- Approvals are recorded with who approved and when.
- Deliverables are checked against the contract before sign-off.
- Payment follows delivery without a separate chase.
Where this is going
Where this is going is toward more automation of the routine parts, with AI agents scheduling, chasing approvals and flagging risk. TikTok's Symphony Agent, unveiled at Cannes in June 2026, and similar tools point clearly in that direction. We are building toward that carefully, on the principle that automation should make the record more complete, not less legible. A campaign should be auditable from brief to final payment, and the more of it that machines touch, the more that matters.
How we help
One schedule
Every deliverable has a date, an owner and an approval path, set at the start and visible throughout. Changes are logged with who asked for them and when.
The schedule is the same document for the brand, the creator and our team.
Explore related issues:
Approvals that hold
Drafts move through a fixed approval path with named reviewers. A creator is never asked to redo work because a comment arrived late from someone who was not on the list.
Approved work is frozen with a timestamp, so there is no argument later about which version went live.
Explore related issues:
Payments on time
Payment milestones are tied to approvals, not to invoices chasing each other. When a deliverable is approved, the payment it unlocks moves without another conversation.
Statements show the math.
Explore related issues:
Our thinking
