How to charge clients for social media scheduling

Three models cover most of what agencies actually charge for social scheduling, often blended:

• Per-client flat fee. One monthly rate per client covering scheduling and publishing across their connected accounts, regardless of exact post count within a reasonable range. Simple to sell and simple for a client to budget for, but it only stays profitable if your own delivery cost per client is predictable — which is easier when every client is cleanly isolated instead of tangled together in shared tooling.
• Per-platform pricing. A base fee plus an add-on per connected platform (Instagram, LinkedIn, TikTok, and so on). This maps naturally onto how much work each platform actually adds — a client running five platforms genuinely creates more format variations, review cycles, and failure surface than one running two — and it gives you a clean upsell path when a client wants to add a new channel.
• Tiered by post volume. A small number of packages (e.g., a lower tier for a handful of posts a week, a higher tier for daily posting across channels) rather than metering every individual post. Volume tiers are easy for clients to compare against competitors and easy for you to forecast capacity against, without the friction of a true pay-per-post model.

Whichever model you pick, the one thing all three depend on is being able to run every client's accounts from a single account of your own without their data bleeding into each other — and being able to show, not just claim, that the posting actually happened.

PostGate models each client as its own profile group — a real boundary around that client's connected profiles, schedules, and posts, created with POST /api/profile-groups, not a naming convention layered on top of one shared pool of accounts. That distinction matters directly for pricing: a per-client or per-platform fee only makes operational sense if you can actually isolate what belongs to which client. Keys can be bound to a single profile group, so a team member or integration working on one client's content literally cannot see or touch another client's accounts — which is also what lets you safely delegate execution to junior staff or automation without a data-mixing incident becoming a client-trust incident. Offboarding a client, when a retainer ends, deletes its group and dependent data in one call instead of a manual cleanup pass across shared tables.

A client paying a flat monthly fee for scheduling eventually asks, reasonably, what they got for it. "We scheduled your posts" is a weak answer if a post silently failed to publish and nobody noticed — see the worst failure mode in social publishing. PostGate's answer is structural, not a summary you reconstruct by hand: every post carries a targets array with per-platform status, attempt count, error detail, and permalink once published, and GET /api/posts/{id}/logs returns a sanitized delivery timeline you can hand directly to a client as proof of work. That's the difference between billing for effort and billing for a result you can point to.

Beyond confirming a post went out, GET /api/posts/stats returns analytics snapshots scoped per profile group — meaning per client. That's the same boundary the pricing model relies on: you can pull a clean, client-scoped performance summary for a monthly report without filtering it out of a shared, cross-client dataset, and without a client ever seeing another client's numbers by accident.

Most agencies don't need white-labeling to charge a client — PostGate's own connection screens carry the PostGate name by default, which is invisible to a client who never sees a connection flow because you connected their accounts on their behalf. White-label becomes relevant specifically when a client connects their own accounts through a hosted flow you send them, and you don't want that flow to say "PostGate" instead of your agency's name. Because that's an entitlement on specific plans, not a default, it's a natural premium-tier line item — see white-label & BYOK — rather than something every client-priced plan needs to absorb the cost of.

If you run your agency on an off-the-shelf dashboard instead, white label means different things on different tools; our comparison of social media management software for agencies shows which plans brand the reports, the dashboard or the domain.

It's tempting to price scheduling per post, because that maps directly onto POST /api/posts calls. In practice this under-prices the actual work (content strategy, approval, and handling a failed delivery don't scale down just because a client posts less that week) and creates an incentive to under-post rather than post well. A flat or tiered structure, backed by real delivery evidence you can show on demand, is what lets you price the outcome — reliable, accountable publishing across every one of a client's platforms — instead of the individual API call underneath it.