Dispatch software knows where your trucks are. It does not run your lead funnel, your maintenance renewals, your replacement opportunities, or your review pipeline. Strkr is the revenue layer that sits around your field service stack and treats every address as an account that generates revenue for a decade.
HVAC and plumbing shops in the 5 to 50 technician band run into the same wall. Housecall Pro and workyard-tier tools cover dispatch and invoicing well, but they treat the CRM half of the business as an afterthought. ServiceTitan solves most of it, but the price tag and the implementation cost assume a 50 plus tech operation that has a dedicated office administrator and a willingness to invest a quarter in rollout. In between sits a growing shop with real revenue problems the dispatch tool was never designed to solve. The lead funnel leaks. The quote follow-up is inconsistent. The membership plan renewals lapse quietly. The replacement opportunities in the installed base never surface. The review funnel is a hope and a prayer. The after-hours messaging piles up on a voicemail nobody wants to clear. None of these are dispatch problems. All of them are revenue problems, and every one of them lives inside the CRM layer that most shops in this size range never built.
Phone calls, web form fills, Google LSA leads, Angi leads, Facebook form ads, Nextdoor messages, and the dispatcher scribbling on a notepad. Dispatch tools capture the ones that turn into a job today. The ones that need a two week follow-up or a seasonal nudge disappear. A real CRM holds every lead until it closes, cancels, or three years go by.
The tech gives a 7,200 dollar system replacement quote on a service call. Three days later the office is calling to see if the homeowner wants to move forward. Who follows up? What does the sequence look like? What is the win rate on quotes over 5,000 dollars? Most shops cannot answer any of these because the quote lives in the dispatch tool and the follow-up lives nowhere.
A 199 dollar maintenance plan is pure margin until the office forgets to renew it. Many shops run their renewal process on a spreadsheet that gets updated the month a renewal is due, which means the renewals that lapsed six months ago never come back. A real CRM clocks every agreement, fires reminders at 60 and 30 days, auto-books the tune-up, and reports the renewal rate as a number.
Every address has an installed system. Every system has an install year, a tonnage, a brand, a known failure curve. A shop that knows which 400 customers are on systems older than 12 years has a six to seven figure replacement pipeline. Most shops have this data buried in service history notes and never surface it. The dispatch tool was not built to track equipment as a sellable asset.
HVAC revenue is lumpy. Peak cooling in July. Peak heat in January. The shoulder seasons (April to May, September to October) are when maintenance work and replacement planning happen, and they are where margin is made. Most shops run shoulder season campaigns ad hoc, if at all. A real CRM has a timed sequence that fires on the right week every year without a human remembering.
Google reviews drive LSA lead cost and show up above the fold on the brand search. The window to ask for a review is roughly 24 hours after the job wraps, before the homeowner forgets how it felt. Most shops either ask nobody or ask everybody, which turns into a one star from the one job that went sideways. A real review funnel asks the happy customers first, routes complaints internally, and tracks who converted.
Be clear about this up front. Strkr is not a replacement for Housecall Pro, ServiceTitan, FieldEdge, Service Fusion, or any dispatch and routing platform. It does not route trucks, run a tech mobile app, manage inventory on the shelf, or print work orders. It sits around that tool as the CRM, marketing, project tracking, messaging, and reporting layer. Many shops run Strkr with Housecall Pro integrated as the dispatch side.
The account record holds equipment installed, system ages, service history, membership plan status, payment history, open quotes, lifetime revenue, and the family members who live there. A residential account is a household. A commercial account is a property. The data model treats them the same so you can run the whole book.
A new call enters as a lead. Dispatch confirms the appointment and the lead becomes an opportunity. The tech runs the call and sends a quote. The quote becomes an estimate opportunity with a known amount, close date, and probability. Won estimates convert to work orders in the dispatch tool. Lost ones go into a nurture sequence. Nothing falls through.
Each HVAC system, water heater, boiler, and softener is a custom object linked to the account. Install date, brand, model, serial, tonnage, warranty expiration, filter size, refrigerant type. The data lets you query: show me every residential account on an R-22 system older than 11 years inside the 60657 zip. That query is a Saturday morning direct mail list.
A service agreement is a custom object with a start date, end date, plan tier, billing cadence, visits included, and visits used. A nightly flow looks 60 days ahead at every expiring agreement, creates a renewal task, and sends the first touch email. The office stops forgetting renewals because the system remembers them.
Every system has a known failure curve. A system over 12 years old on a residential account has a measurable probability of needing replacement inside 18 months. A nightly flow surfaces those accounts, creates a soft opportunity, and queues them into a replacement nurture sequence. By year two the shop knows exactly how many replacement dollars are in the installed base.
Spring tune-up campaign fires March 15 to April 30 every year to every residential account that had cooling service last year. Fall furnace tune-up fires September 1 to October 15. Pre-cold-snap reminder fires when the 7-day forecast dips below 40 degrees. These sequences compound year over year because they are built once and fire forever.
Job marked complete triggers a 2-hour-delay satisfaction text: how did it go, 1 to 10? Replies of 9 or 10 get the Google review link. Replies of 7 or 8 get a thank you plus a service manager follow-up task. Replies of 6 or below create a complaint ticket for the service manager inside 15 minutes. The 5-star window is used, the one-stars are intercepted.
An after-hours inbound text triggers an auto-response acknowledging the message, a dispatch alert to the on-call tech, and a lead record on the account. The office walks in at 7 AM and sees every after-hours contact already triaged. No voicemail backlog, no customer who assumed the shop is closed.
When an estimate converts to a signed install over 5,000 dollars, a project is created on the account with milestones: permit pulled, equipment ordered, install day, inspection, follow-up at 7 days, follow-up at 30 days. The office sees every active install on a board. Nothing stalls in receiving or waits for an inspection without a flag.
Dispatch and routing tools are built to answer: where is the truck, what is the next job, did the invoice go out? Those are the right questions for a field service tool. The CRM questions sit somewhere else and get neglected because the dispatch tool was never built to answer them.
When a quote over a threshold is sent, Strkr fires a 7-day nurture sequence: day 1 thank you with the written quote, day 3 financing option follow-up, day 7 call-out task to the comfort advisor, day 14 a case study of a similar install. Win rate on quotes over 5,000 dollars climbs 8 to 15 points for shops that run this consistently.
A nightly flow checks every active service agreement. At 60 days from expiration, a renewal task is created on the owner. At 30 days, a renewal email with the one-click accept link fires. At 7 days, the office gets a call-out task. The lapse rate drops from a typical 25 to 35 percent down to 10 to 15, which is pure margin on an existing book.
The 220 residential accounts on systems older than 12 years get a quarterly touch: homeowner tips, financing info, a system health check offer, a case study of a recent replacement. By year two the shop converts 8 to 14 percent of this list into a replacement conversation, which is a six-figure annual revenue line that otherwise sits dormant.
A lost estimate does not die. It goes into a 12-month nurture cadence timed to the system failure curve and the next seasonal peak. Some shops recover 10 to 20 percent of lost estimates on a 6 to 12 month lag just by not letting the record go cold.
Across every job, every tune-up, every membership renewal, every parts upcharge, every replacement, every referral. Most shops have no idea what their average residential customer is worth over 10 years. Strkr rolls it up by zip, by lead source, by referral partner, by system age at acquisition. The number changes how acquisition is budgeted.
The 12 realtors who sent 60 leads last year are a channel. They should get a quarterly touch, a holiday card, a track-record report showing the leads they sent and the revenue produced. Property managers running 40 doors are a channel with a renewal cycle. Strkr treats them as accounts with their own activity history, which turns a casual relationship into a measurable pipeline.
Commercial accounts have service contracts with renewal dates, equipment lists across many buildings, preventive maintenance schedules, and primary contacts who turn over every 18 to 36 months. Strkr tracks the account health, the contact turnover, the maintenance history, and the contract renewal clock. Losing a 20-building property manager because the office never knew the facilities contact changed is a story every shop has.
By tech: average ticket, close rate on quotes, membership plans sold, 5-star review rate, callback rate, revenue per hour. The numbers come from the real data the dispatch tool and the CRM already produce, assembled into a monthly scorecard. The service manager has the coaching conversation with evidence instead of impression.
Strkr integrates with the dispatch and routing side of the house, not against it. A typical HVAC shop running Strkr pairs it with Housecall Pro or another field service platform, QuickBooks or Xero for accounting, and the lead sources that produce the top of the funnel. The integrations are native, API-based, and ship as first-class software, not as third-party automation glue.
Customers, jobs, invoices, and estimates flow bidirectionally between Housecall Pro and Strkr. The dispatcher works in Housecall Pro. The office manager and the owner run reports, campaigns, and renewal engines in Strkr. The tech sees the next job on the Housecall Pro mobile app. Both tools do what they are good at.
Native accounting integration syncs invoices, payments, and customer balances. Strkr uses that data to compute lifetime value, membership plan ROI, and campaign attribution. The accounting data lives in accounting. The reporting lives in the CRM.
LSA leads, Google Ads leads, and organic form fills land in Strkr tagged with the source, the campaign, and the keyword where available. The shop can finally answer: what is the real cost per acquisition for an LSA lead by zip code, net of the leads that never close? The reporting pays for the lead tool.
Native messaging ships as a module with per-tenant numbers. Appointment reminders, on-the-way texts, review requests, after-hours auto-replies, and two-way conversations all land on the account record. Shops that want to keep an existing carrier can bring Twilio credentials; most run native and pay predictable per-message rates with no third-party vendor exposed in customer-facing strings.
The post-job satisfaction survey knows which platform the customer prefers and routes the review request accordingly. Google is the default because of the LSA impact. The review tracker rolls up the volume, average rating, and response rate by platform so the shop can see the real reputation health in one view.
Marketing is a native module, not a third-party send. Seasonal campaigns, newsletters, replacement nurture sequences, review follow-ups, and membership renewal reminders all fire from inside the CRM against the same account records that hold the equipment, the service agreements, and the lifetime revenue. One system, one audience, one bill.
When a replacement proposal needs a signature, the shop sends it through DocuSign or PandaDoc. The signed document and the signature event flow back to the opportunity record and move the stage automatically. Strkr Docs is a wiki for internal process documentation; e-signature runs through the two established tools shops already know.
Strkr does not route trucks, schedule the day on a dispatch board, run a tech mobile app with a time clock, manage inventory on the shelf, or print work orders. Those are the dispatch tool's job. If the shop is on a dispatch tool with a weak API, the integration is thinner. Shops without a dispatch tool should get one before adding Strkr.
A 5 to 50 tech HVAC shop has an operating rhythm that most CRMs do not understand. The office opens at 7 AM. Dispatch is live by 7:30. The first follow-up calls happen at 9. The membership renewals get worked between emergency dispatches. The replacement sales conversation happens at 3 PM when the comfort advisor is back from a 2-hour appointment. Strkr is built for that rhythm.
Overnight after-hours messages, overnight web form leads, overdue estimate follow-ups, memberships expiring in 7 days, replacement opportunities aging past 14 days, callbacks owed from yesterday. One queue, prioritized, assigned. The office does not open five tabs to find the day.
Open estimates by stage and age, scheduled sales appointments for the week, replacement opportunities ripened to a sales call, lost-estimate reactivation list. The comfort advisor runs their own book inside Strkr with their own scorecard and their own forecast.
Per-tech weekly scorecards, open callbacks, complaint tickets opened from the review funnel, membership plans sold week-to-date, average ticket trend. The service manager uses this for Monday morning huddles and quarterly coaching.
Monthly revenue vs plan, replacement pipeline by month, membership plan count trend, lead source cost and quality, lifetime value by zip, year-over-year on the shoulder seasons. The owner opens the dashboard, reads it, and goes to bed.
The dispatcher runs in Housecall Pro or whichever dispatch tool. Strkr pushes the lead context (new vs returning, membership status, open estimate, last call history) so the dispatcher knows which calls are worth the morning slots and which are tune-ups that can wait. The two tools stay in sync.
The owner leaving a Rotary meeting at 2 PM opens the Strkr app and sees: today's revenue run-rate, open estimates over 5,000 dollars with the comfort advisor name next to each, memberships expiring this week, 1-star reviews opened. The data model works on mobile without being a scaled-down web page.
Most HVAC shops in the 5 to 50 tech range run some combination of a dispatch tool, a few spreadsheets, a Mailchimp account that goes stale, and a reminder app for renewals. The gap is the CRM and revenue layer. Here is the honest side-by-side.
| Feature | Strkr | Housecall Pro + spreadsheets + Mailchimp |
|---|---|---|
| Lead to estimate pipeline | Stage-based pipeline with age, probability, and nurture per stage | Jobs list in dispatch, no stage logic, no follow-up timing |
| Service agreement renewals | Agreement object with 60-day and 30-day auto-nurture, lapse report | Spreadsheet updated when the office remembers |
| Replacement opportunity tracking | Equipment object with install year, auto-surfaces aged systems | Buried in service notes, never queried |
| Seasonal campaigns | Native marketing module with timed shoulder season sequences | Mailchimp list that goes stale between sends |
| Review funnel | Satisfaction gate routes 9-10 to Google, under 7 to service manager | Manual ask, one-stars slip through, 5-star window missed |
| Lifetime value reporting | Rolls up jobs, memberships, parts, replacements, referrals by segment | Not computed, no way to answer per-customer worth |
| After-hours lead capture | Auto-reply, on-call dispatch, lead record created inside 60 seconds | Voicemail or missed text, triaged the next morning if at all |
| Referral partner tracking | Realtor, property manager, inspector as accounts with activity history | Verbal relationships, no attribution, no track-record reports |
| Technician scorecards | Per-tech close rate, membership sales, review rate, revenue per hour | Impression-based coaching, no monthly scorecard |
| Install project tracking | Native projects module with milestones from permit to 30-day follow-up | Dispatch job plus a side group chat for the install crew |
| Commercial account visibility | Property-level equipment list, contract clock, contact turnover alerts | One record per site, no multi-building visibility |
| Pricing basis | Per seat, every paid tier includes CRM, Marketing, Projects, Messaging | Dispatch per user plus Mailchimp per contact plus spreadsheet labor |
The pattern across customers in this category is consistent. The dispatch tool stays. Strkr layers on and runs the CRM, marketing, and project tracking work. The payback shows up inside the first two quarters because the renewals, the quote follow-ups, and the replacement pipeline are already in the installed base, just not surfaced.
A small residential HVAC shop had 1,100 active maintenance plans with a 28 percent annual lapse rate. Strkr turned on the 60-day and 30-day renewal flows with auto-booking of the tune-up visit. Inside 10 months the lapse rate was 11 percent. The recovered margin on roughly 190 plans at a 199 dollar price point funded a second comfort advisor hire.
A mixed HVAC and plumbing shop loaded 2,400 installed systems with install dates. 310 systems were older than 12 years. Strkr fired a quarterly replacement nurture sequence to that cohort. In 18 months, 42 replacement conversations converted to signed installs, and the shop reported seven-figure attributable revenue to the sequence.
A commercial-leaning HVAC shop turned on the satisfaction gate on every completed job. Google review volume increased 4x in six months. The one-star rate dropped because complaints were routed internally to the service manager inside 15 minutes instead of posted publicly. LSA cost per lead decreased because the review score lifted the ad placement.
A 35-tech multi-trade shop had three comfort advisors each sitting on 15 to 20 open quotes with no visibility for the owner. Strkr built the pipeline board with stage, age, probability, and the quote-nurture sequence running automatically. Close rate on quotes over 5,000 dollars climbed from 24 to 38 percent inside two quarters.
A regional operator had an informal realtor and property manager referral book. Strkr turned the 60 partners into accounts with quarterly touchpoints, track-record reports, and a holiday campaign. Attributed partner-sourced revenue doubled in year one because the partners finally knew how many leads they had sent and how much revenue they had produced.
See how Strkr sits around your dispatch tool and turns the install base into a measurable pipeline. Transparent per-seat pricing with CRM, Marketing, Projects, Messaging, and Docs on every paid tier. Compare the features list before you book a call.
No. Be direct about this. Strkr is not a dispatch, routing, inventory, or technician mobile app platform. Housecall Pro, ServiceTitan, FieldEdge, Service Fusion, and the rest of the field service category do that work and do it well. Strkr is the revenue layer around the dispatch tool. It handles the CRM, marketing, service agreement renewals, replacement opportunity tracking, project management for installs, review funnels, and reporting. Most HVAC shops run Strkr with Housecall Pro integrated and get the best of both. Shops without a dispatch tool should get one first.
The sweet spot is 5 to 50 technicians. Below 5 techs, the shop can usually run on Housecall Pro alone until the lead funnel and the renewal engine start leaking. Above 50 techs, ServiceTitan often makes sense because the dispatch tool, the CRM, and the reporting all come in one bundle at that scale. In between, the dispatch tool solves half the problem and Strkr solves the other half at a fraction of the cost of a ServiceTitan rollout.
A service agreement is a first-class object with a start date, end date, plan tier, billing cadence, visits included, and visits used. A nightly flow looks at every active agreement, creates renewal tasks at 60 days out, fires renewal emails at 30 days, and queues call-out tasks at 7 days. Expired agreements that lapsed go into a reactivation sequence. The office stops forgetting renewals and the reporting shows the real lapse rate as a number per month.
Yes, and this is one of the highest-ROI features for the category. Every installed HVAC system, water heater, boiler, or softener is a custom object linked to the account. Install year, brand, model, serial, tonnage, warranty expiration, refrigerant type, and filter size are all tracked. A nightly flow queries the install base and surfaces systems older than configurable thresholds (usually 12 to 15 years for HVAC) and queues them into a replacement nurture sequence. The install base becomes a measurable pipeline instead of a service note.
Marketing is a native module. Shoulder season campaigns (spring tune-up, fall furnace tune-up) are built as timed sequences that fire on the same date range every year to the right segment of residential or commercial accounts. Weather-triggered sequences fire when the local 7-day forecast crosses a configured threshold, like the first cold snap of fall. Membership-plan renewal reminders and replacement nurture sequences run continuously year-round. All sequences are built once and compound in effectiveness year over year.
Job marked complete in the dispatch tool triggers a satisfaction text to the homeowner on a 2-hour delay. The question is a simple 1 to 10 rating. Replies of 9 or 10 get the Google review link with a one-click flow. Replies of 7 or 8 get a thank-you message plus a service manager follow-up task to call the customer. Replies of 6 or below create a complaint ticket for the service manager inside 15 minutes so the problem is resolved before it hits Google. The result is more 5-star reviews and fewer public 1-stars.
The typical path is 4 to 8 weeks running the existing dispatch tool unchanged. Week 1, connect the dispatch tool and import customers, jobs, and invoices through the native integration. Week 2, build the equipment list from service history or a one-time field load. Week 3, build the service agreement objects from the current renewal spreadsheet. Week 4, turn on the renewal flows and the review funnel. Weeks 5 to 8, build the seasonal campaigns and the replacement nurture sequence. Most shops see the first clear ROI from the renewal engine inside the first full quarter.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
