OpusDocs for Solar

Built for solar. Paperwork, automated.

OpusDocs was designed first for residential solar. Generate state, utility, and local document packages from Salesforce across all 50 states, with templates your team can easily manage. Help legal stay aware when authorities publish new form versions.

Designed first for residential solar
Published PDFs filled from Salesforce
Visual PDF editing and Word template authoring
Form-version awareness for legal teams
  • CPUC Agreement
  • State Disclosures
  • Utility interconnection
  • NEM Agreement
  • Permit Applications
Hand-drawn solar home and sun beside a stack of documents to sign

From Salesforce to signature

Every document. One connected workflow.

  1. Consumer protection guide
  2. Customer agreement
  3. Utility interconnection
  4. Local permits
  5. Incentives and rebates
  6. Ready for signature

OpusDocs AI for solar

Stay aware when authorities publish new versions

Keeping up with every regulator, utility, city, and county is a constant burden for solar legal teams. OpusDocs AI monitors the sources configured for your markets, prepares an initial template, and automatically alerts your business when a new or changed document is published.

Monitor regulators and localities

OpusDocs AI watches configured regulator, utility, city, and county sources for new forms and revised versions, reducing the manual checking that falls on legal teams.

Prepare the initial template

When a new or changed document is detected, OpusDocs AI prepares an initial template for your team to review, giving operations a starting point for the update.

Automatically alert the business

Your business is automatically alerted to the new or changed document, so legal and operations know there is an update to review and a template to validate.

AI prepares. Your team approves. Legal and operations review the document, validate the initial template, and approve it before use in customer packages.

Solar paperwork is conditional, regulated, and always changing

A battery, a different account holder, or a new permit jurisdiction can change the package. Use Salesforce data to select the documents that apply.

  • State, utility, and authority having jurisdiction
  • System size and utility program rules
  • Solar only, or solar with battery storage
  • Homeowner and utility account holder are different people
  • Language and sales channel requirements
  • Incentive and rebate eligibility

Fixed forms, real data

Work directly with published utility and government PDFs. Map account numbers, meter numbers, system ratings, and production estimates to Salesforce fields, then assign signature, initial, and date tags to the appropriate signer roles.

From PG&E and SCE agreements to ComEd storage forms and local permit authorizations, the layout stays intact while your team controls the data and signing rules.

See OpusDocs in action

From smarter templates to documents at scale.

See how AI helps your team build templates, automate generation, and keep your workflows moving.

Explore what OpusDocs can do for your business
21,500+
documents per day
In one production deployment
1.1 sec
production average generation time
Across the full daily document mix
3.1M+
documents since Nov 2024
Generated since the customer launch

Measured customer performance

Conga vs. OpusDocs: measured solar document performance

Compare measured times for a lightweight document and a complex Customer Agreement from one customer.

faster generation

High-complexity Customer Agreement · 257-page source template

Median elapsed time · one customer

Conga legacy workflow
OpusDocs generation
Median elapsed time · two measured customer workloads
Document complexityCongaLegacy workflowOpusDocsDocument generation
Low complexityLightweight document · 8-page source template
High complexityCustomer Agreement · 257-page source template

Separate samples from one customer. Conga measures the wait from starting the workflow to a completed file. OpusDocs measures generating and storing the PDF after the data is supplied. These results show individual document speed, not simultaneous processing capacity.

The paperwork behind every install

In California, Texas, and Illinois, each state, utility, and permit office adds its own forms, signers, and revisions. Choose a category to explore the document workflows you can configure in OpusDocs.

Consumer protection / 4 document examples

  • CPUC Solar Consumer Protection Guide

  • CSLB Solar Energy System Disclosure and Supporting Information

  • Illinois Shines purchase, lease, and PPA disclosures

  • Language-specific versions for the sale

From Salesforce record to signature-ready package

Four steps, all driven by the data your team already keeps in Salesforce.

  1. Trigger

    Start from the Salesforce record

    A Salesforce action, automation, or API request starts generation using the customer, site, utility account, and system design already on the record.

  2. Select

    Assemble the package

    Rules choose the consumer protection, utility, incentive, and permit forms that apply to this deal and put them in signing order.

  3. Generate

    Fill every form

    Each form is filled from CRM data, including calculated values, and tagged for every required signature, initial, and date.

  4. Sign and store

    Collect signatures and file

    Packages route to each signer. Signed files land in your storage, and Salesforce keeps the status of every document.

Moving beyond a hard-to-maintain template library?

If you use Conga Composer or another document tool, bring a form your team regularly updates. See how OpusDocs handles field mapping, conditional content, signatures, and previews with Salesforce data. Compare the work it takes to maintain the package as well as generate it.

Frequently asked questions

How does OpusDocs make solar templates easier to manage?

Your team can map fields and signer tags visually on published PDFs, maintain customer agreements in Word with AI-assisted field discovery and conditions, and preview output with Salesforce data. Template versions go through review so routine updates have a clear path from editing to approval.

Does OpusDocs support solar teams operating in all 50 states?

Yes. Configure the state, utility, and local forms your team uses, then generate them from Salesforce through one workflow. Your approved template library and package rules define coverage for each market, including California, Texas, and Illinois.

What solar documents can OpusDocs generate?

Utility interconnection and net billing agreements, state consumer protection guides and disclosures, incentive and rebate forms, customer authorizations, city and county permit applications, and your own customer agreements, cover sheets, and change orders. Your team configures the templates and rules for each state, utility, and jurisdiction.

Can OpusDocs fill utility PDF forms without recreating them?

Yes. The published PDF layout is preserved. In the OpusDocs PDF editor, your team places merge fields bound to Salesforce and signature, initial, and date tags directly on the original PDF.

How does OpusDocs decide which forms a deal needs?

Conditional rules evaluate the fields you already track in Salesforce, such as state, utility, authority having jurisdiction, system size, battery storage, language, and whether the homeowner is also the utility account holder. Each deal receives the forms that apply to it.

How can OpusDocs help legal stay aware of new form versions?

OpusDocs AI monitors the regulator, utility, city, and county sources configured for your markets. When a new or changed document is published, it prepares an initial template and automatically alerts your business. Legal and operations review the document, validate the template and package rules, and approve it before use.

Can OpusDocs handle state consumer protection requirements, such as the CPUC rules in California?

OpusDocs can populate approved consumer protection templates, select configured language versions, and prepare initial and signature tags. Configure disclosures to precede contracts where required. Your team controls the approved forms and gives customers the required opportunity to read and review them.

Which e-signature providers are supported?

OpusDocs places signature tags for DocuSign and lets your team preview the real envelope against a Salesforce record before it is sent. Ask us about any other provider your process uses.

How much volume can OpusDocs handle?

Generation runs outside Salesforce on infrastructure built for concurrent requests. In one production deployment, OpusDocs generates more than 21,500 documents per day with an average generation time of 1.1 seconds. Performance depends on document complexity and workload, so we test with your own packages.

Where are signed documents stored?

Generated and signed documents can be stored in your own Amazon S3 environment or another supported cloud provider. Salesforce keeps the document status, links, and e-signature activity for each deal.

Bring us your hardest utility package

Bring the forms that slow your team down. See how OpusDocs selects the package, fills it from Salesforce, and helps legal stay aware when authorities publish new versions.