How to Standardize a Roofing Sales Playbook Across Multiple Locations

The first branch was easy because you were in it. You ran the morning huddle, you sat in on the hard appointments, you re-priced the jobs that looked thin, and you knew within a day when a rep was sliding. The playbook lived in your head, and your head was in the building.

The second branch is where that stops working. You are forty minutes away on a good day. The branch manager you promoted ran great numbers as a rep, which tells you almost nothing about whether he can install a process he never had to write down. Two months in, you pull the reports and the close rate is eleven points lower than your home office, the average job is smaller, and three deals fell apart in the supplement stage because nobody documented the original scope correctly. By the time you open a third and fourth location, the variance between your best and worst branch is wider than the margin on a typical job. You are no longer running a roofing company. You are running four roofing companies that happen to share a logo.

Standardizing a sales playbook across locations is the work of turning what your best people do instinctively into something a new branch can execute on week one and a mediocre rep can execute on a bad day. It is not a binder. A binder is where good intentions go to die in a drawer. A real playbook is a defined sequence of stages, each with an entry condition, a required action, a piece of evidence the rep has to produce, and an exit condition that the system checks — so that "how we sell here" is the same sentence in every market, and you can see the moment a branch drifts off it.

What follows is the operating system: how to write the stages, how to standardize the parts that must be identical and flex the parts that legitimately differ by market, how to onboard a new branch in 30 days, which numbers to watch by location, and where the whole thing tends to break. It is written for the owner or regional sales leader who already sells well in one place and now has to make it travel.

Why your best branch doesn't clone itself

Before writing a single stage, it helps to be honest about why performance does not copy on its own. Owners tend to blame "talent" — the new market just doesn't have reps as good as the originals. Occasionally true. Far more often, the gap comes from four things that have nothing to do with talent.

The process was never externalized. Your top branch runs on tacit knowledge — a thousand small decisions your veterans make without thinking. Tacit knowledge does not transfer by osmosis when the veteran is 200 miles away. If you cannot write down what a rep does between "knocked the door" and "signed the contract," you cannot teach it, and you certainly cannot audit it.

Local managers re-invent instead of install. Promote a strong rep to branch manager and his instinct is to sell the way he sold, then teach that. Now you have two playbooks. Promote four managers and you have five. The variance compounds because each manager is optimizing for his own comfort, not for a system.

There is no shared definition of the stages. When "qualified lead" means a storm-damaged roof in one branch and "answered the phone" in another, your pipeline reports are fiction. You cannot compare close rates across locations if the denominators mean different things. Most multi-branch roofers discover their CRM stages were configured ad hoc per office and no two are the same.

Nobody measures leading indicators per location. By the time revenue shows a problem, the problem is 60–90 days old — the length of a roofing sales cycle in many markets. If the only number you watch by branch is monthly revenue, you are driving by looking in the rearview mirror.

Standardization fixes all four, but only if you treat the playbook as a product you ship and maintain, not a document you publish once.

What actually belongs in a roofing sales playbook

A playbook that travels has seven layers. Skip any of them and a new branch will fill the gap with improvisation, which is the thing you are trying to eliminate.

1. The pipeline stages — the named steps every opportunity moves through, with hard entry and exit criteria.
2. The qualification standard — the definition of a real opportunity, identical in every market.
3. The scripts and talk tracks — what reps say at the door, on the phone, at the table, and on the follow-up, with room for local facts.
4. The estimate and documentation standard — how every roof gets measured, photographed, scoped, and priced so the file is complete and defensible.
5. The pricing and discount guardrails — the bands a rep can quote inside, and the approval path for anything outside them.
6. The follow-up cadence — the exact sequence and timing of touches after each stage, so nothing rots in the pipeline.
7. The metrics and review rhythm — the KPIs per rep and per branch, and the weekly and monthly cadence that catches drift.

The trick to multi-location is knowing which layers must be byte-for-byte identical and which must flex. Get that division wrong and you either crush a branch with rules that don't fit its market or let it drift until it is a different company. Here is the division that holds up.

