How to Build a Roofing Pipeline Before You Hire Your First Sales Rep

Every owner I talk to has the same instinct backwards. They think the order is: hire a sales rep, then get leads. So they post a job, pay a base salary plus commission, and wait for that person to magically conjure demand out of thin air. Ninety days later the rep is frustrated, the owner is out fifteen to twenty grand in salary and ramp, and nobody can tell whether the problem was the person or the fact that there was no pipeline for them to work in the first place.

The order that actually works is the reverse. Build the pipeline first. Prove that a defined list of homes plus a repeatable outreach motion plus a follow-up system produces booked inspections and signed contracts. Get it producing while you, the owner, are the one doing it (or supervising whoever is). Only then do you hand a working machine to a salesperson whose job is to run it harder than you had time to.

A pipeline is not a pile of leads. It is a system that reliably converts a known population of roofs into appointments, and appointments into jobs, at a measurable rate. If you can describe yours as a set of stages with conversion rates between them, you have a pipeline. If you can't, you have hope. This piece walks through how to build the real thing from zero, what numbers to track, where the storm and roof-age data fits, and how to know you're actually ready to hire.

Why "hire first, leads later" fails so reliably

The math is brutal and most owners never run it before they make the hire. A decent residential roofing sales rep in a healthy market expects to earn somewhere in the range of $70,000 to $120,000 in total comp, and a lot of that has to come early or they leave. The Bureau of Labor Statistics tracks roofers and sales workers separately, but the pattern in the field is consistent: commission-only reps churn fast when there is no flow, and salary-plus-commission reps burn your cash while they ramp.

Here is the ramp reality. A new rep needs leads on week one. If you have no system, you are now asking a brand-new employee to do the single hardest thing in the business — generate demand from scratch — at the exact moment they know the least about your company, your install quality, and your market. They will knock cold, get demoralized, and either quit or coast. Either way you paid for it.

There is a second, quieter failure. When you have no pipeline and the rep happens to be good at hustling, you become dependent on that one person's personal hustle. They own the relationships, the door list lives in their head or their phone, and the day they leave for a competitor, your "pipeline" walks out the door. You didn't build an asset. You rented one and then it left.

Building the pipeline first solves both. The demand exists before the person arrives, so they ramp on warm activity instead of cold despair. And the system — the list, the cadence, the CRM, the scripts — belongs to the company, so it survives turnover. Your first rep becomes a throughput multiplier on a proven engine, not a Hail Mary.

The honest precondition

None of this works if your install quality and customer experience are shaky. A pipeline pours water into a bucket; if the bucket leaks — bad workmanship, no callbacks returned, sloppy cleanup — you'll generate leads and incinerate your reputation faster. Before you build demand, make sure a homeowner who hires you will tell their neighbor to hire you too. The whole referral and review flywheel later depends on it.

There's a related trap. Owners who've never personally sold a roof sometimes think the rep will figure out the sales process for them. But you can't manage what you've never done, and you can't write a script for a motion you've never run. The owners who build a pipeline first end up understanding their own market better than any rep they could hire — they know which neighborhoods answer the door, which objection comes up most, what price the market actually bears. That knowledge is the real product of these ninety days. The list and the CRM are the artifacts; the understanding is the asset.

What this costs you up front

Be realistic about the investment so you don't quit halfway. Building a pipeline before hiring is cheap in dollars and expensive in your hours. You'll spend a few hundred dollars on parcel/property data and maybe a roof-data subscription, a small monthly fee for a CRM, and some money on mail if you use it. The big cost is your time: expect to put real hours per week into knocking, calling, inspecting, and logging for two months. That's the trade. You're spending your own time now so you don't spend a rep's salary on an unproven model later. If you're unwilling to spend the time, you're not ready to spend the salary either.

What a roofing pipeline actually is: stages and math

A pipeline is a sequence of stages, each with a number of records in it and a conversion rate to the next stage. Write yours down like this and everything else gets easier:

The power of writing it this way is that it forces you to know your conversion rates, and conversion rates are where money hides. Suppose you want 4 jobs a month at a $14,000 average ticket. Work backward through plausible rates:

