Client history and equipment history are 2 different records and only 1 of them gets kept properly. The equipment has a file.

Every product can send a notification.

Maintenance software has 3 jobs in a commercial kitchen: hold an interval per piece of equipment rather than per address, produce a task list that yields comparable results, and prove the visit happened.

Residential scheduling optimizes a route.

Refrigeration assets carry 4 things other kitchen equipment does not: refrigerant type, charge size, per-visit quantities added or recovered, and readings that only mean something as a series.

Technicians resist time tracking for reasons that are usually correct.

A commercial kitchen offers 3 windows and only 1 of them is convenient for you.

9 clauses cover a service agreement properly and 3 of them cause almost every dispute: what equipment is covered, what counts as included, and what happens when the portfolio changes.

An estimate is a priced expectation. A proposal argues for a scope and a price together. For commercial kitchen work neither label decides the outcome.

1 broken fryer produces 2 records in 2 systems owned by 2 companies. The restaurant's system tracks a request and a cost.

"Restaurant software" covers 6 categories and 5 of them are bought by the restaurant.

A single kitchen can hold 3 ownership positions at once: units the restaurant owns, units leased from a finance company, and units placed by a supplier as part of a supply agreement.

The pain starts around your third or fourth technician, and what breaks is not scheduling.

A service company runs 4 software layers and the boundaries between them decide how much double entry it lives with.

Most of the time lost at month end goes to 1 problem: what left the customer and what arrived in the bank are not the same number or the same shape.

A credit note is a document. A customer credit is a balance sitting on an account waiting to be applied.

Being on Desktop is not the constraint most owners think it is, and it should not decide your field platform.

Equipment installed together comes out of coverage together.

The category was built for assets you own and maintain in one building.

Your board and their portals only have to agree on 3 states: accepted, scheduled, complete. Everything else can differ.

One repair touches inventory at 5 points and stock goes untracked at 3 of them: the part taken off the van, the part ordered and then used elsewhere, and the part fitted but never recorded.

A CRM tracks relationships and a pipeline. Inventory tracks physical stock.

Approval is a delegation problem before it is a software problem.

A purchase order feature has 7 jobs, and the one that decides the rest is carrying cost onto the job it was created for.