Notice the pattern: the definitions, sequences, and rules are universal; the local facts and the numbers flex. A rep in Tulsa and a rep in Tampa run the identical seven stages, use the identical objection frame, and produce the identical photo set — but the Tampa rep quotes higher wind-rated material, references a different building code, and works to a close-rate target set off Tampa's baseline, not Tulsa's. That is the line.

Layer 1: Define the pipeline stages once, then never let a branch redefine them

Every standardization effort starts here because every other layer hangs off the stages. The stages are the skeleton. If each branch has its own skeleton, nothing else lines up.

A roofing sales pipeline that works across retail and storm/insurance work, and across residential branches, usually settles into these stages. Adjust the names to your business, but lock the criteria.

A reference stage set

Stage 0 — Target / Lead. A home or property that has entered your world: a canvass knock, an inbound call, a form fill, a referral, a mailer response. Entry: a contact record exists with an address. Exit: rep has made first qualifying contact.

Stage 1 — Contacting. Rep is actively reaching the prospect to set an inspection. Entry: first attempt logged. Exit: an inspection is scheduled OR the lead is disqualified with a reason.

Stage 2 — Inspection scheduled. A date and time exist on the calendar. Entry: appointment booked. Exit: rep has been on the roof / property.

Stage 3 — Inspected / Scoped. The roof has been physically assessed and documented. Entry: rep on site. Exit: a complete documentation file exists — required photos, measurements, condition notes — and the opportunity is classified (retail repair, retail replacement, or insurance/storm path).

Stage 4 — Estimate presented. A priced proposal has been put in front of the decision-maker. Entry: documentation complete and priced. Exit: prospect has seen the number and the scope.

Stage 5 — Negotiation / Follow-up. The deal is live but unsigned. Entry: estimate presented, no decision yet. Exit: signed contract OR lost with reason.

Stage 6 — Won (contract signed). A signed agreement exists. This is the only "won." Verbal yes is Stage 5.

