Hiring Operators, Not Managers
The difference between an operator and a manager is not a matter of seniority or title. It’s a matter of how someone relates to problems.
A manager sees a broken process and asks: who should fix this? An operator sees a broken process and fixes it. A manager monitors performance and reports what they find. An operator monitors performance, identifies the root cause of gaps, and changes the inputs to move the outputs.
In agency operations—where everything from chat quality to creator performance to revenue generation depends on well-functioning processes—you almost always need operators. Most agencies hire managers.
The result is a team that can describe problems precisely but struggles to solve them systematically.
What Managers Actually Do
Managers are coordination specialists. Their native environment is a functioning system that needs to be maintained and directed. They’re excellent at running meetings, communicating between teams, tracking project status, and holding people accountable to existing standards.
In the right context, managers are invaluable. Once an agency has built functioning systems and needs those systems coordinated across a larger team, managerial skill becomes essential.
The problem is that most agencies aren’t at that stage when they start hiring. They’re at the stage where the systems don’t exist yet, where processes are inconsistent or nonexistent, where the business is held together by the founder’s personal involvement in everything.
That stage needs operators—people who build systems—not people to oversee them.
When you hire a manager into an environment that needs an operator, two things happen. First, the manager defaults to coordination mode: they spend their time communicating, organizing, and facilitating, but the core operational problems don’t get solved because nobody is actually solving them. Second, the founder stays in the system because someone needs to and the manager isn’t doing it.
The result is an expensive hire that makes the founder feel like things should be improving without actually improving them.
What Operators Actually Do
Operators are systems builders. Their instinct is to understand how a process works, identify where it breaks down, and redesign it to produce better outputs. They’re process-oriented by nature—not because they love bureaucracy, but because they understand that consistent outputs require consistent inputs, and consistent inputs require designed processes.
In an agency context, operational talent looks like this:
They think in metrics. When an operator takes responsibility for chat quality, they’re not just reading conversations and giving feedback. They’re defining what good chat quality looks like in measurable terms, building a way to track it, identifying what variables affect it, and adjusting those variables to improve the number. The metric is the accountability mechanism.
They document what they do. Operators understand that if they hit by a bus, the work should survive them. They build SOPs not because they’re told to but because they understand that undocumented processes are fragile. Their processes live in files, not their heads.
They identify root causes. When revenue dips on an account, an operator doesn’t just report the dip. They trace it back. Was it subscriber count? Chat frequency? PPV performance? Content quality? They find the actual cause because the cause determines the fix.
They improve systems over time. Operators don’t just maintain processes—they iterate on them. They test variations, measure results, and implement improvements. The process in month six is better than the process in month one because someone has been actively refining it.
They can train others on what they built. An operator who can’t transfer their systems to someone else hasn’t actually built a system—they’ve just created a more organized version of knowledge-in-one-person’s-head. True operators design processes that can be documented and taught.
Why Agencies Keep Hiring Managers
The default hire in almost every agency is a manager, and there are understandable reasons for it.
Managers interview better. They’re experienced at articulating their roles and responsibilities, talking about teams they’ve led, projects they’ve delivered. They have a vocabulary for organizational work that sounds authoritative and competent.
Operators are harder to interview because their value isn’t in articulation—it’s in specificity. An operator will walk you through a process they built in detail: the inputs, the outputs, the failure modes they identified, the iterations they ran. That conversation requires the interviewer to understand operations well enough to evaluate what they’re hearing. Many founders aren’t there yet.
Managers also feel safer. Hiring someone to “manage” a function creates the impression that the function will now be taken care of. The founder can step back. The manager is in charge.
But a manager without functional systems underneath them doesn’t take care of the function—they monitor a broken process and report on it clearly. The function doesn’t improve. The founder stays involved because someone has to be.
The other common trap is hiring for title rather than capability. “Head of Chat” sounds like an operational role. But if the person you hire defaults to coordination and communication rather than systems design, you have a manager with a title that suggests operational ownership. The function stays broken.
How to Identify Operational Talent
Operational talent shows up in how people talk about their past work. The interview questions that surface it aren’t the standard “tell me about a time you led a team” questions. They’re questions that require specificity about process.
“Walk me through a process you built from scratch.” What were the inputs? What were the outputs? How did you measure whether it was working? What did you change after the initial version? Someone who has actually built operational systems will have concrete answers to all of these. Someone who managed a team will give you a vague description of what the process did without being able to explain how it worked.
“Tell me about a time a metric was moving in the wrong direction. What did you do?” Operators will describe a specific investigative process: what they looked at, what hypotheses they formed, what they tested, what worked. Managers will describe who they talked to about the problem.
“How do you onboard someone new to a process you own?” Operators have actual onboarding documentation or can describe how they’d build it. They’ve thought about knowledge transfer because they understand that undocumented processes are operational liabilities.
“What does a good week in this role look like, measured in actual numbers?” Operators think in metrics. If someone can’t describe the quantitative output of their work, they’re not in operator mode.
Attracting Operators to Your Agency
Strong operators are rare, and they know it. They’re not going to join an agency that can’t demonstrate that operational excellence is actually valued.
Several things make your agency attractive to operator talent:
Defined accountability. Operators want to own something—not assist with something. If the role is “help with chat management,” that’s a support role. If the role is “own chat performance with full authority over the process and accountability for the outcomes,” that’s an operator role. The framing matters.
Metrics that matter. Operators evaluate whether they’ll be measured on things within their control. If performance review is vague or based on subjective impressions, an operator knows they’ll be fighting the system instead of running it. Define the metrics upfront. Make them measurable. Make them the actual basis for evaluation.
Investment in the function. Operators don’t want to join an agency that expects them to build a world-class chat operation with inadequate tools, training resources, or budget. Show them you’re invested in operational excellence, not just hoping someone will fix things for you.
Autonomy. The best operators don’t want a boss who second-guesses every process decision. They want direction on outcomes and authority over methods. Micromanaging an operator is the fastest way to lose them.
The Build-Then-Manage Sequence
The correct hiring sequence for an agency is to hire operators first—build the systems—and then bring in managers to coordinate across those systems as the team grows.
This sounds obvious. Almost nobody does it.
Most agencies hire managers early because managers look like leadership, and founders want to feel like they’re building a leadership team. The result is a leadership team overseeing broken systems that nobody is actually fixing.
The alternative: hire operationally oriented people who will build your chat management system, your creator performance system, your onboarding process, your quality tracking infrastructure. Once those systems exist and are running well, hire coordinators and managers to maintain them at scale.
The agencies operating at true scale—$500K, $700K, $1M/month—have both. They have operational talent that built the systems and management infrastructure that keeps them running across a larger team. But the operational talent came first. The systems were the foundation.
You can’t manage a system that hasn’t been built. Hire the builders first.