General Manager vs COO: Which One Your Business Needs

A General Manager fixes execution inside one department — sales, production, or service delivery. A Chief Operating Officer fixes how every department connects to the next. The difference is scope: one function versus the entire operating system. If you are still approving purchase orders, signing off on hiring plans, and jumping into weekly stand-ups, you have a system problem, not a department problem. Here is how to decide which role your business needs, what each does day to day, how to set the role up before you make an offer, and what to do first.

What a General Manager Does

A General Manager runs a single function end-to-end. They take ownership of a department's revenue targets, deadlines, staffing, and quality standards. Their authority stops at the edge of that function. If production delays are causing sales to miss quotes, the GM flags the issue to the founder or a COO rather than trying to fix the production schedule themselves.

Hiring a GM works when one department is leaking revenue, missing deadlines, or losing talent while the rest of the company runs relatively smoothly. The role is cheaper and faster to fill than a COO because the scope is narrower and the decision-making stays within one domain. The GM's authority stops at their department; they report up to the founder or a COO.

The comparison below shows where the role works and where it falls short.

• Owns one department's full P&L and delivery: Where it works well: One team is underperforming while others are on track · Where it falls short: Cross-department bottlenecks — production delays hitting sales
• Sets hiring plans, training, and KPIs for their team: Where it works well: You need someone who can execute without you approving every step · Where it falls short: Building systems that connect across departments
• Escalates issues outside their function to the founder: Where it works well: The problem is clearly inside one silo · Where it falls short: Fixing why departments keep stepping on each other
• Reports directly to the founder or a COO: Where it works well: The founder still needs a person running a specific area · Where it falls short: Replacing the founder's role in setting company-wide priorities
• Cheaper and faster to hire than a COO: Where it works well: Budget is tight; you need someone operational now · Where it falls short: You need strategic judgment that spans all functions

When a General Manager is the right hire

A GM is the right hire when you have a clear function that is broken and the rest of the business is holding together. A sales team that keeps losing deals because follow-ups are inconsistent. A production floor that misses shipment deadlines because no one owns the schedule. A service desk where ticket turnaround has drifted and customer satisfaction is slipping. In each case the problem lives inside one department. A GM takes ownership there and frees the founder from daily firefighting in that area.

What a General Manager cannot fix

A GM cannot fix problems that live between departments. If sales is overpromising because production does not tell them the real capacity, a sales GM will not solve that. The issue is a system design problem: no one has built the handoff process, the feedback loop, or the priority rule that connects the two teams. That work belongs to a COO or to a liquid leadership engagement — where seasoned executives step into the gap, run the function, fix the cross-functional breakdown, teach the team, and hand the reins back — before you even consider hiring a permanent leader.

What a COO Does

A Chief Operating Officer owns the operating system. They connect strategy to execution across every department, set priorities that override department heads when necessary, and allocate resources so the whole business moves in the same direction. Their authority spans sales, production, finance, technology, and customer experience. A COO typically reports directly to the CEO or the founder.

The role is more expensive and harder to fill than a GM because it requires strategic judgment, not just operational skill. A COO must decide which department gets resources when everything is urgent. They must build the rules for how the company makes decisions when the founder is unavailable. They must design the systems — the reporting cadence, the escalation paths, the budget approval thresholds — that let the business run without the founder's constant intervention.

The mechanics of what changes when a COO takes over can be described in terms that apply to any small-to-mid-sized business. The difference is whether the problem lives inside one department or across the whole system. Without a COO, decisions pile up at the founder's desk. With one, decisions follow a written process: the department head proposes a plan, the COO reviews it against company priorities, the founder approves only what exceeds the pre-set threshold, and the rest executes. The founder stops approving purchase orders and starts reviewing the weekly dashboard instead. The time saved compounds quickly because the founder no longer re-checks work that already passed through the process.

A COO cannot fix a problem that does not exist yet. If the company is small, the owner can still hold the operating system in their head. If the company has grown large enough that the founder is still handling daily tasks, a COO is the minimum — not a luxury.

Decision Framework: GM or COO

The decision comes down to one question: is the broken thing inside one department, or is the whole system broken?

The rule:

• If the problem is one function is broken, hire a GM.
• If the problem is the whole system is broken, hire a COO.
• If the founder is still approving every purchase order, the company needs a COO, not a GM.
• If the company is small, neither role is needed yet. The founder should build the process first.
• If the company has grown large enough and the founder is still handling daily tasks, a COO is the minimum.

The test for each role

Before making an offer, run a test. Write the outcome on paper: what must be different once the role is filled. For a GM, it might be "the sales team closes more deals because follow-up is no longer optional." For a COO, it might be "the founder no longer approves purchase orders because the process is written and enforced." If you cannot write that outcome in one sentence, you have not defined the role clearly enough to hire for it.

A short-term engagement lets you test the person before committing to a long-term role. This is where project rescue work often overlaps with hiring decisions: a consultant fixes the immediate breakdown, then the owner decides whether the fix requires a permanent role or a new system.

A GM will not fix a COO problem, and a COO will waste months fixing a GM problem. Start with a free strategic review: Confluunt's advisors assess what's working, what's not, and recommend next steps.

How to Set Up the Role Before Hiring

A bad hire costs more than a vacancy. Setting the role up correctly before you post the job saves time, money, and frustration. Use this checklist.

• Write the role as a problem to solve, not a title to fill. "We need someone who runs the production floor" is better than "We need a production manager." The first tells candidates exactly what they will do. The second leaves them guessing and attracts people who want a title, not the work.
• Define the authority boundary. What can the hire decide without asking? If they cannot approve a hire without founder sign-off, say so. If they can spend on a tool without founder sign-off, write that down. Vague boundaries create dependency, not delegation.
• Set the outcome. What must be different once the role is filled? Write it in one sentence. If you cannot, the role is not ready to be filled.
• Budget for the role including the cost of the founder's time during the ramp. A new hire takes weeks to learn your systems. Add the hours the founder spends training them, reviewing their first decisions, and correcting course. That time has a real cost.
• Test the hire with a short-term engagement before committing to a long-term role. A trial or a project-based contract lets you see how the person works inside your actual business before you give them permanent authority over your operations.

This work falls under strategic management: assessing the current state, designing a plan, and placing the right people to execute. A GM or COO hire is one of those plans.

Frequently asked questions