Loading
Because a campaign has ten deliverables and each one is approved in email. Version four is approved, version five is sent, and the thing that goes live is whichever the person publishing happened to have open.
When a client says they never signed that off, reconstructing the truth takes an afternoon and produces a maybe.
A campaign is a project with phases and deliverables. Each deliverable has an approval state, an approver and a dated record of what was approved, visible in the client portal rather than in somebody's inbox.
Recurring work — the monthly report, the weekly posts — is a recurring task rather than a thing somebody remembers.
It does not schedule social posts or send campaigns. It manages the work that produces them, and integrates with whatever publishes.
And it will not make a client approve faster. It will show exactly how long each approval has been waiting, with a name against it.
The client sees the same records the team works from, so the status conversation stops being a weekly assembly job. Approvals happen where the work is.
Books bills from the sold lines when a phase completes, so a retainer and a project piece do not need reconciling by hand at month end.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, through the client portal, which shows only what you publish to it.
Yes — recurring phases with time tracked against them, and margin visible per month.
Yes, per version, with who approved what and when.
Half an hour on your own numbers is usually enough to say whether Loop is the right place to start.