• Won from proposal: 35% → you need ~11 proposals
• Proposal from inspection: 70% → you need ~16 inspections
• Inspection from engaged lead: 50% → you need ~32 engaged leads
• Engaged from contacted: 8% → you need ~400 contacts
• Contacted from target list: you can contact your whole target list, so the list needs to be at least 400 deep per month, ideally several times that for selection

Those rates are illustrative, not promises — yours will differ by market, season, channel, and how good your documentation is. But the discipline matters more than the exact figures. The moment you have real stage counts, you stop guessing. If you're getting plenty of inspections but few wins, your problem is the proposal and the close, not lead gen. If you're getting tons of contacts but almost no engagement, your list or your message is wrong. The pipeline view tells you which lever to pull instead of just "do more."

Build a simple model before you build the pipeline

Spend an hour in a spreadsheet. Put your target monthly jobs at the top, your average ticket, your gross margin, and your assumed conversion rates. Let it calculate how many contacts per month you need. Now you have a target volume, and every list-building and outreach decision gets measured against it. Most owners skip this and then wonder why their effort feels random. It feels random because it is.

Step one: define your geography and your universe

Before any list, define where you will and won't work. Draw your real service radius — not aspirational, real, the area where your crews can be on a roof within a sensible drive and where you can service a warranty without groaning. Density beats sprawl. A pipeline concentrated in three zip codes is cheaper to work, produces tighter routes, and compounds referrals because your trucks and yard signs cluster.

Within that radius, your universe is every owner-occupied single-family home of an age and type you can sell profitably. You can size it roughly with public data: the U.S. Census Bureau's American Community Survey publishes housing unit counts, owner-occupancy rates, and year-structure-built distributions by census tract. That tells you how many homes exist and, crucially, how old the housing stock is. A tract where the median home was built in 1998 is a very different opportunity than one built in 2019.

You are not contacting the universe. You are choosing a target list out of it. But knowing the universe size keeps you honest about whether your market can support your growth plans. If your whole serviceable area has 6,000 owner-occupied homes of the right vintage, you can't plan to do 200 jobs a year there forever without expanding geography or services.

Step two: build the target list — the part that decides everything

This is the hinge of the whole operation. A pipeline built on a sharp list will outperform a pipeline built on a random list by a wide margin, with the same outreach effort. Two factors make a roof worth contacting now:

1. Roof age. A roof aging out of its service life is statistically closer to needing replacement. Most common asphalt shingle roofs run a usable life in the high teens to mid twenties of years depending on product, ventilation, and climate. A home whose roof is 18 to 25 years old is a far better target than one whose roof is 4 years old.
2. Storm exposure. A roof that took meaningful hail or wind has functional damage that may justify an insurance-funded replacement, and the homeowner has a real, time-bound reason to act — often a filing deadline.

The homes where both are true — an older roof that also caught a storm — are your highest-intent targets. The homes where one is true are your second tier. Everything else is your someday list.

Sourcing roof age

The naive approach is to use year-built as a proxy for roof age. It's better than nothing, but it's a weak signal because roofs get replaced. A 1995 house might have a 2016 roof. What you actually want is the age of the current roof, which you can estimate from aerial and satellite imagery: granule loss, color fade, patching, streaking, and surface texture change visibly as a shingle roof ages, and historical imagery lets you bracket when the current roof was installed.

The honest framing matters here. You cannot get an exact install date from a picture. What you can responsibly produce is a range — "this roof is most likely 17 to 22 years old" — which is exactly what you need for targeting. You're not certifying anything to a homeowner; you're prioritizing which doors to knock. A range that's right most of the time turns a random list into a ranked one, and ranking is the entire game.

This is the kind of work that does not scale by hand. Eyeballing imagery for one street is fine; doing it for 6,000 homes is not a person's job. We'll come back to how to get this at list scale in a dedicated section, because it's where a tool earns its keep.

Sourcing storm exposure

For storm history you have excellent public data, and you should know it cold:

• NOAA's Storm Prediction Center (SPC) publishes daily and archived storm reports including hail and wind, with locations and magnitudes.
• The National Weather Service issues and archives severe thunderstorm and tornado warnings and local storm reports.
• NOAA's Storm Events Database lets you query historical hail and wind events by county and date.
• The Insurance Institute for Business & Home Safety (IBHS) publishes research on hail and wind damage to roofing assemblies — useful for understanding what a given hail size actually does to a roof.

