Back to Blog
solar business19 min read

Solar Dealer and Franchise Models: Operating Guide

Understand solar dealer, reseller, franchise, referral, and license models through control, claims, delivery, economics, and customer responsibility.

Rainer Neumann

Written by

Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Answer

A solar dealer model separates customer acquisition or sales from some combination of design, finance, supply, installation, and service. A franchise adds a licensed brand and operating system under a regulated agreement. Choose only after qualified legal and financial review of control, economics, data, claims, territory, customer responsibility, and exit obligations.

“Solar dealer” can describe a local seller with its own installation team, a sales organization handing projects to an EPC, an authorized reseller of a product, or a company that does little more than introduce a lead. “Franchise” can carry a specific legal test and disclosure obligations. A brand name on the proposal does not tell the customer which arrangement they are buying from.

Before choosing a channel model, map the real activities and responsibilities. Who finds the customer? Who makes the claim? Who controls price? Who collects the bill? Who designs, contracts, finances, installs, warrants, services, and answers when something goes wrong?

This guide helps solar founders and channel leaders ask those operating questions. It is general desk research, not legal, tax, financial, licensing, employment, franchise, securities, or investment advice. Relationships must be reviewed under current law and written agreements in every applicable jurisdiction.

Begin with functions, not labels

List every function in the customer and project path. Then assign it to the dealer, network operator, franchisor, franchisee, EPC, finance provider, equipment supplier, subcontractor, or another responsible party.

At minimum, map:

  • Marketing, lead capture, consent, and qualification.
  • Site and electricity evidence collection.
  • Design, engineering, estimating, and proposal preparation.
  • Customer presentation, claims, and price authority.
  • Contract, cancellation, payment, and finance process.
  • Permitting, interconnection, procurement, and installation.
  • Inspection, commissioning, monitoring, warranty, and service.
  • Complaints, data requests, incidents, changes, and termination.

The same company may perform several functions. That is fine. The map matters because control, competence, economics, and liability attach to activity, not the marketing label.

Use a responsibility table:

Function Performer Reviewer or approval Customer identity shown Record owner
Lead generation Named entity Marketing or compliance role Brand and relationship disclosed Defined CRM
Design request Dealer or central team Technical acceptance role Not yet customer release Project record
Proposal Named preparer Commercial and technical reviewers Contracting relationship clear Current version owner
Contract Named legal entity Authorized signers and advisers Contracting entity explicit Contract system
Installation Licensed or qualified provider as required Applicable responsible roles Installer identity explicit Delivery record
Service Named company or provider Warranty and service owner Contact route explicit Service system

If a row says “depends,” write the decision rule. Ambiguity becomes expensive when a customer calls the company whose logo they remember and discovers it does not own the problem.

Understand the model spectrum

Channel structures sit on a spectrum of local independence and central control. Legal classification must come from qualified counsel, but operational patterns can be described.

Referral arrangement

The local party introduces a customer under agreed consent, qualification, disclosure, and compensation rules. It may not quote, contract, or make detailed project claims. This narrower role can reduce operational scope, though lead quality, marketing conduct, data, payment, and customer identity still need governance.

Authorized dealer or sales agent

The local party may conduct discovery, collect information, present approved material, or help the customer enter a contract with another entity. Price authority, representations, finance activity, licensing, data, and supervision must be explicit.

Reseller

A reseller may buy and sell products or services under its own commercial arrangement. It can carry pricing, customer contract, delivery, tax, warranty, inventory, or credit responsibilities depending on the actual model.

Licensed brand or operating system

A company may license marks, methods, software, templates, or other intellectual property. Legal review is needed to determine whether the arrangement triggers franchise or other requirements regardless of the name used.

Franchise

In the United States, the Federal Trade Commission’s Franchise Rule and Franchise Rule Compliance Guide address federal franchise disclosure and the elements relevant to coverage. State laws and other jurisdictions may add or differ. Obtain specialized counsel before offering, selling, buying, or restructuring a franchise.

Do not choose the “dealer” label merely to avoid a regulated classification. Counsel should examine trademark use, control or assistance, required payments, documents, conduct, and the full relationship.

