"Research agency" is a label that stretches to cover a two-person qual boutique and a fifty-person mixed-method firm — organisations with almost nothing in common operationally. Build software for this market and you learn fast that the label predicts very little about the problems, the buying process, or the appetite for change.
Flip the perspective and the same is true. An agency leader wondering whether purpose-built resource planning is worth the money is really asking a narrower question: are we the sort of operation this kind of software is actually for?
Usefully, the answer looks the same from both sides of the table. The signals that suggest an agency is shopping for better tooling are precisely the signals that predict it will get value from that tooling. Here's the field guide.
First, who shouldn't buy this (yet)
Honesty up front: if your resourcing runs on a whiteboard, a Monday stand-up, and one person who simply knows who's on what — and that's working — inserting a system into the middle of it can genuinely make things worse. Small teams with little project overlap coordinate faster by talking than by clicking.
Similarly, if what actually hurts is generic delivery stuff — tasks slipping, files scattered, deadlines missed — rather than capacity and availability specifically, then an ordinary project management tool is probably the smarter first purchase. Software built around billable hours and researcher calendars solves a different problem.
Neither situation is permanent. These agencies usually aren't in the market yet — until the operating model shifts underneath them.
The tells that an agency is in the market
The agencies actively searching — or one bruising week away from it — tend to share a recognisable profile:
- Projects that pile up rather than queue up. Overlapping fieldwork, analysis and reporting windows, where collisions have stopped being freak events.
- A plan that has a salaried caretaker. When keeping the spreadsheet honest is a named chunk of someone's role, the business is already paying for a system — just a bad one.
- People with complicated hours. Part-timers, fractional directors, a regular freelancer bench, all with different availability rules that generic tools mangle.
- Sales and delivery reading different scripts. The pipeline conversation and the capacity conversation happen in different rooms, weeks apart, and the delivery team finds out about wins at contract signature.
- Board numbers that require excavation. Any utilisation question triggers exports, merges and manual reconciliation across several sources.
Tick three or more of those and somebody in the building has already muttered the sentence that starts every one of these projects: "there has to be something better than this sheet."
"It's rarely the biggest agencies that gain the most from purpose-built planning. It's the ones where invisible coordination work has quietly become a payroll line."
Follow the pain to the right people
Job titles vary wildly across agencies; the pain map doesn't. Three roles carry it:
- The ops or resourcing lead — owns the master plan, takes the blame when it's wrong.
- The MD or COO — needs utilisation and headroom figures they can defend, not a narrative stitched together at 11pm.
- The commercial lead — wants to promise start dates to clients without triggering a delivery fire drill.
For vendors, outreach that only reaches IT or a "transformation" owner will sail straight past the person who lives inside the spreadsheet. For agency leaders, your best internal sponsor is whoever can answer, without checking: "what breaks if we double-book a senior researcher next month?"
Does qual versus quant change the picture?
Less than you'd expect. The shape of the work differs — qual firms sweat moderator diaries and fieldwork windows, quant firms sweat scripting peaks and analyst load, full-service shops sweat both at once — but the underlying question never changes: how many client hours does this work consume, who has hours to give and when, and does the pipeline fit the people.
Software that genuinely serves "research agencies" is therefore flexible about project shape but stubborn about the unit of account: time, capacity and commitments — never just tasks with due dates.
A note for the people building this stuff
If you're on the vendor side, resist turning these signals into a qualification interrogation. The better play is marketing that self-filters: talk plainly about pipeline-to-capacity, freelancer benches, client-facing hours and utilisation, and the agencies that recognise themselves will lean in — while everyone shopping for a prettier task list quietly self-selects out.
Both sides win from that filtering. The most painful bespoke projects are nearly always expectation mismatches: a buyer who wanted a nicer spreadsheet meeting a builder who assumed appetite for rewiring how commercial connects to delivery.
Sound like your operation?
Insight Planner exists for agencies matching this exact profile — resource planning built around how insight consultancies genuinely run, not a rebadged task tracker.
See how it works →The ten-minute litmus test
Whichever side of the table you're on, one question cuts through the whole assessment:
Could you answer "do we have capacity for new work next month?" inside ten minutes — and would you bet a client deadline on what you found?
If the honest answer is no — or "yes, but only after someone burns three hours assembling it" — you're squarely in the group ready for a serious tooling conversation. If the answer comes back effortlessly and reliably, congratulations: you're not the urgent case, and you can spend the budget elsewhere for now.
Recognising your agency in this piece? We'll walk you through Insight Planner against your actual team size, project mix and current stack — the opposite of a generic product tour.