Setting up a GoHighLevel sub-account for a roofing client is different from setting one up for a dentist, a realtor, or a med spa. Roofing has extreme seasonality driven by weather events rather than calendar cycles. The sales process is heavily influenced by insurance claims. Lead urgency ranges from a homeowner casually considering a 20-year-old roof replacement to someone with an active leak that needs tarping today. And the competitive dynamics during storm season are intense: multiple contractors canvassing the same neighborhoods, all racing to the same inspection appointments.
A GoHighLevel roofing setup that accounts for these realities looks fundamentally different from a generic sub-account with a contact form and a basic pipeline. This guide walks through every component a roofing sub-account needs, in the order they should be built, so each piece connects to the next without broken triggers or orphaned automations.
Custom fields: the foundation everything else depends on
Custom fields must be created before any automation, email sequence, or quiz is built. Every merge field in an email, every conditional trigger in a workflow, and every data point in an internal notification references a custom field. If the field does not exist when the automation tries to populate it, the merge fails silently and the lead receives a broken message or the notification arrives with blank data.
The roofing custom field set:
| Field Name | Type | Used In |
|---|---|---|
| Damage Type | Dropdown | Quiz, pipeline routing, email merge |
| Insurance Status | Dropdown | Quiz, scoring, email sequence selection |
| Insurance Company | Text | Internal notification, adjuster coordination |
| Policy Number | Text | Internal notification |
| Roof Age | Dropdown | Quiz, scoring |
| Property Type | Dropdown | Quiz, pipeline routing |
| Lead Score | Number | Scoring workflow, pipeline routing |
| Lead Temperature | Dropdown | Pipeline stage assignment, email selection |
| Preferred Inspection Date | Date | Booking, internal notification |
| Referral Source | Dropdown | Attribution, reporting |
These ten fields cover the minimum data requirements for roofing lead management. Additional fields like adjuster name, supplement status, and job completion date become relevant for post-sale automation but are not required for the initial lead capture and booking pipeline.
Building the roofing pipeline with temperature tiers
The roofing pipeline needs more granularity than a generic sales pipeline because the urgency spectrum is wider than most industries. An active leak and a "thinking about it for next year" inquiry require completely different handling, and mixing them into the same pipeline stages creates chaos for the sales team.
The recommended pipeline stages for roofing:
Emergency. Active leaks, structural compromise, or tarping requests. These leads skip all nurture sequences and trigger immediate internal alerts. The sales team's only job is to get someone on-site as fast as possible.
Hot: Insurance Storm Damage. Leads with active insurance claims for weather-related damage. These are the highest-value non-emergency leads because the budget is pre-approved by the insurer. The follow-up sequence focuses on scheduling the inspection and positioning the company as the preferred contractor for the adjuster walkthrough.
Warm: Damage, No Claim. Leads who report damage but have not filed an insurance claim. The nurture sequence educates them on the claims process, helps them understand whether their damage qualifies, and positions the roofing company as a guide through the insurance workflow. Many of these leads convert to hot once they file and get approved.
Nurture: Routine Maintenance. Leads requesting age-related inspections, cosmetic upgrades, or preventive maintenance with no urgency. These enter a longer nurture sequence with seasonal content, maintenance tips, and periodic offers for free inspections. They convert when the timing aligns with their budget and motivation.
Inspection Scheduled. Any lead who has booked an on-site inspection, regardless of their original tier. At this stage, the automation shifts to confirmation messages, preparation instructions, and the day-before reminder.
Estimate Delivered. The inspection is complete and the estimate has been sent. This stage triggers the estimate follow-up sequence, which is the most revenue-critical automation in the entire system. The average roofing close rate on estimates without systematic follow-up sits around 25 to 30 percent. Consistent multi-touch follow-up after the estimate can push that toward 35 to 40 percent.
Job Sold. The homeowner has signed. The system sends the onboarding confirmation, schedules the project start date, and begins the insurance documentation coordination sequence if applicable.
Job Complete. Work is finished. The post-service engine activates: review request, referral incentive, and seasonal maintenance reminder sequence.
Configuring the roofing damage assessment quiz
The quiz is the intake mechanism that feeds every downstream automation. For roofing, the quiz needs to capture three categories of information: the nature of the damage or need, the insurance context, and the homeowner's timeline and property details.
The quiz question sequence matters. Start with damage type because it establishes the context for every subsequent question. A homeowner who selects "active leak" should see urgency-appropriate follow-up questions, not the same leisurely pathway as someone selecting "considering replacement." Follow damage type with insurance status, then timeline, then property details, then contact information.
Each answer carries a weighted score. Hail damage with an active insurance claim and an immediate timeline produces the maximum score. Age-related wear with no insurance and a flexible timeline produces the minimum. The scoring threshold creates the temperature tiers that determine which pipeline stage the lead enters and which email sequence they receive.
The quiz code that Origin compiles for roofing uses image cards for damage type selection (homeowners can identify hail damage, wind damage, or leak symptoms more accurately when shown reference images), slider inputs for roof age estimation, and dropdown selects for insurance status. The visual quality of the quiz matters because it is the homeowner's first interaction with the roofing company's brand. A polished, image-rich quiz conveys professionalism. A plain text form conveys nothing.
Writing the four essential email sequences
Each temperature tier requires a dedicated email sequence because the homeowner's situation, urgency, and information needs are fundamentally different across categories.
Sequence 1: Hot lead (insurance storm damage)
Timing: aggressive. Email 1 fires immediately after quiz submission confirming receipt and next steps. Email 2 fires 2 hours later with the company's storm damage credentials, photos of recent completed work, and a direct booking link. Email 3 fires the next morning if no inspection has been booked, emphasizing that insurance companies have filing deadlines and that early inspection documentation strengthens the claim. This sequence is 3 to 5 emails over 5 days. Every email includes the booking link. The tone is urgent but helpful, not pushy.
Sequence 2: Warm lead (damage, no claim)
Timing: educational. Email 1 acknowledges the damage report and explains the basic insurance claims process. Email 2 provides a checklist of what the homeowner needs to file a claim: policy number, photos of damage, date of the weather event, and the insurance company's claims phone number. Email 3 offers a free inspection that produces documentation the homeowner can use to support their claim. This sequence is 5 to 7 emails over 14 days. The goal is to convert the lead from warm to hot by guiding them through claim filing.
Sequence 3: Nurture (routine maintenance)
Timing: patient. One email per week for 6 weeks, then monthly. Content focuses on roof maintenance tips, seasonal preparation guides, the warning signs that indicate replacement is approaching, and periodic free inspection offers. These leads may take months to convert, but they cost nothing to maintain in the nurture sequence and they convert at high rates when the timing aligns.
Sequence 4: Post-service follow-up
Timing: milestone-based. Email 1 fires 24 hours after job completion with a satisfaction check and a direct link to leave a Google review. Email 2 fires at day 7 with a referral incentive: a $50 electronic gift card (Visa or Amazon) for every referred neighbor who books an inspection. Email 3 fires at 90 days with a seasonal maintenance reminder. Email 4 fires at 12 months with an annual inspection offer. This sequence runs indefinitely, keeping the roofing company in the homeowner's awareness for the next time their roof needs attention or a neighbor asks for a recommendation.
Internal notifications and booking configuration
Internal notifications are the bridge between the automation system and the sales team. Every hot lead and every emergency lead must trigger a notification that reaches the right person within 60 seconds. The notification must include actionable data: the lead's name, phone number, address, damage type, insurance status, lead score, and temperature tier. A notification that says "New lead submitted a form" is useless. A notification that says "Emergency: Active leak at 1423 Oak Street, homeowner Sarah Johnson, phone 555-0142, no insurance claim filed, score 92" gives the sales rep everything they need to make an effective callback immediately.
The booking calendar for roofing operates in two modes. During normal periods, inspection slots are 60 minutes with 6 to 8 available per day across the inspection team. During storm season, slots compress to 30 minutes with 12 to 16 available per day. The confirmation email includes specific preparation instructions: have the insurance policy number ready, note the date damage was first observed, ensure access to the attic, and clear any items stored against the house that block the inspector's access to the foundation line.
Every booking confirmation also includes the inspector's name, photo, and direct phone number. In roofing, the homeowner is letting a stranger onto their property and into their attic. Putting a face and name to the appointment reduces no-shows and increases the homeowner's comfort level before the inspector arrives.
Connecting traffic channels on day one
The system is only as valuable as the leads it processes. A fully built roofing sub-account with zero traffic is an expensive empty pipeline. The Launch Kit inside Origin generates pre-written copy for seven traffic channels: Facebook ads targeting storm-affected zip codes, email blasts to the roofing company's existing customer list, QR code mailers for neighborhood canvassing, Google Business profile posts, email signatures for every team member, door hangers for post-inspection neighbor outreach, and Nextdoor posts for hyperlocal community visibility.
The most effective day-one channel for roofing is the existing customer email blast combined with the scored quiz. Past customers already trust the company. Sending them a storm preparedness quiz 30 to 45 days before peak season fills the pipeline with warm leads who convert to hot the moment weather hits. This costs nothing beyond the time it takes to segment the email list and schedule the send.
The second most effective channel is Facebook ads targeting homeowners in zip codes with recent storm activity. The ad drives to the damage assessment quiz. The quiz scores and segments the lead. The automation handles everything after submission. The agency owner's job is to manage the ad spend and monitor the cost per booked inspection. Everything between the click and the booking is handled by the system.
The Origin shortcut: one import instead of 18 hours
Building every component described above from scratch takes 12 to 18 hours of focused GHL configuration time. That is 12 to 18 hours per roofing client. For an agency serving five roofing companies, the manual build approach consumes 60 to 90 hours before any traffic flows.
Origin's roofing niche ecosystem snapshot deploys the complete system as a single import. The custom fields, the temperature-tiered pipeline, the scored quiz with image cards, the four email sequences, the internal notifications with scoring data, the booking calendar with storm-season configuration, and the trigger connections between all components import in under five minutes. Brand customization for the specific roofing client takes another 15 to 30 minutes.
The agency owner signs a roofing client, imports the snapshot, customizes the brand, and launches the first traffic channel the same afternoon. The client sees leads entering their pipeline before the end of the business day. That deployment speed is the difference between an agency that onboards one new roofing client per month and an agency that onboards four.
Explore the full Origin platform to see what ships with every niche ecosystem.