What are the concrete steps to build a GTM playbook for an HVAC contractor in 2027?
PULSEKNOWLEDGE LIBRARY
Build the playbook in five concrete steps: define your service-area and job-type ICP, price by job class with membership attached, script the phone and in-home process, wire dispatch-to-CRM tracking with call recording, then set weekly revenue and close-rate reviews. An HVAC contractor should ship a working v1 in roughly 60 days, then refine quarterly.
What changes by company stage
The single biggest mistake HVAC owners make with a go-to-market playbook is copying a document built for a company at a different size. A two-truck shop and a thirty-truck regional operator both need a playbook, but almost nothing inside them overlaps except the pricing philosophy. Stage determines what the document is even for.
At one to three trucks (typically $400K–$1.2M in annual revenue), the owner is usually still in the field or answering the phone. The playbook here is not a sales enablement system — it is a memory aid that makes the owner's own instincts repeatable when a second technician runs a call. It should be short enough to read in fifteen minutes: a service-area map with drive-time boundaries, a flat-rate price book, three phone scripts (no-heat emergency, maintenance booking, quote request), and one option-presentation sheet for replacements. The failure mode at this stage is over-engineering. Do not buy a CRM with a sales pipeline module. Do not build a lead-scoring model. You have maybe 40–120 calls a month; the constraint is capacity, not lead flow.
At four to twelve trucks ($1.5M–$5M), you have hired a dispatcher or CSR and probably a comfort advisor who runs replacement leads. Now the playbook becomes a coordination artifact, because the person who books the call is no longer the person who runs it, and neither is the person who sells the system. This is where booking-rate accountability and a handoff protocol matter more than anything else in the document. You need call recording, a defined lead-to-appointment SLA, and a written definition of what makes a service call "convertible" to a replacement conversation. The failure mode is a leaky handoff: the CSR books a $95 diagnostic, the tech finds a 19-year-old failing system, and nobody schedules the comfort advisor before the customer's furnace gets patched and the urgency evaporates.

At thirteen-plus trucks ($6M+, often private-equity-backed or acquisitive), the playbook stops being one document and becomes a system of linked documents with owners, review cadences, and version control. Marketing spend is meaningful enough that channel attribution changes decisions. You are likely running multiple brands or recently acquired locations, which means the playbook has to specify what is standardized (price book structure, membership terms, warranty language) versus what is local (call scripts referencing the neighborhood, seasonal timing, which utility rebates apply). The failure mode here is standardizing the wrong layer — forcing a uniform script on a market where the local brand's whole advantage was that the CSR knew the caller's street.
There is also a seasonality overlay that cuts across all three stages and does not exist in most B2B GTM templates. HVAC demand is violently non-uniform: the first sustained heat wave and the first hard freeze produce call volumes several times the shoulder-season baseline. A playbook that only optimizes for conversion is wrong in July, when the constraint is scheduling capacity and the correct behavior is triage, not selling. The document needs an explicit "peak mode" and "shoulder mode" for at least the phone script, the dispatch rules, and the maintenance-membership push.

Stage-by-stage playbook build
Here is the concrete build order. Work top to bottom; each step produces an artifact you can point at, and no step depends on software you have not already bought.
Step 1 — Define the ICP by geography and job type (week 1). Pull the last 12 months of completed jobs from your dispatch software or your invoices. Bucket them three ways: by ZIP code, by job class (diagnostic, repair, maintenance, replacement, IAQ add-on, commercial light), and by gross margin per job. You are looking for the intersection where margin and volume are both acceptable. Most residential contractors find that replacements carry the highest absolute gross profit per job while maintenance memberships carry the highest lifetime value, and that a handful of outlying ZIPs consume disproportionate drive time. Write down, in one paragraph, who you serve: the drive-time radius, the housing stock (age of homes matters enormously — a neighborhood of 1998-built houses is a replacement pipeline), and the job classes you actively want. Write down what you decline or price punitively: long-haul calls, brands you do not stock parts for, rental-property work if it historically fights you on price.
Step 2 — Build or rebuild the flat-rate price book (weeks 1–3). Flat-rate pricing is the foundation of everything downstream, because scripts, options sheets, and technician incentives all reference it. Compute your actual hourly cost of doing business: total overhead plus fully burdened labor divided by billable hours, and be honest that billable hours are a fraction of paid hours — drive time, restocking, and callbacks are real. Then set task prices to hit your target gross margin by category rather than a single blended number. Repairs typically carry a higher margin percentage than equipment replacement, because replacement price includes a large pass-through equipment cost. Publish the book to every technician's tablet so no one is doing mental math in a customer's basement.