Decide who controls the customer promise

The customer needs to know who is speaking and the basis of the statement. Create a claims matrix for each channel role.

Cover:

  • Company and partner identity.
  • Service and product scope.
  • Equipment facts and warranty sources.
  • Design and production modeling.
  • Price, discounts, access, and availability.
  • Financing, taxes, incentives, and tariffs.
  • Timeline, permit, interconnection, and installation.
  • Savings, performance, customer outcomes, and comparisons.

The U.S. Federal Trade Commission publishes advertising and marketing guidance. Use current applicable regulator sources and qualified advisers for the markets and channels involved. Operationally, a dealer should work from controlled claims with source, jurisdiction, owner, and review date.

Do not give a local seller blank marketing authority and expect a contract disclaimer to repair unsupported promises. Monitor public pages, ads, scripts, webinars, proposals, and finance conversations within the lawful agreement. Preserve the released version.

The Federal Trade Commission’s consumer solar guidance offers U.S. consumer context about providers, offers, written bids, financing, and contracts. It can support training, but it does not replace law, company review, or customer-specific evidence.

Assign lead and territory rights precisely

Territory can mean exclusive marketing, lead distribution, customer contracting, installation service, or use of a brand. Define the geography, customer types, products, channels, exceptions, online leads, national accounts, existing customers, and what exclusivity requires from each party.

Create lead registration rules with minimum identity, contact basis, site, source, submission time, duplicate treatment, acceptance, ownership duration, inactivity, reassignment, and dispute process. A bare company name should not automatically block another legitimate customer relationship.

Avoid turning sales territories into technical authority. A dealer authorized to sell in a region still needs the required local licenses, professionals, utility knowledge, and delivery capability for the work it performs. Verify those through appropriate sources.

Map cross-border and portfolio cases. A customer headquartered in one territory may have sites in several. The party managing the account, the party conducting local work, and the party contracting may differ. Decide before the first multi-site opportunity forces an improvised revenue split.

Use performance conditions cautiously and with counsel. Targets based on submitted leads can encourage low-quality volume. Targets based on customer revenue can ignore contribution, cancellation, or delivery. Define evidence, periods, exceptions, and cure or review processes in the actual agreement.

Build the economic model from activities and cash events

A dealer’s economics can include referral fee, commission, reseller discount, markup, development fee, installation margin, recurring service, or another written arrangement. Build the model from the functions performed and the cash events controlled.

For each revenue line, record:

  • Payer and recipient.
  • Event that earns the amount.
  • Source document and approval.
  • Timing, holdback, cancellation, and chargeback.
  • Tax and accounting treatment from qualified advisers.
  • Costs and capacity needed to perform the related work.

Do not confuse customer contract price with dealer revenue. Do not confuse dealer revenue with profit. Include marketing, sales labor, office, software, training, insurance, licensing, professional review, travel, support, cancellations, financing delays, chargebacks, and customer recovery as applicable.

Model cash timing. A sale can appear profitable while long payment delays and clawbacks create working-capital pressure. Use scenario analysis with source-labeled assumptions. A prospective dealer should obtain independent financial and legal advice rather than relying solely on the network seller’s projections.

The U.S. Small Business Administration provides a high-level resource on choosing a business structure. Entity choice affects taxes, liability, filing, and operations, but the correct structure requires advice specific to the owners and jurisdiction.

Give a Dealer Network a Controlled Project Record

Explore how SurgePV can support roof, layout, shading, energy, financial, electrical-workflow, material, and proposal work within the responsibilities your agreements assign.

Explore Channel Workflows

Define worker and company relationships carefully

Calling a salesperson an independent contractor does not by itself determine legal status. In the United States, the IRS provides an overview of the independent contractor definition for federal tax purposes, and other federal and state tests or obligations may apply. Other countries use different rules.

Obtain employment, tax, franchise, agency, and licensing advice for the actual control, compensation, tools, schedule, exclusivity, supervision, and work. Misclassification can affect the business and the individual.

