How to Choose a Platform for a Commercial Service Company

Choosing a platform for a commercial service company is 4 decisions in sequence, and most service companies make them backwards. Start with who approves the money, then what happens between the diagnosis and the payment, then what your records have to hold, and only then price. Getting the order right eliminates most of the market.

The short version

Almost every guide on this question starts with a feature list. That is the wrong end. Feature lists are how vendors describe themselves, and every product in this category has scheduling, dispatch and invoicing, so comparing them compares the things that are identical.

The decisions that actually eliminate candidates are about your business rather than about the software, and they have an order:

1. Who approves the money. This decides how work arrives and how it gets paid.
2. What happens between the diagnosis and the payment. This is where commercial work has steps residential work does not.
3. What your records have to hold. Customers change. Equipment does not.
4. Price. Last, and for a reason.

Work through them in that order and the shortlist is usually two or three products by the end of the second one.

Commercial work has 4 parties, and only 1 of them calls you

This is the difference the word commercial is doing, and it is the reason residential-first software fits awkwardly. A residential service call has one party. They notice the fault, they let you in, they approve the cost, and they pay. One person, one decision, one transaction.

Commercial work usually has four:

Party	What they do	What they need from you
The person who notices	Reports the fault. A kitchen manager or a shift lead	Speed, and to be told when you are coming
The person who approves	Authorizes the spend, often with a cap	Enough detail to create a purchase order without asking
The person who pays	Accounts payable at a head office, weeks later	A clean invoice that matches their purchase order
Sometimes a manufacturer	Covers the part or the labor under warranty	Their paperwork, their timeline, their labor rate

Software built for one party assumes the caller is the payer. Every mismatch downstream comes from that assumption, and no amount of configuration removes it.

Decision 1 is who approves the money, not what the software does

Answer this first because it determines which product category you are even shopping in.

Ask three questions about last month's work:

• How much arrived without a phone call? Through a facilities management portal, a standing contract, or a manager who already had your number. If most of it did, features built around being found are not your gains.
• How often was the approver someone you have never met? If a facilities manager you have not spoken to approves your quotes, the document has to be complete on its own.
• How many of your invoices went to a head office rather than to the site? That one number tells you whether your receivables cycle is days or weeks.

If the answers point at portals, remote approvers and head offices, you are buying commercial service software rather than field service software in general, and the shortlist is much smaller than the category suggests.

Decision 2 is what happens between the diagnosis and the payment

This is where the money leaks, and it is the part of the workflow that vendors demonstrate least. A residential call ends at the invoice. A commercial repair has a chain in the middle.

The chain, in order:

1. The fault is diagnosed and the part is identified from the nameplate
2. A quote or an authorization goes to the approver, often against a spending cap
3. A purchase order is created with a supplier, against this job
4. The part arrives, is received, and is issued to a technician or a van
5. The part is fitted, and the cost lands on the job it belongs to
6. The customer is invoiced, and the supplier's bill arrives afterwards
7. The supplier bill is matched to the purchase order and reaches the books

Every product in this category handles steps 1, 2 and 6. Fewer handle 3, 4, 5 and 7, because a homeowner service call does not have them. Purchase orders created inside a job, parts inventory across the warehouse and every van, and vendor bills reaching accounts payable are the four capabilities that follow from commercial work, and they are the ones worth testing rather than reading about.

Ask any vendor to walk one job through all seven steps live. A product that handles the whole chain shows you in ten minutes. A product that does not will show you steps 1, 2 and 6 very well.

Decision 3 is what the record holds when the customer changes

Commercial customers churn at the contract level and the equipment stays where it is. Franchisees change hands, facilities contracts go out to tender, and managers move on. The equipment in the corner of that kitchen is the same piece of equipment.

So the data model question is whether history attaches to the customer, the site, or the equipment. Attach it to the customer and a contract change erases your own institutional memory. Attach it to the site and the same unit becomes a new record every time somebody books it against the address instead.

The specification worth holding any product to is whether the equipment record carries manufacturer, model, serial number, service history, location history and warranty agreements, and whether planned maintenance contracts sit against the equipment rather than against the address. Six attributes on the unit itself, and location history is the one most often missing.

