The CRM Problem in Field Service Isn't Software. It's the Notebook.

A quote request comes in by phone and lives in one person's notebook until it goes cold.

That's the whole problem. Not that contractors lack a CRM. Not that they haven't tried a CRM. The problem is that the customer call lands somewhere informal, gets handled by whoever picked up, and then sits in the memory or the notes app or the spiral-bound pad of a single human being. If that person gets slammed with a service emergency, which, in a mixed service-and-project shop, happens every week, the follow-up never happens. The opportunity doesn't die loudly. It just quietly disappears.

Why Trade Contractors Have a Harder Sales Problem Than They Think

Most field-service businesses don't think of themselves as having a "sales process." They answer phones, send quotes, do the work. But in a shop doing both reactive service and planned projects, the sales surface is wide.

A facilities manager calls about a mechanical issue at a Mississauga property they manage. You fix the immediate problem. During the visit, your tech notes that two RTUs are approaching end-of-life. Someone mentions it in the truck on the way back. It never makes it into a quote.

Or a general contractor you've worked with in Brampton sends an email about a new build. You respond, send a rough scope, say you'll follow up after you pull the permit timelines. Three weeks later, three service emergencies and one change order dispute have buried it.

This isn't a pipeline problem. It's an information retention problem. The customer exists in too many places at once: in dispatch's head, in the owner's inbox, in a spreadsheet someone started and forgot to update. Nobody has the full picture, so nobody acts with the full picture.

The Three Handoffs Where Opportunities Go Cold

In most mid-sized trade shops (20 to 150 people), a customer interaction touches at least three people before it becomes a job. Here's where it breaks:

1. The intake call. A service coordinator takes the call, writes down the customer name, address, and rough scope. This lives in a call log, a sticky note, or a text to the owner.

2. The quote. Someone, the owner, a PM, or an estimator, builds the quote in a spreadsheet or a proposal tool that isn't connected to the intake record. The quote goes out. The CRM record (if one exists) doesn't update.

3. The follow-up. This is the one that breaks most often. Nobody owns it formally. If the person who sent the quote is on a job site in Scarborough for two weeks, the follow-up depends entirely on whether they remember to do it.

The result: quotes expire, prospects go with someone else who called them back, and the opportunity never even shows up as lost because it was never tracked to begin with.

What a Proper Customer Record Actually Looks Like

This is where the mechanics matter. A customer record that prevents the above isn't just a name and a phone number. It needs to hold, in one place, all of the following:

• Site history: what work has been done at this location, when, by whom, and what was found. If a tech visited that Mississauga property six months ago and flagged the aging RTUs, that note needs to be readable by whoever picks up the next call.
• Open opportunities: what quotes are outstanding, what the dollar value is, when they were sent, and when follow-up is due.
• Contacts at the site: who the facilities manager is, who signs off on scope, who the billing contact is. These are often three different people at a larger account.
• Cross-functional visibility: dispatch needs to know if a site visit is part of an active sales cycle before they schedule a routine service call. Finance needs to see the open quote before they can forecast the month.

When these pieces are in separate systems, or in one person's notebook, none of those conversations happen. The left hand doesn't know what the right is doing.

How PolarPath Handles It

PolarPath's customer intake and CRM keeps the customer, the site, the history, and the open opportunity in one record that dispatch and finance can both see.

That's the whole mechanic. When a call comes in, the record gets created or updated right there. The open quote attaches to it. The site history is already there if the customer has worked with you before. The next follow-up gets logged against the opportunity, not against someone's memory.

A dispatcher booking a service visit can see that an open proposal exists for that site. A controller running end-of-month can see which proposals are still outstanding and what the combined value is. The owner can look at the pipeline on a Monday morning and see exactly which opportunities are aging past follow-up.

Nobody has to ask anyone else what's happening with an account. The record holds the answer.

A Practical Framework for Tightening Your Sales Process

Whether or not you use PolarPath, here's how to think about fixing the notebook problem in your shop:

1. Define one place the intake lives. Phone calls, emails, and walk-ins all need to land somewhere structured. If it's a spreadsheet, that's fine, as long as everyone uses it and it's visible to more than one person.

2. Attach the quote to the customer, not to the quoting tool. The quote should be findable by anyone who looks up the customer. If your quoting tool is disconnected from your customer list, you will lose track of open opportunities.

3. Own the follow-up with a date, not a reminder. "Follow up next week" is not a follow-up. Assign a specific date, assign a specific person, and make both visible to the team.

4. Make site history available to dispatch before they schedule. If dispatch is booking a service call without knowing a proposal is open at that site, you're creating the conditions for a missed conversation.

5. Review open opportunities weekly, not quarterly. A weekly five-minute scan of what's outstanding (and what's aging) will catch more revenue than any new tool will.

The Takeaway

The notebook isn't the villain. It's just the symptom of a system where customer information belongs to a person instead of to the business.

When the customer record, the site history, and the open opportunity live in the same place and are visible to the people who need them, follow-up stops being a memory exercise. It becomes a workflow.

That's the shift worth making, and it's less about software than it is about deciding that customer information is an operational asset, not a personal one.

If you want to see how PolarPath's CRM and customer intake fit into a field-service and project shop, polarpath.ca is where to start.