By Ahsan Zafeer

Business owners in home services often ask the wrong question. They ask:
“Should our process be different for solar vs roofing vs pest?”

It’s a trap. If you answer “Yes,” you build three separate, disconnected companies that are impossible to manage. If you answer “No,” you try to force a solar workflow onto a pest control job, and you break the business.

The better, more profitable question is:
What parts must never change—so we can scale—and what parts must adapt—so we can win per industry?

If you customize everything, you get chaos. You have different CRMs, different login portals, different reporting standards, and no one knows what “success” looks like.
If you standardize everything, you become rigid. You lose deals because your process moves too slow for roofing or too fast for solar financing.

To scale a multi-trade home services empire (or even just add a second vertical), you need a framework. We call it The Rule of 70/30.

For home services with a Door-to-Door (D2D) or field sales motion:

• 70% Standardized: This is your Company Operating System. The non-negotiables.
• 30% Customized: This is your Industry-Specific Execution. The tactical nuance.

If you flip this ratio—if you try to customize 70% of your business—you get training bloat, inconsistent data, broken handoffs, and installs that depend entirely on “who sold it” rather than “how we do it.”

Here is the blueprint for building one operating system to rule them all.

Part 1: What You Standardize (The 70% – The Backbone)

These are the elements that should look exactly the same whether you are selling a $50 pest subscription or a $50,000 solar array.

1) Pipeline Stages & Definitions

Your CRM should be the single source of truth. To do that, the language of business must be universal.

Standardize these stages:

• Lead Created: Data entered.
• Contacted: Two-way communication established.
• Qualified: Needs, budget, and authority verified.
• Presented: Solution shown.
• Closed/Won: Contract signed.
• Handoff Complete: The operational trigger (see Blog 1).
• Scheduled: Date on calendar.
• In Progress: Crews on site.
• Completed: Work done.
• Finalized: Money in the bank.

Why: You need to be able to look at a dashboard and see the health of the entire company. If Solar calls it “NTP Issued” and Roofing calls it “Material Drop,” you can’t compare velocity. Your CRM should support custom workflows underneath, but the high-level reporting stages must remain the unified operating model from “lead to sale to install.”

2) The Handoff Checklist Philosophy

While the specific questions change (we’ll get to that), the categories of the handoff are universal.

Standardize these buckets:

• Contract + Financials
• Scope of Work
• Property Validation
• Measurements/Conditions
• Expectations
• Risk Flags

Why: A roofing manager should be able to step into a solar meeting and understand if a job is “clean” or “dirty” based on these categories. The backbone of ops execution doesn’t change just because the product changes.

3) Data Capture Standards

If Ops is guessing, you are losing money. You must standardize how data is captured.

Standardize:

• Required Fields: No skipping email addresses or gate codes.
• Photo Standards: Always clear, always labeled, always uploaded to the specific Job ID.
• Notes Format: Do not allow reps to write novels. Use standard tags like [URGENT], [ACCESS], [FINANCE].

Why: Tools that emphasize lead management, smart scheduling, and territory/route workflows are designed to reduce missed steps. If you allow different data standards for different departments, your automation tools break. You can’t set up an automated “Pre-Install Text” if the Pest team collects cell numbers in the “Notes” field but the Solar team collects them in the “Mobile” field.

4) Management Cadence

How you run the business is the business. The rhythm of meetings and accountability must be identical.

Standardize:

• Daily Huddles: 15 minutes, standing up. Field execution focus.
• Weekly Pipeline Reviews: Moving deals from left to right.
• Scorecards: Tracking activities, conversion rates, and cancel rates.

Why: D2D organizations win because they run a measurable cadence, not because they “hope.” If your Solar team meets daily but your Pest team meets monthly, your culture is fractured.

5) Training Skeleton

The content differs, but the structure of how you build a rep should be identical.

Standardize:

• Onboarding Sequence: Day 1-3 agenda.
• Role-Play Cadence: Everyone practices before they pitch.
• Ride-Along Structure: How a rookie shadows a pro.
• Certification Gates: You don’t knock solo until you pass the test.