The limitation of raw public storm data is resolution. A county-level hail report tells you a storm happened somewhere in the county; it does not tell you that a specific roof on a specific street took 1.5-inch stones at a damaging angle. The gap between "a storm hit the area" and "this roof was likely damaged" is real, and it's the difference between knocking a whole zip code and knocking the 40% of it that was actually in the swath.

The list-building workflow, concretely

Here's a repeatable way to assemble a target list from scratch in a week:

1. Pull the parcel/owner data for your target zips. County assessor and parcel data (often available as open data or through a property-data vendor) gives you addresses, owner-occupancy, year built, and roof square footage estimates.
2. Filter to fit. Owner-occupied, single-family, year built old enough to plausibly have an aging roof, in your service radius. This alone cuts a huge amount of noise.
3. Layer storm history. Mark which of those addresses fall inside documented hail/wind footprints from the last several years using the NOAA/NWS sources above.
4. Estimate roof age from imagery to convert "old house" into "old roof," and rank.
5. Score and sort. Give each address a simple priority score: highest = old roof + recent damaging storm; next = old roof, no storm; next = newer roof + storm; bottom = newer roof, no storm.
6. De-dupe against your CRM so you're not re-contacting existing customers or open opportunities.

The output is a ranked list. The top of that list is where your first 400 monthly contacts come from, and because it's ranked by genuine likelihood-to-need, your engagement rate climbs versus a cold random sweep.

A worked scoring example

Make the scoring concrete so you can build it in a spreadsheet. Give each address points and sort descending:

An address scoring 75+ (old roof in a recent hail swath) goes to the top of the knock list this week. A 35 (older roof, no storm) is a steady-state target you'll get to. A 15 (newer roof, minor event) waits. The exact weights are yours to tune as your close data comes in — if storm-driven addresses close at twice the rate of age-only addresses in your market, push storm points up. The discipline of scoring, not the specific numbers, is what turns a list into a route.

Refreshing the list

A pipeline you can hand off has to keep filling, so your list needs a refresh source, not a one-time pull. Roof age advances on its own — homes that were borderline last year cross into your target range this year. Storms create brand-new high-priority addresses overnight; the morning after a hail event, the homes in that footprint jump to the top of your list and they have a filing clock running, which makes them both high-intent and time-sensitive. Set a standing habit: re-pull storm data after any significant local event and re-rank. The owner who's first to document roofs in a fresh swath, honestly and without over-promising, wins a disproportionate share of that storm's work.

Step three: pick your outreach channels (and run them yourself first)

You, the owner, are going to run outreach before you hire. This is non-negotiable and it's the most valuable thing you'll do, because you cannot teach or manage a sales rep on a motion you've never personally executed. Pick two or three channels, not seven.

Door knocking

Still the highest-conversion channel in residential roofing for one reason: you're standing on the customer's property, you can point at their roof, and you can get on it the same day. With a ranked list, knocking becomes efficient — you walk the storm-and-age-prioritized addresses instead of every door. Plan routes geographically so you're not driving back and forth. Track every knock: no-answer, not-interested, callback, booked. Those tallies become your contact-to-engagement rate.

A clean, honest door opener sounds like: "Hi, I'm [name] with [company], a local roofer. We've been documenting storm and wear damage on roofs in this neighborhood — yours looks like it's in the age range where it's worth a free inspection so you know where you stand. No obligation. Can I take a quick look?" Notice what it does not promise. It does not say "you have damage," it does not say "your insurance will pay," and it does not mention a free roof. More on why that wording matters below.

Direct mail

Mail works when the list is sharp and the piece is specific. A generic "We do roofs!" postcard to a random route is wasted money. A piece that says "Homes on your street were in the path of the [month] hail storm — here's how to tell if your roof needs documenting" to a list filtered for that storm and roof age performs because it's relevant. Mail's job is usually to warm the door before you knock or to capture the homeowner who'd never answer a door but will call a number.

Local digital and reputation

