A monthly retainer that promises “12 posts” leaves the hardest questions unanswered: Who finds the ideas? Who records and edits video? How many approval rounds are included? Who answers messages? What happens when a client delays feedback? A useful scope names the work, the handoffs, and the limits. It can set a reliable service level; it cannot guarantee organic reach, leads, or sales.
LinkedIn says its feed systems are being updated to understand post topics and member interests, while reducing repetitive low-substance content and engagement bait. That is a useful reminder for service design: count the assets the team can deliver, but do not sell a fixed outcome as if post volume controls distribution. LinkedIn: How the Feed is improving
Replace the post count with a service map
Separate the work into stages. A client can then see what the fee covers and what requires another owner, budget, or approval.
| Workstream | Define in the scope | Common boundary to make explicit |
|---|---|---|
| Direction | Business goal, audience, channels, themes, cadence, and review date | Strategy is based on the information and access the client supplies |
| Research | Customer questions, approved source material, competitor observations, and idea backlog | Research does not include original field interviews unless listed |
| Production | Asset types, quantity, length, formats, copy, design, filming, editing, captions, and accessibility | State whether the client supplies footage, products, releases, and brand files |
| Publishing | Channels, calendar, scheduling, metadata, links, and final checks | Posting depends on account access and timely approval |
| Community | Monitored channels, coverage windows, response categories, escalation contact, and service hours | Define what is triaged versus answered; exclude crisis response unless contracted |
| Measurement | Metrics, source, reporting interval, and decision meeting | Separate platform activity from attributed inquiries and verified revenue |
A deliverable should have a unit and a completion condition. “Four videos” is incomplete unless the scope says whether that means four scripts, four edited videos from supplied footage, or four shoots with editing. “Community management” needs channels, hours, response-time target, and escalation rules. A fixed unit prevents both sides from silently imagining different workloads.
Estimate the fee from the workflow
Build an effort estimate before attaching a price. Include discovery, research, planning, writing, design, recording or editing, internal review, client approvals, publishing, moderation, reporting, and account management. Then state assumptions about meeting time, turnaround, number of revisions, and client-supplied materials.
A practical fee model is:
monthly fee = planned delivery effort + service overhead + agreed contingency
Translate the estimate into a capacity check: estimated monthly hours × internal delivery cost per hour, plus any agreed margin or pass-through production costs. This is an internal pricing method, not a universal market rate. Do not label it a benchmark for Egypt, Saudi Arabia, or the wider MENA region without current comparable evidence. If production demands, approval latency, or coverage hours rise, revisit the scope and fee together.
Keep media spend, creator fees, travel, studio rental, licensing, and paid tools separate unless the agreement clearly includes them. Name who approves each cost and whether it is billed directly or passed through. A low headline retainer can become misleading if essential production costs appear later.
Separate controllable service levels from outcomes
The agency can commit to a calendar, agreed asset count, accessibility checks, response coverage, and a reporting date. It cannot control platform distribution, audience demand, inventory, offer quality, sales follow-up, or the client's response speed. Describe outcomes as goals to measure, not results owed by the content team.
Choose measures that match the job. For awareness, report relevant reach and video consumption with the platform and time window named. For conversation, categorize meaningful replies and qualified questions rather than counting every reaction equally. For a lead path, use tagged links or a documented handoff and verify the inquiry in the destination system. A view, save, profile visit, or direct message is not automatically a sale.
When comparing formats, topics, or cadence, record what changed and avoid treating one month's movement as causal proof. LinkedIn says its feed is becoming more topic- and interest-aware and that it is reducing repetitive and engagement-bait content; a package centered on manufacturing volume or empty comment prompts can therefore work against the platform's stated direction. This does not reveal the full ranking system or predict an individual post's reach.
A sample scope that can be priced
Use this as a planning example, not a standard offer: one brand, two agreed channels, one monthly planning session, a four-week calendar, eight core feed assets adapted to each channel, two short-video edits from client-supplied footage, copy and captions, scheduled publishing, weekday community triage for a named daily window, and one monthly measurement review. The statement of work would also define whether adaptation counts as a new asset, the included revision rounds, approval deadline, response-time target, excluded crisis work, and the client's owner for leads.
Before quoting, ask for the client goal, audience, active channels, current approval path, asset library, required languages, response hours, and any compliance review. If the answers are unknown, price discovery as its own phase or write a provisional scope with a change-control trigger. Do not promise to “fix engagement” when the underlying cause has not been diagnosed.
Keep changes visible during the month
Use a simple change log. Record the request, why it falls outside the agreed unit, the added effort, the schedule effect, and who approved it. Typical change triggers include an extra channel, a new language, on-site filming, weekend monitoring, more revision rounds, a campaign landing page, or a rush deadline. A scope adjustment is easier to discuss before work starts than after the team has absorbed it.
At month-end, compare planned and delivered work, note client-side delays, review the outcome measures, and decide what to continue, stop, or test next. Renew the retainer around the next operating need rather than automatically increasing the number of posts.
Short-video script: explain what a social retainer buys
Opening: “If a social retainer says only ‘12 posts a month,’ you still do not know what you are buying.”
Show: A scope sheet with six rows: direction, research, production, publishing, community, measurement.
Voice: “Define the asset type, who supplies footage, how many revisions are included, when approvals are due, which hours are monitored, and how inquiries are verified. Then price the real workflow.”
Close: “Commit to the service your team controls. Measure outcomes without guaranteeing what the platforms and the client also control.”
Educational carousel: turn a vague retainer into a clear scope
- Cover: “12 posts” is a count, not a service definition.
- Direction: Name the goal, audience, channel, and monthly decision.
- Production: Specify scripts, designs, filming, editing, captions, and supplied assets.
- Publishing: State channels, calendar, approval owner, and deadline.
- Community: Name coverage hours, response categories, escalation, and exclusions.
- Measurement: Separate reach and engagement from verified inquiries and sales.
- Price the work: Include research, revisions, meetings, reporting, and production costs.
- Protect both sides: Document change triggers and the approval path before extra work begins.
Field experiment thread: test whether the scope is understandable
A proposed service-design test; no client result is assumed.
1/ Take one anonymized draft retainer and ask a colleague unfamiliar with it to explain what happens in a normal month.
2/ Ask them to identify the asset count, who supplies footage, included revisions, approval deadlines, moderation hours, and how a lead is verified.
3/ Record each item they cannot answer from the document. Do not coach them while they read.
4/ Rewrite only the ambiguous scope language, then run the same comprehension check with a different reviewer.
5/ Compare the number of unanswered questions and the time needed to explain the scope. Keep the versions and reviewer notes.
6/ This small review checks clarity; it does not prove client satisfaction, profitability, or better campaign performance.
Tool-neutral prompt pack: draft a retainer scope from real inputs
Help me draft a social media retainer scope using only the facts below. Do not invent market prices, performance benchmarks, client results, or platform guarantees. Business goal: [goal]. Audience and markets: [audience/markets]. Channels: [channels]. Deliverables and units: [asset type, quantity, length, language]. Client-supplied inputs: [footage, product access, brand files, approvals]. Agency work: [research, strategy, copy, design, editing, publishing]. Community coverage: [channels, days, hours, response categories, escalation]. Measurement source and interval: [metrics/system/window]. Included revisions and meeting time: [limits]. Exclusions and pass-through costs: [items]. Approval deadline and owner: [details]. Change triggers: [examples]. Produce (1) a deliverables table, (2) assumptions, (3) exclusions, (4) dependencies, (5) a change-control clause in plain language, and (6) a list of unresolved questions. Mark every missing input instead of filling it with a guess.
Stop-doing swipe file: replace vague promises
- Stop: “We guarantee more engagement.” Use: “We will deliver [defined work] and report [named engagement measures] for [window]. Distribution and response vary.”
- Stop: “Community management included.” Use: “We monitor [channels] on [days/hours], triage [categories], and escalate [cases] to [client owner].”
- Stop: “Twelve videos per month.” Use: “We deliver [number] edited videos of [length] from [who supplies footage], including [captions/revisions].”
- Stop: “Unlimited revisions.” Use: “The fee includes [number] consolidated revision rounds before approval; new direction follows change control.”
- Stop: “We generate leads from social.” Use: “We track [observable path] and report inquiries verified in [system]; sales attribution depends on the agreed measurement setup.”
Hook–Value–Template: price a retainer around named work
Hook: “A post count cannot tell a client who researches, edits, replies, or reports.”
Value: “A useful retainer defines delivery units, client dependencies, service hours, measurement, and change triggers. That makes the workload easier to estimate without promising an outcome controlled by multiple parties.”
Template: “For [goal and audience], we deliver [units and formats] on [channels]. The client supplies [inputs] by [deadline]. We include [revision limit], monitor [channels/hours], escalate [cases] to [owner], and report [metrics/source/window]. The fee excludes [costs]. Requests beyond this scope use [change process]. We will measure [outcome indicators] and will not guarantee [external outcomes].”
Example: “For a bilingual retail brand, the monthly scope lists the Arabic and English assets separately, names who provides product footage, defines the approval owner, and records how a WhatsApp inquiry is matched to a campaign. It does not promise a fixed number of sales from organic posts.”
LinkedIn source and scope boundary
LinkedIn's March 2026 feed update describes more topic-aware and interest-aware recommendations and an effort to reduce repetitive low-substance posts and engagement bait. Treat this as the platform's stated direction, not a complete ranking formula or a forecast. The scope decision remains operational: agree what the team will make, publish, monitor, and measure. LinkedIn: How the Feed is improving