The short answer
Field service software manages work you already have. A CRM manages work you might get. For most residential HVAC companies the first one is the entire answer, because the work arrives already sold: a system fails, someone calls, you dispatch. Nothing had to be won.
The moment a meaningful share of your revenue has to be sold before it can be scheduled, that logic breaks. A $12,000 replacement quote that a homeowner sits on for three weeks is not a job. A commercial retrofit bid that goes through two revisions and a facilities committee is not a job. Your FSM platform has nowhere honest to put either of them, so they end up in a spreadsheet, and the spreadsheet is where the revenue leaks.
So skip the feature comparison. Run one test instead.
The test: what share of your revenue is sold before it is scheduled
Take last year's revenue and split it into two piles.
Pile one is demand capture. The customer already decided they needed you before they called. Service calls, no-heat calls, warranty work, contracted maintenance visits. You did not sell this work, you scheduled it.
Pile two is demand creation. Somebody had to propose, price, follow up and close before this could ever hit the board. Replacements and changeouts, IAQ add-ons, commercial service agreements, retrofit bids, new construction.
Divide pile two by the total. That percentage is your answer.
| Sold before scheduled | What you actually need | Why |
|---|---|---|
| Under 20 percent | FSM only | The unsold-estimate list inside your FSM covers it |
| 20 to 40 percent | FSM plus deliberate pipeline discipline | Enough proposal volume to lose track of it |
| Over 40 percent | FSM plus a real CRM layer | You have salespeople, and salespeople need stages |
| Over 40 percent with commercial or new construction | Two systems, integrated | Bid cycles and job costing outgrow both categories |
This is a better cut than the one most guides use. The common advice is to size by truck count, and truck count is a poor proxy. A ten-truck maintenance-heavy commercial shop with two estimators has a far bigger pipeline problem than a twenty-truck residential service company where every job arrives as an inbound call.
What each system is actually modeling
The clearest definition of the split I found while researching this came from Field Ascend, which puts it plainly: a CRM is built around customers and sales activity, while field service management software is built around doing the work, meaning scheduling work orders, sending technicians, capturing evidence, recording time, pricing labor and turning completed work into invoices.
That is correct as far as it goes, but it stops short of the thing that matters operationally. The real difference is the primary record.
| Field service software | CRM | |
|---|---|---|
| Primary record | The job | The opportunity |
| Exists before a sale? | No | Yes, that is the point |
| Can it be worth zero? | No, a job has a value | Yes, most opportunities die |
| Time horizon | Days | Weeks to months |
| Owned by | Dispatch and the tech | A named salesperson |
| Dies quietly when | Never, jobs get invoiced | Nobody follows up |
Look at the last row. A job cannot silently disappear from an FSM platform, because the whole system is built to chase it to an invoice. An opportunity disappears silently by default. Nothing breaks, no invoice goes unpaid, no customer calls to complain. It just stops existing, and your revenue is quietly smaller than it should have been.
That asymmetry is the entire argument for CRM behavior in an HVAC company.
The seam is measurable, and it is expensive
Here is the part the vendor comparison pages leave out: we can actually size the gap between quote given and job sold.
Hatch analyzed 163,212 HVAC estimate follow-up campaigns run on its platform over a six month period, counting only campaigns with at least 100 launches and 100 responses. Each campaign triggered two days after a technician or sales rep delivered an estimate.
By the numbers
Across those 163,212 HVAC estimate follow-up campaigns, the average response rate was 60 percent. The best performing campaign hit 90.06 percent and the worst hit 17.82 percent. Only 22,429 campaigns cleared 70 percent, and just 1,229 of the full set, well under 1 percent, cleared 80 percent.
Sit with that spread. Same trade, same customer, same moment in the buying process, and the response rate ranges by a factor of five. The variable is not the offer. It is whether anything systematic happened after the estimate left the truck.
The mechanics Hatch found are specific enough to copy. The top campaign ran seven messages, five texts and two emails, over seven days with two pause days, opening with a 200 character text and a 134 character email. The worst campaign sent almost the same volume, six messages over ten days, but split them across texts, emails and voicemails and opened with a 434 character text. Longer messages, fewer texts, worse results. Hatch also reports that waiting more than two days after the estimate causes engagement to drop sharply.
The revenue on the other side of that discipline is real. John Wilson, CEO of The Wilson Companies, told Hatch that his inside sales team did not exist until the prior year and now contributes nearly $400,000 a month in revenue.
None of that is a dispatch problem. Every piece of it is pipeline work: a record that persists after the visit, an owner, a cadence, and a next action date. Ask whether your current system does that, or whether it just files the estimate as "unsold" and waits.
If your estimates are dying in an unsold list and your follow-up lives in someone's head, that is a systems gap, not an effort gap. We build custom CRMs for HVAC and trades businesses that sit on top of the dispatch software you already run.
Why the estimator's pipeline always ends up in Excel
Ask any HVAC owner running commercial or replacement work where their open bids live, and you get a version of the same answer. Here is one, stated directly.
A Canadian HVAC contractor with 20 service and install techs, running residential and commercial work on QuickBooks Enterprise, posted in r/HVAC looking to replace their software. Their first stated requirement was this: they quote with an Excel document that does not link to their software, and they would love to find something that does.
That is the seam, described by someone standing on it. They already had field management software. It was not missing scheduling or invoicing. It was missing a place to keep a quote alive between the day it was sent and the day it was won.
The same pattern shows up at larger scale. An owner at a mid-sized commercial HVAC company posted in r/hvacadvice with a 30 person team: four estimators and project managers, four administrative staff, one service manager, ten service techs and ten installers. Their customer information was spread across QuickBooks, Team Up, Dropbox and Excel, and they needed a job numbering system that covered service calls, preventative maintenance and construction jobs in one scheme. Their own words on the odds of finding one product that did it: "I may be looking for a unicorn here."
Note the org chart. Four estimators and project managers against ten service techs. Nearly a third of that back office exists to sell and manage work that has not been scheduled yet, and none of it fits a dispatch board.
Watch out
If your estimators keep a personal spreadsheet, do not treat it as a discipline problem to be trained away. It is a schema problem. They are storing a record type your software does not have, and no amount of process enforcement creates a field that does not exist.
Where the honest answer is two systems
Most buyer guides will not say this, because most are published by a vendor selling one platform. Sometimes you genuinely need two.
An A/C contractor doing new construction multi-family and light commercial, now adding service work, laid out the market accurately in r/HVAC. FieldEdge, ServiceTitan and Housecall Pro are geared toward service work, changeouts and small jobs. Sage, Contractor Foreman and similar tools are geared toward larger, longer duration new construction jobs but handle service work poorly. The question of what does both well went essentially unanswered, and the replies were a list of ERP-scale suggestions.
The mismatch is structural, not a gap in the market. Service work is high volume, short cycle, and priced per task. Construction work is low volume, long cycle, and costed against a fixed contract with retainage and progress billing. Those are different data models, and a product that flexes to cover both tends to be an ERP with an ERP's price.
An operator running a generator service business with the same mixed model put the failure precisely. They had tried FieldEdge and Housecall Pro on a QuickBooks Online backend, and found that most software does fine with time and materials work but does not understand a fixed price contract for a full install where you pull from your own inventory, buy from a supply house, and track everyone's time against the job.
If that describes you, stop searching for the unicorn. Choose the system that fits your larger revenue stream, run the smaller stream in a tool built for it, and spend your integration budget on making the customer and equipment records agree across both.
What "our FSM already has a CRM built in" actually means
You will hear this in every demo, and it is not a lie. It is just doing a lot of work in a small phrase.
BDR's 2026 HVAC CRM buyer's guide devotes a full section to the point that most HVAC CRM tools are included in your FSM software, and answers "do I need a separate CRM if I already have field service software" directly in its FAQ. For a residential service shop, that is the right conclusion. Buying a second system to manage twelve open estimates is overhead with no return.
But watch what happens as the sales side gets serious, using the strongest vendor in the category as evidence. ServiceTitan's own commercial HVAC CRM pages market opportunity tracking with a dedicated command center, agreement templates to standardize proposals, automated equipment capture that flows into quotes and agreements, built-in margin targets, and version management so negotiations do not lose the thread.
Every one of those is a pipeline feature. None of them is dispatch. The dominant FSM vendor in the trade built a distinct opportunity layer for commercial customers because the job record could not carry that work. That is the clearest possible confirmation that the two categories are not the same thing, offered by the company with the most incentive to say they are.
So when a vendor says the CRM is built in, ask which meaning applies:
- Customer history. Every FSM has this. It is a contact record with past invoices, not a CRM.
- Unsold estimates. A filtered list of quotes with no follow-up structure attached. Better than nothing, not a pipeline.
- Actual opportunity records. Stages, owners, expected close dates, forecast values, revision history. Rare below the enterprise tier, and usually priced there.
The demo script
Vendors demo the dispatch board because it is the best-built part of every product in this category. Refuse to spend the hour there. One operator's warning after evaluating several systems is worth taping to your monitor: everybody says they do it, then they grossly underdeliver.
Make them do these five things live, in their software, with your kind of data:
- Show every open proposal over 30 days old, with a dollar value, an owner and a next action date, on one screen. If this requires an export, they do not have a pipeline.
- Take one quote through revision. Change the scope, reprice it, and show both versions still attached to the same opportunity. Commercial work is won on version three.
- Follow one piece of equipment from quote to install to maintenance agreement to a service call two years later, with no re-entry at any step.
- Trigger a follow-up sequence on an unsold estimate and show where the replies land. Ask who owns the reply when the estimator is on a roof.
- Produce a forecast: total open pipeline value by expected close month. If the answer is a report they will build during onboarding, treat that as a no.
Tip
Do items one and five with your own numbers, not the demo dataset. Vendor sample data is seeded to make reports look complete. Your data is what exposes whether the fields you need actually exist.
The decision framework
Run these in order. Stop at the first one that fits.
- Is over 80 percent of your revenue inbound service and contracted maintenance? Buy the FSM platform your techs will tolerate and stop reading. Our HVAC CRM shortlist covers how to pick between the main options on reporting rather than features.
- Do you have anyone whose job title includes "sales" or "estimator"? They need stages, owners and a forecast. Start with the pipeline features inside your FSM and measure whether anything is still landing in a spreadsheet after 90 days.
- Is a spreadsheet still carrying open bids after 90 days? You have outgrown the built-in layer. See the signs you have outgrown your CRM for the other symptoms that usually cluster with this one.
- Do you run both new construction and service? Plan for two systems and budget for the integration rather than hunting for one product that does both.
- Does your pipeline have trade-specific structure no product ships with? Dealer rebate tiers, utility program paperwork, multi-building commercial accounts with different decision makers per site. This is where configuration stops and building starts.
When a custom build is the honest answer
Not often, and not first. The correct sequence is almost always FSM first, then push its built-in pipeline until it visibly breaks, then decide.
A custom layer makes sense in a narrow case: your operational system of record is fine, your techs are productive on it, but the revenue that has not been sold yet has structure the market does not serve. The mid-sized commercial shop above is the archetype. Their dispatch was not the problem. Four estimators coordinating across QuickBooks, Team Up, Dropbox and Excel was the problem, and no off-the-shelf product was going to hold a job numbering scheme spanning service, preventative maintenance and construction in one sequence.
What that build actually is, in practice, is small: an opportunity object, a stage model that matches how you really sell, a follow-up engine, and a two-way sync so a won opportunity becomes a job without anyone retyping an address. Any proposal that starts by replacing your field software should be treated with suspicion.
If you are weighing that path, why CRM implementations fail is worth reading first, because the failure modes are almost never technical.
The bottom line
The CRM versus field service software question dissolves once you stop treating it as a product comparison. Both categories are real, they model different objects, and which one you need is set by your revenue mix rather than your truck count.
Run the number. If most of your work arrives already sold, buy field service software and put your energy into technician adoption. If a real share of your revenue has to be won first, understand that your FSM platform will happily let those opportunities die without a single error message, and that across 163,212 HVAC campaigns the difference between systematic follow-up and none was a response rate spread of 17.82 to 90.06 percent.
The spreadsheet on your estimator's desktop already told you which situation you are in. It just did not tell you why.
Sources
- Hatch, "New Data: HVAC Estimate Follow-Up Response Rates," analysis of 163,212 HVAC estimate follow-up campaigns, including the John Wilson interview: usehatchapp.com
- Field Ascend, "FSM vs CRM for U.S. Trade Contractors," on the definitional split between the categories: field-ascend.com
- ServiceTitan, "Commercial HVAC CRM: How to Choose the Right Software," on opportunity tracking, agreement templates and proposal version control: servicetitan.com
- BDR, "The Best HVAC CRM Software In 2026: A Profit-First Buyer's Guide," on CRM tools being included in FSM software: bdrco.com
- r/HVAC, "HVAC Field Management Software Recommendations," 20-tech contractor quoting in Excel: reddit.com
- r/hvacadvice, "Mid-Sized Commercial HVAC Company - Software Advice," 30-person team across QuickBooks, Team Up, Dropbox and Excel: reddit.com
- r/hvacadvice, "CRM And Job Management Software," on fixed price contracts versus time and materials: reddit.com
- r/HVAC, "Accounting/CRM software for both new construction AND service work?" on the service versus construction software split: reddit.com