Step 3 — Script the phone (week 3). The CSR call is where most contractor revenue is silently lost. Write three scripts: the emergency no-heat/no-cool call, the maintenance or membership call, and the price-shopper call. Each script needs a booking attempt, a defined objection response, and a capture of the data the tech will need (system age, brand, symptom, whether the customer owns or rents). Set a booking-rate target and measure it per CSR from recorded calls. Do not let the script become a robot recitation — the goal is that no call ends without either an appointment or a written reason.
Step 4 — Script the in-home process (weeks 3–5). Define the technician's sequence: system-health assessment with photos, a written finding, and — this is the pivotal branch — a rule for when the tech stops repairing and calls the comfort advisor. The rule should be objective and written down, something like equipment age past a threshold, a failed compressor or heat exchanger, or a repair quote exceeding a set share of replacement cost. Then define the replacement presentation: good/better/best options, financing shown as a monthly figure alongside the cash price, and the membership offered on every single call regardless of outcome.
Step 5 — Instrument it (weeks 5–7). Every call recorded, every lead source tagged at intake, every quote logged with an outcome and a reason code. Whether you run ServiceTitan, Housecall Pro, Jobber, or a spreadsheet plus a call-tracking line, the requirement is the same: you must be able to answer "of 100 inbound calls last month, how many booked, how many ran, how many turned into quotes, how many closed, at what average ticket." If you cannot produce that funnel, you do not have a playbook, you have a pamphlet.

Step 6 — Set the review cadence (week 8 onward). Weekly thirty-minute revenue review with the dispatcher and lead tech. Monthly margin-by-job-class review. Quarterly price book and script revision. The playbook is a living document; version it with a date on the cover page so nobody argues about which copy is current.
Numbers that matter at each stage
A playbook without target numbers is a wish. These are the metrics to instrument, roughly in order of how much leverage each one carries, along with the reasoning about what moves them. Treat specific targets as things you set from your own baseline — pull your trailing twelve months first, then set a target that is a real improvement over your own number rather than an industry figure you read somewhere.
Booking rate — the share of inbound service calls that become scheduled appointments. This is the highest-leverage number in a small contracting business because it costs nothing to improve. Marketing spend is already sunk by the time the phone rings. If you are running paid search or LSAs, every unbooked call is a paid lead thrown away. Measure it per CSR, per shift, and per call type separately; the emergency-call booking rate should be dramatically higher than the price-shopper booking rate, and blending them hides the problem. Listen to ten recorded unbooked calls a week. Most of the loss is one of three things: the caller was quoted a diagnostic fee with no framing of value, the first available slot was too far out, or the CSR answered a price question with a number instead of a question.

Average ticket, split by job class. A single blended average ticket is close to useless because it moves entirely with your repair-to-replacement mix. Track diagnostic-plus-repair separately from replacement separately from maintenance. A rising blended ticket that comes purely from a heavy replacement month tells you nothing about whether your repair process improved.
Close rate on replacement quotes. Measure by comfort advisor and by lead source. Quotes generated from your own service calls should close meaningfully better than cold quotes from a lead aggregator, because you already have trust and diagnostic evidence. If they do not, your handoff is broken or your options presentation is confusing the customer. Also track the *time from quote to decision* — quotes that sit past a few days close at a fraction of the same-visit rate, which is the whole argument for presenting options in the home rather than emailing a PDF later.