Why: D2D Experts explicitly positions training and playbooks as something you implement, not just “motivational content.” You want a “Plug and Play” talent engine.

---

Part 2: What You Customize (The 30% – The Reality)

Now, we look at where you must deviate. This is where reality hits. You cannot treat a roof install like a pest spray.

1) Solar: The Finance, Compliance & Multi-Step Beast

Solar is a logistics company disguised as a sales company. It has the longest cycle time and the highest regulatory friction.

Customize for:

• Finance & Stipulations: Solar requires credit checks, loan documents, stipulations (stips), and often milestone payments. Your workflow must have gates for “Credit Approved” and “NTP Issued.”
• Interconnection & Permitting: Unlike pest control, you need government permission to turn the product on. You need specific workflow stages for “Permit Submitted,” “Permit Approved,” and “PTO” (Permission to Operate).
• Engineering: You need a step for CAD design and structural review.

The Handoff Specifics:
The solar handoff must focus heavily on the Main Electrical Panel (MPU). Does it need an upgrade? Where is the meter? It must also focus on Utility Bill data. Without the account number and usage history, the engineer cannot size the system.

2) Roofing: The Insurance, Production & Speed Beast

Roofing is high-stakes physical labor. It lives and dies by material accuracy and insurance supplements.

Customize for:

• Inspection Proof: The sale often depends on proving damage to an insurance adjuster. The workflow needs heavy photo-ingestion capabilities for storm damage.
• Supplements: The initial price is rarely the final price in insurance work. You need a workflow for “Supplement Submitted” and “Supplement Approved.”
• Production Speed: Roofing installs happen in 1-2 days. The logistics are about dumpsters, material drops, and crew size.

The Handoff Specifics:
The roofing handoff is about Measurements and Access. Can a boom truck reach the roof? Is the driveway paver or concrete (will the dumpster crack it)? Are there satellite dishes that need to be recalibrated? The “Contingency” conversation is vital here: “If we rip off the shingles and find rotten decking, here is the price per sheet to replace it.”

3) Pest: The Retention & Routing Beast

Pest control is a recurring revenue game. The initial sale is just an acquisition cost; the profit comes from the next 5 years of service.

Customize for:

• Routing Efficiency: In Solar, you might drive across town for one job. In Pest, “Windshield time” kills margin. Your system must optimize routes based on territory density.
• Subscription Management: The workflow isn’t “Job Complete.” It’s “Subscription Active.” You need automation for credit card failures and renewal reminders.
• The “Start” vs. “Finish”: The install is just the beginning.

The Handoff Specifics:
The pest handoff is about Lifestyle and Safety. Do they have koi ponds (sensitive to chemicals)? Do they have aggressive dogs? What are the gate codes? The expectations script here is crucial: “You might see more bugs in the first 2 days as we flush them out.” This prevents the immediate cancel.

The Decision Filter

How do you decide if a new process should be part of the 70% (Standard) or the 30% (Custom)?

Use this simple filter:

Standardize it if:

1. It affects internal execution (handoffs, data integrity, accountability).
2. It creates a metric that every employee should be judged on.
3. It prevents chaos regardless of the product sold.

Customize it if:

1. A regulator, bank, or city permit office requires it.
2. The physical fulfillment is fundamentally different (e.g., a 2-hour spray vs. a 3-day construction project).
3. The customer’s buying psychology differs materially (e.g., “Save money on bills” vs. “Get rats out of my attic”).

The Owner Play: One Operating System

If you are running Solar + Roofing + Pest under one roof, do not build three separate businesses.

Build:

• One Scoreboard
• One CRM Workflow Backbone
• One Handoff Standard
• One Management Cadence

Then, plug in the industry modules.

That is how you scale without the company depending on you to translate between departments. You build a common language, a common standard, and a common goal. The methods change, but the mission remains the same: profitable, clean, reference-able installs.