Brand context leaks between accounts
Voice notes, forbidden claims and subject boundaries need to belong to the client project, not to whichever prompt an editor copied last.
Aboveboard for agencies
Draft at agency speed. Let the client make the final call.
Aboveboard separates client briefs, connected channels, private media and review authority by project. Your team researches, drafts and prepares channel visuals; the client or account lead approves the exact copy and media ready to publish.
Pro includes 6 projects, 20 connected channels and 5 seats. Scale removes the project and channel caps and includes 25 seats.
- 6
- projects included on Pro
- 20
- connected channels on Pro
- 25
- seats included on Scale
The agency handoff
Every client adds context, access and approval — not just another content calendar.
Agency volume becomes difficult when the operating system treats every brand as one workspace and every collaborator as the same kind of user.
Client review arrives without evidence
A draft sent through chat or a document rarely carries the source trail and rule checks that produced it.
The agency absorbs opaque AI costs
When a tool hides generation inside a plan, it is difficult to understand which client or action consumed the allowance.
A cleaner client operation
Give each brand its own rules and each reviewer the right boundary.
Aboveboard keeps the agency efficient without asking a client to surrender the final publishing decision.
A separate brief for every client
Store the voice, claims, source requirements and off-limit topics with the project that owns them.
Agency drafting, client approval
Editors can prepare and revise content while a client reviewer or account lead controls approval and publishing.
Usage that can be explained
Credit costs are published per action, making it possible to understand the difference between a relevance check, a draft and a research run.
Each client project keeps its own growth story. Aboveboard separates measured signals from derived or estimated ones, surfaces patterns with their evidence, and lets the agency turn a useful pattern into a new client-ready draft without mixing one brand’s learning into another.
The client loop
A repeatable workflow with project-specific judgement.
The system repeats. The client context does not get flattened.
See the complete product workflow- 01
Set up the client project
Use client-approved websites or documents to prepare an editable brand proposal, or enter it manually. Review its voice, facts, restricted topics and campaign direction before saving; channels can wait.
Each project keeps its own evidence and rules together. - 02
Find worthwhile opportunities
Use discovery to surface conversations related to the client’s topics and run a relevance check before spending more credits on a reply.
A relevance check costs 1 credit. - 03
Research and draft
Build a cited research brief when the post needs evidence, then adapt the draft for the chosen destination.
A research run costs 8 credits; a post draft costs 4. - 04
Route it to the reviewer
The agency revises inside the queue. The person carrying approval authority sees the copy, rules and sources together.
The reviewer can approve, reject or send the draft back. - 05
Schedule only the approved version
Choose the channel and time after approval, then match the published post with the engagement it earns.
Only the approved version is eligible to publish.
Mechanisms a client can inspect
A credible approval process should survive a client question.
When someone asks where a claim came from, why the wording changed or who authorised it, the answer should be visible in the work.
Project-level boundaries
Voice rules and restricted claims belong to the client project, reducing the risk of carrying one brand’s context into another.
A named approval role
Drafting access and publishing authority are separate, so the agency can do the work while the designated reviewer keeps control.
Official account connections
Clients connect channels through each platform’s sign-in rather than handing an agency their platform password.
Published unit costs
Credits are attached to specific actions, and purchased credits do not expire. Monthly plan credits reset each calendar month.
The system does not promise client growth, reach or engagement. It makes the drafting and approval process easier to inspect. Read the privacy policy (English)
Agency questions
How projects, clients and costs fit together.
Need a plan-level answer? Compare the limits and credit allowances.
Can a client approve while the agency does the drafting?
Yes. An editor can generate and edit but cannot publish. A reviewer approves and publishes, which supports an agency-drafts, client-signs-off workflow.
How are different client brands kept separate?
Each project carries its own brief, rules, connected channels and collaborators. The project is the boundary for the client’s working context.
Do clients need to give us their social passwords?
No. Channels connect through each platform’s official sign-in. Access can be revoked at the platform.
Can we estimate AI usage by action?
Yes. Relevance checks cost 1 credit, reply drafts cost 2, post drafts cost 4 and research runs cost 8. X publishing has its own published credit costs because X charges per post through its API.
Which plan is intended for several clients?
Pro includes 6 projects, 20 channels and 5 seats. Scale has no project or channel cap and includes 25 seats.
Aboveboard for agencies
Put one client through a cleaner approval loop.
Create the brief, draft with sources attached and let the designated reviewer decide what is ready.