A basic Google Business Profile with real photos and steady reviews, plus a simple website that ranks for "[your town] roof replacement," produces inbound that's higher-intent than anything outbound. It's slower to build but it compounds. While you're knocking, also ask every satisfied customer for a review and a referral — referrals are the cheapest, highest-closing leads you will ever get, and they cost a phone call.

Canvassing partnerships

Property managers, real estate agents doing pre-sale inspections, and solar installers all touch roofs and can refer. These take longer to set up but feed the pipeline steadily once established.

Run whichever two or three fit your market and your stomach. Track each channel's contacts, engagement, and cost so that when you hire, you can point the rep at the channel with the best return and say "do more of this, here's exactly how."

Why two channels, not seven

New owners scatter. They try door knocking and mail and Facebook ads and a billboard and a lead-buying service all at once, run none of them well, and can't tell which one worked. Two channels run with discipline beat seven run halfway every time, for a simple reason: you can only learn a channel by doing enough volume to get a real conversion rate out of it, and you can't get volume on seven things by yourself. Pick the two that fit your market — in most residential markets that's knocking your ranked list plus targeted mail to the same list — and run them until you have hard numbers. Add a third only once the first two are systematized enough to hand off.

A note on buying leads

Shared internet leads have a place, but don't build your pipeline on them, and especially don't build a pre-hire pipeline on them. They're expensive, sold to several contractors at once, and they teach you nothing about your market because someone else generated the demand. The whole point of building first is to own the demand-generation system. A rented lead source is the opposite — it's the dependency you're trying to avoid, just with a vendor instead of a star rep. Use bought leads to smooth a slow week if you must, never as the engine.

Safety is part of the system

The moment you're getting on roofs to inspect and the moment a crew is up there installing, OSHA fall-protection rules apply, and a single fall can erase a year of pipeline work in claims and reputation. Bake safe inspection practices into the workflow from day one — proper ladder setup, fall protection where required, and a hard rule that nobody walks a roof that's wet, frosted, or too steep to be safe. It's not a tangent to sales; an injury or a citation is a pipeline-ending event, and a rep you hire later will copy whatever habits you modeled.

Step four: the follow-up system that most roofers don't have

This is where pipelines are won and lost, and it's the least glamorous part, which is exactly why your competitors are bad at it. The data on follow-up in home services is consistent: most homeowners don't buy on first contact, most contractors quit after one or two touches, and the deals go to whoever is still politely present when the homeowner is finally ready.

Your follow-up system needs four things:

1. A CRM where every contact is a record with a stage and a next action. It does not need to be expensive. It needs to be the single source of truth, not five reps' phones and a notebook. Every prospect has a status and a date for the next touch. If a record has no next action, it's dead by neglect — and that's a choice you're making by accident.
2. A defined cadence. For an engaged-but-not-booked lead, something like: same-day text recap, day-2 call, day-5 email with the inspection offer, day-10 value touch (a photo of a similar roof you documented, a note about the filing window if a storm applies), then a monthly check-in. For inspected-but-not-signed, a tighter cadence because the iron is hot.
3. Speed to first response. When an inbound lead comes in — a form fill, a missed call, a referral — the clock starts. Responding within minutes versus hours is the single biggest controllable factor in whether you ever talk to that person. Before you hire, you answer fast. After you hire, this becomes the rep's first rule.
4. Documentation that travels with the record. Every inspection produces photos and notes attached to the CRM record. This is your proof, your proposal input, and — if a storm claim is involved — the homeowner's evidence. It also means a record can be picked up by anyone, which is what makes the pipeline a company asset instead of one person's memory.

The inspection and estimate, done right

The inspection is where a contact becomes an opportunity, and the quality of your documentation is the single biggest lever on whether the proposal closes and, when a storm is involved, whether the homeowner's claim has any evidence behind it. Treat every inspection like you'll have to defend it later, because sometimes you will.

A documentation standard worth running on every roof:

• Overview shots of every elevation and slope, so anyone can orient the close-ups.
• Measurements — total squares, pitch, number of layers, penetrations, flashing condition — captured the same way every time so estimates are consistent.
• Damage close-ups with something for scale on hail bruising, mat fractures, creased or missing shingles, and granule loss in gutters, each one tied to a slope.
• System components — ventilation, underlayment type where visible, drip edge, valleys, pipe boots — because these drive scope and price.
• Interior and attic where accessible, for active leaks and decking condition.

