Draw the Approval Map Before You Talk to a Single Agency

You hire a social media agency, everyone agrees on scope and price, and then week three brings a name nobody mentioned during the pitch. Legal wants to review claims language. A regional lead wants sign off on anything touching their market. The calendar that looked realistic in the proposal is not realistic anymore, and the agency is the one who looks slow.

The slow first quarter has a cause, and it is usually not the agency

The brand assumes one person signs off on content, and because that person ran point during the pitch, the agency assumes the same thing. Everyone prices and schedules around a single approver. Then, three or four weeks in, someone else surfaces with real veto power: a legal reviewer who has to clear claims language, a creative director who was never in the discovery calls, or a regional lead whose market the calendar quietly assumed did not need separate approval. None of these people did anything wrong by showing up. They were always part of the chain. Nobody wrote it down before the agency was chosen.

This is a sequencing problem, not a competence problem. The map of who can say no should exist before a single agency is contacted, not after the calendar has already missed its first deadlines.

What agencies actually do differently when they know the approval structure upfront

An account manager’s job changes shape with how many people can stop a post. With one approver, the job is mostly coordination: draft, send, get a note or a yes, publish. With three separate sign offs, sometimes conflicting, the job becomes sequencing and buffering. Agencies that price this correctly build in more revision rounds, more calendar buffer, and sometimes a named senior staffer whose job is managing stakeholder friction. That is simply what it costs to move content through more than one gate.

An agency that does not know the real structure prices as though one person approves. The mismatch surfaces later as scope creep, or as a client concluding the agency is slow. Both conclusions are wrong: the agency priced accurately against the information it had, and that information was incomplete. This is reasoning about how staffing responds to review complexity, not a guaranteed formula or a quotable number.

Draw the map before you write the RFP

• List everyone with power to stop a post, not just the people who attend agency calls: the marketing lead, a legal or compliance reviewer, whoever holds brand or creative sign off, any regional or country lead, a founder or executive who reviews client facing work, and any committee that meets on a fixed schedule rather than on demand.
• For each name, note not just whether they approve but how often they meet and how long they take. A committee that convenes every two weeks changes what is achievable in a posting calendar as much as a slow individual reviewer does.
• Write it down as a simple list: name, role, what they can veto, typical turnaround. It does not need to be formal. It needs to exist, in writing, before a single finalist is contacted.

What the good version of this disclosure looks like, and what the bad version looks like

Good version: the brand tells every finalist, in the RFP or the discovery call, who signs off and how long each layer takes. Every agency prices and staffs against the same real picture, so the proposals become comparable, not just comparable pitches.

Bad version: during the pitch, someone says “it’s just me” because that is who is in the room that day. Weeks after the retainer starts, a legal reviewer or regional director appears with authority nobody mentioned, and the agency absorbs a cost it never priced for.

The bad version is rarely dishonest on purpose. More often the brand had not mapped its own structure before the RFP went out, so there was nothing accurate to disclose. That gap is what this exercise closes.

Where this belongs in the hiring timeline

The map needs to exist before any finalist is contacted, so it goes into the RFP as a fixed input every agency prices against, not a surprise raised once staffing decisions are made.

This is distinct from how a client’s daily habits shape revisions once an agency is already working, covered separately in how your approval process shapes the work once an agency is already running. That is the rhythm for reviewing content after the relationship exists. The map is earlier: who has veto power at all, before there is any content to review.

A hypothetical walk-through

Picture a hypothetical brand, not a real client, with three layers: a marketing lead who owns day to day decisions, a legal reviewer who clears claims language, and a regional director over two international markets.

Disclosed at the RFP stage, each finalist proposes a realistic review buffer and names a legal contact from day one, with the regional director’s calendar built into the schedule from the start. Discovered in week four instead, the agency loses roughly its first month figuring out who signs off on what.

Ready to find the right agency for your approval structure?

Once you know who signs off and how long each layer takes, you can ask finalists to price and staff against that reality. Browse vetted agencies to shortlist candidates who fit the structure you have mapped, or if you run a social media agency, list your agency free.

FAQ

Should I include the approval map in the RFP itself, or save it for the discovery call?

Put it in the RFP. Finalists price and staff differently depending on approval layers, and they need that information at the proposal stage to submit something genuinely comparable.

What if my company’s approval process is genuinely simple, just one person?

That is fine, and still worth stating explicitly. A single, clear sign off is useful information an agency can price against. This exercise is about accuracy, not assuming complexity that is not there.

Does disclosing a complicated approval structure make my company a less attractive client?

Agencies price complexity either way. Disclosing it upfront gets it priced in and staffed for. Hiding it gets it discovered mid engagement and blamed on the agency being slow, when the actual cause was a structure nobody described.

How is this different from an approval workflow once the agency is already working?

This exercise happens before any agency is chosen and answers who has veto power at all. A workflow is the rhythm for reviewing specific posts once there is already work to review, a related but separate problem solved at a later stage.