Bring a real case to the demo: a piece of equipment with several visits behind it. Ask to see its full history in one place. If the answer involves searching two customer records, that is the answer.

Decision 4 is price, and it comes last for a reason

Price is the easiest thing to compare and the least useful thing to compare first. Not because it does not matter, but because a cheaper product that needs a workaround at step 4 of the chain costs more within a year.

When you do get to it, three things make the comparison honest:

• Price the team you have. Per-seat and per-company models cross over somewhere around six or seven users, so the cheapest product at two technicians is often not the cheapest at eight.
• Price the modules you would turn on. Inventory management and job costing are add-ons on some products in this category, and for commercial service work they are not optional.
• Price the second year. Introductory rates and annual discounts are normal here. The number you live with is the one after the first twelve months.

Two vendors in this category quote per business rather than publishing tiers, so part of this decision needs a phone call regardless of how much reading you do.

Doing it backwards costs a year, because switching costs history

The common sequence is price, then features, then a demo, then a decision. That produces a shortlist of the cheapest products that tick the most boxes, which is a list of general products, because general products have more boxes.

The cost of getting it wrong is not the subscription. It is the second migration. Customers and locations usually move between systems. Equipment records, open purchase orders and warranty agreements often do not, and those are the ones that cannot be rebuilt from a spreadsheet.

That asymmetry is why the order matters. A wrong decision on price is recoverable in a month. A wrong decision on the data model costs you the history you have been accumulating since you started.

How to test the shortlist in one afternoon

Pick one job from last month where the work went fine and the paperwork did not. That job is your test case and it is more informative than any feature matrix.

Good candidates: a part ordered for one customer and fitted at another, a warranty claim that took three weeks to get paid, a quote that died in an approval queue, or an invoice disputed because it exceeded an authorization nobody could find.

Walk that job end to end through each product. Watch for the moment somebody says "you would handle that outside the system". Note it. That moment is the product's boundary, and your job is to find out whether the boundary sits inside your week.

Roopairs is built for commercial kitchen and refrigeration equipment service, which is the case where all four decisions above point the same way. Their shorter guide to running a software selection covers the process side, and their product tour is where you can bring that job and follow it from the portal ticket to the supplier bill.

What service companies in the trade say

“Roopairs is a top notch software that is enabling us to better serve our restaurants!!! From the Estimate to Job automation, to the Inventory and Invoicing, Roopairs is just what we needed to take our service to the next level.” — Clif Schrock

Also worth reading

• Commercial Food Equipment Service Software Guide
• 4 Davisware Alternatives for Kitchen Service
• Should I use OEM or non OEM commercial kitchen parts

Frequently asked questions

What is the difference between commercial and residential field service software?

The number of parties in the transaction. Residential software assumes the person who calls is the person who pays. Commercial work separates those roles and adds an approver with a spending cap, an accounts payable department, and sometimes a manufacturer covering part of the cost. Everything else follows from that.

Do I need software specific to my trade?

It depends on whether your work carries a parts chain. If most jobs are one visit with parts the technician carried, general software fits well. If a typical job involves ordering a part against a purchase order, receiving it, and reconciling a supplier bill afterwards, that chain either exists in the software or lives in a spreadsheet beside it.

How long should choosing take?

Two to four weeks of real work, not months. Most of the time goes into two things: answering the four decisions honestly about your own business, and running one real job through two or three products. Reading review sites and feature comparisons expands to fill whatever time you give it and rarely changes the answer.

What should I ask on a demo that a feature list will not tell me?

Ask to see a purchase order created inside a job with the cost landing on that job when the part is received. Ask to see everything that has ever happened to one piece of equipment. Ask what happens when a part is ordered and not used. Then ask what the product does not do for your trade.

Is it worth switching if the current system mostly works?

Usually not, unless one specific thing has become somebody's daily job. Reconciling parts by hand, chasing warranty claims, or rebuilding equipment history out of old invoices are the three that justify the cost of moving. If none of those describes your week, the switch costs more than it returns.

What is the most common mistake in this decision?

Comparing the parts of the products that are identical. Every platform schedules, dispatches and invoices, so a comparison built on those is a comparison of pricing pages. The parts that differ sit between the diagnosis and the payment, and they are the ones a demo has to cover.