# What to Charge for Social Media Management

Build the number from your own cost to run the page, not a borrowed average: add the backend tool cost per page to the hours you spend deciding, writing and checking it, then add your margin. A per-page backend keeps that first number small and predictable per client, unlike a per-seat tool.

## How much should I charge a client for social media management?

Build the number from what the page actually costs you to run, not from a number somebody else quotes you: start with the backend tool cost for that page, add the hours you spend deciding, writing and checking it, then add your margin. That total is the floor; anything you charge under it is working for free.

We are not going to hand you a flat industry figure here. Every client's page is a different size, a different posting cadence and a different amount of hand-holding, and a borrowed number tells you nothing about the client in front of you.

## What does the backend side of that number actually look like?

The part you can make predictable is the tool cost: Content OS prices by the page in tiers from a single page up to sixty, the per-page rate falling at every tier, with 60% off on annual payment; see the [current plans](/). Because it bills by the page rather than by a seat, adding a client adds one line to your own cost, not a seat upgrade that changes your margin on every client you already have.

That matters most once you are past a handful of clients: a [per-seat pricing comparison](/compare/hootsuite-alternative) against a tool like Hootsuite shows why a per-seat bill stops tracking your actual page count the moment you add your sixth or tenth client, while a per-page bill keeps moving with you one line at a time.

## What is the minimum defensible price per client?

The backend cost for that page, plus your hourly rate times the hours the page still takes you even with posting handled: deciding what to say, checking the result against the client's brand, and being ready to explain why a post ran if they ask. Anything below that number is a page you are running at a loss.

Posting itself stops being the hour sink once it runs on a schedule, so the hours left to price are mostly the deciding and the checking, which is also [is automation worth paying for](/tools/is-automation-worth-it) in more detail if you want the full test rather than the shorthand here.

## Why is this harder to predict on a per-seat tool?

Because a seat covers a block of accounts rather than one client, your cost per client moves every time your client count crosses a seat boundary, up or down, so pricing a new client off last month's seat math can be wrong the moment you add the next one. A per-page cost does not move when your client count does, which is why this question is easier to answer once the backend is priced per page.

## Should the price change once the client wants its own look kept exactly right?

Yes, charge more for that, because it costs you more time, not because the posting itself got harder. A client who wants every post checked against their own brand voice and their own photos is asking for the checking step to be thorough, and thorough checking is hours, which belongs in the price the same way any other hour does.

## What if I am pricing thirty or fifty client pages, not one?

Run the same formula per page and let it scale on its own: backend cost per page plus your hours per page plus your margin, multiplied by the page count. Because the backend side stays per page rather than jumping in seat-sized blocks, the formula does not break as your client list grows, which is the condition that matters most once you are the one holding thirty or fifty client relationships rather than one.

Which parts of the job a machine can honestly take before you price the rest is in [can an AI social media manager run my page](/tools/ai-social-media-manager).

The tools themselves are compared in the [tools section](/tools), and the short versions are in the [FAQ](/faq).

If the backend cost in this formula is the part you want to lock in before you quote the next client, [here is how Content OS works](/how-it-works). Join the waitlist from the [home page](/).

## Where this stands

There is no white label client report built yet, so showing a client why a post ran still means walking them through the run log yourself.