From that you write an accurate repair estimate. Align it to the standard line-item structure the carrier's estimating software uses if a claim is in play — not to inflate anything, but because a clean, itemized, correctly-measured estimate is far easier for everyone to act on and far harder to dispute. The estimate is a contracting document about your scope and your price. It is not a coverage determination, and you don't present it as one. You hand it to the homeowner; what happens with insurance is between them and their insurer.

A worked follow-up example

You knock a prioritized door on Monday. Homeowner is interested but busy. You log them as Engaged, next action: text recap today, call Wednesday. Wednesday they don't answer; you leave a voicemail and move next action to Friday email. Friday you email the free-inspection offer with a photo of their roof's age indicators. Following Tuesday they reply and book for Thursday. You inspect, document 60 photos, write the estimate, send it Friday. They go quiet. You move them to a tighter cadence: call Monday, value-touch Thursday, call the following Monday. Three weeks after the first knock, they sign. Without the system, that deal evaporated after Wednesday's missed call. With it, it closed. Multiply that across a list and the difference is your year.

Where roof-age and storm data does the heavy lifting (and where RoofPredict fits)

Everything above assumes you can produce a ranked target list and know which roofs caught a storm. Doing that by hand — pulling parcels, cross-referencing NOAA footprints, eyeballing imagery for roof age across thousands of addresses — is possible, but it's a real labor cost, and labor is the thing you're trying not to spend before you've proven the model.

This is the specific job RoofPredict does. It looks at the homes in your service area and gives you, address by address, an estimated roof-age range from aerial imagery, plus storm exposure modeled per individual roof rather than per county. It will also enrich a list you already have — your old quotes, your canvassing route, your mailing list — by appending those roof-age and storm signals so you can rank what you already own. The output is the ranked target list this whole approach depends on, without you or a future rep grinding through imagery by hand.

Be clear-eyed about what it is and isn't. The roof age is a range and an estimate, not a certified install date — it's for prioritizing doors, not for telling a homeowner a fact about their property. The storm modeling is odds of meaningful exposure, not proof of damage on a specific roof; only an inspection establishes actual damage. It does not buy or sell you leads, and it does not contact homeowners for you — it ranks who's worth your contact so your knocking, mailing, and follow-up land where demand actually is. Used that way, it turns the most labor-intensive step of pipeline building — figuring out which roofs are due — into a list you can hand to a rep on day one. Used as a magic lead button, it'll disappoint you, because no data replaces the door, the inspection, and the follow-up.

The reason this matters for the "before you hire" sequence: the single biggest reason a new rep stalls is a bad or nonexistent list. If you can hand your first hire a ranked list of the roofs most likely to be due in their territory, you've removed the hardest part of their ramp and you can hold them accountable on activity instead of excuses.

Staying legal when storms are involved: the documentation line

If any part of your pipeline touches storm damage and insurance — and in most markets it will — you have to know exactly where the legal line is, because crossing it is how roofers get into real trouble and damage the whole trade's reputation. The line is about who does what, and it's not subtle once you see it.

What a roofer may do. You may inspect a roof. You may thoroughly document damage with photos and measurements. You may prepare an accurate repair estimate for your own scope of work — ideally aligned to the standard estimating line items the carrier's software uses — and hand that estimate to the homeowner. You may state facts about your scope to the carrier. That is contracting work, and it's exactly what your documentation system above is built to produce.

What a roofer may not do. You may not, for a fee, negotiate or adjust or "handle" the homeowner's claim. You may not interpret their policy or tell them what is or isn't covered. You may not promise a specific payout or that the claim will be approved. You may not tell them the deductible will be waived, absorbed, or made to disappear — that's both illegal in many states and an insurance-fraud trap. You may not advertise a "free roof." And you may not represent the homeowner against their insurer. All of that is the licensed work of a public adjuster, and doing it without a license is a serious violation. State insurance departments — Texas's TDI, for example — publish guidance on exactly this distinction, and several states have statutes specifically barring contractors from acting as public adjusters or from rebating deductibles.

