Lesson 8 of 87 min read
Packaging and pricing your service
Turn your client system into clear service tiers defined by scope, hours and deliverables, so pricing becomes a calculation instead of a guess.
In this lesson you will
- Measure the real hours each client task takes
- Define two or three tiers by scope and deliverables, with what is excluded
- See where automation frees hours without lowering quality
Most freelancers and small agencies price social media work by feel. A number that sounded right for the first client gets reused, adjusted up a little for the bigger one, down a little for the friend of a friend. Then scope creeps: "could you also reply to our reviews", "just one more network", "a quick report for the board". A year later the busiest client is the least profitable one, and nobody can say exactly why.
This lesson does not tell you what to charge. That depends on your market, your experience and your costs, and any figure we typed here would be wrong for most readers. Instead, it gives you the inputs that make pricing a calculation: the hours each task really takes, tiers defined by scope, a written list of what is not included, and a clear view of where automation saves time. With those in hand, the number is yours to set.
Measure before you package
You cannot package what you have not measured. For two months, log time per client per task. Not to the minute; to the quarter hour is enough. Use the same task list as the rest of this course, so the numbers map straight onto your tiers:
Onboarding (one-off) lesson 1
Planning lesson 3
Drafting and adaptation lessons 3 and 5
Assets and scheduling lesson 3
Approval rounds lesson 4
Community management lesson 6
Reporting lesson 7
Client communication calls, emails, ad-hoc requests
Keep the log honest. Count the time spent reading a client's long email, the five minutes finding a missing logo, the call that ran over. If logging feels like overhead, log only the start and end of each client block and the task you were on; that is accurate enough.
The last line is the one people forget. Ad-hoc requests and "quick questions" are often a large share of the real time, and they are invisible until you log them.
After two months, you will have three useful numbers per client: total hours per month, hours per post, and hours of community management per week. Compare clients. The differences are usually not the number of posts; they are approval rounds, client communication and inbox volume. Those are exactly what tiers should control.
Define tiers by scope, not by effort
A tier is a promise of deliverables, not a promise of hours. Clients understand "twelve posts a month across three networks, approved weekly, with a one-page report" much better than "about seven hours of social media". Hours stay your internal number; scope is what you sell.
Two or three tiers are enough. A typical structure:
| Essentials | Standard | Full service | |
|---|---|---|---|
| Networks | Up to 2 | Up to 4 | Agreed per client |
| Posts per month | A fixed number | More, with per-network adaptation | Agreed per client |
| Planning | Monthly grid | Monthly grid plus a planning check-in | Monthly grid plus campaign planning |
| Approvals | One batch a month | One batch a week | One batch a week, with a second approver |
| Community management | Not included | Comments on own posts, business hours | Comments, messages, reviews, with escalation |
| Reporting | One-page report | One-page report | One-page report plus a quarterly review |
| Revision rounds per batch | One | One | Two |
Fill in the numbers from your own measurements. Then, for each tier, calculate the expected hours from your logs. If one tier needs far more hours than the others relative to what it offers, the scope is wrong, not the client.
Three rules that keep tiers honest:
- Every tier has the same quality bar. A smaller tier gets fewer deliverables, never sloppier ones. Every post still passes the pre-flight check and an approval step.
- Community management is scoped separately. It is the least predictable work. Define it by channels and hours of coverage, never as "unlimited replies".
- Revision rounds are counted. One or two rounds per batch is included; more becomes a change request.
Write down what is not included
The exclusions list protects you more than the inclusions. Put it in every proposal and contract:
Not included in any tier unless agreed in writing:
- Paid ads setup or management
- Photo or video shoots
- Crisis communication beyond the escalation path
- Networks not listed in the tier
- Replies outside agreed hours
- Extra revision rounds beyond the tier
- Reports or decks for other audiences (board, investors)
When a client asks for something on the list, the answer is not "no". It is "happy to; that is outside the current scope, so here is what it adds". A written list turns an awkward conversation into a routine one.
Review tiers twice a year
Tiers are not set once. Every six months, put your time logs next to each tier and look for three things:
- Clients outgrowing their tier. If a client on the smaller tier consistently needs extra revision rounds, more networks or inbox coverage, offer the next tier with the evidence from your logs. Framed as "here is what you have been asking for", it is a service conversation, not a sales pitch.
- A tier nobody buys. It is probably defined badly: too close to its neighbor, or missing the one deliverable that tier's clients care about. Merge it or redefine it.
- Tasks that take longer than the tier assumes. Usually approvals or community management. Either tighten the scope (fewer rounds, narrower hours) or change the tier's expected hours and the price you set for it.
When you change a tier, existing clients keep their current terms until their next renewal, with notice in writing. Changing scope mid-term is the fastest way to turn a good client into a difficult one.
Automation as margin
Once tiers are defined, look at your time logs again and ask which hours are repetitive. Those are the hours that automation can give back without lowering quality, and freed hours are where an agency's margin comes from.
Good candidates:
- Event-driven posts. A client who publishes new listings, new stock, release notes or portfolio work produces a steady stream of announcement posts with the same shape. Drafting each one by hand is pure repetition.
- First drafts from a source. Turning a client's blog post or newsletter into network posts.
- Report assembly. Pulling the same numbers in the same format every month.
- Spreadsheet imports. Loading an approved monthly plan in one step instead of post by post.
Two rules for automation in client work. First, automation produces drafts, never published posts: every automated post goes through the same approval step as the rest. Second, do not pass the saved hours straight back as a lower price by default. Use them for the things automation cannot do: better ideas, faster replies, a sharper insight in the report. That is what clients keep paying for.
Worked example: packaging our own brand as a client
If an agency packaged a service for a software company like us, here is how we would expect the scope to read, using the tier structure above. No prices; the agency sets those.
Tier: Standard. Networks: X, LinkedIn, Bluesky and Discord. A fixed number of posts per month across the four pillars from lesson 3. Weekly approval batch on Thursday. Comments on our own posts during business hours, with billing and account questions routed to us. One-page monthly report.
Automation in scope. Because we are a software company, our most repetitive posts are release announcements. The agency would set up the industry workflow template "New release → changelog posts" against our releases feed. When we publish a release, a changelog thread for X and posts for the other networks are drafted from its notes, and they wait for approval like everything else. The hours this saves go into the how-to pillar, which needs real thought.
Hours, roughly. The agency would log the first two months and then check the tier against them: planning, drafting, the weekly approval round, a daily inbox pass and the report. If the inbox pass turned out heavier than assumed, the scope note would say so at the next review, not quietly absorb it.
Excluded, in writing. Paid campaigns, video production, and anything about features that have not shipped.
The hypothetical second client. Say the same agency also runs a regional real-estate brokerage (a hypothetical). The equivalent automation there is "New listing → posts on every network", fed by the brokerage's listings feed. The tier structure is identical; only the event changes. That is the point of packaging: one system, many clients.
Recap
- Log time per task per client for two months before you set or change tiers.
- Sell scope and deliverables; keep hours as your internal number.
- Define two or three tiers with the same quality bar, scoped community management and counted revision rounds.
- Write the exclusions list into every proposal and treat extras as change requests.
- Automate repetitive drafting, keep every automated post behind approval, and reinvest the freed hours.
Exercise
Map your tiers to your hours
- Copy the task list above into a spreadsheet and log your time for one client for at least two weeks, to the quarter hour.
- Time yourself producing one complete post from idea to scheduled draft, using the free Instagram caption generator for a first pass and editing it into the client's voice. Record the minutes.
- Fill in the tier table with your own deliverables per tier, and calculate expected monthly hours per tier from your log.
- Write your exclusions list.
- Mark which logged tasks are repetitive enough to automate.
- Done looks like: a tier table with deliverables and expected hours per tier, an exclusions list, and a short list of tasks to automate. No price needed yet.
Go further
Industry workflow templates
In FoPost, open Workflows inside the client's brand and choose From Template to install one of the industry templates: "New listing → posts on every network", "New car in stock → posts on every network", "Latest work on Instagram → everywhere else" or "New release → changelog posts". A template is saved switched off, with approval on, aimed at the accounts you pick, so nothing publishes until you turn it on and approve each post. See the automations feature page.
Check yourself
1Why sell tiers by scope rather than by hours?Show answer
Clients understand deliverables much better than hours, and scope is what you can control; hours stay your internal measure of whether a tier works.
2Which part of the service should always be scoped separately, and why?Show answer
Community management, because it is the least predictable work. Define it by channels and coverage hours, never as unlimited replies.
3What are the two rules for automation in client work?Show answer
Automation only produces drafts that go through the same approval step, and freed hours are reinvested in better work rather than passed straight back as a lower price.
Keep reading, free
Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.