WANOGuide · Templates included
Roofing referral programs that actually get used
Most referral programs die on paper — announced once, never asked again, one uncredited referral away from a customer quietly quitting. The ones that work come down to three decisions: a reward anyone can understand ($100 cash when the referred job closes), an ask that runs on a clock instead of memory, and tracking that makes sure every referral gets credited. This page has the timing data, the reward math, and the copy-paste ask templates.
The highest-trust lead you can get
Every roofer already knows this one. Across industry surveys, roughly 70% of roofers name referrals their number-one lead source — and the trust math explains why. Per Nielsen's consumer research, 92% of people trust a recommendation from someone they know, which is a level of credibility no ad budget buys. A referred homeowner arrives pre-sold by the neighbor whose roof you already did.
The value compounds after the sale, too: JobNimbus's referral research puts referred customers at 16% higher lifetime value than customers from other channels. They close easier, they price-shop less, and they refer in turn.
So the problem isn't belief — it's system. For most roofing companies, referrals happen by accident. There's no consistent ask, no tracking, and no reliable reward, so the channel everyone calls their best one runs entirely on luck. You can spend your time prospecting strangers, or you can spend it working the customers you already won. The rest of this page is the second option, written down.
The ask runs on a clock — not on memory
First: don't ask the day the crew leaves. Day-of belongs to the review ask, and a message that asks for a review and a referral gets neither. Give the review its moment, then come back for the referral.
Come back fast, though. JobNimbus CRM data shows that asking within 48 hours of job completion earns up to 40% higher referral response rates than waiting a week. Satisfaction peaks right after the project — so the first referral ask lands on day 2 or 3, while the roof is still the newest thing on the street and your yard sign is still in the ground doing quiet credibility work.
Then the sequence keeps going, because referral moments don't stop when the job does. A soft check-in at day 30 — by then the neighbors have noticed the roof and some have asked about it. After that, seasonal touches at months 3, 6, 12, 18, and 24. Per JobNimbus, fall is historically the strongest referral window in roofing: homeowners are getting their houses ready for winter, roof conversations are happening up and down the street, and your work is still visible in the neighborhood. A fall re-ask every year the drip runs catches that window on purpose.
Two years of well-timed asks per customer. Nobody does that by hand — which is exactly why it's an automation sequence and not a sticky note.
Pay cash, pay on close, pay fast
Reward design is where programs get overthought. The version that works fits in one sentence: "Tell someone, get $100 when they sign."
- Cash wins. Per JobNimbus's incentive research, $100 cash per closed referral is the benchmark — clear, universally understood, and motivating. Gift cards run a close second. Service discounts sound clever but move fewer people; a homeowner who just got a new roof doesn't need 10% off another one.
- Pay on the closed job, not the lead. The reward triggers when the referred job signs — not when a name gets submitted. That keeps the math clean and the referrals real.
- Pay fast. Delays in delivering the reward reduce future participation more than any other mistake. The customer told a friend, the job closed — the $100 should show up that week, with a thank-you attached.
- Reward both sides if you can. A small discount for the referred neighbor takes the "profiting off a friend" awkwardness out of the ask — the advocate isn't selling a buddy out, they're doing them a favor too.
- Simple beats tiered. Tiers can work at scale — one referral = $100, three = $350 — but only if a customer can recite the whole program from memory. If the terms need a table, they need a rewrite.
The ask, word for word
Swap the [bracketed] placeholders for real names, your reward amount, and your referral link. The tone rule: sound like the owner thanking a customer, not a rewards program. These go out on day 2–3, after the review ask has had its moment.
Hi [Name], it's [Your name] with [Company] — thanks again for trusting us with your roof. If a neighbor or friend ever needs roofing work, send them my way and we'll pay you $[100] when their job closes. Here's your link: [Referral link]
Hi [Name],
[Your name] here with [Company]. Hope the new roof is treating you well.
Quick thing: most of our work comes from folks like you telling a neighbor. If you know anyone who needs roofing work — a repair, a replacement, or just an honest look — send them this link: [Referral link]
When their job closes, we send you $[100]. The full terms are written out on that page — no fine print.
Thanks again for the work,
[Your name]
[Company] · [Phone]
Hi [Name], [Your name] with [Company] — how's the roof holding up a month in? If any neighbors have asked about the work, your referral link's still live: [Referral link]. $[100] to you when their job closes.
Hi [Name], [Your name] with [Company]. Winter's coming, and this is the season folks finally get their roofs checked. If anyone you know is putting it off, send them our way — the $[100] referral bonus is still running: [Referral link]
Ground rules: these are texts to past customers you've done work for — prior-relationship only, opt-out honored from message one, nothing before 9am or after 8pm. If they refer someone, the drip pauses and a thank-you goes out instead.
If a referral can't be credited, the program is already dead
Here's how informal programs actually die: a customer sends a neighbor, the neighbor calls the office, nobody asks who referred them, and the $100 never happens. The customer notices. They don't complain — they just never refer again, and they mention it at a barbecue. One uncredited referral costs you every future one from that street.
The fix is boring and mechanical. Every ask carries a referral link tied to that customer, so credit is automatic instead of remembered. A QR code on the invoice and the yard sign points to the same referral page, which captures the neighbor's name and who sent them. Both land in the CRM as a referral with a source attached, and when the job closes, the reward triggers on its own — no one has to remember to be grateful.
That's the whole tracking system: unique links, one landing page, source logged, reward on close. Per JobNimbus's guide, this is the difference between a formal program and word of mouth by accident — without tracking there are no consistent rewards, and without consistent rewards there's no program.
Two rules that keep it clean
- Referrals and reviews are separate programs. Paying a customer for sending you a job is a referral fee — legal, normal, and as old as the trades. Paying anything for a Google review — cash, discount, gift card — violates Google's review policy and risks the profile that makes your phone ring. So the messages never mix: "leave us a review and refer a friend for $100" is a sentence that should never go out. Review ask day-of, referral ask day 2–3, money only ever attached to the second one. The full review playbook is in our Google reviews guide.
- Insurance jobs need the terms in writing. Referral bonuses tied to insurance-paid restoration work can run into anti-kickback rules in some states. Write the program terms down, disclose the bonus, and check your state's rules before paying rewards on claim work. Retail jobs are simpler — a written terms page on your referral link covers you.
Common questions
Want the two-year drip to run itself?
Everything on this page works done by hand — for about three weeks, until the season picks up and the day-30 check-ins stop going out. We wire it into your existing CRM as a system: job marked complete triggers the sequence, the fall re-ask fires every year, referral links track who sent whom, and the reward triggers when the job closes. This drip runs for two years automatically — per customer, every customer. If you'd rather run it manually, the templates are yours — no email gate, no catch.