Key takeaways
- State platforms, posting cadence, and what counts as a deliverable explicitly.
- Define the approval process and how many revision rounds are included.
- Specify what reporting the client receives and how often.
- Vague scope is the most common cause of later disputes — be specific upfront.
What to include
- Platforms covered and posting cadence per platform
- What counts as one deliverable (a single post? a post with a set number of revisions?)
- The approval process: who approves, how many rounds, and turnaround time
- What reporting is included, and how often it’s delivered
- What is explicitly out of scope, to prevent later disagreement
Why vague scope causes problems
A proposal that says "social media management" without specifics leaves room for a client to expect more than what was priced. Being specific about cadence and deliverables protects both sides.
Setting expectations on reporting
Decide upfront whether reports are automated (delivered on a schedule) or manually prepared, and make sure that’s reflected in what you price and promise.
proposalagency operationsclient management
FAQ
- What should a social media proposal always include?
- Platforms and cadence, what counts as a deliverable, the approval process with revision limits, and what reporting is included.
- How many revision rounds should be included?
- There’s no universal number, but it should be stated explicitly in the proposal — an unlimited-revisions promise is a common source of scope creep.
- Should reporting be automated or manual?
- Either works, but decide upfront and reflect it in the proposal — automated, scheduled reports scale better as you take on more clients.