Operational documents should match the reviewed relationship. Training, approvals, system access, scripts, performance management, and customer representation can all matter. Do not write a contract that declares independence while daily practice assumes employment-like control, or vice versa, without counsel.

Keep access proportional. A salesperson or dealer may need customer and proposal records but not every financial or technical file. Remove access at role change or termination and transfer active customers through a controlled process.

Establish design, engineering, and technical boundaries

A dealer network often centralizes design or relies on an EPC. Define what the dealer may collect, interpret, modify, present, and promise.

Use separate statuses for customer information, verified site evidence, planning assumptions, design work, reviewed output, and external approval. Train dealers to explain preliminary models without converting them into guarantees.

The technical service contract should state:

  1. Inputs and acceptance for each deliverable.
  2. Project classes and jurisdictions supported.
  3. Ordinary turnaround measurement and priority rules without unsupported promises.
  4. Reviewer and release authority.
  5. Revision and equipment-substitution process.
  6. Exception and specialist route.
  7. Ownership and retention of records.

The solar design request process can form the operational handoff. Add channel identity, customer contract status, price authority, and dealer communication responsibility.

SurgePV’s approved product scope includes 3D roof modeling, array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Software can support the record. It cannot make a dealer qualified for professional work or approve a project.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

Make finance relationships visible

If dealers discuss or facilitate loans, leases, PPAs, or other finance products, define authorized statements, licensing or registration needs, application handling, customer disclosures, compensation, data, adverse decisions, cancellations, and complaint routes with qualified counsel and providers.

Do not blend the system price, dealer fee, finance charges, tax claims, projected savings, and customer payment into one sales message. The customer-facing document should identify the responsible entities and current written terms.

Train dealers to route legal, tax, accounting, credit, and investment questions. Approved educational material should be sourced and dated. A customer’s eligibility or economic outcome is not guaranteed because a generic example worked.

Review incentives for conflicts. Compensation linked to a particular product or finance choice may create disclosure and conduct obligations. Qualified reviewers should determine the applicable requirements. Operational leaders should make the relationship visible and audit actual conversations.

Govern installation, warranty, and service handoffs

The sale creates a delivery obligation somewhere. Identify the contracting installer, permit and interconnection applicant, equipment buyer, site-safety roles, customer communication owner, schedule owner, inspection and commissioning roles, warranty providers, monitoring support, and service contacts.

The dealer should not disappear after signature unless the customer has been introduced to the next owner and the agreement supports that transition. Transfer the current proposal, design basis, source evidence, customer decisions, commitments, exclusions, finance status, and open conditions.

Create a responsibility matrix for workmanship warranty, manufacturer warranty support, roof issues, performance questions, system monitoring, service response, and business failure or termination. Do not use “covered by warranty” without naming the provider, terms, exclusions, and claim path from current documents.

Complaint ownership should be immediate. Even when another company must resolve the underlying issue, the customer needs one acknowledged route. Preserve original communication, notify responsible parties, avoid speculative blame, and follow current incident or complaint procedures.

The solar proposal acceptance handoff guide can prevent a sold project from becoming a PDF without operational context.

Compare dealer, branch, and franchise control through decisions

Instead of asking which model is “better,” compare the control each business needs and can support. Keep legal classification separate and counsel-led.

Decision Independent dealer tendency Company branch tendency Franchise tendency
Local entity economics Dealer bears defined local business economics Parent company bears branch economics Franchisee bears economics under franchise terms
Brand and method Agreement may authorize limited use Company controls its own brand and process Licensed brand and system with defined controls
Customer contract Varies by agency, reseller, or EPC arrangement Company entity or branch structure Varies under franchise and delivery structure
Local hiring Dealer manages within actual relationship and law Company manages employees or contractors Franchisee commonly manages its workforce, subject to actual terms and law
Exit Dealer agreement and customer transfer Internal closure or restructuring Franchise termination, transfer, and disclosure rules may apply

This table describes operational tendencies, not legal conclusions. The written agreements, actual practice, laws, and professional advice control.

