Salesforce for energy companies: solar, storage and energy services

Energy companies use Salesforce to connect a long, site-driven sale to the work that follows it. Solar and storage developers, installers, energy services firms and commercial suppliers want one record per customer. It should run from first inquiry through survey, proposal, contract, permits, interconnection, installation and service. Sales Cloud and Service Cloud cover most of this. Field Service adds crews and maintenance. Salesforce's energy and utilities industry product mainly suits companies that manage meters, service points and utility-style customer accounts.

What makes the energy sale different from a typical B2B pipeline?

The deal depends on a physical site, and the site keeps changing the numbers. Roof condition, load data, utility tariffs and available incentives all shape the proposal before a customer can say yes.

That creates a few patterns most generic CRM setups handle poorly.

• Site assessments come before pricing. A proposal built without survey data often has to be redone, so the assessment is a real pipeline gate.
• Proposals get revised several times. System size, equipment choice and financing options shift as the customer reviews them.
• Incentives carry their own deadlines and paperwork. Rebates, tax credits and utility programs can each need applications, approvals and proof of completion.
• Signing the contract is the midpoint, not the finish. Permits, utility approval and installation still stand between the sale and recognized revenue.
• Commercial and residential buyers behave differently. A homeowner decides in one household; a commercial buyer may involve facilities, finance and a board.

If Salesforce only tracks the opportunity, the operations team rebuilds the story in spreadsheets after signature. Most of the value comes from closing that gap.

How should solar and storage companies structure the pipeline?

Build stages around the evidence each step produces, not around sales activity. A stage should change when a survey is complete or a proposal is accepted, not when a rep feels optimistic.

A practical pattern for a developer or installer looks like this.

• Lead and qualification: capture the site address, utility, rough usage and decision maker early, so routing and territory rules can work.
• Site assessment: schedule the survey, attach photos and measurements, and record whether the site is viable.
• Design and proposal: link the proposal version, system size and financing option to the opportunity so revisions stay traceable.
• Contract signed: lock the commercial terms and trigger the handoff to project operations.
• Closed and handed off: the opportunity closes, and a project record takes over the post-sale milestones.

Keep incentive tracking separate from the opportunity. A related record per incentive, with program name, status, submission date and amount expected, lets finance see what is pending without reading sales notes.

How do we track permits and interconnection milestones?

Most teams use a custom project object with related milestone records, because no standard object matches every jurisdiction and utility. The design should stay generic enough to survive a new market.

Each milestone record typically holds a type, an owner, a target date, an actual date, a status and a link to supporting documents. Types might include permit submitted, permit approved, utility application filed, inspection passed and permission to operate. Avoid one field per milestone on the project record. That design breaks the first time a utility adds a step.

Flows can create the standard milestone set when a contract is signed. Operations can then add or skip steps per project. Reports on overdue milestones become the daily worklist for the permitting team, and sales can see status without chasing anyone.

How does the handoff from sales to installation work?

Signature should automatically create the project record and carry over everything the field team needs. Nobody should retype the site address, system design or customer contacts.

Agree on the handoff fields with operations before building anything. A common list covers site details, final design, equipment list, access notes, financing status, and the salesperson's commitments to the customer. Missing commitments cause most post-sale friction, so give them a dedicated field rather than burying them in notes.

If installation crews are employees or tightly scheduled subcontractors, Salesforce Field Service can take over from the project. It handles work orders, scheduling, mobile checklists, parts and completion photos. If a partner installer runs its own tools, a lighter status integration is usually enough.

Where do Service Cloud and Field Service fit after installation?

Once a system is live, the relationship becomes a service relationship that can last for decades. Service Cloud handles cases and warranty claims; Field Service handles truck rolls and preventive maintenance.

• Create an asset record for each installed system, with components, serial numbers, install date and warranty terms.
• Route inbound issues from phone, email, web forms or a customer portal into cases tied to that asset.
• Use entitlements where service contracts promise response times, and report on missed commitments.
• Schedule recurring maintenance visits from the asset or contract, not from a technician's memory.
• Feed monitoring alerts into cases when an integration is justified, so a production drop opens a ticket automatically.

Energy services firms and commercial suppliers use the same structure for audits, retrofits and account management. The asset might be a building, a meter or a supply agreement rather than a solar array.

How should energy companies handle marketing and customer communications?

Connect marketing to the CRM so lead source, engagement and conversion sit on the same records sales uses. Separate email tools cause duplicate contacts and make it hard to see which campaigns produce projects.

The choice between Salesforce's two marketing products depends on the audience. Account Engagement, formerly Pardot, suits B2B nurture with lead scoring and sales alignment. Marketing Cloud Engagement suits higher-volume consumer journeys, such as homeowner updates. Confirm current packaging and editions with your Salesforce account team.

Post-sale communication deserves the same care. Customers waiting on permits or utility approval want proactive status updates. Automated emails triggered by milestone changes cut inbound calls and set expectations honestly.

What systems do energy companies usually integrate with Salesforce?

Integrate the systems that own money, designs and operational data, and let Salesforce own the customer and the pipeline. Decide which system is the source of truth for each field before choosing tools.

• Billing or ERP: invoices, payments and contract values, so account teams see financial status.
• Solar design and proposal tools: system size, production estimates and proposal documents, pushed back to the opportunity.
• Financing providers: application status, which often gates the contract stage.
• E-signature: signed contracts that trigger the project handoff.
• Monitoring platforms: production and fault data that can open service cases.
• Utility or market data sources: usage history and tariff details for commercial proposals.

Start with the one or two integrations that remove the most rekeying. Batch updates are often fine for billing data; financing status and signatures usually need to move faster.

When does Salesforce's energy and utilities industry product fit?

It fits companies that run utility-style operations: service points, meters, rate plans, program enrollment and large volumes of residential accounts. Most developers, installers and energy services firms are better served by Sales Cloud, Service Cloud and Field Service.

Salesforce offers an industry product for energy and utilities with a data model built around premises, meters and utility accounts. It is aimed mainly at utilities, retail energy providers and similar organizations. Feature scope, licensing and prerequisites change, so confirm what it includes with your Salesforce account team before planning around it.

A useful test is to describe your customer in one sentence. If it is "a site owner buying a project," core clouds with a few custom objects usually fit. If it is "an account holder billed per meter under a rate plan," the industry product deserves a serious look. Some companies straddle both, so get a fit assessment before committing.

What mistakes do energy companies make with Salesforce?

Most problems trace back to treating the sale and the project as separate worlds. A second group comes from over-customizing early.

• Closing the opportunity and losing track of the customer until installation day.
• Hard-coding one utility's interconnection steps into fields that cannot handle a second utility.
• Storing incentive status in notes, so nobody can report on pending rebates.
• Buying an industry product because of the label, without checking whether its data model matches the business.
• Running marketing in a separate email tool, which creates duplicate contacts and hides campaign results.
• Skipping asset records at installation, which makes later warranty and maintenance work guesswork.

What should phase one include for an energy company?

Phase one should cover the path from inquiry to signed contract, plus the handoff record operations needs. Everything else can build on that foundation.

• Lead capture and routing with site and utility details.
• Opportunity stages gated on site assessment and proposal acceptance.
• A proposal version history and a basic incentive tracking object.
• An automatically created project record at signature with agreed handoff fields.
• Generic milestone records for permits and interconnection, with overdue reporting.
• Clean migration of existing contacts and open deals, with duplicates resolved first.

Later phases often add Field Service for crews, Service Cloud for warranty and maintenance, marketing automation, a customer portal and design or billing integrations. Sequence them by where the most manual work sits today.