The safe frame, said plainly. You document thoroughly. You write an accurate, defensible repair estimate. You hand it to the homeowner. The homeowner files the claim. The insurer decides coverage. Your value to them is the quality and completeness of your documentation and estimate, plus doing excellent work — not steering the claim.

The do-not-say list, for you and your future rep

Teach this to anyone who knocks or talks to homeowners for you, before they ever say a word in the field:

• Don't say "your insurance will pay for this" or "this is a covered claim."
• Don't say "we'll get your deductible waived / we'll eat the deductible / no out-of-pocket."
• Don't say "free roof" or "free roof replacement."
• Don't say "we'll handle the whole claim for you" or "we'll deal with the adjuster for you."
• Don't say "you're guaranteed approval" or promise any specific dollar figure.
• Don't interpret their policy language or tell them what their coverage means.

Do say: "We'll document everything we find and write you a detailed estimate. You file the claim; your insurer decides what's covered. If they approve it, we'd be glad to do the work to that scope." That sentence captures every bit of the homeowner's real interest while keeping you on the right side of the line. Build it into your scripts now, because a brand-new commission-hungry rep is exactly the person most tempted to over-promise, and you want the compliant version baked into the system before they arrive.

Step five: instrument the pipeline so it's a system, not a vibe

A pipeline you can't measure can't be improved, taught, or handed off. Track these numbers weekly from the day you start:

The reason to instrument before hiring is that these numbers become the rep's scorecard and your management dashboard at the same time. "Your contact-to-engaged rate is half mine, let's ride along" is a coaching conversation. "You're not selling enough" is not. The first one fixes things; the second one loses reps.

Keep a simple weekly review: pull the stage counts, look at where the biggest drop-off is, and pick one lever to work on that week. That single habit will make you better at sales than ninety percent of owners, and it's the habit you'll most want to instill in your first hire.

Reading the numbers: three common patterns

Once you have a few weeks of data, the shape of your funnel usually tells one of a few stories. Learn to read them so you fix the right thing:

Lots of contacts, almost no engagement. Your list or your message is off. Either you're contacting roofs that aren't actually due (weak ranking) or your opener isn't landing. Tighten the list first — re-check your roof-age and storm filters — then test a sharper, more specific message. This is the most common early failure and it's almost always a list problem masquerading as a sales problem.

Good engagement and inspections, weak proposal-to-won. People let you on the roof but don't sign. Your problem is downstream: pricing, the proposal itself, or the close. Look at whether your estimates are clear and itemized, whether you're following up tightly after sending, and whether you're losing on price or on trust. This is fixable with better proposals and discipline, not more leads.

Good close rate, not enough volume. When you do talk to someone you win, but you're not talking to enough people. This is the happy problem — your sales motion works and you just need more top-of-funnel. It's also the clearest signal that you're ready to hire, because adding a person to a high-converting motion is pure upside.

The reason to know these patterns before you hire is that a rep will produce the same shapes, and you'll need to coach to the actual constraint instead of just saying "sell more."

Step six: know when you're actually ready to hire

Don't hire on hope. Hire on evidence. You're ready when you can answer yes to most of these:

• You have a ranked target list that refreshes — you're not going to run out of prioritized doors.
• You know your conversion rates at each stage from your own real activity, not assumptions.
• Your follow-up system runs in a CRM, not in your head, so it can be handed to someone else.
• Your unit economics work. You know your cost per booked job and your margin, and there's room in it to pay a rep and still profit.
• You're at capacity. The honest trigger to hire is that you, the owner, can no longer personally work the pipeline and run the business — demand exceeds the hours you can give it. That's a good problem and the right moment.
• You have a compliant script and a do-not-say list written down, so you're handing over a safe motion, not a liability.

When those are true, hiring is low-risk: you're plugging a person into a working machine, with a list to work, a cadence to follow, a scorecard to be measured against, and rules that keep them legal. That rep ramps in weeks, not quarters, because there's warm activity from day one.

What to look for in that first rep, given a working pipeline

