Resource Manager

Every agency has someone who decides which people work on which projects. In a 10-person shop, that's usually the founder juggling allocations between client calls. At 30+ people, it's a dedicated role — the resource manager — and it's arguably the most strategically important position nobody talks about.

A resource manager owns the big picture of resource allocation. While project managers advocate for *their* project ("I need two developers full-time for six weeks"), the resource manager advocates for the *portfolio* — making sure that no single project starves the others, that workloads stay balanced, and that the team's capacity is used efficiently across all active work.

What the Role Actually Involves

A typical week for a resource manager includes:

• Weekly allocation review. Scanning the timeline for overallocation, underallocation, and conflicts. Adjusting blocks before they become problems.
• Pipeline planning. Working with sales and account managers to understand what's coming. Creating placeholder allocations for probable projects so capacity is reserved early.
• Staffing decisions. When three projects want the same person, the resource manager decides based on priority, skill fit, and availability — not who asked first or loudest.
• Headcount conversations. When the data shows sustained utilization above 90% or a skill gap that keeps recurring, the resource manager makes the case for hiring — backed by data, not feelings.
• Conflict resolution. PMs fight over shared resources. The resource manager mediates, using the schedule as objective ground truth.

Resource Manager vs. Project Manager

The distinction matters. A PM optimizes for one project's success. A resource manager optimizes for the organization's success across all projects. These goals sometimes conflict — a PM might want to hoard their best developer, but the resource manager sees that developer is needed more urgently elsewhere.

Healthy agencies make this tension productive rather than adversarial. The resource manager has the authority to move people between projects, and the PM has the responsibility to flag when that movement puts their project at risk. Both voices matter; the resource manager just holds the tiebreaker.

When to Create the Role

Most agencies don't need a dedicated resource manager until they hit 20-25 people with 8+ concurrent projects. Below that, a senior PM or operations lead can handle it as part of their role. The trigger isn't a specific headcount — it's when allocation decisions start falling through the cracks: people double-booked, bench time going unnoticed, projects understaffed while others are overstaffed.

When that happens, someone needs to own resource management as their primary function. And the first thing they'll need? A scheduling tool that gives them a single view of everyone's allocations, capacity, and availability — because managing resources from a spreadsheet at 25+ people is a game you've already lost.