How to choose a digital marketing agency without getting burned
Most agency relationships fail for reasons that were visible in the pitch. Here is what to look for, what to ask and what should end the conversation.
By Digiloom editorial team · Published · Updated
Start with the problem, not the service
Before you speak to anyone, write down what you would need to be true in twelve months for the spend to have been worth it. Not 'more traffic' — a number, attached to revenue or pipeline, with a rough timeline.
Agencies will happily sell you the service they are best at. If you arrive without a defined problem, you will be sold whatever is currently easiest for them to staff.
Ask who actually does the work
The single most common failure mode is a pitch delivered by senior people and delivery handled by whoever joined last month. Ask directly: who will be on this account, what else are they working on, and can I meet them before signing?
A good answer names people and describes their workload honestly. A bad answer talks about 'our team' without specifics.
Interrogate the case studies
Ask what the starting position was, what else changed during the period, and what would have happened without the work. Any agency that has thought carefully about a result can answer that. Most cannot, because the result was largely seasonal or coincided with a product launch.
Also ask for a client where things went badly and what they did about it. The answer tells you more than five success stories.
Red flags worth ending a conversation over
Guaranteed rankings or guaranteed lead volumes. Nobody controls the search results or the market.
Refusing to let you own your ad accounts, analytics properties or website code.
Reporting built on impressions, reach and 'engagement' with no line to revenue.
Contracts longer than twelve months with no exit clause, or a notice period longer than 60 days.
Link building sold by the unit at a fixed price per link.
Compare proposals on scope, not price
Two proposals at very different prices usually differ in scope, seniority and implementation. One includes the developer time to ship the fixes; the other hands you a document. Build a simple comparison table of deliverables before you look at the numbers.
The cheapest proposal is often the most expensive one, because you pay for it twice.
What a fair contract looks like
A three-month initial term is reasonable for setup-heavy work; after that, monthly or quarterly rolling with 30 to 60 days' notice. You own all accounts, data, code and content. Deliverables are listed specifically enough to argue about. There is a named escalation path.
If an agency resists all of that, the contract is protecting them from something.