Because the system does the demand-generation heavy lifting, you don't need a unicorn rainmaker — you need someone coachable, organized, and relentless about follow-up, who will run your cadence and log everything. Pay structure should reward both activity (doors knocked, inspections booked, records kept current) and outcomes (signed jobs), so the leading indicators stay healthy and don't get sacrificed for short-term closes. Ride along for the first weeks; the pipeline is yours, and you're teaching them to run it, not abdicating it.

Structuring the comp so it protects the system

The two extremes both fail. Pure commission attracts people who'll over-promise to close — the exact behavior that gets a roofer into compliance trouble — and who'll cherry-pick easy deals while letting your follow-up cadence rot. Pure salary removes the urgency that makes a sales role work. The middle that protects a system you built carefully is a modest base that covers ramp, plus commission on signed jobs, plus a small activity component tied to the leading indicators you already track: doors worked, inspections booked, and records kept current in the CRM. You're paying for the behaviors that keep the pipeline healthy, not only the closes that happen to fall out this month.

Write the do-not-say list and the documentation standard into the comp conversation explicitly. Make it clear that a deal closed by promising a waived deductible or a free roof isn't a win — it's a liability you'll claw back, and a fireable one. A rep who learns your compliant motion from day one will never know any other way to sell, which is exactly what you want. The owner who hands over a vague "go sell roofs" mandate with a fat commission and no rules is the owner who ends up with a state insurance-department complaint and a reputation problem. The owner who hands over a ranked list, a cadence, a scorecard, and a clear compliance line gets a rep who multiplies a clean machine.

Onboarding the first hire onto the pipeline

Don't drop a new rep into the deep end even with a working system. Spend the first week with them in the CRM and on ride-alongs: show them how the list is ranked and why, knock a few doors together so they hear your compliant opener live, walk an inspection and show them the documentation standard, and sit with them while they send a proposal and set the follow-up cadence. Give them a slice of the ranked list to own, not the whole thing, so you can watch their numbers against yours on the same kind of addresses. Within a few weeks their stage conversion rates should approach yours; where they don't, you've found the exact thing to coach. Because you measured everything yourself first, you have a baseline — and a baseline is the difference between coaching and guessing.

A 90-day plan to go from zero to a pipeline you can hand off

Here's the whole thing sequenced. Adjust to your market, but follow the order.

Days 1–10: Foundation. Confirm install quality is solid. Define your service radius and target zips. Pull Census housing data to size your universe. Stand up a simple CRM. Build your spreadsheet model (target jobs → required contacts). Write your honest door script and your do-not-say list.

Days 11–25: Build the list. Pull parcel/owner data for your zips. Filter to owner-occupied, single-family, right vintage. Layer storm history from NOAA/NWS. Add roof-age estimates from imagery (by hand for a test block, or use a tool like RoofPredict to rank the full list). Produce a ranked target list and de-dupe against any existing customers.

Days 26–60: Run outreach yourself. Pick two channels (say, knocking the ranked list plus targeted mail). Work them personally. Log every contact in the CRM with a stage and next action. Run the follow-up cadence religiously. Answer every inbound within minutes. Book and run inspections; document thoroughly; write clean estimates; hand them to homeowners.

Days 61–80: Measure and tune. Compute your stage conversion rates and cost per booked job. Find the biggest drop-off and improve it. Confirm your unit economics leave room to pay a rep. By now you should have real jobs closed and real numbers, not theories.

Days 81–90: Prepare the handoff. Write down the playbook: the list source and ranking logic, the channels and scripts, the cadence, the CRM stages, the scorecard, the compliance rules. This document is what makes your pipeline a transferable asset. Post the role. When you hire, you hand over a machine and a manual, not a wish.

Do this and your first sales rep walks into warm activity, a list of roofs that are genuinely likely to be due, a follow-up system that doesn't let deals rot, and rules that keep them out of trouble. That's the difference between a hire that pays for itself in a quarter and a hire that quietly drains your bank account while everyone wonders what went wrong. Build the pipeline first. The rep is the multiplier, not the engine.

If the piece of this you'd most like to skip is the grind of figuring out which roofs in your area are actually due — the imagery, the storm cross-referencing, the ranking — that's the part RoofPredict is built to hand you as a finished, prioritized list (roof-age ranges and per-roof storm odds, honest about their limits), or to layer onto the list you already have. Start with one or two zip codes, work the top of the ranked list yourself for sixty days, and let the numbers tell you when it's time to hire.

