what "solutions" means in a proposal.
vague nouns are a pricing strategy. here is the translation table, line by line.
every abstract line item should convert into a number, a frequency and a named owner. if it cannot, it is not scope — it is a placeholder you will argue about in month three.
proposals get vague for two reasons, and only one of them is cynical. the honest reason is that scope genuinely depends on what an audit finds, so a good agency hedges before it has your data. the less honest reason is that abstraction protects margin — a line reading "content solutions" can be delivered at almost any volume. the fix is the same either way: convert every noun into a number before you sign.
this matters most in the months when the relationship is under strain. nobody rereads the proposal while things are going well. it gets opened when output feels light or a deadline slips, and at that point a document full of abstractions cannot settle anything — both sides simply restate their interpretation and the conversation becomes about goodwill instead of facts.
— 01the translation table.
most proposals in this market reuse the same dozen phrases. the table below is what each usually contains and what it should say instead. none of these are dishonest terms; they are simply incomplete, and the incompleteness always resolves in the supplier's favour once work starts.
the pattern to notice: every vague phrase omits either a quantity, a frequency or an owner. "ongoing optimisation" has no quantity. "monthly reporting" has no depth. "community management" has no response time. the missing element is exactly the thing you will want to hold someone to in month four.
there is one more thing missing from most proposals, and it is the most telling: what is not included. an exclusions list is unusual enough that clients often assume it signals a limited service. in practice it signals the opposite — a supplier who has thought carefully about scope and would rather tell you now than argue later.
| the phrase | what it usually means | what it should say |
|---|---|---|
| content solutions | an unspecified number of posts | 12 posts, 4 reels, 2 carousels / month |
| ongoing optimisation | someone looks at the account sometimes | weekly review, named owner, documented changes |
| social media management | scheduling | calendar, captions, publishing, replies within 4h |
| brand strategy | a moodboard | positioning, pillars, voice, templates — a written doc |
| monthly reporting | a platform screenshot | spend, qualified enquiries, cost per enquiry, next actions |
| seo | meta tags | technical fixes, page mapping, content plan, link work |
| community management | deleting spam | reply-time target, dm handling, escalation rules |
| creative production | canva templates | shoot days per month, crew, deliverable counts |
| account management | a weekly email | named contact, call cadence, approval workflow |
— 02the three questions that fix any line.
how many, per month? content, ads, pages, edits, reports — everything countable should be counted. an agency that resists counting is protecting flexibility it has not priced for you.
who does it, by name? not a role, a person — the people you meet in the pitch should be the people on the account in month four. the difference between a senior editor and a junior with the same job title is the entire quality question, and it is invisible in a proposal.
what does month one produce? deliverables, not adjectives. "foundations laid" is not a deliverable. "tracking verified, 12 pages rewritten, first shoot delivered" is.
ask those three about every line and a four-page proposal collapses into one page of real commitments. do it in the meeting rather than by email: the hesitation tells you as much as the answer, and you will hear immediately which lines were written to be delivered and which were written to be sold. that page is the document worth signing, and any agency that would rather not produce it has told you something useful.
— 03where flexibility is genuinely reasonable.
not everything should be fixed. an agency that commits to exact deliverables for twelve months has committed to ignoring what it learns in month two, which is worse for you. the honest structure is a fixed floor and a variable mix: a minimum monthly output that does not change, with the composition reviewed quarterly.
seo and paid are the clearest cases. nobody can promise which pages will need rewriting in month five, and nobody should promise a fixed number of campaigns. what they can promise is a cadence of work, a reporting standard and a decision rule for when something gets cut.
the test for whether flexibility is reasonable: is it flexibility about what to do, or flexibility about how much to do? the first is judgment you are paying for. the second is scope you have not agreed.
the same logic applies to timelines. "ongoing" is fine for work that genuinely never ends, like community management. it is not fine for a deliverable — a website, a playbook, a brand system — where the absence of a date is the absence of a commitment. put dates on everything that finishes.
— 04what to put in writing.
four things, and they fit on a page. the monthly floor — countable outputs that do not move. named people and their roles. the reporting standard, including which numbers appear and when it arrives. and the exit terms: notice period, who owns the accounts and assets, and what handover includes.
most disputes we hear about from clients switching agencies trace back to one of those four being absent rather than to bad work. our own digital marketing solutions are published as scope for exactly that reason — it is easier to argue about a number now than about an adjective later.
one closing suggestion: write your own one-page version of the proposal and send it back for confirmation. it takes twenty minutes, it surfaces every place where your understanding and theirs diverge, and the reply tells you a great deal about how the next twelve months will be handled.
more on this: reading a social media proposal.