## The CRM Doesn't Fit Service companies — the ones that install, maintain, and repair equipment at customer locations — have a data problem that CRMs weren't designed to solve. A CRM tracks relationships: contacts, deals, communication history, pipeline stages. That's useful for sales. But once the deal closes and equipment gets installed, the CRM's data model falls apart. You need to track: what equipment is installed where, when it was installed, what serial number it has, which firmware version it runs, when it was last serviced, what parts were replaced, when the next maintenance is due, and what the customer's service contract covers. Try fitting all of that into "custom fields" on a CRM contact record. It gets ugly fast. ## What Service Companies Actually Track Talk to any service company owner and they'll describe a similar set of data needs: **The installation register.** Every piece of equipment installed at every customer site. Not just "Customer X has 3 units" but the specific model, serial number, installation date, and configuration details for each unit. **Service history.** Every visit, every repair, every part replaced. Linked to the specific unit, not just the customer. When a technician arrives on site, they need to see what's been done to this exact machine before. **Maintenance schedules.** Preventive maintenance intervals tied to each installation. Some equipment needs annual service, some needs quarterly inspection, some needs service after X operating hours. The system should remind you before things are overdue. **Contract coverage.** What's covered under warranty, what's under a service contract, and what's billable. Getting this wrong means either giving away free labor or billing a customer for covered work — both expensive mistakes. **Spare parts and compatibility.** Which parts fit which equipment version. A technician showing up with the wrong parts wastes a trip, frustrates the customer, and costs real money. ## The Spreadsheet Phase (and Why It Ends) Every service company starts with spreadsheets. They work well for the first 50 installations. Column A: customer name. Column B: equipment model. Column C: serial number. Clean, simple, functional. Then you hit 200 installations across 80 customers. The spreadsheet has 15 tabs, three people edit it, and nobody trusts the data anymore. Someone updates the installation list but forgets to update the maintenance schedule tab. A technician checks the spreadsheet for a serial number and finds conflicting entries. The breaking point usually comes when a customer asks a simple question — "When was the last service on our Unit #3?" — and it takes someone 20 minutes to piece together an answer from multiple spreadsheets and email threads. ## Building a Practical Installation Tracking System You don't need a specialized CMMS (Computerized Maintenance Management System) that costs €5,000/month and takes six months to implement. What you need is a structured data system with the right relationships. **The core structure:** - **Customers** have one or more **Locations** - Each **Location** has one or more **Installations** - Each **Installation** has a **Service History** (list of visits) - Each **Installation** has a **Maintenance Schedule** (upcoming work) - Each **Service Visit** links to **Parts Used** and **Time Logged** That's it. Five entities with clear relationships. Any flexible business platform can model this. **What makes it work in practice:** - Technicians can look up installations on their phone, on site, offline if needed - Adding a service record takes under 3 minutes - The system automatically calculates when the next maintenance is due - Managers see a dashboard of overdue and upcoming maintenance across all customers - Customers can access their own installation history through a portal ## The Revenue Opportunity Most Service Companies Miss Tracking installations isn't just about efficiency — it's a revenue driver. When you know exactly what's installed where and when it needs attention, you can: **Proactively sell maintenance contracts.** "Your Unit X was installed 11 months ago. The manufacturer recommends first service at 12 months. Want to set up a contract?" That's a warm lead based on data, not a cold call. **Identify upgrade opportunities.** Equipment that's been repaired three times in a year might be cheaper to replace. You have the data to make that case to the customer. **Predict parts demand.** If you know you have 200 installations of Model Y, all installed within the same 6-month window, you can predict when they'll all need a specific wearing part — and stock accordingly. **Prove your value during contract renewal.** "Here's a report of the 14 service visits we performed this year, the 3 emergency calls we resolved within 4 hours, and the 2 potential failures we caught during preventive maintenance." That's a compelling renewal conversation. ## Implementation: The 30-Day Plan **Week 1:** Define your installation data model. What fields do you actually need for each installation? Be ruthless — start with 10-15 fields, not 50. You can always add more later. **Week 2:** Enter your top 20 customers' installations. Have technicians verify the data during their next site visits. This catches errors before you scale. **Week 3:** Start logging new service visits digitally. Every visit from this point forward goes into the system, not onto paper. Don't worry about historical data yet. **Week 4:** Set up maintenance schedules for the installations you've entered. Configure reminders. Review the upcoming maintenance dashboard and use it to plan next month's schedule. After 30 days, you won't have migrated everything, but you'll have a working system with your most important customers. The momentum from those first wins makes expanding to the rest of your customer base much easier.