How to Scope a Social Media Retainer

Use the management pricing calculator after you have named the work units. This guide follows a fictional two-channel retail brief to show how small scope choices change hours. Its amounts are invented cost-planning inputs, not market rates or a ready-made offer.

Describe a finished deliverable rather than a broad service

Start with the question a delivery team needs answered: what counts as finished? Content management is too broad to estimate on its own. A prepared asset might include a design, caption, internal check, and one approved output file. Publishing support might cover placing approved items into an agreed schedule and checking them afterward. Neither label automatically includes photography, customer support, or responding to a last-minute campaign idea. Name those responsibilities before discussing volume.

A work unit should be easy to count and reasonably consistent. Use an original asset when production effort is similar across the set. Use a monthly block when work is time-based and spread across the month. Use a meeting when there is a recognizable preparation, attendance, and follow-up task. You do not need a row for every tiny action. You need units that can be estimated honestly and checked after delivery.

Separate a delivery commitment from an outcome the team cannot control. Preparing an approved campaign is work you can describe. Producing a fixed number of sales is a different promise and does not follow from hours or a fee. Reach, audience growth, and commercial results can be discussed as goals without becoming assumed outputs of the retainer. This keeps the scope useful even when a campaign performs differently from expectations.

Write the short service description before entering numbers. For a retail client, that might be a monthly set of product assets, adapted for two named channels, with scheduled publishing support and a bounded community block. Read the sentence aloud. If it leaves you asking who supplies the product images or who approves an offer, the scope is not ready. A calculator can price an assumption, but it cannot resolve an unstated responsibility.

Make client inputs and handoffs part of the plan

List what must arrive before production can begin. That may include approved product details, usable images, campaign dates, brand guidance, account access, and the name of the reviewer. An estimate based on complete inputs should say so. Otherwise, the agency may quietly become responsible for finding missing information. That work consumes time even if it never appears in the published content, and it should not be treated as an invisible gift.

Be specific about supplied material. A folder of unselected footage can require much more work than a small set of approved clips. A product spreadsheet with missing descriptions is different from approved copy. If your package includes selecting, cleaning, or checking those inputs, include the effort in a task estimate. If it does not, state the expected condition of the handoff. Both sides need the same picture of the starting line.

Agree on one practical route for collecting feedback. Scattered comments across email, chat, and several files are difficult to reconcile. Ask who will combine internal client feedback before it reaches the delivery team. This is a workflow choice, not a calculator setting. You can estimate coordination time, but adding a fee does not automatically create a reliable review process. The scope should explain who returns the final set of requested changes.

Describe how a late input affects the proposed schedule without inventing an automatic rule. You might plan to agree a revised delivery date when required material is late. The calculator does not move deadlines, contact reviewers, or manage access permissions. Use a separate operational record for those details. The content calendar generator can support scheduling after the responsibilities are clear, but a calendar cannot supply missing product decisions.

Count source production once and adaptations separately

A multi-channel retainer often starts with one core idea or source asset. The first production effort might include selecting a product angle, arranging supplied imagery, and preparing approved copy. Another channel may then need a different opening, layout, or crop. These are related tasks, not identical tasks. Count the original work once and estimate the additional adaptation effort separately. That approach makes reuse visible without pretending that every placement is a new production.

For the retail brief, define six source assets and six adaptations for a second channel. This is twelve prepared placements, not twelve independent source productions. The distinction helps the client understand what changes when they add a channel. Some work may be reusable, while review, formatting, and final checks remain. A price based only on the number of channels can miss both the genuine efficiencies and the real extra effort.

Define what an adaptation excludes. Replacing a caption opening may be a small change. Turning a static product asset into an original video may require a new script, footage, and editing process. Do not hide that change inside a label that suggests a minor variation. If a request needs a different production method, consider a different work unit. The aim is a repeatable description, not an argument about whether something technically counts as content.

Platform context can help identify the right questions, but it does not set the fee. Compare the Instagram management guide with the LinkedIn management guide when the same source material serves different audiences. In the calculator, the platform selector changes context only. Your task rows must still reflect the actual work, and switching that selector does not silently add research, rewriting, or review time.

Define revision rounds and distinguish a changed brief

A revision round needs a shared meaning. One workable definition is a consolidated set of comments on the submitted batch, followed by an update to that batch. That is different from an open channel for unlimited individual requests. Explain what the team is reviewing and when the round ends. A simple definition makes it easier to estimate effort and helps a client gather decisions before returning feedback to the person doing the work.

Separate correcting a delivery error from requesting a new direction. A wrong product name needs different handling from replacing the campaign concept after approval. You can explain that distinction in everyday language without treating every client comment as a dispute. Ask whether the request stays within the original deliverable and supplied brief. If the answer is unclear, pause the affected task and agree what will change before more production time is spent.

The calculator allows a revision-round count, but that field describes scope only. It does not increase hours, add a task, or raise the fee. Put the expected review effort into the relevant task estimates or a clearly named review block. Increasing rounds without changing those estimates can leave the same price attached to a larger promise. Test that change deliberately instead of assuming the software has priced it in the background.

Keep review timing and creative volume separate. Two rounds of feedback do not guarantee that an item can be approved tomorrow. A client may need several people to review it, and the team may already have other work scheduled. Discuss turnaround expectations outside the arithmetic. A useful scope states the review process and dependencies. It does not imply instant availability, unlimited priority access, or a guaranteed response from every client stakeholder.

Bound community support, meetings, and reporting work

