Customer Referral Program for Roofing Companies

A roofing referral program should make it easy for a willing customer to introduce someone who may need help. It should not turn every service conversation into a pressure campaign or treat a positive review as the price of receiving a reward.

The operating system is simple: define eligibility, choose a modest and lawful reward, ask permission at an appropriate moment, disclose the incentive where it matters, track the introduction, and thank the customer whether or not the referral becomes a job.

Use this page to set up the program. Use the referral ask script generator for a conversation draft and keep review requests separate from paid referral activity.

Download the roofing referral tracking worksheet

Use one row per introduction and keep the reward decision separate from the sales stage. This roofing referral tracking spreadsheet template gives the office an answer to three questions: did the person expect our contact, what happened to the opportunity, and has the published reward condition actually been met?

Completed example: a collected-job reward

Illustrative only: a fictional roofing company’s approved program pays a $150 thank-you after an eligible new customer’s job is completed and collected. This demonstrates the ledger; it does not recommend that amount or establish permission for an incentive in your market.

The second example row shows why “qualified” and “eligible for reward” need separate fields. The referred person already has an open opportunity, so the coordinator marks duplicate review, leaves the reward unapproved, and assigns a next action to the program owner. Do not delete that introduction or promise a payment while ownership is unresolved.

Use the worksheet in the weekly referral review

1. At introduction: record the permission reference, contact channel, date, referrer, and owner. A name supplied by somebody else is not the permission record.
2. At qualification: complete the duplicate check and write the result. Keep lost or ineligible opportunities visible so the denominator does not become only the jobs that won.
3. At each milestone: add actual held, signed, completed, and collected dates. Leave future milestones blank rather than filling them with forecasts.
4. Before payment: compare the program version and trigger with the job evidence. Record approver, amount, delivery date, and payment reference. “Approved” and “issued” are different statuses.
5. At follow-up: filter for a due next action or an approved reward without delivery. Resolve the exception with one named owner.

For the customer-facing conversation, open the permission-based referral ask tool. The tracker manages the program after the introduction; it does not replace a thoughtful ask or your CRM’s contact controls.

Roofing referral program template

Publish the terms in plain language. A participant should not have to guess whether a neighbor's name, a completed appointment, or a paid project earns the reward.

Keep referrals, reviews, and testimonials separate

These are different actions:

• A referral introduces a potential customer.
• A review describes a customer's experience on a review platform.
• A testimonial is an endorsement the company may reuse in marketing.

Keep referral incentives separate from reviews. Google Maps prohibits incentives for any review, including a neutral one. Do not condition a referral payment on praise, and do not quietly reuse a private thank-you as a public testimonial.

Use the Google review request tool for a separate, neutral request that does not depend on a referral reward.

The Federal Trade Commission says endorsements must be truthful and not misleading, and material connections that could affect how people evaluate an endorsement should be disclosed. Its current endorsement guidance also addresses compensated promotion and reviews. State law, platform rules, licensing rules, and contract terms can add requirements; review the program with qualified counsel before launch.

If a customer posts publicly about the company while receiving a referral benefit, provide a clear disclosure instruction appropriate to the channel. A vague hashtag or disclosure hidden elsewhere may not be enough.

Choose the trigger before choosing the reward

The trigger determines cost, delay, and participant expectations.

Avoid calling one option “best” for every roofer. Model the program using your close rate, gross profit, administrative cost, fraud risk, and payment timing.

Example: if a company pays $150 after a completed eligible job, it should budget not only the reward but also administration, software, disputes, taxes or reporting if applicable, and the possibility of cancellations. This is an illustration, not a recommended amount.

Pick an appropriate moment to ask

Ask after a real, documented service moment—not because a script says the customer must be happy.

Potential moments include:

• the customer gives unsolicited positive feedback;
• a promised update or correction is completed and acknowledged;
• the final walkthrough is complete and open items are resolved;
• a past customer checks in with a new question and confirms the prior work went well.

Do not ask while a complaint, punch-list item, billing dispute, leak, warranty issue, or insurance confusion remains open. The CRM status should prevent an automated ask in those cases.