FAQ

How long does it take to build a roofing pipeline before hiring a sales rep?

Plan on about 90 days of focused effort to go from zero to a handoff-ready pipeline: roughly two weeks to define geography and build a ranked target list, a month of running outreach and follow-up yourself, and a few weeks to measure your conversion rates and write down the playbook. The point isn't speed — it's having real numbers and a working system before you spend money on a hire.

How many leads do I need in my pipeline before I hire my first rep?

Work backward from a revenue target instead of guessing a lead count. Pick your target monthly jobs and average ticket, apply realistic stage conversion rates, and the model tells you how many contacts and engaged leads you need per month. Practically, you want a ranked target list deep enough that you never run out of prioritized doors and a refresh source so it keeps filling.

What's the difference between a roofing pipeline and just having leads?

Leads are a pile of names. A pipeline is a sequence of stages — target list, contacted, engaged, inspection booked, inspected, proposal sent, won — each with a known conversion rate to the next. If you can state your stage counts and rates, you can diagnose exactly where deals are leaking and fix that lever. A pile of leads tells you nothing about why you are or aren't closing.

How do I figure out which roofs in my area are most likely to need replacement?

Two signals do most of the work: roof age and storm exposure. Estimate roof age from aerial and historical imagery as a range, not an exact date, and layer documented hail and wind footprints from NOAA and the National Weather Service. Roofs that are aging out and also caught a damaging storm are your highest-intent targets. Doing this at scale by hand is heavy, which is where roof-data tools that rank addresses for you save the most time.

Can I promise homeowners that insurance will pay for their roof or that I'll waive their deductible?

No, and doing so creates serious legal exposure. You may inspect, document damage, and write an accurate repair estimate for your own scope and hand it to the homeowner. You may not promise coverage or approval, interpret their policy, advertise a free roof, or waive, absorb, or rebate the deductible — that crosses into unlicensed public adjusting and, with deductibles, into fraud in many states. The homeowner files; the insurer decides coverage.

What should I say at the door to stay compliant on storm-damage outreach?

Offer a free, no-obligation inspection based on the roof's age and the neighborhood's storm exposure, and commit only to documenting what you find and writing a detailed estimate. Make clear the homeowner files the claim and the insurer decides coverage. Avoid saying their insurance will pay, that the claim is covered, that the deductible disappears, or that the roof is free. Build the compliant wording into your script before any rep uses it.

Do I really need a CRM before I hire a sales rep?

Yes — a simple one, but yes. The CRM is what makes your pipeline a company asset instead of one person's phone and memory. Every prospect needs a stage and a next action so deals don't rot from neglect, and the follow-up cadence has to live somewhere transferable. If your pipeline lives in your head, it walks out the door the day a rep leaves.

What follow-up cadence actually works for roofing leads?

Most homeowners don't buy on first contact and most contractors quit too early, so persistence wins. For an engaged lead, a workable rhythm is a same-day text recap, a day-two call, a day-five inspection offer by email, a day-ten value touch, then monthly check-ins. For an inspected-but-unsigned prospect, tighten it up. Above all, respond to inbound leads within minutes — speed to first response is the biggest controllable factor in whether you ever talk to them.

How does roof-age and storm data actually help before I hire?

The hardest part of a new rep's ramp is a bad or nonexistent list. If you can hand them a list of addresses ranked by likelihood the roof is due — roof-age range plus per-roof storm odds — you remove the demand-generation guesswork and can hold them accountable on activity and follow-up instead of excuses. Tools like RoofPredict produce or enrich that ranked list; just treat the age as a range and storm exposure as odds, not proof of damage.

When is the right time to actually make the hire?

When the evidence says yes: you have a refreshing ranked list, you know your real conversion rates, your follow-up runs in a CRM, your unit economics leave room to pay a rep and still profit, you have a compliant script written down, and — the honest trigger — you personally can no longer work the pipeline and run the business at the same time. At that point you're plugging a person into a proven machine, which is a low-risk hire.