How a 58-Year-Old HVAC Company Got Its FSM to Work Its Way

The Business Had Been Running Since 1968. The Software Still Wanted to Bill by the Hour.

Guyette Air Conditioning and Heating is a second-generation family business in Iowa Park, Texas, serving residential, commercial, and new construction customers across Iowa Park, Wichita Falls, and the surrounding markets.

For more than five decades, the company has installed, maintained, and repaired HVAC systems, from ducted and ductless systems to air quality work and annual maintenance.

And in a Texas summer, the work doesn’t wait for office hours.

The crew is moving from early morning, and every service call eventually reaches the same moment: the technician finishes the job, writes the ticket, and takes payment before leaving the driveway.

There was just one problem. Guyette doesn’t bill by the hour.

Every service and every part carries a fixed price. There are no hourly labor charges and no itemized expenses.

But the mobile billing workflow its technicians were using was designed around exactly that model.

The software wasn’t broken. It simply wasn’t built for the way Guyette ran its business.

Every Job Was Carrying Software Steps Guyette Didn’t Need

On every job, technicians were being pushed through labor and expense fields that had nothing to do with how Guyette priced its work.

That meant extra steps on every invoice.

And during the busy season, Guyette was processing 25 to 35 invoices a day across service calls and installations. At two to three minutes of unnecessary work per invoice, those small steps added up to 5–8 hours of technician time every week.

But the billing workflow had a more important problem than speed.

Residential HVAC work often includes both parts and labor, and Guyette doesn’t treat them the same way for tax purposes. The software didn’t give technicians control over the taxable status of individual line items, so a single ticket could require taxable and non-taxable items side by side.

Almost every residential repair touched that problem. The QuickBooks sync was also failing, which meant work that had already been billed in the field wasn’t reliably reaching accounting.

For a business that expects the job to be finished and paid for at the customer’s home, these weren’t minor inconveniences

They were gaps in the way the business actually collected revenue.

The Office Closed at Five. Texas Heat Didn’t.

There was another part of the operation that didn’t fit the software. Guyette’s office runs Monday through Friday, 9 to 5. Customers don’t.

When someone submitted a request through the company’s website at 9 p.m. on a Saturday, there wasn’t a straightforward way to make sure that request reached the right person.

So a potential customer could be waiting simply because the office was closed. For a service business, that creates an uncomfortable disconnect. The customer doesn’t care whether the request came in during business hours. They just know they need someone to help.

Russell Didn’t Want to Change the Way Guyette Priced Jobs. He Wanted the Software to Catch Up.

When Russell sat down with the Upvoit team, he didn’t arrive with a long list of abstract software requirements. He started with something very specific.

He wanted an invoice creation button on the mobile app’s home screen. That request was committed during the first call and shipped within days. And that became the pattern.

Russell would explain what wasn’t working in the actual operation, and the product team would build around it. That matters because Guyette didn’t need another generic HVAC platform with a long feature list. It needed software that understood one simple reality:

The company’s pricing model wasn’t going to change just to make the software easier to use. The software had to work around the business.

The Billing Screen Was Rebuilt Around the Driveway

The new workflow starts where Guyette’s work actually ends: at the customer’s property.

The technician completes the job, creates the invoice directly from the mobile app, adjusts the line items when needed, captures the customer’s signature, and collects payment before leaving.

The labor and expense steps that Guyette never uses are gone. The entire billing flow was rebuilt around flat-rate pricing, and that initial rebuild took about a day.

That changes the final few minutes of every service call.

Instead of finishing the work and then navigating a billing workflow designed for a different business model, the technician can close the job in the same way Guyette has always wanted to close it:

job done → invoice created → customer signs → payment collected.

Right there in the driveway.

Then Guyette Fixed the Problem Behind the Invoice

The next issue was tax treatment. Guyette needed individual line items to be marked taxable or non-taxable, depending on the service or product. Upvoit added a taxable toggle to each line item, with the default setting stored against the service or product itself.

Set the equipment once, and future work orders inherit the correct setting. That capability was delivered roughly ten days after Russell requested it. The result is simple for the technician.

A ticket containing both parts and labor can be built correctly without forcing the field team into a workaround.

The software is no longer asking the business to change how it prices.

It’s reflecting how the business already prices.

The Other Pieces Started Falling Into Place

The QuickBooks problem was diagnosed too.

Unusually long customer first and last names were causing the sync to fail. Once identified, the issue was fixed, and Guyette was given a way to re-sync records that had already failed. The website request form was also connected to Upvoit, with notifications routed to the appropriate inbox.

So when a customer submits a request after the office closes, it no longer disappears into an unattended inbox. It reaches a person. Even training was handled around the way Guyette works, with recorded mobile walkthroughs instead of a manual that technicians would have to work through on their own.

The theme was consistent throughout.

If a part of the software didn’t fit the operation, Guyette didn’t have to redesign the operation. The workflow was adjusted around the business.

The Difference Shows Up in Every Busy Season Invoice

Today, the flat-rate call can close where it should: in the driveway, with the invoice created, the line items editable, the customer’s signature captured, and payment collected.

The unnecessary billing steps have also disappeared.

During the busy season, Guyette gets back 5–8 hours of technician time every week that previously went into labor and expense fields the company never used.

Taxable status can now be handled at the line-item level. The QuickBooks sync runs with a recovery path for failed records.

And website requests, including those arriving after hours, can reach the right person instead of sitting unread until Monday. These aren’t dramatic changes when looked at individually.

But together, they remove friction from the exact moments where a field service business makes money.

Because Good FSM Software Should Adapt to the Business

There’s another piece of this story that matters. Guyette has been installing HVAC systems since 1968.

The company already knows how it wants to price its work. It already knows how technicians should close a service call. It already knows what information accounting needs.

The problem wasn’t a lack of operational experience.

The problem was software trying to force a different operating model onto a business that had already figured out its own.

That’s why Russell’s takeaway isn’t about a particular feature.

That’s the real difference. A feature list tells you what software can do.

The way a vendor responds when your business doesn’t fit the standard workflow tells you a lot more about what it will be like to actually run your business on it.

The Software Should Fit the Way You Already Win

Guyette has been installing and servicing HVAC systems since decades. Its pricing model isn’t complicated. Its technicians know how to sell the work, complete the job, and collect payment. What was complicated was making software designed for a different business model fit into that process.

Upvoit changed that.

The billing screen now reflects Guyette’s flat-rate pricing. Technicians can invoice and collect payment from the driveway. Tax treatment follows the actual line items. After-hours requests reach the right person. And the team gets back hours every week that used to disappear into unnecessary billing steps.

None of that required Guyette to change the way it runs its business. The software changed instead. And that may be the more important question to ask when choosing an FSM.

Not, “Does this software have the features we need?”

But:
“What happens when the way we work doesn’t fit the way the software works?”

For Guyette, the answer was simple. They showed Upvoit how they worked. And Upvoit built around it.

What Would Your FSM Look Like If It Worked Your Way?

Maybe it’s your billing screen. Maybe it’s the way you price jobs. Maybe your technicians need a workflow your current FSM wasn’t designed for.

You shouldn’t have to change a proven business process just because your software wasn’t built for it. Show us how your operation works. We’ll show you what it could look like in Upvoit. Book a demo and let’s talk through the part that doesn’t fit.