Membership count and attachment rate. The number of active maintenance agreements is the most durable asset in a residential HVAC business, and it is the number a buyer looks at first if you ever sell. Attachment rate is memberships sold divided by eligible calls. This should be scripted and measured on every technician individually, because it varies enormously by person and it is highly coachable. Memberships matter beyond their own revenue: they generate shoulder-season work that keeps technicians paid in spring and fall, and they produce a captive list for replacement conversations on aging equipment.
Cost per booked call, by channel. Not cost per lead — cost per *booked* call. Google Local Services Ads, traditional paid search, direct mail, yard signs, and referrals all produce different booking rates, and ranking channels by raw lead cost will systematically overvalue whichever channel produces the most tire-kickers. This requires tagging lead source at intake, which is why step 5 exists.
Gross margin per job class. Repairs, replacements, and maintenance have structurally different margin profiles because replacement revenue carries a large equipment pass-through. Watch the trend, not the level. A slowly eroding repair margin usually means your price book has not kept up with parts and labor cost — a common failure, since price books get built once and then quietly go stale while wages and equipment costs move.

Callback and warranty rate. Every callback is a truck roll you do not get paid for plus a customer whose confidence you just spent. This is a quality metric that shows up as a revenue metric.
Technician revenue per day. Useful for capacity planning, dangerous as an incentive if used alone. Tie any variable compensation to a blend of revenue, callback rate, and customer review score, or you will train technicians to oversell and you will find out about it in your reviews six months later.
For stage calibration: a one-to-three-truck shop should track booking rate, average ticket, and membership count, and nothing else, on a whiteboard. A four-to-twelve-truck shop adds close rate by advisor, cost per booked call by channel, and margin by job class. A thirteen-plus operation adds cohort retention on memberships, per-location variance, and marginal return by channel at the spend level where the next dollar starts underperforming.

Decision framework for what to build first
Owners routinely start the playbook at the wrong end — they buy software, or they write a beautiful mission statement, or they redesign the truck wrap. The correct first move depends entirely on which constraint is actually binding. Diagnose before you build.
If the phone is ringing and you are not booking, the constraint is the CSR layer. Fix the script and the booking-rate measurement first. This is the cheapest fix in the business and it usually produces the fastest revenue change, because it converts already-purchased demand.
If you are booking calls but average ticket is flat and low, the constraint is either the price book or the in-home process. Check the price book first: if it has not been repriced against current labor and parts costs within the last year, that is your answer and it takes days to fix, not months.

If techs are running plenty of calls but almost no replacement quotes are generated, the constraint is the repair-versus-replace trigger and the handoff. Write the objective trigger, train it, then audit ten calls where the tech repaired equipment past your age threshold and ask why.
If quotes are plentiful but close rate is poor, the constraint is the options presentation, the financing offer, or the advisor's process. Ride along on five appointments before you change the document.