When a customer issue is still active, move it into the service recovery process instead of trying to create a referral moment.

A permission-based referral conversation

Use four parts:

1. Reference the real moment: “I’m glad the final walkthrough answered your questions.”
2. Ask permission: “Would it be alright if I explain our referral program?”
3. Explain the terms: state who qualifies, what action earns the reward, and when it is delivered.
4. Offer a low-friction next step: an introduction link or message the customer can send if someone asks for help.

Example without an incentive:

If a neighbor asks who handled the project, would you feel comfortable introducing us? No pressure—I can send a short contact card you can share if it is useful.

Example with an incentive:

Would it be alright if I explain our referral program? If a new customer you introduce completes an eligible project, we send a $[amount] thank-you after final payment. I can send the full terms and a link. If you mention us publicly, please disclose that referral benefit.

The referral ask script generator deliberately excludes incentive terms and does not assume satisfaction. A manager should verify the final message against the published program and add any required incentive disclosure through the approved process.

Build consent into the introduction

The cleanest referral is an introduction the prospective customer expects.

Prefer one of these flows:

• the customer shares a company contact card and the neighbor reaches out;
• the customer sends a group text or email introducing both parties;
• the customer submits a form confirming the person agreed to be contacted.

Avoid adding a name and phone number to automated marketing because someone else submitted it. Respect applicable calling, texting, email, privacy, and do-not-contact requirements.

If the customer needs a documented project next step rather than a referral request, use the follow-up generator and keep the purposes separate.

CRM workflow

Create a distinct referral source and preserve the relationship between the referrer and opportunity.

Minimum fields:

• referrer name and customer record;
• referred person's consent path;
• date and source of introduction;
• duplicate-lead check;
• program version and eligibility status;
• milestone dates;
• reward amount and approval;
• payment or delivery date;
• exceptions and dispute notes.

Automations should prompt a person to review eligibility rather than paying blindly. Put open service issues, cancellations, refunds, employee referrals, and duplicate ownership into a manual-review queue.

Measure the program honestly

Track the funnel without declaring that referrals universally beat every paid channel.

• introductions received;
• contactable, consented introductions;
• appointments held;
• agreements signed;
• jobs completed and collected;
• rewards issued;
• total program cost;
• gross profit from referred work;
• time from introduction to reward;
• complaints, disputes, and opt-outs.

Useful formulas:

Cost per qualified referral = total program cost ÷ qualified referrals

Cost per collected referred job = total program cost ÷ collected referred jobs

Program contribution = gross profit from collected referred jobs − program cost

Compare those values with the same definition and time period used for other lead sources. Do not compare referral cost after close with an ad platform's cost per raw lead.

The roofing marketing ROI calculator provides a broader channel model when referrals need to be compared with paid and owned acquisition sources.

Launch checklist

• define eligibility, trigger, exclusions, and reward timing;
• review federal, state, local, platform, licensing, privacy, and tax considerations;
• publish readable terms and a contact for questions;
• separate referral, review, and testimonial workflows;
• create a consent-based introduction path;
• configure CRM fields and duplicate handling;
• train reps with permission-based examples;
• test reward approval and accounting;
• audit a sample after 30 days;
• pause the automation when service issues are open.

Frequently asked questions

How much should a roofing company pay for a referral?

There is no universal amount. Work backward from gross profit, expected conversion, administrative cost, legal constraints, and the milestone that earns the reward. Publish the amount and timing before the introduction.

When should a roofer ask for a referral?

After a genuine positive service moment and only when open issues are resolved. Ask permission before explaining the program.

Can we pay for a Google review?

No. Google Maps prohibits payment, discounts, free goods, or other incentives in exchange for any review, including changing or removing one. Keep the referral reward separate and request reviews without influencing the rating.

What if the referral is already in the CRM?

Use the published duplicate-lead rule and a documented review process. Do not improvise after the customer expects a reward.

Should the rep enter the neighbor's contact information?

Prefer a direct or group introduction that confirms the person expects contact. Follow applicable communication, privacy, and company requirements before adding someone to marketing.