These guides are the method we use on CRM projects, written out so you can use it yourself. Each one covers one stage of a setup, in the order you would do them. They are vendor-neutral and assume only that your CRM supports custom fields, pipelines and tasks, which almost every modern system does.
-
Getting your team to use the CRM: a 90-day adoption plan
Train a champion first, then the office, then the field. Measure completed fields and closed tasks every week, fix the screens people struggle with, and make the owner the first one to work from the system.
-
The HVAC CRM blueprint: fields, job types and pipeline stages
Design four record types, keep the intake screen under ten required fields, give every stage an exit rule and use pick lists for anything you want to count. That is most of a good HVAC CRM.
-
Cleaning and importing customer and equipment history
Inventory every source, decide the structure first, clean addresses and phones, match duplicates on several signals, parse equipment notes into fields, test a sample and reconcile the counts.
Guide 1: Fields, job types and pipeline stages
The HVAC CRM blueprint: fields, job types and stages shows how to decide what your CRM records and how a job moves through it. It covers the four record types an HVAC CRM needs, the short list of intake fields that CSRs will actually fill in, how to define estimate stages with exit rules, and how to pick lost reasons you can report on.
You'll learn: why customers and service sites should be separate records, how to keep required fields under ten, and how to write a stage definition nobody can argue with.
Best for: anyone setting up a new system, or living with one where every person uses the statuses differently.
Guide 2: Cleaning and importing equipment history
Cleaning and importing customer and equipment history is a step-by-step method for getting years of records into a new CRM without duplicates. It covers building a source inventory, normalising Canadian addresses and phone numbers, matching duplicates, parsing equipment notes into fields, test loads and reconciliation.
You'll learn: a duplicate-matching approach that uses several signals together, how to handle landlords and multi-property owners, and what to do with records you can't confidently match.
Best for: companies moving off old dispatch software, merging systems after an acquisition, or replacing a spreadsheet.
Guide 3: A 90-day adoption plan
Getting your team to use the CRM: a 90-day plan covers the part most setups skip. It lays out a week-by-week sequence from launch to habit: champion first, then office roles, then field roles, then weekly usage checks and small fixes.
You'll learn: which numbers show real use, how to handle a technician who refuses the app, and why the owner's own habits decide whether everyone else follows.
Best for: any company launching a CRM, or rescuing one that people have quietly abandoned.
How to use these guides with your team
Read each guide yourself first, then share it with the person who will act as your internal champion. Work through the fields and stages guide together in one sitting, ideally with a CSR and a technician present, because they will spot the fields that don't make sense on a busy day. Use the import guide as a checklist during the migration, ticking off each step. Give the adoption plan to your managers before launch, so everyone knows what will be measured and why.
You don't need to finish everything at once. Many companies spend a few weeks on structure, a few more on the import, and then launch with training. What matters is the order: structure, data, then people.
What the guides don't cover
The guides don't compare CRM products, recommend a vendor or explain how to configure specific software menus. Every system differs, and settings change with updates. For choosing software, our sister site HVACSoftware.ca is a buyer's guide. For configuration, your vendor's help centre is the place to look, and our services fill the gap between the two.
How the guides connect to our services
Each guide maps to a service. The first matches the CRM blueprint, the second the data import and the third training and adoption. If you'd rather have the work done, the services overview explains how each is scoped.
A note on facts and sources
Where a guide mentions a Canadian law or program, such as privacy or anti-spam rules, it links to the official source and is dated. Rules and programs change, so confirm current details with the administrator or your own advisor. We summarise; we don't give legal advice.
Questions about a guide? Contact us by call, text or email.
Frequently asked questions
Do the guides apply to any CRM?
Yes. They are written to be vendor-neutral. The structure, cleaning rules and adoption steps work in any system that supports custom fields, pipelines and tasks.
Which guide should I read first?
Start with the fields and stages guide. The import and adoption guides both assume you have agreed on structure first.
Can I use these guides with my own team instead of hiring you?
Yes, that is what they are for. If you get stuck, call, text or email and we can talk through the part that isn't working.