An agency profile document is a short, structured file — usually 8 to 20 pages — that answers four questions a prospective client has before they'll take a meeting seriously: who you are, what you do, proof that you've done it, and who they'd actually be working with. Most agencies build it once as a master document, then cut and re-order it for each pitch.
Here's how that process actually works, section by section.
Start with the master document, not the pitch
The mistake is writing a profile from scratch for every opportunity. The efficient version is a master deck or PDF containing every credential, case study, team bio and capability you have — far more than any one client would read. For each pitch you pull from it, re-order, and delete.
That's why agencies with a tidy master document can turn a tailored profile around in an afternoon, while agencies without one spend three days hunting for a logo file and arguing about which case study won the award.
The master document should hold:
- Positioning statement and what the agency refuses to do
- Full service list, with the depth of each one honestly described
- Every case study, written to a consistent template
- Team bios at two lengths — one line and one paragraph
- Client logos, with permission status noted
- Process and ways-of-working diagrams
- Commercial models (retainer, project, performance) described without figures
The opening page does one job
The first page is not an introduction to your agency. It's a statement of what the client gets. A good opening says something specific enough that a competitor couldn't paste their own logo onto it.
"A full-service agency delivering integrated solutions across channels" fails that test. "We take mid-market B2B brands from a messy founder-led website to a demand engine that the sales team actually trusts" passes it. Specificity is uncomfortable because it rules people out. That's the point — the profile is a filter, not a net.
If the pitch is for a defined brief, the opening page should mirror the brief's language back. The client wrote that brief; seeing their own framing on page one signals you read it.
Case studies carry the document
Everything else is claim. Case studies are evidence, and they're the part prospects skip to. A consistent template makes them scannable:
| Element | What to include |
|---|---|
| Client and sector | Enough to show relevance, respecting any NDA |
| The problem | In the client's words, not agency jargon |
| What you did | Specific tactics, not "we developed a strategy" |
| The result | Numbers you can defend if challenged |
| Timeframe | How long before the result appeared |
Two rules on results. Only use figures you could produce evidence for in a follow-up meeting — a prospect who asks and gets vagueness will assume the rest of the document is inflated too. And choose case studies by relevance to the prospect, not by prestige. A mid-size manufacturer would rather see another mid-size manufacturer than a famous consumer brand with a budget they'll never have.
Show the actual team
Clients buy people. The profile should name who would work on the account and what they'd do, not display a wall of headshots from the whole company.
The credibility problem here is the pitch-and-switch — senior names present, juniors deliver. Smart agencies pre-empt it by stating plainly who runs the account day to day, who the client sees weekly, and who they'd escalate to. If a named senior person is genuinely only on the account for the first eight weeks, say so in the document. It costs you nothing and buys enormous trust.
Process, pricing and the questions clients actually ask
A process section should answer: what happens in week one, how often we meet, how work gets approved, and what reporting looks like. Diagrams help, but only if they describe something real.
On money, a profile document is usually the wrong place for a detailed quote — that belongs in the proposal that follows. What the profile should do is explain the commercial models you work in and what drives cost up or down: scope breadth, speed, seniority of the team involved, volume of deliverables, and whether media or production spend sits inside or outside the fee. If a prospect asks for a figure at profile stage, the honest answer is a range tied to a defined scope, with the variables named.
Clients also commonly want to know about contract length and notice periods, data and IP ownership, who owns the accounts and assets you create, and how you handle conflicts with competing clients. A short FAQ page covering these removes friction that otherwise surfaces in procurement weeks later.
Format, length and the practical details
Send a PDF unless asked otherwise. It renders the same everywhere, can't be half-edited, and survives being forwarded to the finance director. Keep file size manageable so it doesn't bounce off an email filter.
On length: aim for something a busy person can skim in four minutes and read properly in fifteen. If the brief caps the page count, respect the cap — ignoring it is the first evidence of how you'll handle other constraints.
A few details that quietly matter:
- Name the file with the client's name in it, not "Agency Profile FINAL v7"
- Put a contact route on the last page and on the cover
- Date it, so an old version resurfacing doesn't embarrass you
- Check that every logo you're displaying is one you're allowed to display
Keep it current, or it stops working
Profile documents rot. Case studies age, people leave, services change. The agencies that pitch well review the master document on a schedule — quarterly is common — rather than discovering at 11pm that the lead case study features a client who churned last year.
A profile document is a sales asset with a maintenance cost. Treat it that way and each new pitch becomes an assembly job instead of a crisis.