Many clients, many accounts, one integration, and no seat licences.
Agency tooling is usually priced per seat and organised around a dashboard. If you are automating, both are the wrong shape: you pay for people who never log in, and you cannot script the thing you do fifty times a day.
Profiles keep each client's accounts separate. Post to one brand by name without naming every channel it owns.
You are not charged per account or per seat. You are charged for posts, which is the thing that actually scales with your work.
If you hand automation to a client's own agent, restrict it to their brand and their networks so it cannot reach anything else.
Analytics come back in one shape across every client and network, so a monthly report is a query rather than an afternoon.
Create a profile per client, connect their accounts to it with a link they open themselves, then post by profile name.
curl -X POST https://api.postlake.dev/v1/posts \
-H "Authorization: Bearer $POSTLAKE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "…", "accounts": ["acc_…"]}'No. There are no seat licences and no per-account fees. You pay for posts.
Each client is a profile owning its own connected accounts. A post addressed to one profile can never reach another's channels.
Yes. Generate a signed connection link and send it to them. They approve on the network's own screen, which is the one step that always needs a human.