If everything converts fine but the phone does not ring enough in shoulder season, the constraint is demand generation and membership base. Push maintenance agreements hard, because they are the mechanism that manufactures shoulder-season demand from your existing customer list.
The other thing this framework is for is sequencing software purchases. Do not buy a field service platform to fix a scripting problem. A contractor with three trucks and a broken phone process will get more revenue from ten hours of call review than from a five-figure annual platform commitment. Conversely, at twelve trucks you genuinely cannot run dispatch, price book versioning, membership renewals, and lead-source attribution on spreadsheets, and refusing to buy the tooling becomes the constraint itself.
One trade-off worth naming explicitly: standardization has a real cost. Every script you write reduces variance, which raises the floor and lowers the ceiling. Your best CSR will be slightly worse on script than off it; your worst three will be dramatically better. That trade is almost always worth taking, but it means the right response to a top performer deviating from the script is to study what they are doing and update the document — not to enforce compliance.
Related questions
How long does a first version take to build?
Roughly 60 days of part-time work for a small shop. Week one is data pull and ICP, weeks two and three are the price book, weeks three through five are scripts, weeks five through seven are instrumentation, and week eight starts the review cadence. Ship a rough v1 rather than perfecting.
Should a small contractor buy field service software first?
No. Buy tooling when spreadsheets are demonstrably the constraint — usually somewhere around five to ten trucks, when dispatch, memberships, and price book versioning stop fitting in one person's head. Software cannot fix a scripting or pricing problem.
What belongs in the price book versus the playbook?
The price book holds task-level prices and is versioned separately because it changes on its own cadence with parts and labor costs. The playbook holds the process: who does what, in what order, with what scripts and triggers, measured against what targets.
How do you handle seasonal demand swings?
Write explicit peak and shoulder modes. In peak, dispatch triages and the phone script prioritizes scheduling capacity. In shoulder, the same script pushes maintenance memberships and replacement conversations on aging equipment, converting your existing list into work.
Who owns the playbook once it exists?
At small scale, the owner. Past roughly ten trucks, a general manager or operations lead owns it with named section owners, a version date on the cover, and a standing quarterly revision meeting. Unowned documents go stale within two seasons.
FAQ
What are the concrete steps to build a GTM playbook for an HVAC contractor in 2027?
Six steps in order: define the ICP from twelve months of completed jobs by ZIP, job class, and margin; rebuild the flat-rate price book against your real cost of doing business; script the phone for emergency, maintenance, and price-shopper calls; script the in-home process including an objective repair-versus-replace trigger and a good/better/best options presentation; instrument the funnel so every call is recorded and every lead source tagged at intake; then set weekly, monthly, and quarterly review cadences that actually revise the document.
How is an HVAC playbook different from a standard B2B GTM playbook?
Three ways. Demand is inbound and urgency-driven rather than prospected, so booking rate matters more than pipeline generation. Seasonality is extreme enough that the correct behavior inverts between peak and shoulder months. And the sale happens in a customer's home by a technician or comfort advisor rather than over email by a salesperson, which makes the in-home script and the handoff the highest-leverage documents in the whole system.
What is the single highest-return section to write first?
The CSR phone scripts, in almost every case. Marketing money is already spent by the time the phone rings, so an unbooked call is pure waste, and scripting is free. Record calls, listen to ten unbooked ones weekly, and revise. Most contractors find the same three failure patterns and can fix them inside a month.
Do you need call recording to make this work?
Effectively yes. Booking rate is the number you will manage against most often, and you cannot coach it from a summary statistic — you need to hear what actually happened on the calls that did not book. Check your state's call-recording consent requirements and use the standard disclosure at the start of the call.
How should technician incentives connect to the playbook?
Tie variable pay to a blend, never to revenue alone. Revenue-only incentives reliably produce overselling, which surfaces months later as callbacks, refund requests, and bad reviews. A workable blend weights revenue per day, callback and warranty rate, membership attachment, and customer review score, so a technician cannot win on one dimension by destroying another.
How often should the playbook be revised?
Scripts and targets quarterly; the price book at least annually and immediately whenever equipment or labor costs move materially; the ICP and service-area definition annually. Put a version date on the cover page. The most common failure is not a bad playbook but a stale one that everyone quietly stopped following.
Sources
- https://www.acca.org/ — Air Conditioning Contractors of America, industry standards and contractor business resources
- https://www.ashrae.org/ — ASHRAE, technical standards for HVAC systems
- https://www.energy.gov/energysaver/heating-and-cooling — U.S. Department of Energy, heating and cooling efficiency guidance
- https://www.energystar.gov/products/heating_cooling — ENERGY STAR, equipment efficiency ratings and rebate context
- https://www.bls.gov/ooh/construction-and-extraction/heating-air-conditioning-and-refrigeration-mechanics-and-installers.htm — Bureau of Labor Statistics, HVAC workforce and wage data
- https://www.sba.gov/business-guide — U.S. Small Business Administration, small business planning and financial guidance
- https://www.ftc.gov/business-guidance/advertising-marketing — FTC advertising and marketing compliance guidance
- https://www.contractingbusiness.com/ — Contracting Business, HVAC trade publication
- https://www.achrnews.com/ — ACHR News, HVAC/R industry trade coverage
Related on PULSE
- How to price a flat-rate service book without eroding gross margin
- What booking rate should a home services CSR team target
- How to structure a maintenance membership program that survives shoulder season
- When a home services business should move off spreadsheets to field service software
- How to design technician compensation that does not encourage overselling









