Ask a dealer about their sales pipeline and you'll get a number to one decimal. Ask about their installed base — every machine they've ever sold, where it is, what it's covered by, when it needs replacing — and you'll usually get "it's in a spreadsheet somewhere". That asymmetry is expensive: for most equipment dealers, the installed base generates more margin than new-unit sales, on capital that's already been deployed. This guide covers what installed base management actually involves and how to run it like the asset it is.
What "installed base" means — and why it beats the pipeline
Your installed base is the population of machines you've sold or service, alive in the field, each attached to a customer relationship. It's the OEM-world term (GE, Philips and Siemens run entire divisions on "IB data"), but it applies with full force one level down, at the dealer and distributor layer — arguably more, because the dealer owns the local relationship.
The commercial logic is brutal and simple:
- Service attach is the margin engine. New-unit sales win the customer; parts, contracts, extensions and eventually replacements are where the profit accumulates — often at 2-3× the margin of the original sale, recurring.
- You already paid the acquisition cost. Selling a service contract to a clinic that owns your autoclave converts at a rate no cold outreach will ever touch.
- Every machine is a future deal with a date on it. Warranty expiry, contract renewal, end-of-life — each one is scheduled revenue, visible years ahead, to whoever keeps the data.
The data model: customer-centric, serial-anchored
Installed base management lives or dies on one structural decision: the record is anchored on the serial number, and organized around the customer. Per machine you need identity (serial, model, OEM), location (customer, site, room), the clocks (install date, warranty start/end, extended warranty, useful-life end), coverage (service contract, visits), and the full service history. Per customer, you need the roll-up: every machine, every contract, every open ticket, one screen.
| View | Question it answers | Who uses it |
|---|---|---|
| Customer 360 | "What does Clínica Almada own, and what's covered?" | Service desk, account owner |
| Warranty pipeline | "What expires in the next 90 days, worth how much?" | Service sales (see warranty management) |
| Lifecycle fleet view | "How is the fleet distributed from in-warranty to end-of-life?" | Management (see asset lifecycle management) |
| Machine page + QR | "What is this unit and is it covered?" — answered at the machine | Technicians, the customer |
Servatio imports your equipment spreadsheet with AI column mapping, attaches OEM defaults for 168+ models, and gives you the customer 360, warranty pipeline and lifecycle view on day one.
Start free trialOperationalizing it: from record to revenue
- Consolidate and import. The installed base usually exists in fragments — a sales export, a service log, a warranty sheet. Merge on serial number; let an AI importer map the fuzzy columns and flag the gaps.
- Attach OEM intelligence per model. Standard warranty months, preventive-maintenance cadence, expected useful life. This is what turns a static list into clocks that fire.
- Let the alert engine run. Warranty expirations at 90/60/30 days, contract renewals, EOL signals — pushed to owners with the value at risk attached, not waiting in a filter.
- Put the machine online. A QR code per unit and a customer portal turn the installed base into a service channel: faults get reported against the right serial, quotes get approved in one click, and every interaction lands back on the record. (How that flows into work orders.)
- Manage the lifecycle deliberately. Stage every asset from in-warranty to end-of-life and work the transitions — contracts on expiry, replacement planning a year before EOL.
The metrics that tell you it's working
- Coverage rate — % of active installed machines under warranty or contract. The single best health number; mature dealers run 60-80%.
- Leakage rate — % of expirations that passed with no offer made. The number to drive toward zero (playbook in our leakage guide).
- Service revenue per installed machine per year — the unit economics of the base; watch it trend as coverage climbs.
- Data completeness — % of machines with serial, install date and warranty dates filled. Below ~90%, every other metric is fiction.
Build vs. buy
OEM-grade installed base platforms (ServiceMax, PTC) are six-figure implementations aimed at manufacturers. CRMs hold accounts, not serial-anchored machines — warranty becomes a custom field nobody updates. Spreadsheets hold the data but never act on it. The dealer-shaped answer is vertical software that ships the data model (customer → machine → clocks → history) and the workflows (alerts, pipelines, portal, contracts) out of the box — which is exactly the gap Servatio exists to fill, at dealer pricing ($199-$1,499+/month) rather than OEM pricing.
Frequently asked questions
What is installed base management?
Maintaining a live, structured record of every machine you've sold or service — per serial, per customer — and running commercial workflows (renewals, contracts, replacements) on top of it.
Why does it matter more than the sales pipeline?
Because service attach on machines you already sold converts better and at a higher margin than new-account acquisition — and it compounds: every replacement restarts the clock on a new machine.
What data should each record hold?
Serial, model/OEM, customer and site, install date, warranty and extended warranty dates, contract coverage, service history, lifecycle stage — rolled up per customer into one 360 view.
How do I build one from spreadsheets?
Consolidate what you have, import with AI column mapping, let OEM defaults fill the model-level blanks, fix the flagged rows. Days, not months.