Agency Operations and Project Management: Staffing, Capacity, and Client Trust
A 42-minute Time Limit conversation with Rob Harr, VP of Sparkbox, and Brett Harned examines how agency operations and project management work together. The discussion focuses on a practical question: how can an agency stay profitable without overworking its team or disappointing clients?
Operations is the bridge between selling and profit
Operations sits between a sale and the money left after delivery. It is the working method that converts commitments into results. Because people carry out that method, processes should be designed around human capacity rather than treating deliverables as self-moving. A useful test is whether a process still works when someone needs to cover extra work for a week without dropping other responsibilities.
Sell availability, then make progress visible
Fixed scope can make learning difficult when a project reveals a better approach midway. Selling team availability toward a shared goal gives both sides more flexibility. Points and velocity then provide a visible rhythm for progress, so clients can see how work is advancing without reducing the engagement to a rigid list of predetermined outputs.
Use whole or half allocations and visible capacity limits
Staffing someone in small fragments across many projects may look efficient on a roster while quietly consuming attention through repeated switching. Whole or half allocations make commitments clearer. For project managers, the conversation gives three starting checks: budget about 15 percent of project time for project management, keep each manager on one to four projects, and watch 25 billable hours a week as a warning line. These are planning prompts, not universal standards, and should be recalibrated for project complexity and risk.
Deliver bad news early to protect trust
Trust depends on candor before a problem becomes expensive. Bad news should be delivered early because projects rarely improve on their own after launch. A simple operating checklist can help: name the risk, state what it affects, share the current status, explain the next action, and update the client before the project slips further. The goal is to keep work from drifting into a warning state while recovery options remain open.
A practical review checklist
Use this sequence when reviewing an agency project: confirm the shared goal, check whether the team is selling availability or fixed scope, inspect allocations for thin slices and switching costs, compare project-manager load with the 15 percent planning budget and 25-hour warning line, review points and velocity with the client, and surface risks before they worsen. The episode also covers how operations shapes culture, how to improve profitability without losing sight of people, and how to judge whether operations could be a suitable next step after project management.
Frequently asked questions
What does agency operations do that project management does not?
Operations connects the work sold to the profit earned. It covers the numbers and processes behind delivery, while project management turns those processes into day-to-day coordination. When either side is overloaded or unclear, profitability and client confidence suffer.
How should staffing avoid hidden context-switching costs?
Assign people in whole or half allocations rather than thin slices across many projects. A person spread across six projects carries hidden switching costs that do not show in a simple headcount. Keeping project managers on one to four projects makes that load visible and manageable.
What capacity checks help keep project managers sustainable?
Use roughly 15 percent of project time for project management as a starting budget, keep project managers on one to four projects, and treat 25 billable hours a week as a warning line. Adjust the budget when the work, client, or risk profile changes, rather than treating the figures as fixed rules.
Why sell team availability instead of fixed scope?
Sell access to the team and progress toward a shared goal instead of locking every outcome into fixed scope. That gives the team room to learn during delivery. Use points and velocity to keep clients informed about pace and progress.
When should bad project news be shared?
Raise problems as soon as they appear. A project is usually in its best condition at the start, so delay lets issues move from manageable to yellow or worse. Early, honest updates preserve trust and leave more room to recover.