Choose from the customer backward. How much local entrepreneurship is desired? Which functions need central consistency? Which risks and records must the brand owner control? Can each local operator fund, staff, and govern its duties? What happens to customers if the relationship ends?

Conduct diligence in both directions

A prospective dealer or franchisee should investigate the network, agreements, economics, litigation or complaints where lawfully available, support, territory, training, suppliers, finance relationships, customer obligations, termination, restrictions, and former or current operator experience through appropriate sources and advisers.

The network operator should investigate the prospective partner’s identity, ownership, finances, experience, licenses, insurance, reputation, customer conduct, data and security capability, staffing, market knowledge, conflicts, and capacity under lawful procedures.

Do not replace primary evidence with testimonials selected by the selling party. Speak to multiple relevant operators where permitted, verify claims, and preserve the date and context. A business model that worked in another territory or market period may not transfer.

For a U.S. franchise, use the required disclosure process and timing under current law with franchise counsel. Do not rely on this article or a sales deck to interpret the Franchise Disclosure Document.

Pilot the operating model before expanding territory

Where the lawful structure permits, test a narrow set of activities, project types, and customers before scale. A franchise sale itself may have prescribed documents and obligations, so counsel must approve the sequence.

Operational testing should include lead acceptance, claims, data transfer, design request, proposal review, customer presentation, revision, contract handoff, delivery, complaint, and termination or continuity scenario. Use representative cases and protect real customers.

Track handoff returns, unsupported claims, data corrections, support requests, stage age, cancellations, customer questions, and delivery exceptions. Do not publish performance conclusions from a small uncontrolled sample.

Set expansion gates for competence, customer experience, cash, capacity, compliance, and record quality. More territory can multiply the unresolved operating defect. A partner who sells well but bypasses claim or handoff rules is not ready for more authority.

Plan exit and customer continuity at the beginning

Dealer and franchise relationships end. Define notice, access removal, use of marks, lead and customer records, active proposals, contracts, payments, chargebacks, inventory, equipment, warranties, service, customer communication, data return or deletion, post-termination restrictions, and dispute routes in the agreement with counsel.

The customer should not be stranded between entities. Assign active projects and service responsibilities. State who may contact customers and how the relationship change will be explained. Preserve records required for delivery, warranty, law, and disputes under approved retention policies.

Test the continuity plan before launch. Ask what happens if a local operator stops responding during an active installation, if a finance provider changes, or if the central company discontinues a program. The answer may require insurance, reserve, step-in rights, supplier arrangements, or another treatment determined by advisers.

What should a solar dealer operating-model record contain?

A solar dealer operating-model record should contain the parties, customer promise, lead and territory rights, data custody, qualification, design and technical boundaries, pricing and contract authority, finance relationships, installation and service ownership, payment events, insurance and compliance review, incident routes, customer continuity, exit duties, and review triggers. Every field needs an authorized owner. The record describes activities before choosing labels.

The record maps actual activities before anyone chooses a label. Calling a relationship a dealer, franchise, branch, representative, or partner does not by itself establish the legal, tax, employment, licensing, finance, warranty, or regulatory consequences. Qualified advisers must review the proposed facts and jurisdiction.

Operating field Decision to document Specialist review to route as applicable
Customer promise Which party says what and bears correction duties Contract, advertising, consumer, and commercial review
Lead and territory Registration, ownership, overlap, expiry, and reassignment Contract and competition considerations
Data custody Collection, access, correction, retention, and deletion Privacy, security, and system governance
Technical work Intake, design, engineering, release, and outside approval boundaries Licensing, engineering, code, utility, and authority review
Commercial authority Pricing, discounts, scope, finance discussion, and contract signature Finance, lending, contract, tax, and regulatory review
Delivery Procurement, installation, scheduling, change, and acceptance Licensing, safety, insurance, and subcontract review
Service Warranty intake, diagnosis, remedy, and customer updates Manufacturer, installer, contract, and consumer obligations
Payment events Activity, evidence, timing, reversal, and dispute route Accounting, tax, employment, finance, and contract review
Exit Active projects, records, customers, warranties, and communications Contract, privacy, service, and continuity review

