
A CRM is built to win customers. A refrigeration contractor's customers are already won, and an account has 4 layers: the customer, the sites, the assets and the contract. A CRM models the 1st well and the last 2 not at all, which is where the relationship actually lives.
CRM as a category answers a specific question: how do we turn strangers into customers and track that process.
A refrigeration contractor with eighty accounts has a different problem. The customers exist, the equipment is installed, and the question is whether they call you next time and whether they renew.
Which means the thing holding an account together is not a contact history. It is the record of their equipment, what has happened to each one, and what is coming.
| Layer | What it holds | Does a CRM model it? |
|---|---|---|
| The customer | Who decides, spending limits, payment behavior | Yes, and this is its strength |
| The sites | Access, service hours, keys, plant room locations | Partly, usually as addresses |
| The assets | Each unit by serial, with refrigerant, charge and history | No |
| The contract | Covered equipment, intervals, exclusions, renewal date | Rarely, and not tied to assets |
Rows three and four are where a refrigeration relationship lives, and they are the two a CRM was never asked to hold.
The claim this article rests on, and it is specific to equipment trades.
What keeps a refrigeration customer is that you know their equipment better than anybody else does, including them. Which unit is fifteen years old, which one has been charged three times, which one is due for replacement next year.
That knowledge is what makes the annual conversation a planning meeting rather than a price review, and it is held in the equipment records rather than in a contact log.
Roopairs tracks manufacturer, model, serial, service history, location history and warranty agreements on the equipment record with planned maintenance held against it, which is the version of an account record this trade actually needs.
A CRM's account view answers who you spoke to and when. It does not answer which of their fourteen equipment is about to fail, and that is the question that retains the account.
The refrigeration-specific reason the category misfits.
Refrigerant type, charge size, quantities added or recovered per visit, and leak history with repair attempts. Those attach to a specific appliance and they have record-keeping weight rather than commercial weight.
No CRM models them, and it would be an odd thing for one to attempt. They belong on the asset alongside the service history, where a technician and a dispatcher can both see them.
Which produces a practical consequence for a contractor evaluating a CRM: the records with the most consequence attached would live outside it, which makes it a partial system for your most regulated work.
Two cases, and being fair about them matters.
Chasing multi-site contracts through a long cycle, with a tender date, several stakeholders and a decision months away, is a pipeline. That is what CRM is good at and a spreadsheet handles it worse.
And a contractor with a genuine outbound sales function, building a book from a standing start, has volume and follow-up to manage that an equipment record does not touch.
Both are real. What they have in common is that they end at the point the customer says yes, which is where the asset register takes over.
And they are driven by dates on contracts and equipment.
A refrigeration contractor's growth comes disproportionately from three moments: a contract renewal, a manufacturer warranty expiring, and a piece of equipment reaching a replacement decision.
All three are dates. All three sit on the contract or the equipment record. None of them is a marketing activity, and a CRM's campaign machinery has almost nothing to do with them.
What is worth building instead is a short report: contracts ending in the next six months, coverage expiring next quarter, and units where repair spend is approaching the replacement case. That is the pipeline in this trade, and it comes from the asset side.
Two checks, and one boundary to agree.
Ask what a specific piece of equipment has had done to it over three years. If the answer is a search through notes, you have contact history where you need equipment history.
Ask what refrigerant was added to that unit and when. If nothing answers it, the compliance record is somewhere else and probably on paper.
Then agree the boundary rather than replacing anything. The CRM holds prospects and opportunities up to winning the account. The service system holds everything after, including the customer record itself, because that is where the sites, assets and contracts live.
What does not work is both holding live customers. They diverge within weeks, and the version the technicians see is the one that matters while the other is the one being maintained.
The requirement list, stated plainly.
A product covering those five is doing the account management job. One covering contacts and a pipeline is doing a different job well.
The pain starts around your third or fourth technician.
Below that, a contractor holds the customer relationships and the equipment knowledge in a small number of heads, and a CRM plus a spreadsheet genuinely works.
Above it, both stop fitting. The account knowledge fragments and the equipment history becomes the only durable version of it, which is the point at which the asset register stops being a technical record and becomes the commercial one.
Roopairs runs a product tour where you can see clients, their sites and the equipment records beneath them.
“Great process getting set up and rolling with Roopairs. We transitioned from a different platform and my crew was able to Master Roopairs with ease.” — Chris Sockriter
For winning new multi-site contracts through a long cycle, yes. For managing existing accounts, the record that holds a relationship together is the asset register rather than a contact history, because what retains a customer is knowing their equipment.
Assets by serial with service history, and contracts tied to named equipment. Those are the two layers a refrigeration relationship actually lives in, and neither is something a CRM was built to model.
Because refrigerant type, charge, per-visit quantities and leak history attach to a specific appliance and carry record-keeping weight. No CRM models them, which would leave your most regulated records outside the system.
Chasing multi-site contracts with tender dates and several stakeholders, and building a book from a standing start with real outbound volume. Both end when the customer says yes, and the asset register takes over there.
Three dates: a contract renewal, a manufacturer warranty expiring, and a piece of equipment reaching a replacement decision. All three sit on contracts or equipment records rather than in campaign tooling.
Yes, with a boundary. The CRM holds prospects up to winning the account and the service platform holds everything after, including the customer record. Both holding live customers means they diverge within weeks.
The all-in-one platform built for commercial kitchen service companies. Dispatch, invoicing, parts ordering — all in one place.
Book a product tour →