Salesforce Energy United States

Sunnova

Sales Automation

Sunnova needed to connect dealer, homeowner, utility, jurisdiction, and finance workflows so it could design, sell, and support solar systems quickly without breaking privacy rules or depending on brittle point integrations.

100 million homeowners
4 million are utilizing solar energy
96 million homeowners
Generate energy designs and contracts in less than 15 minutes

Reported impact

Business outcome

Sunnova accelerated proposal and contract generation, made field-service response more proactive, and built an automation layer that lets it scale renewable-energy operations across dealers and external partners.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Sunnova uses MuleSoft, MuleSoft RPA, and Service Cloud to connect the distributed data flows behind residential solar sales, system design, support, financing, and local-jurisdiction coordination. Sales reps can combine homeowner information, utility data, and other external records into one view to generate personalized 3D proposals, model long-term energy output, and move from lead creation to signed contract in minutes instead of waiting on manual back-office prep. Once a system is active, the same integration layer connects data from grid-service and solar-meter providers so Sunnova can monitor hardware performance and automatically create work orders in Service Cloud, where predictive AI helps determine the right maintenance response. MuleSoft RPA extends the architecture to slower or less modern partners by publishing payment documents, supporting renewable-credit workflows, and handling jurisdictions that still depend on outdated technology.

Data flow

Homeowner and utility data is combined through MuleSoft to produce proposals and contracts, meter and grid data later feeds the same platform for hardware monitoring and work-order creation in Service Cloud, and MuleSoft RPA handles document exchange with portals and jurisdictions that lack modern integrations.

Solution architecture

3 components · 3 layers
  1. Ingest
    • MuleSoft Connects homeowner, dealer, utility, and operational systems for proposal, service, and partner workflows.
  2. Serving
    • Service Cloud Receives automatically created work orders and service activity tied to connected solar hardware.
  3. Orchestration
    • MuleSoft RPA Automates interactions with portals and partners that do not expose modern APIs.

Architecture clues

  • MuleSoft is the privacy-conscious data-sharing backbone across Sunnova's ecosystem.
  • RPA is used specifically to integrate with older jurisdiction and partner technology.
  • Service Cloud work orders can be created automatically from performance data coming from third-party systems.

Evidence from the source

Now, Sunnova can integrate with any partner technology - regardless of how modern it is - thanks to MuleSoft RPA.
Now, Sunnova streamlines the time from initial lead creation to contract signature, and can generate energy designs and contracts in less than 15 minutes.
Sunnova's finance team uses MuleSoft RPA to automatically publish payment documents to portals.
Using MuleSoft, Sunnova built intelligent automations to personalize energy systems.
Transparency Evidence & methodology 86/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value86/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Salesforce

    Sunnova customer story

    First-party
    https://www.salesforce.com/customer-stories/sunnova-connected-data-automation/
    Source type
    Vendor-published customer story
    Published
    Oct 21, 2023
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Oct 21, 2023 · Salesforce · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.