Do not treat the rightmost column as a universal legal checklist. The necessary reviewers depend on the market, facts, parties, and model. The purpose is to expose decisions that a commercial label can hide so the founders can obtain advice on the actual arrangement.

How should a dealer model be piloted before expansion?

Pilot a solar dealer model with a limited territory, defined customer promise, representative lead and project scenarios, controlled data access, tested technical and commercial handoffs, incident routing, and customer-continuity exercise. Expansion should stop when private rescue, unclear authority, unsupported claims, or missing records prevent either party from completing the published operating model. The pilot must expose missing operating ownership clearly.

The pilot should test work through the customer lifecycle rather than count signed dealer agreements. Start with lead registration and qualification, then follow the current project through design request, customer proposal, contract route, delivery handoff, service question, and closure as applicable to the proposed model.

  1. Register a lead and resolve an overlap scenario.
  2. Qualify the opportunity using the required evidence.
  3. Transfer project and customer data through approved access.
  4. Prepare customer language within the published claims boundary.
  5. Route a technical exception and a commercial exception separately.
  6. Test installation or delivery handoff for the model’s actual scope.
  7. Open a service case and simulate dealer unavailability.
  8. Reconcile payment-event evidence without inferring legal classification.

Use this copy-ready pilot record:

Parties and pilot scope:
Territory and customer promise:
Lead registration result:
Qualification handoff result:
Data access and custody check:
Technical decision and reviewer:
Commercial decision and authorized owner:
Delivery or installation handoff:
Service and incident route:
Payment-event evidence:
Private rescue required:
Customer-continuity result:
Expansion status and limitations:

The pilot record does not replace executed agreements or professional advice. It tests whether the intended operational responsibilities can be performed and evidenced. A legal structure can be documented on paper while the real workflow contradicts it; advisers need the actual activity map, not only the chosen name.

How should customer continuity work if a dealer exits?

Customer continuity after a solar dealer exits should identify active opportunities and projects, current agreements, data custody, design and proposal versions, installed-system records, service and warranty routes, payment disputes, communication authority, and receiving owners. The transition plan must follow applicable contracts, law, privacy duties, and qualified advice rather than improvised reassignment. Customer records remain controlled throughout the entire planned transition.

Illustrative example, not a dealer dispute: A dealer stops responding while several opportunities remain active and one installed customer has an open service question. The operating record shows which party holds the customer data, who signed each agreement, which design revision is current, and which role owns service intake.

The immediate task is customer and project continuity under the actual agreements and applicable obligations. The parties should not send conflicting promises or move data simply because one system administrator has access. Authorized legal, privacy, contract, service, and management owners determine the communication and transfer steps.

After the live cases are controlled, the program owner reviews the model. Missing continuity fields, unclear service ownership, or inaccessible project records become operating changes for future dealers. A specific dispute does not let the company rewrite rights after the fact, but it can expose a gap that future agreements and systems need to address.

Use a continuity register with one row per affected customer or opportunity. Include current stage, agreement party, last customer commitment, project source of truth, open condition, receiving owner, permitted communication, and next review. Preserve disputed items rather than assigning certainty for convenience.

The plan should be tested during the pilot with a simulated absence. If every answer depends on the dealer’s private inbox or personal drive, the model is not ready to scale. Customer continuity is part of the product being sold through the channel, even when the brand story focuses on territory growth.

Compare models by control, not by headline growth

Use the same activity map to compare a dealer arrangement with a branch, referral relationship, franchise concept, or another legitimate structure under consideration. Do not assume one option is inherently more scalable. Compare where each model places authority, evidence, cost, risk, and customer continuity, then obtain qualified advice on the actual facts.

Comparison dimension Question for each model Evidence to retain
Customer control Who owns the relationship and may make commitments? Proposed workflow and agreement position
Brand control Who approves language, experience, and corrective action? Claims library, review route, and incident record
Technical control Who requests, performs, reviews, and releases work? Decision-rights map and qualification evidence
Economic activity Who performs each activity and bears each cost or reversal? Activity map and proposed payment events
Local variation Which decisions depend on market, workforce, supplier, or jurisdiction facts? Local evidence and escalation boundary
Customer continuity What happens during absence, dispute, failure, or exit? Tested transition and receiving owners

