If you run a research agency of any size, you've almost certainly had this conversation. It usually happens after a particularly painful resourcing collision — two researchers double-booked, a project going over because nobody realised the senior lead was away that week, or a board meeting where the MD spent 40 minutes manually compiling a utilisation report the night before.
Someone says: "We need to sort this out. We can't keep doing it in spreadsheets."
Everyone nods. And then, usually, nothing changes. Or you try something — a project management tool, a shared calendar, a new tab structure — and six months later you're back to where you started, just with more tabs.
This piece is about why that happens, and what a better path forward looks like for boutique qual and quant agencies specifically.
Why spreadsheets persist (they're not stupid)
First, it's worth being honest about why spreadsheets have survived this long. They're not the enemy. They're flexible, fast to set up, and everyone already knows how to use them. When your agency was five people, a shared sheet probably worked just fine.
The problems emerge at scale. Not necessarily headcount scale — you can have the same issues with eight people as with thirty — but operational complexity scale. The moment you have:
- More than a handful of concurrent projects
- Researchers with varying client-facing hour commitments (part-time, fractional, or freelance)
- A pipeline of upcoming projects that need to be resourced before they're won
- Any need to report on utilisation, capacity, or team health
…a spreadsheet stops being a tool and starts being a liability. The data lives in it, but so does all the risk. One person forgets to update a row. Someone edits the wrong column. A freelancer's availability changes and nobody propagates the update. The sheet reflects last Tuesday, not today.
"The spreadsheet doesn't lie — but it doesn't know what it doesn't know. And by the time you find out, it's usually too late to fix it cleanly."
Why generic project management tools don't fit
The next instinct is usually to reach for an off-the-shelf PM tool. Monday.com, Asana, ClickUp, Notion — all decent products, all designed for a generic knowledge-work team. And that's precisely the problem.
Insight agencies don't work like generic knowledge-work teams. The project lifecycle in a research agency has very specific phases — commissioning, design, recruitment, fieldwork, analysis, reporting, debrief — and the resourcing needs shift dramatically between them. A quant project might need one researcher heavily committed during scripting and then almost nobody during fieldwork. A qual project flips the other way.
Generic tools don't understand this. They let you create tasks and assign people, but they don't have a concept of available client hours — the real currency of a research agency. They don't know that Priya is contracted for 28 hours a week, or that three bank holidays in April effectively remove a full day of capacity across your team, or that your regular freelancer has told you she's available 60 hours next month but you've only committed 40 of them.
You can model all of this in Monday.com if you work hard enough at it. But you'll spend more time maintaining the tool than doing the work it's meant to support.
What resource planning actually needs to do
When we talk to Operations Managers and MDs at research agencies, the asks are usually the same. They want to know:
- How many billable hours does each project require this month? Not a rough guess — a real number derived from the project scope.
- How many hours does each team member actually have available? After holidays, public holidays, internal commitments, and part-time adjustments are accounted for.
- Is there a gap — and if so, where? Which months are tight? Which projects are pushing people over capacity? Where is there genuine headroom to take on more work?
- What's the freelance picture? Which freelancers are available, what have we committed to them, and what do we still have in reserve?
That's not a complicated list. But it requires a system that knows all four things at once, updates them in the same place, and surfaces the answers without anyone having to run a manual calculation.
The Pipedrive gap
Many agencies we speak to use Pipedrive for their CRM and sales pipeline. It's a sensible choice — clean, simple, focused on deals. But Pipedrive stops at the point of a project being won. It doesn't know anything about delivery.
This creates a dangerous gap. Your commercial director knows that three new projects are coming in over the next six weeks. Your ops manager doesn't find out until the contracts are signed. By then, the resourcing conversation becomes reactive — who can we move around, who can we call, can we push the start date — rather than planned.
A good resource planning system should be able to ingest pipeline information — even at a provisional stage — so that you can start planning capacity before a project is confirmed. "We've got a 70% chance of winning this tracker project. If we do, it'll need Sarah and one freelancer from July through October. Are we covered?" That's the conversation you want to have in May, not in June.
Why custom-built tends to win for agencies at this stage
Off-the-shelf tools can get you 60–70% of the way there. If your needs are straightforward and you're willing to adapt your processes to the tool, they might be enough. But the agencies that tend to get the most value from proper resource planning software are the ones that build something shaped around how they actually work.
That means your own terminology — not "tasks" and "projects" but "studies", "trackers", "modules". It means your own workflow — the way your specific team moves a project from brief to debrief. It means your reporting structured around the metrics your MD actually cares about, not a generic dashboard.
The upfront investment in custom software is higher. But the ongoing cost of working around a tool that doesn't quite fit — in time, in workarounds, in errors — tends to be higher still. And more importantly, a tool that fits how you work actually gets used. Generic tools get abandoned.
We build this for research agencies
If this resonates, we'd be happy to show you how we approach resource planning software for insight consultancies — built around your workflows, not a generic template.
See how it works →Where to actually start
If you're mid-spreadsheet-chaos right now, the answer isn't to immediately commission custom software. It's to get clear on what's actually broken before you try to fix it.
A few questions worth sitting with:
- Where does information currently live, and who is responsible for keeping it up to date?
- What's the last thing that went wrong specifically because of a resourcing visibility gap?
- How long does it currently take you to answer "do we have capacity to take on a new project next month?" — and is that answer reliable?
- What would you do differently if you could see, in real time, which of your researchers were under-utilised right now?
The answers tend to make it very clear what kind of solution you need. Sometimes it's a better process. Sometimes it's a lighter tool. Sometimes it's bespoke software. But you can only make that call when you're honest about the actual problem, not just the symptom.
If you're at the point where you want to explore what a purpose-built system looks like for your agency, we're happy to walk you through it. No generic demo — we'd look at your team size, your project mix, your current setup, and show you what it would look like built for you.