Community support is easy to underestimate because the work arrives in small pieces. Define the covered channels, the type of interaction, and the time block. A monthly allocation for routine review is not the same as continuous monitoring. State what happens when a message needs a business decision, specialist answer, or sensitive escalation. The person managing social content should know where their responsibility ends and who receives the next question.

For the retail example, the community task is one four-hour monthly block for routine triage and a handoff list. It is not a promise to resolve every customer problem or cover every hour of the week. If the client wants wider availability, estimate the required staffing and coordination separately. A reserve for uncertain costs does not turn a bounded support block into unlimited coverage, and the calculator does not schedule a support roster.

Meetings need boundaries too. Name their purpose, expected length, and any preparation or follow-up included in the estimate. A monthly planning call differs from joining every internal campaign meeting. Reporting can include organizing results, writing observations, and discussing next steps, but it should identify the measures and accounts involved. Use the social media report builder for a structured reporting document rather than implying that a price worksheet measures performance.

Write exclusions as useful choices, not as a wall of warnings. A client should be able to see that paid campaign production, filming days, weekend support, or a new channel would need a separate discussion if they are outside the package. Choose exclusions that match the actual brief. A long generic list can still miss the one responsibility most likely to create extra work. Specific boundaries support a clearer working relationship.

Work through a two-channel scope with its own numbers

Here is the fictional retail estimate in USD. Six source assets at 1.50 hours each and an internal hourly cost of 28 produce 252 in labor cost. Six adaptations at 0.50 hours and the same cost produce 84. A two-hour monthly publishing block costs 56. The quantities represent the defined work units, not an automatic claim about how many posts any agency should include in a management package.

Add the four-hour community block at 24 per hour for 96. A planning task of 1.50 hours at 36 costs 54, and a reporting task with the same time and cost adds another 54. The six rows total 596 in labor and twenty-one planned hours. Each block has a specific purpose. That makes it possible to discuss reducing one responsibility without pretending the entire service can shrink proportionately.

Monthly direct costs of 44 and allocated overhead of 60 bring the base to 700. An eight percent reserve adds 56, making covered cost 756. At a twenty-five percent target margin, the service fee is 1,008. Add an at-cost pass-through budget of 80 for a monthly quote total of 1,088. These are consequences of this brief and its internal inputs, not evidence that a comparable retail client should pay that amount.

Onboarding is three hours at 36 plus a direct expense of 12. The base is 120; the same reserve and margin produce a separate one-off fee of 172.80. The first-month model is 1,260.80. Keep this setup work distinct from the recurring scope. In this example it establishes the handoff and review process. It is not a payment request, an invoice, or an assumption that setup repeats in every later month.

Negotiate the workload using three editable scenarios

Use the three independently editable packages to compare real choices. In the first scenario, keep the retail scope just described. In a leaner scenario, reduce the community block from four hours to two and keep all other assumptions unchanged. Labor falls by 48 and planned hours fall to nineteen. The monthly base becomes 652, covered cost becomes 704.16, and the service fee becomes 938.88 at the same reserve and margin.

That leaner package has a monthly quote total of 1,018.88 after the unchanged pass-through budget. Explain what the smaller support block means before presenting the lower number. The client is not receiving the original promise at a hidden discount. They are choosing a smaller allocation of work. If their need still requires four hours, this alternative is not a suitable fit merely because the total is easier to approve.

For the expanded scenario, increase the original six source assets and six adaptations to eight of each. With the other rows unchanged, planned hours become twenty-five. Labor increases by 112, the base becomes 812, and covered cost becomes 876.96. The resulting service fee is 1,169.28, with a monthly quote total of 1,249.28. Enter these changes separately; packages do not inherit edits or update one another automatically.

If available monthly capacity is twenty-four hours, the expanded scenario exceeds it by one hour before you consider the wider schedule. The calculator compares entered task hours with your entered capacity; it does not add onboarding to that recurring comparison or book staff. Review launch demands separately. Zero capacity means not provided. For the arithmetic behind changing targets rather than scope, read the margin and onboarding cost guide.

Export the agreed scope and keep the cost model private

Select the intended package before copying or exporting. Copy quote and PDF include the active package only, not a three-option comparison sheet. Client quote is the default audience view. It shows deliverables and units, fees, pass-through budget, onboarding, the first-month model, revision scope, and your notes. It omits loaded hourly rates, labor cost, reserve, margin, overhead, and modeled surplus. Those figures belong to your private planning discussion.

Read task labels and notes as if the client already has them. Do not type internal wage details or margin reasoning into those fields. The scope note holds up to 600 characters, so use it for the most important inclusions, exclusions, and dependencies. Keep longer operating arrangements elsewhere. The exported quote is a planning communication, not a replacement for separately prepared agreements, terms, invoices, or any professional advice you may need.

Internal worksheet and the explicit internal CSV cost worksheet are for cost review of the active package. The JSON project contains all three editable scenarios and should stay private. Save it deliberately because the browser-only planner has no autosave or server upload. Before sharing any document, check its audience and contents. A useful final check is whether someone could understand the offer without learning how your team pays for delivering it.

Revisit the scope after delivery and adjust the assumptions that proved wrong. Return to the retainer calculator when that review changes the work. SMTasker can support eligible execution workflows, but it does not replace human strategy, filming, approvals, or business decisions. There is no automatic connection between this planner and Skye or account data. Explore SMTasker setup only after deciding which supported tasks belong in the service.

Questions about Retainer Scope

Continue with another service pricing guide

Build your own package in the Management Pricing Calculator, or explore another scope below. Find more practical planning tools in the free tools directory.