Stage 7 — Lost. Closed with a required, picklist reason (price, timing, competitor, no decision-maker, didn't qualify, went DIY, claim path stalled).

The single most valuable rule across multiple locations is this: a stage advances only when its exit evidence exists, not when a rep feels good about it. "Inspected" requires the photo set, not the rep's word that he looked at it. "Won" requires the signed contract in the file, not a handshake. When every branch enforces the same evidence gates, your cross-branch reports finally mean something, because a Stage 4 deal in one office is genuinely the same animal as a Stage 4 deal in another.

The disqualification discipline

New branches inflate their pipelines because nobody makes them disqualify. A lead with no roof problem and no budget sits in "Contacting" forever, making the branch look busy and making the close rate (wins ÷ qualified) look terrible. Force a disqualification reason at Stage 1 and Stage 7. A clean pipeline is a comparable pipeline.

Layer 2: One qualification standard, enforced at the door

Qualification is where branches drift fastest because it is the most judgment-heavy moment in the process. Standardize it with a short, hard checklist that every rep applies before an opportunity is allowed to consume a real appointment slot.

A workable residential qualifier — make it identical in every market:

• Property fit: owner-occupied or decision-maker reachable; single-family or target property type for the branch.
• Roof condition signal: age band of the roof or a visible/known issue. A roof in a recent-install band with no leak is a low-priority lead; a roof in the overdue band, or one in a storm-exposed area, is a real opportunity.
• Decision-maker present or scheduled: you are not presenting a replacement to someone who has to "ask my husband" with no plan to get him in the room.
• Path clarity: is this a retail cash/finance job or a storm/insurance-claim job? They run different downstream steps, and misclassifying here wrecks the follow-up.

The roof-condition signal is where multi-location roofers either build an edge or leave money on the table. Knocking a neighborhood blind, every house is a coin flip. But roof age runs in bands you can reason about, and storm exposure varies street by street. If a branch can walk into a territory already knowing which roofs sit in the overdue band and which streets took the worst of the last hail event, qualification stops being a guess and starts being a sort. We will come back to how to operationalize that, because it is one of the few places technology genuinely changes the unit economics rather than just digitizing a clipboard.

One honest caveat to bake into the standard: roof age is a range, not a birthday. Permit records, satellite-imagery change detection, and material-weathering signals get you a band — "likely 18–24 years" — not "installed on this date." Teach reps to treat it as a prioritization signal, not a fact to assert to a homeowner. Overstating precision is how a rep loses trust at the door.

Layer 3: Scripts that are identical in structure and local in fact

Reps resist scripts because they have heard bad ones — wooden, salesy, obviously canned. The fix is not to abandon scripts; it is to standardize the structure and the frames while letting the facts be local. A good roofing script across locations has the same bones everywhere:

1. Opening / reason for the visit — short, specific, non-threatening. ("We've been working on [street/neighborhood] after the [month] storm and doing free roof inspections — takes about fifteen minutes.")
2. Permission and qualification — confirm the decision-maker and the path.
3. Inspection narration — what the rep is looking at and why, building credibility without diagnosing damage they can't see from the ground.
4. Findings and scope — what the documentation showed, in plain terms.
5. The number and the options — price, financing, scope, presented without flinching.
6. Objection handling — a fixed set of frames for the five objections that account for most stalls: price, timing, "need to think," spouse, and "getting other quotes."
7. The close and the next step — sign now, or a specific dated follow-up. Never "I'll check back sometime."

What flexes per branch: the storm dates and the specific event, the local roof systems and material names, the building-code references, and the price examples. A Gulf Coast branch talks wind ratings and a specific named storm; a Midwest branch talks hail and freeze-thaw. Same seven beats, different nouns.

The compliance frame that must be word-for-word everywhere

This is the one place in the script where you do not let a single branch improvise, because the legal exposure is real and it is the company's, not the rep's. Any time a rep talks about insurance, claims, deductibles, or storm damage, the language has to stay on the right side of the line that separates a roofing contractor from an unlicensed public adjuster.

What a roofing contractor may do, and should train every rep to do identically: inspect the roof, document the damage thoroughly with photos and measurements, write an accurate, Xactimate-aligned repair estimate for the work they would perform, and hand that estimate and documentation to the homeowner. The contractor states facts about their own scope to the carrier when asked.

What a rep may not say or do, in any market, and what belongs on a do-not-say list posted at every branch:

• Do not offer to negotiate, adjust, or "handle" the claim for the homeowner. That is the homeowner's and the carrier's role.
• Do not interpret the policy or tell the homeowner what is or isn't covered.
• Do not promise an approval or a specific payout.
• Do not promise the deductible will be waived, absorbed, eaten, or made to disappear. The homeowner is legally responsible for it.
• Do not advertise or imply a "free roof."
• Do not represent the homeowner against their insurer.

The safe frame, said the same way in every office: we document the damage thoroughly and write you an accurate estimate; you file the claim and your insurer decides coverage. The contractor's job is the documentation and the estimate. The homeowner files. The insurer decides. When you standardize one thing across locations word-for-word, make it this — because a single rogue branch promising free roofs is a regulatory and reputational problem that lands on the whole company.

Layer 4: The documentation and estimate standard — the file that wins later

The estimate and inspection file is the most under-standardized layer in most multi-branch roofers, and it is the one that costs the most downstream. A thin file at the inspection stage becomes a stalled deal at the negotiation stage and a lost supplement three weeks later. Standardize the file and you fix problems you won't see until much later.

The required photo set

Every inspected roof, every branch, produces the same minimum photo set. Make it a checklist the rep cannot skip:

• Full elevations from all four sides (context shots).
• Overall roof planes from the roof or a safe vantage.
• Each slope showing field condition.
• All penetrations: pipe boots, vents, chimneys, skylights — close and in context.
• Flashing details: step, counter, valley, drip edge.
• Damage close-ups with a reference (chalk circle, measuring tape, or marker) so scale is unambiguous.
• Decking/substrate where visible.
• The address or a slate/whiteboard in the first frame to bind the set to the property.

The "with a reference" detail matters more than reps think. A close-up of a hail bruise with a tape measure in frame is evidence; the same bruise with no scale is a JPEG. When documentation later supports an estimate that goes to a carrier, the photo set's completeness is the difference between a clean file and a back-and-forth that kills the timeline.

The measurement and scope standard

Standardize how the roof is measured (aerial report, drone, or manual with a defined method) and what the scope must enumerate: squares, pitch, layers, penetrations, flashing linear footage, ventilation, and code-required items for the local jurisdiction. The branch flexes the local code items; everything else is identical.

The payoff of an identical documentation standard is that any reviewer — a sales manager, a production manager, an owner reviewing a branch's files — can open any opportunity in any location and instantly see whether the work was done right. You are not auditing the rep's memory; you are auditing the file. And a complete file is what lets the back end recover the money the front end earned, which is the next layer.

Layer 5: Pricing guardrails — the part owners are most afraid to give up

The fear is reasonable: hand a remote branch the pricing book and watch it discount its way to volume and zero margin, or quote so high it loses every comparison. Standardization here is not about forcing one price list onto every market — material and labor genuinely differ between Tampa and Tulsa. It is about standardizing the rules around price, not the price itself.

Three guardrails, identical everywhere, numbers local:

1. The margin floor. Every branch has a minimum gross margin below which a job cannot be sold without owner/regional approval. The floor is a company rule; the price that hits it is local. A rep who wants to go below floor triggers an approval, not a unilateral decision.

2. The discount ladder. Define exactly who can approve what. A rep can move price within a small band on their own; beyond that, the branch manager; beyond that, the regional. Put real numbers on it:

3. The never-free list. Some things are never given away in any market because they create legal or margin exposure: the deductible is never "absorbed" or waived (it is the homeowner's responsibility and offering to eat it is a compliance problem as much as a margin one), and the company never advertises a free roof. This guardrail does double duty as a compliance control.

The reason to standardize the rules and localize the prices is that it gives you control without pretending markets are identical. You can let a branch price for its market and still guarantee that no branch sells below the number that keeps the company healthy. And because every discount over the rep's band leaves an approval trail, you can later see which branch is buying volume with margin — usually the one whose manager is afraid to hold price.

Layer 6: The follow-up cadence — where most pipeline value leaks

Reps are good at the appointment and bad at the eleven days after it. The deals that die in Stage 5 mostly die from silence, not from "no." A standardized cadence fixes this because it removes the decision — the rep doesn't choose whether to follow up; the sequence does.

A reference cadence for an estimate-presented, undecided residential deal — identical structure, local channel mix:

The cadence is the same in every branch; the channel is local (some markets answer texts, some need a knock). What standardization buys you is that a deal cannot quietly sit untouched for nine days in one branch while another branch works it on day two. The sequence is the floor.

For the storm/insurance path, the cadence runs longer and is gated on documents rather than on a decision — but the same principle holds: a defined sequence, a named owner per touch, and a hard reclassify-or-advance step so nothing rots. The danger in the claim path is that "waiting on insurance" becomes the place deals go to be forgotten. A standardized cadence with packet-completeness checkpoints prevents that.

Layer 7: The metrics and review rhythm that catch drift early

You cannot manage four branches by reading four P&Ls once a month. By the time revenue moves, the cause is two months gone. Standardize a small set of leading indicators, defined identically, reviewed on a fixed rhythm, per rep and per branch.

The core KPI set, defined once

Definitions must be identical across locations or comparisons are meaningless. These are the ones that matter most for sales standardization:

• Set rate = inspections scheduled ÷ qualified leads. Tests qualification and contacting.
• Inspection completion rate = inspections done ÷ scheduled. Tests scheduling discipline and no-show handling.
• Close rate = wins ÷ qualified opportunities. The headline, but only comparable if "qualified" means the same thing everywhere (which is why Layer 2 exists).
• Average contract value. Tests whether reps are scoping fully or leaving items off.
• Documentation completeness = files with the full photo+measurement set ÷ inspected. The leading indicator nobody watches; a falling number here predicts lost supplements and stalled claims weeks before they show up.
• Stage cycle time = days in each stage. Spikes flag follow-up failures by stage.
• Cost per lead and cost per win, by source and by branch. Tells you which branch's pipeline is expensive and which marketing is actually producing sold jobs.

Targets are local; the method is universal

Do not impose the home branch's close rate on a six-week-old market. Set each branch's targets off its own baseline plus an improvement slope, but use the same KPI definitions and the same way of setting targets everywhere. A new branch's first job is to hit its documentation-completeness and set-rate targets; revenue follows process, not the other way around.

The review cadence

• Daily (branch): a short huddle on yesterday's sets, inspections, and any deals stuck past cadence.
• Weekly (branch + regional): pipeline review against the KPI set; every Stage 5 deal past day 10 gets a named next action.
• Monthly (regional + owner): branch-vs-branch on the standardized KPIs, drift flags, and one process fix to install everywhere.

The monthly cross-branch view is where standardization pays off. Because every branch reports the same KPIs with the same definitions, you can rank them honestly and — more useful — you can see which stage a lagging branch is losing at. A branch with a fine set rate but a low close rate has a presentation or pricing problem; a branch with a low set rate has a qualification or contacting problem. The stage tells you which page of the playbook to re-train, instead of just yelling "sell more."

Installing the playbook in a new branch: a 30-day plan

Writing the playbook is half the work. Installing it so a new branch runs it on muscle memory is the other half. A binder handed to a branch manager achieves nothing. Here is a 30-day install that actually sticks.

Days 1–5: Configure the system before the people

Do not let a new branch open its CRM and start improvising stages. Before reps touch it:

• Clone the standardized pipeline stages, exit-evidence requirements, and disqualification reasons into the branch's CRM instance so the rails exist on day one.
• Load the qualification checklist, the photo-set requirement, and the scope checklist as required fields/steps, not optional ones.
• Set the local pricing bands inside the company guardrails and wire the discount-approval routing.
• Pre-load the local facts into the scripts: the market's storm history, roof systems, and code references.

The principle: the system should make the right behavior the path of least resistance. If skipping the photo set is harder than doing it, reps do it.

Days 6–15: Train to the stages, not to "selling"

Train the branch on the sequence and the evidence, role-played to the standard:

• Walk every stage with its entry/exit criteria until reps can recite what advances a deal.
• Role-play the seven script beats and the five objection frames until they're automatic, including the compliance language word-for-word.
• Shadow live: a veteran from the home branch (in person or on video) rides along on the first real inspections and grades the file against the documentation standard.
• Certify reps on the documentation standard before they run solo — a rep who can't produce a complete file is not ready.

Days 16–30: Run live with tight feedback

• Daily file review by the branch manager: every inspected roof's documentation checked against the standard, with same-day correction.
• Regional reviews the branch's KPIs twice weekly, watching set rate and documentation completeness first (the leading indicators), not revenue.
• One process drift caught per week is normal and good — it means you're seeing the gaps while they're small.

By day 30 the branch should be running the identical stages, producing identical files, and quoting inside the guardrails. It will not yet match the home branch's close rate — that takes longer — but it will be measurably on the same playbook, which means every future improvement you make to the playbook lands here too.

A new-branch readiness checklist

Before a branch goes fully solo, it should be able to check every box:

• Pipeline stages and exit-evidence gates live in the CRM
• Qualification checklist enforced at Stage 1
• Required photo set and scope checklist enforced at Stage 3
• Compliance / do-not-say language trained and posted
• Local pricing bands set inside company margin floor; discount routing live
• Follow-up cadence loaded with owners assigned per touch
• KPI definitions identical to the company standard; local targets set
• Branch manager trained to run the daily huddle and file review
• Every rep certified on the documentation standard

Where standardization actually breaks (and how to keep it alive)

The playbook does not fail at launch. It fails at month four, when the founder's attention moves to the fifth location and the third branch quietly reverts to how its manager likes to sell. Drift is the default state of any process not actively maintained. The failure modes are predictable.

The branch manager who "knows better." A strong-selling manager edits the playbook informally because his way worked for him. The fix is not a lecture; it is making the standard the path of least resistance in the system and reviewing his branch's stage-level KPIs so the cost of his edits shows up in the numbers. If his off-book close rate is genuinely higher, you have found an improvement to roll out everywhere — capture it, don't tolerate it as a one-branch secret.

The pipeline that fills with junk. Without enforced disqualification, branches inflate Stage 0–1 to look busy, and every ratio downstream lies. The fix is the disqualification discipline from Layer 1, enforced as a required field.

The documentation that thins out. Under volume pressure, reps cut the photo set. It doesn't hurt today; it hurts in three weeks when a deal stalls or a supplement can't be supported. Watch documentation completeness as a leading indicator and correct it same-day.

The metrics that quietly diverge. A branch tweaks its CRM stages or its "qualified" definition and now its close rate isn't comparable. The fix is to lock stage and field definitions at the company level and audit them quarterly.

The playbook that never updates. The opposite failure: the playbook ossifies, stops reflecting what's working, and reps route around a document that's now wrong. Treat the playbook as versioned. When a branch finds something that works, test it, then ship it to all branches as the new standard. A living playbook earns compliance; a dead one earns contempt.

The through-line: standardization is not a one-time rollout. It is a maintained system with an owner, a review rhythm, and a version number.

How RoofPredict standardizes the front end of the playbook

Most of what makes a playbook travel is operational discipline — but two layers are dramatically easier when the underlying data and the rails are the same in every market. The first is targeting and qualification; the second is the pipeline and its measurement. RoofPredict is the platform a contractor runs both on, which is why it matters here rather than as a generic plug.

On targeting, the problem multi-location sales leaders face is that qualification quality depends on knowing which roofs are worth knocking — and that knowledge usually lives in the head of a veteran who knows the territory. RoofPredict externalizes it. It scores every home in a service area by roof-age band — recent, mid-life, due, overdue — layered with that property's storm exposure and an overall opportunity score, and produces a ranked target audience: which roofs are due, house by house, with a "why this home" evidence chain behind each one. A brand-new branch in a market nobody on your team knows can open a territory and immediately work the overdue, storm-exposed roofs first instead of coin-flipping a neighborhood. That is qualification (Layer 2) made identical across locations, because every branch is sorting its market by the same signals rather than by local intuition. Honest framing, the same you'd teach reps: the score is a roof-age-plus-storm-exposure heuristic, age is a band not a date, and storm exposure is odds of impact, not proof of damage — a prioritization tool, not a diagnosis.

From that ranked list, the front end of the playbook runs on the same rails everywhere. The due-roof list becomes a tracked direct-mail campaign with personalized proofs (brand, copy, and address checked before vendor release) and per-piece delivery and return tracking, so a new branch's outreach looks identical to the flagship's. Every targeted home gets a personalized microsite and PDF report — roof profile, storm history, the cost of waiting — with a lead-capture form and a per-home QR code for the mail piece or the door hanger, so a homeowner who isn't ready at the door can self-serve later into the same pipeline. And the field layer — canvass routes, canvasser assignments, and a mobile app with next-stop, the standardized outcome form, voice notes, and the leave-behind QR — means the door-knock workflow, including the data a rep is required to capture, is the same in every market by construction, not by hoping the branch manager enforces it.

How RoofPredict keeps the pipeline and the back end standardized

The second layer technology genuinely standardizes is the pipeline itself and the measurement on top of it — Layers 1, 6, and 7.

RoofPredict runs a lead pipeline on the exact stage logic built out above — new → contacting → appointment → inspected → won/lost — with an immutable first-touch source on every lead, so a branch can't quietly re-attribute where a deal came from. Because the stages and their definitions live in one platform, your cross-branch KPIs are finally comparable by construction: a Stage 4 deal means the same thing in every office. And it syncs two-way with 13 CRMs — HubSpot, ServiceTitan, JobNimbus, AccuLynx, Jobber, Housecall Pro, Salesforce, Pipedrive, Leap, Roofr, SalesRabbit, CompanyCam, plus Zapier and CSV — so you can standardize the sales rails without ripping out the system a branch already runs production on.

On measurement, the results funnel is the multi-location KPI view from Layer 7, built in: delivered → views → form → calls → leads → wins, with cost-per-lead and cost-per-win, and — the number that matters most for holding branches accountable — actual versus estimate versus industry benchmark, plus A/B variants so a branch can prove which approach worked rather than argue about it. When a lagging branch shows up in the monthly review, the funnel tells you which stage it's losing at, which is the difference between a useful retrain and a useless "sell more."

And because the documentation standard (Layer 4) is what protects revenue downstream, the back-end claim work runs on the same locked rails. RoofClaim ties claim intake to the home, auto-classifies and OCRs the claim documents, and runs opportunity detection that maps estimate line items against a roofing knowledge base to flag missing scope, code-required items, and missed supplements — each with an evidence anchor and pricing — so a thin file in one branch gets caught instead of costing the company a recovery. It runs a recoverable-depreciation autopilot (completion-evidence and final-invoice checklist), deductible tracking (never waived — the compliance line from Layer 5, enforced in the tool), and supplement aging with a follow-up cadence and packet-completeness scoring so claim-path deals don't rot in "waiting on insurance." Every output — supplement packets, depreciation-release letters, deductible invoices, missing-docs letters, audit reports — is generated on locked, UPPA-gated, contractor-documentation-only templates. The contractor documents and estimates; the homeowner files; the insurer decides. The platform enforces that line so a remote branch can't cross it.

The point is not that software replaces the playbook. The playbook — the stages, the scripts, the guardrails, the cadence, the review rhythm — is yours to write and maintain. What a single platform does is make the rails identical in every market: the same ranked targeting, the same outreach assets, the same pipeline stages, the same KPI definitions, and the same compliance-locked back end, so that the only thing varying between your branches is the thing that should vary — the local market — and not the process itself.

A 90-day rollout sequence for an existing multi-branch roofer

If you already run multiple locations with divergent processes, you don't standardize everything at once. Sequence it.

Days 1–30 — Define and lock the skeleton. Write the seven stages with exit-evidence gates, the qualification checklist, and the do-not-say compliance language. Lock these in your CRM at the company level so no branch can redefine them. Audit current stage definitions across branches and reconcile them to the standard — this alone usually surfaces why your reports never agreed.

Days 31–60 — Standardize documentation, pricing, and cadence. Roll out the required photo set and scope checklist as enforced steps. Set company margin floor and discount ladder; let each branch place its local price bands inside them. Install the follow-up cadence with named owners per touch. Begin tracking documentation completeness and stage cycle time per branch.

Days 61–90 — Install the metric and review rhythm. Stand up the standardized KPI set with identical definitions, local targets, and the daily/weekly/monthly review cadence. Run the first cross-branch monthly review on apples-to-apples numbers. Pick the single biggest drift you find and ship the fix to every branch as the new playbook version.

After 90 days you have one playbook, installed and measured. From there it is maintenance: every new branch gets the 30-day install, every working idea gets tested and shipped company-wide, and the version number keeps climbing. That is the difference between four roofing companies sharing a logo and one roofing company with four addresses.

The bottom line

Standardizing a roofing sales playbook across locations comes down to a simple division of labor: make the definitions, sequences, and rules identical everywhere — the stages and their evidence gates, the qualification standard, the script structure and compliance language, the documentation file, the pricing guardrails, the follow-up cadence, and the KPI definitions — and let only the local facts and the numeric targets flex by market. Install it branch by branch with a real 30-day onboarding, watch the leading indicators (set rate and documentation completeness) per location so you catch drift before revenue does, and treat the playbook as a versioned product you maintain, not a binder you publish. Do that, and your best branch finally clones itself — not because the new market has better reps, but because they're all running the same machine.

FAQ

How long does it take to standardize a sales playbook across multiple roofing branches?

Plan on 90 days to standardize an existing multi-branch operation and 30 days to install the finished playbook in each new branch. The first 30 days lock the pipeline stages, qualification standard, and compliance language at the company level; days 31–60 standardize documentation, pricing guardrails, and follow-up cadence; days 61–90 install the KPI definitions and the review rhythm. The reason it isn't faster is that you have to reconcile divergent CRM stage definitions across existing branches before any cross-branch number means anything.

Which parts of the playbook should be identical across locations and which should flex?

Standardize the definitions, sequences, and rules: the pipeline stage names and exit-evidence gates, the qualification checklist, the script structure and objection frames, the compliance language, the required documentation and photo set, the margin floor and discount-approval ladder, the follow-up cadence, and the KPI definitions. Localize only the facts and the numbers: local roof systems and storm dates in scripts, building-code items in the scope, the actual price bands (labor and material differ by market), and the numeric KPI targets, which should be set off each branch's own baseline.

How do I keep a strong branch manager from re-inventing his own sales process?

Make the standard the path of least resistance in the system — enforced fields, required photo sets, routed discount approvals — so going off-book is harder than following it. Then review his branch's stage-level KPIs, rather than only revenue, so the cost of any informal edits shows up in the numbers. If his off-book approach genuinely produces a higher close rate, you've found an improvement: capture it, test it, and ship it to every branch as the new playbook version rather than letting it stay a one-branch secret.

What KPIs should I track per location to manage a multi-branch sales team?

Track leading indicators, rather than only revenue, with identical definitions everywhere: set rate (inspections scheduled ÷ qualified leads), inspection completion rate, close rate (wins ÷ qualified opportunities), average contract value, documentation completeness, stage cycle time, and cost per lead and cost per win by source and branch. Documentation completeness and set rate are the two most predictive and the most ignored — a falling documentation-completeness number predicts stalled deals and lost supplements weeks before revenue shows the problem.

How should reps talk about insurance and claims without crossing into public adjusting?

Train one compliance frame word-for-word in every branch. A roofing contractor may inspect, document damage with photos and measurements, write an accurate Xactimate-aligned repair estimate for their own work, and hand it to the homeowner. A rep may not negotiate or 'handle' the claim, interpret what the policy covers, promise an approval or payout, promise the deductible is waived or absorbed, advertise a 'free roof,' or represent the homeowner against the insurer — that is unlicensed public adjusting. The safe sentence: we document and estimate, you file the claim, and your insurer decides coverage.

How do I set pricing guardrails for remote branches without imposing one price list everywhere?

Standardize the rules around price, not the price itself, because material and labor genuinely differ by market. Set a company-wide minimum gross margin floor that no branch can sell below without owner approval. Define a discount-approval ladder with real thresholds — for example, reps self-serve to 5 percent, branch managers to 10, regional to 15, owner beyond that or below the floor. Keep a never-free list: the deductible is never waived or absorbed and the company never advertises a free roof. Then let each branch set its actual price bands inside those rules.

Why does my second branch close at a lower rate than my home office even with good reps?

Usually it isn't talent. The four common causes are: the home-office process was never externalized so it can't transfer; the new branch manager re-invented his own process; the pipeline stages or 'qualified' definition differ so the close rates aren't even comparable; and nobody is watching leading indicators per branch, so problems aren't caught until revenue moves 60–90 days later. Standardizing the stages, the qualification definition, and the KPI definitions usually closes most of the gap before you ever discuss rep skill.

What documentation should every inspection produce, regardless of branch?

A fixed minimum file: four-side elevations, overall roof planes, each slope's field condition, all penetrations (pipe boots, vents, chimneys, skylights), flashing details (step, counter, valley, drip edge), damage close-ups with a scale reference like a tape or chalk circle, decking where visible, and an address shot to bind the set to the property. Standardize the measurement method and a scope checklist (squares, pitch, layers, penetrations, flashing footage, ventilation, local code items) too. A complete file is what lets any manager audit any deal in any location and what protects a supplement or claim weeks later.

How does RoofPredict help standardize sales across multiple locations?

It makes the front-end and pipeline rails identical in every market. It scores every home by roof-age band plus storm exposure into a ranked, house-by-house target audience with a 'why this home' evidence chain, so a new branch qualifies by the same signals instead of local guesswork. The due-roof list becomes tracked direct mail, personalized microsites and reports, per-home QR codes, and standardized canvass routes in a mobile field app. The lead pipeline runs the same new→contacting→appointment→inspected→won/lost stages with immutable first-touch source, syncs two-way with 13 CRMs, and reports a delivered→views→leads→wins funnel with cost-per-win and actual-vs-estimate-vs-benchmark. RoofClaim keeps the documentation and claim back end on locked, UPPA-gated templates.

Should every branch use the same script even in different storm markets?

Yes for structure, no for facts. Every branch runs the same seven beats — opening, qualification, inspection narration, findings, the number and options, objection handling, and the close with a dated next step — and the same five objection frames for price, timing, 'need to think,' spouse, and 'getting other quotes.' What flexes is the local nouns: the specific storm and date, the local roof systems and materials, the building-code references, and the price examples. The compliance language is the one part that stays word-for-word identical in every market because the legal exposure belongs to the company.