The Short Version
The question I get most often from builders at $2M-$4M is some version of: 'I need help, but I don't know what role to hire.' An operations manager is often the answer — but it's the right answer only if the role is defined clearly before you post the job. Hiring an ops manager into an undefined role produces a confused employee and a frustrated owner within 90 days. Here's how to know when the timing is right, what the role should actually include, and what you need to have in place before the hire can succeed.
Sound Familiar?
Signs you need an operations manager, not just another project manager:
- You're the primary scheduler, the vendor coordinator, and the hiring manager — all at once
- Your project managers escalate every decision to you because they don't have authority to act
- You spend your evenings answering the operational questions your team should be handling
- Revenue has stalled not because of sales but because you can't execute more volume
- When you take a day off, something falls through the cracks
- You've thought about hiring a second project manager but realize the problem isn't PMs — it's coordination
What We Found
The Difference Between an Operations Manager and a Project Manager
This distinction matters because builders often conflate the two and end up hiring the wrong person for the problem they're solving.
A project manager owns individual project outcomes. They're responsible for the schedule, budget, and quality of specific jobs they're assigned. They work in the business — on jobs, with subs, resolving field issues.
An operations manager owns the system that runs all of the projects. They're responsible for the coordination layer above individual jobs: scheduling across the portfolio, resource allocation, vendor management, process compliance, and the daily decision-making that flows between projects. They work on the business — ensuring the system functions, not that any single job gets done.
The clearest test: if every project manager is doing their job well and the company is still chaotic, you have an operations problem, not a project management problem. You need someone whose job is the coordination infrastructure.
What an Operations Manager Actually Does
In a residential construction company running $2M-$5M, an operations manager's scope typically covers:
- Portfolio scheduling: maintaining the master schedule across all active projects, identifying conflicts, and coordinating sub availability across jobs
- Sub and vendor coordination: managing relationships with the trade partner roster, expediting materials, resolving delivery and availability issues
- Process compliance: ensuring project managers follow SOPs — daily logs, change order workflow, invoice submission, closeout checklists
- Team coordination: running the weekly operations meeting, setting priorities, resolving escalations between PMs and field crews
- Hiring and onboarding support: coordinating job postings, scheduling interviews, and managing new hire onboarding alongside the owner
- Owner inbox management: filtering what needs the owner's attention and handling what doesn't
This is not a person who runs jobs. This is a person who runs the machine that runs jobs. That's a different skill set than a great PM, and it requires someone who is process-oriented, comfortable with ambiguity, and genuinely interested in systems over execution.
When the Timing Is Right (And When It Isn't)
The timing question is the one I get most wrong in early conversations, and I've learned to push back on builders who want to hire too early or too late.
Too early (most common): Revenue under $2M with one or two PMs. At this stage, you don't have enough volume to create the coordination problem that an ops manager solves. What you need is better processes and clearer PM accountability, not a new management layer. Adding an ops manager before you have documented processes is expensive and ineffective — you'd be paying someone to manage chaos instead of building the system to eliminate it.
The right window ($2M-$4M): You have 3+ active projects at any time, 2+ project managers or senior foremen, and the owner is spending 20+ hours per week on coordination tasks. Revenue growth is constrained by operational bandwidth, not by sales. At this stage, an ops manager creates leverage that pays for itself in owner time recovered and revenue capacity added.
Too late (also common): Revenue above $4M with a burned-out owner who's been operating in crisis mode for a year. This hire can still work, but the onboarding is harder because the systems are undocumented, the team has learned to operate without clear structure, and the owner has trouble delegating because they've been the single decision point for so long. The Owner's Trap — the operational dependency that keeps the owner executing instead of leading — is especially hard to escape when it's been the mode for years.
What Needs to Be True Before You Hire
An ops manager hired into an undocumented business will spend their first six months trying to understand how things work. That's expensive. Before you post the job:
- Document your core processes: estimating workflow, project startup checklist, sub coordination process, change order process, closeout checklist
- Define what "ops manager success" looks like at 90 days and 12 months
- Identify which decisions the owner will delegate and which stay with the owner
- Set up the tools the ops manager will use: PM software, scheduling system, communication channels
If you can't answer "what does success look like in 90 days?", you're not ready to hire. That answer has to exist before the offer letter.
The Feeding the Machine Problem
The cycle where hiring to grow forces a stressed salesperson or owner to chase jobs they wouldn't otherwise take, compressing margins to cover the new overhead. An operations manager doesn't solve this automatically. But when the role is scoped correctly and the owner actually delegates, it's the highest-leverage hire in the $2M-$5M revenue range.
Compensation, Where to Find Candidates, and What the First 90 Days Look Like
What to Pay
Construction operations manager compensation in 2026 varies significantly by market and scope. Here are the ranges I'm seeing in current placements:
- High-cost metros (NYC, LA, SF Bay, DC metro, Seattle): $95,000-$130,000 base
- Mid-cost metros (Denver, Austin, Nashville, Atlanta, Phoenix): $80,000-$105,000 base
- Lower-cost markets (secondary cities, rural areas): $65,000-$85,000 base
At $2M-$4M revenue, the total comp package (base + performance bonus) should sit at 3-5% of revenue. A $3M company paying an ops manager $90,000 base plus a $10,000 performance bonus at 8%+ gross margin achievement is at the right ratio. An ops manager who genuinely improves your execution capacity should increase your revenue capacity by $500,000-$1.5M, which more than funds the role.
Performance bonuses should tie to outcomes the ops manager actually controls: on-time project delivery rate, gross margin vs. budget, change order processing time, and sub compliance metrics. Don't tie bonuses to outcomes the owner controls, like total revenue or net profit.
Where to Find the Right Person
The best construction ops managers I've seen placed came from three sources:
- Internal promotions from senior project managers who show systems thinking and coordination skills (not just execution skills)
- Construction software companies and vendors — people who have spent years helping builders implement systems understand what good looks like
- General contractor or commercial construction companies downsizing or restructuring — people with enterprise coordination experience who want a more relationship-oriented environment
The least successful hires come from unrelated operations roles (retail, hospitality) without construction context, and from "generalist operations" professionals who've never managed a trade-dependent workflow. Construction operations has physical, scheduling, and sub-management complexity that generic ops experience doesn't prepare you for.
What the First 90 Days Should Look Like
Days 1-30: Documentation and observation. The ops manager shadows the owner and PMs, documents every process they observe, identifies decision points, and maps the current communication structure. They produce a "how we work" document at the end of this period — the first draft of your company's operating manual.
Days 31-60: Assumption of coordination responsibilities. The ops manager begins running the weekly ops meeting, managing the portfolio schedule, and handling the routine coordination and vendor calls the owner was doing. The owner stays available but begins removing themselves from daily escalations.
Days 61-90: First process improvements. Based on their first 60 days of observation, the ops manager proposes and implements the first two or three process improvements. These should be in areas where current process is creating friction — not comprehensive redesigns, just high-value targeted fixes.
If the first 90 days produces a documented operating model and a meaningful reduction in owner hours spent on coordination, the hire is working. If the owner is still the single point of contact on everything and the ops manager is waiting for things to do, the delegation hasn't happened — and that's a management conversation to have immediately, not at the 90-day review.
Find Your Revenue Leaks in 5 Minutes
Answer diagnostic questions about your operations, finances, and sales. Get ranked AI skill recommendations with dollar recovery estimates and an implementation roadmap — free, instant results.
Take the Free SkillMatch Diagnostic →Frequently Asked Questions
The right window is typically $2M-$4M in annual revenue, when the owner is spending 20+ hours per week on coordination tasks and revenue growth is constrained by operational capacity rather than sales. Earlier than $2M, you usually need better processes more than a new management layer. Later than $4M without the hire, owners are typically in burnout territory.
A construction ops manager owns the coordination infrastructure that runs multiple projects simultaneously: portfolio scheduling, sub and vendor coordination, process compliance, team communication, and filtering operational decisions away from the owner. They work on the business — the system that runs projects — rather than on individual projects directly.
Base compensation ranges from $65,000-$85,000 in lower-cost markets to $95,000-$130,000 in high-cost metros. At the $2M-$4M revenue range, total comp including performance bonuses typically runs 3-5% of annual revenue. Bonuses should tie to project delivery metrics and margin performance, not total revenue.
A project manager owns individual project outcomes — schedule, budget, and quality on specific jobs. An operations manager owns the system that runs all projects — coordination across the portfolio, process compliance, resource allocation, and the decision layer between field execution and ownership. They're solving different problems at different levels of the organization.
Document your core processes before posting the job: estimating workflow, project startup, sub coordination, change order process, and project closeout. Define what success looks like at 90 days and 12 months. Identify which decisions you'll delegate and which stay with you. An ops manager hired into an undocumented business spends their first six months trying to understand how things work, which is expensive and frustrating for everyone.