The solar partner enablement checklist provides the operating fields for a broader relationship. Use it to test whether the proposed dealer model has a working qualification, claims, data, support, and incident system before adding specialized legal or economic terms.

Write the comparison memo with explicit unknowns. If worker classification, licensing, franchise regulation, lending activity, tax treatment, insurance, competition, consumer obligations, or another issue requires specialist review, state the question and adviser rather than selecting the answer internally. The operating team supplies accurate facts; qualified professionals interpret them.

Record why the chosen model fits the current decision and what would reopen it. New states, services, finance relationships, installation duties, customer promises, or payment mechanics can change the facts that advisers reviewed. Expansion is a fresh operating and professional-review event, not an automatic copy of the first territory.

A decision checklist for founders and channel leaders

Before adopting a dealer or franchise model, confirm that responsible reviewers have addressed:

  • Legal classification and disclosure in every relevant jurisdiction.
  • Entity, ownership, worker, licensing, tax, and insurance structure.
  • Brand, territory, product, and channel rights.
  • Customer identity, claims, contract, cancellation, and complaints.
  • Lead, data, privacy, security, and system ownership.
  • Design, professional review, external approval, and delivery duties.
  • Finance, compensation, cash timing, chargebacks, and contribution.
  • Training, competence, support, audit, and change control.
  • Warranty, service, failure, transfer, and exit continuity.
  • Pilot scope, capacity, stop conditions, and expansion gates.

If the relationship depends on a verbal understanding, do not scale it. If the economics depend on unverified customer or partner outcomes, do not present them as fact. If the customer cannot tell which company is responsible, repair the model before adding marketing volume.

A solar dealer model can distribute local selling and market knowledge. A franchise can distribute a licensed brand and operating system. Both can also distribute ambiguity. The work is to decide which rights travel, which responsibilities remain, how evidence moves, and who answers when the plan meets a real roof and a real customer. A shared solar designing workflow can support only the responsibilities assigned by agreement.

Discuss the Project Record Behind a Solar Channel Model

Book a guided SurgePV demo and bring the dealer, central-team, design, proposal, and handoff boundaries your operating model must support.

Book a Guided Demo

Frequently Asked Questions

What is a solar dealer model?

A solar dealer model is a channel arrangement in which a local company commonly originates or sells customer projects while another party may provide design, equipment, finance, installation, or service. The exact rights and duties come from current agreements and applicable law. The label alone does not identify the contracting or responsible party.

Is a solar dealer the same as a solar franchise?

Not necessarily. A franchise may involve a licensed trademark, significant control or assistance, and required payment under the legal test that applies. A dealer or reseller arrangement can have different control and branding. Have qualified counsel classify the real relationship; changing the label does not change the underlying facts.

Who signs the customer contract in a solar dealer model?

The agreement should identify the contracting entity, but structures vary. A dealer may contract directly, act as an authorized sales channel for another provider, or only refer the customer. Customer materials must match the actual arrangement, including payment, cancellation, installation, warranty, service, data, and complaint responsibilities.

How does a solar dealer make money?

Possible structures include referral fees, commissions, dealer discounts, resale margin, development fees, or other agreed compensation. Economics depend on scope, price authority, cancellations, finance, chargebacks, delivery cost, tax, and legal treatment. Use a written agreement and finance-approved model; do not infer profit from gross customer price.

What should be checked before joining a solar dealer network?

Review legal classification, disclosure, territory, brand rights, products, claims, training, customer contracts, pricing authority, lead rules, data, technical and delivery responsibility, finance relationships, compensation, chargebacks, warranty, complaints, insurance, audit, termination, noncompete or restriction terms, and record transfer with qualified advisers in each relevant jurisdiction.

Sources

Primary research and reference material used for this desk-research article.

Where this fits

This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.

About the Contributors

Author
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Editor
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.