Ask a fire protection contractor where repair work comes from and you’ll often hear the same answer: our own inspections. A technician finds a failed device or another deficiency, writes it up, and the report goes to the office. What happens next decides whether that finding becomes an approved repair, sits in a PDF until the next inspection finds it again, or gets quoted by another contractor first.
A generic sales CRM tracks leads, calls and deals. A fire protection sales CRM also has to see inspection results, because that’s where much of the pipeline starts. This guide walks through the fire protection sales process, from deficiency follow-up to renewals, for US fire protection contractors with an office team and 10 or more technicians. We build Forz, so the last section says where Forz fits and where it doesn’t.
One boundary: how findings are classified, and what must be reported to an owner or authority having jurisdiction (AHJ), comes from the code edition and local rules you work under. This post covers the sales side only. For inspection intervals, see our NFPA 25 and NFPA 72 frequency charts.
Where the fire protection sales process starts: three sources
Most fire protection sales come from three places, and each needs its own pipeline view:
- Deficiency repairs from your own inspections and service calls. You already have the relationship, the access, and the evidence. The work is turning a finding into a priced quote the customer can approve quickly.
- Agreement renewals and expansion. Inspection and service agreements come up for renewal, and accounts add buildings or systems.
- New accounts. Bids, referrals, and website requests. This is what a generic CRM is built for.
The first stream is the one a stand-alone sales tool can’t see. If the CRM doesn’t know a device failed on Tuesday, nobody gets a task to quote it.
The deficiency-to-repair pipeline, stage by stage
Treat every deficiency like an opportunity with an owner and a next step. The table below is a stage structure you can copy. The stage names are suggestions, so rename them to match your shop.
| Stage | Starts when | Owner | Exit when | What the system should record |
|---|---|---|---|---|
| 1. Found | Tech records a failed device or a finding | Inspector | Finding has a photo, location and description | Device, site, system, result, photo, date |
| 2. Reported | Inspection report goes to the customer | Office | Customer has the report | Report date and recipient |
| 3. Quoting | Office or estimator starts pricing | Estimator or service manager | Quote sent | Line items, scope, customer PO reference |
| 4. Sent / viewed | Quote delivered | Estimator | Customer accepts or declines | Sent date, viewed date, follow-up tasks |
| 5. Approved | Customer accepts in writing | Office | Job created | Acceptance time, signature or PO |
| 6. Scheduled | Repair job on the calendar | Dispatcher | Repair completed | Job date, technician, parts |
| 7. Closed | Repair invoiced | Billing | Invoice paid | Invoice and payment |
Watch two handoffs closely. Found → Quoting: if the finding reaches the office as a line on a PDF, someone retypes the device, location and scope before pricing it. Approved → Scheduled: an approved quote that never becomes a job is revenue won and not collected. A good system carries the site, system and line items across both without retyping.
Who prices the repair? Some shops have inspectors quote simple repairs on site; others route everything to a service manager or estimator. Either can work, as long as the stage has a named owner and the quote is built from the finding, not from memory.
Deficiency follow-up without nagging
Quotes go quiet for ordinary reasons: the property manager needs a PO, the owner wants to bundle repairs, or the email went to the wrong contact. A few rules keep them moving:
- Send to the right person. The person who approves work at a building isn’t always the one who receives the inspection report. Record the decision maker and billing contact separately.
- Set a follow-up window and automate it. Pick a number of business days after a quote is sent and have the system create a task if it’s still open. Base the number on your own history.
- Use “viewed” as a signal. A quote that’s been opened but not approved calls for a different conversation than one that was never opened.
- Make approval easy. An online accept button, a place for the customer’s PO number, and a signature on file remove most of the back-and-forth.
- Keep the safety framing honest. An open deficiency matters because of the building’s protection, not because of your sales quota. Explain what was found and why it matters, and let the customer decide on the repair. If a finding takes a system out of service, handle it through your impairment process first; the quote follow-up comes second.
Contract renewals as a pipeline
Renewals are the quietest part of fire protection sales, and a missed one loses an account you already won. Run them like a pipeline, not a calendar reminder:
- Record each agreement’s renewal date as a field on the customer or site so you can filter and report on it.
- Build a renewal call list well before the dates come up, assign reps, and log each outcome.
- Use renewal calls to check coverage: new buildings, added systems, or services the customer buys from someone else.
- Track renewals won, lost and still open, by rep and by month.
Fire protection sales KPIs (with formulas)
We don’t publish industry benchmarks for these, and you should be wary of anyone who does without showing their data. Measure your own baseline over the last full quarter, then track the trend.
| KPI | Formula | Why it matters |
|---|---|---|
| Quote rate | Deficiencies quoted ÷ deficiencies found | Shows whether findings reach pricing at all |
| Time to quote | Days from inspection completed to quote sent (median) | Slow quotes go stale before the customer reads them |
| Approval rate | Quotes accepted ÷ quotes sent (count and value) | Tests pricing, scope and follow-up |
| Time to approval | Days from quote sent to accepted (median) | Shows where follow-up rules help |
| Stale quotes | Open quotes older than your follow-up window (count and value) | Your work-in-progress list for the week |
| Approved, not scheduled | Accepted quotes with no scheduled job | Won revenue at risk |
| Repair revenue per inspection | Invoiced deficiency-repair revenue ÷ inspections completed | Ties the inspection program to sales |
| Renewal rate | Agreements renewed ÷ agreements up for renewal | Protects the base |
| Weighted pipeline | Sum of (deal amount × win probability) | A forecast instead of a wish list |
A worked example
Here’s how the pipeline looks for one account, using a multi-building customer like a university campus. Each building is its own site, with its own systems, inspection schedule and on-site contacts.
- During a scheduled inspection at one building, the technician records a failed device, attaches a photo, and notes the location.
- The inspection report goes to the building’s facilities contact. The failed device creates a follow-up item for the office.
- The estimator builds the repair quote from that finding, with the site, system and device already attached, and sends it to the campus decision maker with the PO reference field ready.
- The quote is viewed but not approved. On the follow-up day, the system creates a task for the estimator, who calls and learns the campus wants to bundle repairs across two buildings.
- The revised quote is accepted online and the campus PO number is added. The accepted quote becomes a repair job with its line items, and the dispatcher schedules it.
- The repair is invoiced, and the account’s upcoming renewal is already on the renewal call list.
Now the KPI math. Illustrative example, not industry data: the round numbers below only show the arithmetic. Say last quarter’s inspections produced 100 deficiencies. You quoted 70 (quote rate 70%) and customers approved 42 (approval rate 60% by count). Six approved quotes still have no scheduled job. Those six are this week’s first calls, before any new quote goes out. For the forecast, a $10,000 deal at a 60% win probability counts as $6,000 in a weighted pipeline.
What to require from a fire protection sales CRM
Use this list in demos. Each item is something the software should do without a spreadsheet beside it:
- Sees inspection results. A failed device on an inspection can start a quote, with the customer, site, system and device carried over.
- Multi-site accounts. One customer, many buildings, each with its own contacts, systems and history.
- Contact roles. Decision maker, billing and technical contacts recorded separately, and one person linked to several buildings.
- Online approval with a record. Customers accept quotes online, with the time recorded, a signature or PO on file, and view history.
- Quote to job without retyping. An accepted quote becomes a job with its line items.
- Automated follow-up. Rules that create tasks or send emails when a quote’s status hasn’t changed, or a set number of days before a renewal date.
- Renewal call lists. Lists of customers with expiring agreements, assigned reps, scripts and logged outcomes.
- Pipeline and forecast. Your own stages, deal amounts, win probability and a weighted total.
- Reporting. Open quotes by status, amount, age and owner, without exporting to a spreadsheet.
Where Forz fits (and where it doesn’t)
Forz keeps sales and operations in one system. Here’s what our live pages describe against the list above:
- A Fail result flags the device for follow-up. The office quotes the repair, the customer accepts it in the portal, and the accepted estimate converts to a job with the customer, site, system and line items copied over. See fire inspection software.
- In the CRM, leads move through your own stages, and Convert to Customer carries contacts, sites, tasks and deals across. Deals carry an amount, win probability and weighted amount. Contacts link to several customers and sites with roles such as Billing and Decision Maker. Call lists hold scripts, reps and your own outcomes. See field service CRM.
- Estimate statuses move through Draft, Sent, Viewed and Accepted or Declined. There’s a reference field for the customer’s PO number, and signatures are stored on the estimate. See estimates.
- For follow-up and renewals, When-If-Then workflows on estimates, leads and customers can trigger on a status change or a set number of days before or after a date on the record, then add a task, apply a label or send an email. Date custom fields can go on customers and sites. See workflow automation.
- Custom reports on estimates, jobs, customers and invoices can be filtered by status, amount, assignee and labels, and dashboards keep the numbers in view. See reporting dashboards.
- Leads, deals, call lists and customer records are included in every plan: $50 per user per month billed annually or $60 month-to-month, with a 10-user minimum (pricing).
Forz is not the right fit if:
- You have fewer than 10 users and don’t want to pay for the 10-user minimum.
- You want a dedicated sales performance dashboard today. It’s on our roadmap as planned.
- You need live margin on each repair job. Our job costing module is on the roadmap and in progress.
- Your sales team lives in a separate enterprise CRM you won’t replace, and you only need inspection software.
For the wider operations picture, see field service management for fire protection companies. Weighing platforms? See our fire protection software roundup and switching from an inspection-first platform. The inspections that feed the pipeline run on forms like our NFPA 72 inspection form and NFPA 25 sprinkler checklist; more on our fire protection industry page.
FAQ
Do fire protection companies need a separate sales CRM?
Not if the field service system can do the sales work. A separate CRM means re-keying won accounts and quoting without the inspection results behind each repair. What you need is a pipeline from inspection to paid repair, plus renewal tracking. In Forz, the sales CRM for fire protection ties every customer, site and contact to the work.
How fast should a deficiency be quoted?
There’s no universal number for quoting. Correction deadlines set by your AHJ or your contract are a separate question. Measure your median time from inspection to quote, then set a target your office can hold. The point is a written rule and a report that shows when you miss it.
