Listen to the full conversation above, or read the key takeaways below.
Every commercial HVAC contractor knows what busy season feels like. Phones ringing nonstop. Schedules packed. Team stretched thin. But the contractors who actually thrive during the rush aren’t doing something magical — they’ve built operations that hold up under pressure.
We sat down with Brad Boggs, President of B&W Mechanical Contractors in Atlanta, for an honest conversation about what that actually takes. Brad has grown B&W over two decades — from a construction company that did a little service work, to a $30 million service operation running more than 8,500 calls a year. Here’s what he shared.
1. Busy season doesn’t create problems — it reveals them
“Busyness doesn’t really create any issues for us. It just magnifies the ones you already have.”
— Brad Boggs
If dispatch is a little disorganized in March, it’s chaotic in July. If communication is inconsistent when things are slow, it becomes a liability when they’re not. The problems were always there — peak season just turns up the volume.
The implication: the work of improving busy season performance happens before it arrives. Keep score as you go — note the friction points, the process breakdowns, the personnel issues — and fix them in the off-season. Think of it like a sports team. The ones who win in-season are the ones who outworked everyone when the games weren’t counting.
2. Stop filling every slot on the schedule.
Most dispatch teams are trained to keep calendars full. It feels productive. It’s actually a trap.
When every technician is booked for every hour of every day and a reactive call comes in, you have no good options. You pull someone off an existing job — which means demobilization, cross-city travel, and a tech walking cold into a high-pressure situation. The customer being pulled from suffers. The tech suffers. And the new call probably doesn’t go as well as it should.
The fix is to build in capacity on purpose. Designate a rotation of on-call technicians who are available for reactive work — give them something productive to do, but keep them unscheduled and geographically central. During Atlanta summers, B&W runs two to three on-call technicians a week. Not because there’s always enough work to keep three people busy, but because sometimes there’s seven calls in a day and you need the capacity to absorb them without breaking everything else.
“It’s a bit like a firehouse philosophy. A firehouse is full of firefighters sitting by, waiting on a call. They’re training, doing things that are productive — but they’re prepared for the call.”
— Brad Boggs
The key rule: if you’ve already pulled a tech off a job to respond to something reactive, that’s a one-time move. Flag it in your dispatch system. Don’t do it again to the same customer.
3. Not every urgent call is actually an emergency, so ask.
When a customer calls saying a unit is down, the instinct is to react immediately. But customers often call in a panic before they’ve fully assessed the situation. A simple question — Is this truly an emergency? — changes the whole dynamic.
Is there a redundant unit? Is it a critical system or a comfort issue? Can it wait until tomorrow? Most of the time, when you ask directly, customers will admit they can wait. That one question converts a reactive scramble into a scheduled visit.
When it is a genuine emergency — no backup, no redundancy — that’s also a sales conversation. The customer is living proof of exactly what can go wrong when there’s no fallback. That’s the moment to talk about what proactive protection could look like.
4. You set the expectations you’re willing to live with.
“You set the expectations you’re willing to live with. Once you’ve accepted the customer’s demand of expectations, that becomes the standard you’re held to.”
— Brad Boggs
This is one of the harder disciplines in a service business — especially under pressure, when saying yes feels easier than pushing back. But agreeing to a timeline or response commitment you can’t meet doesn’t just affect one job. It cascades into everything else on the schedule.
That pressure doesn’t only come from customers. It comes from your own sales team. A salesperson who’s been nurturing a relationship will promise dispatch capacity they don’t have. Your operations people — dispatch, field supervisors, project managers — all need to understand and own the expectation-setting process, not just the people closest to the customer.
And when customers push back with unreasonable demands? A lot of the time, the industry trained them to expect that. The contractors who chased every reactive call and always said yes created the pattern. Breaking it takes consistency — and it pays off in better relationships over time.
5. Good seasons and bad seasons both come down to one thing: Process
The difference between a busy season that runs smoothly and one that falls apart usually isn’t luck or weather or staffing. It’s whether you planned, and whether you’re executing to a process.
When things go sideways — quality drops, margins fade, techs are making five trips to the supply house — it’s almost always because something bypassed the process. Someone assumed instead of communicating. A job started before the scope was properly laid out. A reactive call jumped the queue and disrupted three other things.
Having a diagnostic process, a dispatch process, a job startup process — these don’t have to be complicated. They just have to exist and be followed consistently. When they’re not, the cost shows up as callbacks, wasted labor, and frustrated customers. And busy season makes all of it worse.
6. Reactive communication is what happens when you skip proactive communication.
Communication sounds like table stakes. In practice, intentional communication is one of the hardest things to maintain under pressure.
Every reactive problem — a tech who showed up without the right information, a customer who expected something different, a job that started wrong — can usually be traced back to a proactive communication that didn’t happen. Someone assumed the tech already knew. Someone skipped the pre-job walkthrough. Someone didn’t ask the right question before committing.
When things get busy, those communications get shorter. The things that get cut are the things that matter most. The fix isn’t just communicating more — it’s treating communication as a planned step in every job and dispatch interaction, not something that happens when there’s time.
7. You’re in a people business… Don’t forget it.
HVAC and plumbing companies fix machines. But the people doing that work are the actual product.
Peak season burns people out in ways that aren’t always visible. A technician who’s been running hard for three weeks straight isn’t going to perform the same as one who’s rested — and the difference shows up in diagnostic quality, callbacks, and customer interactions. Watching for those signs and having the conversation before something goes wrong on a job is part of the job.
Brad’s philosophy: if you’re going to have technical conversations with your team, you also have to have relational ones. Ask how someone is doing. Notice when their work changes. Know enough about their life outside work to understand what might be affecting their focus.
At B&W’s scale, Brad can’t do that with 100 people directly — so the structure is built so that supervisors each carry a small enough group to actually know them. The relationship doesn’t scale by itself. You have to design for it.
8. Planned work isn’t just easier. It’s a different business model
Brad spent time early in his career chasing reactive customers. He was good at showing up in a crisis and solving problems fast. But over time, he realized those customers didn’t value him. The only time they called was when something was broken. Every interaction started with someone in pain.
“What you end up creating is a problem-based relationship. Anytime they’re experiencing pain, that’s when you come involved.”
— Brad Boggs
Planned work is more productive, more profitable, and better for the people doing it. When techs are doing reactive work under pressure, they know they’re hacking it. They’re not doing their best work, and they know it. That wears on people.
Brad closes with a riddle his mentor gave him: a landscaping company’s best customer calls in a panic — their daughter is getting married this weekend and an irrigation line has burst. What does the customer want?
The technical answer: fix the line, lay new sod, respond fast. The real answer: green grass. The customer never wanted an irrigation system. They wanted green grass, and you told them they needed the irrigation system to get it. Everything that can break is there because you put it there.
The question Brad keeps coming back to: if you’re on that property every week, how did you not know the wedding was coming? What could you have done in advance — something that would have taken minutes — to make sure the customer had green grass on Saturday?
For commercial HVAC, the equivalent is maximum uptime. Customers don’t want your maintenance visits. They want their systems to work, their tenants to be comfortable, and their phones not to ring with complaints. Planned work is how you give them that — and how you build a business you can actually predict and grow.
“If you can’t plan, you can’t predict. And if you can’t predict, good luck.”
— Brad Boggs
Listen to the full conversation
Want to think through how any of this applies to your business? Download the Service Revenue Ecosystem Guide — there’s a self-assessment inside that helps you pinpoint where your operation is leaving revenue on the table.
