CRM for Solar Companies: How to Choose and Set It Up

Most CRM mistakes in solar are made before anyone signs: unclear record ownership, leads that arrive twice, and no way out. This guide compares four CRM options on what their own pages publish. It then walks through lead sources, handoffs, permissions, migration and a pilot you can score.

Last updated: November 2026

SurgePV publishes this guide. SurgePV’s CRM page names QuickEstimate as its CRM partner, so the QuickEstimate links here are sponsored. The table lists features and prices from each vendor’s own pages. It does not rank or score the tools.

Solar CRM Options Compared

The tools are in A to Z order. Each price is in the currency the vendor’s page shows. An API is a way for other software to use your data.

Sources: OpenSolar Project Management CRM, OpenSolar API and connector pricing, QuickEstimate pricing, lead capture, pipeline and WhatsApp follow-up pages, Salesforce pricing, and Zoho CRM pricing. We read these sources in October 2026.

QuickEstimate’s own pages differ on two points. Its pricing page lists IndiaMART and Meta connections on Pro. Its lead-capture page lists Facebook Lead Ads through Pabbly. That page also says native IndiaMART and JustDial integrations were planned for Q2 2026. Ask which connections are live on your plan. Its WhatsApp page says the free plan includes 100 WhatsApp messages a month and Pro includes 2,000.

The table lists no Meta or IndiaMART connector for Zoho CRM or Salesforce. If you need one, confirm the connector, the edition it needs and its price in a pilot. For a deeper look at the other two CRMs, read the solar sales CRM guide and Salesforce for solar companies.

What a Five-User CRM Costs

This table shows one year for five users at list price. It leaves out tax, add-ons, message fees and set-up. The currencies differ, so do not compare totals across rows.

A list price leaves out real costs. Add data cleaning and migration, WhatsApp and call fees, connector charges, admin time and training. Add the cost of exporting your data if you leave. Do not call any option cheaper until you price the same scope for each.

Start With How You Sell

Write down how money and work move through your company before you create fields. A residential installer gets many enquiries from individuals. It assigns them by postcode or branch, books a visit, sends a standard quote, and wins or loses within a short time. A C&I (commercial and industrial) installer may work with one company across several sites. It deals with many contacts, technical revisions, approvals and finance plans.

A dealer network adds territories, pricing permissions, lead protection and claims. A group that sells solar, storage, charging or maintenance needs separate security for each business unit. A single generic lead pipeline hurts adoption and forecasts in all of these cases.

Decide which differences need separate pipelines. A required field or a stage path can handle the rest. Too many pipelines split your reporting. Too few hide real decisions.

Decide Which System Owns Each Record

A system of record is the one system that holds the master copy of a record. Pick one for every shared field, and decide which way data flows. If two systems can both edit a phone number, price or status, decide which one wins and keep an audit trail.

Prefer shared IDs over fuzzy matching. Do not start with two-way sync just because an API allows it.

Keep people, accounts, sites and deals as separate records. A residential record should tell apart the enquirer, the person who pays the electricity bill, the property owner and the payer. They may be the same person, but the record should not assume it. A C&I record should separate the legal company, the billing entity, each site, each contact and each decision role. One company can have several site deals with different tariffs and decision dates. Define what “amount” means: total contract value, value before tax, recurring value or weighted forecast. Otherwise dashboards will disagree.

Bring In Leads From WhatsApp, Meta and IndiaMART

Every incoming record should keep its channel, campaign, platform lead ID, creation time, receipt time and any consent proof the source gives. Source history should survive reassignment, merging and import.

Have a lawyer check how you handle lead data against India’s data-protection requirements. MeitY, India’s IT ministry, has a data-protection framework page. Your CRM needs fields for notice, purpose, consent, access, correction, withdrawal and retention.

Use each platform’s own docs:

• IndiaMART. The CRM integration guidance describes two APIs. A Push API sends leads to your webhook URL in real time. A webhook URL is a web address that receives data automatically. A Pull API fetches leads every 5 minutes. The service is for paid sellers. It is do-it-yourself, and IndiaMART’s technical team gives no hand-holding. It has API hit logs and a test screen that sends a dummy lead.
• Meta lead ads. The lead-retrieval documentation says you can get leads by webhook or by bulk read. Full lead data needs the leads_retrieval permission. The page lists the other permissions. Real-time updates can arrive up to a few minutes late.
• WhatsApp. Start with the WhatsApp Business Platform documentation. Zoho’s help article lists what you need first. That is a Facebook Business Manager account, a verified business, a WhatsApp Business account and a registered phone number.
• Email and phone. Agree how mailboxes connect and who the sender is. Agree who owns each number and how call recording consent works. Also plan for when a user leaves.

Do not say a connector is built in until you have seen it work on your exact plan and setup.

Duplicates, routing and reply times

A duplicate check should flag likely matches without quietly dropping enquiries. A repeat enquiry can be a new buying signal. Test these cases:

• Same phone number with a different spelling of the name
• Same person filling in a Meta form and a website form
• One C&I contact asking about several sites
• A shared family phone for two properties
• A dealer sending a customer that direct sales already owns
• An old lost deal that returns after a long gap
• An imported record with no consent proof

Routing rules can use place, language, customer type, branch, dealer, workload or round robin. Add a fallback for a missing postcode, an absent user or a late integration. A reply-time target needs a start event, a stop event, a working calendar and an owner. Measure three times separately: receipt to assignment, assignment to first real attempt, and receipt to a useful reply. An automatic acknowledgement is not a human reply.

Connect Survey, Design, Quote and Handover

A survey request should carry the site ID, the goal, the contact, access limits and the proof needed. The CRM should point to the technical model and not copy every engineering input. A design result should return the model ID, revision, capacity, assumptions, document links and approver.

Use PV design software for the technical model and solar proposal software for controlled customer documents. Give both a shared project ID.

For estimates and proposals, decide who owns the product, labour, tax, discount and margin lists. Decide who may change price or scope. Decide how versions are numbered and which discounts need approval. Never overwrite a proposal that was sent. Keep each version, approval, delivery event and customer reply. For the cost side, see solar estimate software.

Make pipeline stages checkable. Each stage needs entry rules, required fields, an owner and an exit rule. Name stages after buyer or project evidence, not rep optimism. A residential path might run: new, contacted, survey done, quote approved, quote sent, decision pending, won or lost, handed over. A C&I path adds data received, feasibility, site and grid review, commercial submission and negotiation. A tender, a RESCO deal (renewable energy service company) and a repeat-customer site can each need different gates. Keep shared reporting fields across them.

When a deal is won, require an accepted proposal or contract reference. Also require the legal customer, the site, scope, price basis, tax treatment, payment schedule and promised dates. Accounting stays in charge of invoices and receipts. For TallyPrime, start from Tally’s integration documentation. Then set rules for IDs, data direction, approval, retries and reconciliation. After commissioning, link the installed equipment, warranty proof and service history to the same customer record.

Set Roles, Permissions and Audit Controls

Give each role the least access it needs. Define roles for administrator, sales, manager, surveyor, designer, estimator, approver, finance, project, service, partner and auditor. Control who can view records and fields, export, reassign, delete, merge, bulk edit, and use integration credentials.

Territory rules need exceptions for national accounts, cover for absent staff, cross-branch projects and dealer protection. Keep the previous owner and the reason in the audit history. Test what happens when a user leaves. Turn off access, end sessions and tokens, move records and tasks, reassign integrations and review exports.

Test mobile work on your own devices. A site user needs to find a visit, fill in a survey, attach photos, add notes and sync without creating duplicates. If a vendor claims offline use, test what you can read and write offline. Test how sync conflicts are handled and what happens after you reconnect.

Make Retries Safe and Reconcile the Numbers

Every integration needs a source and a destination, a stable ID, a field match, a retry rule, an alert and an owner. Make retries safe, so one retry does not create a second lead. Show a visible status when a handoff is waiting or has failed. A silent failure is worse than a temporary manual step.

Reconcile the counts over an agreed period. That means comparing the numbers on both sides. Compare Meta leads received with CRM records created. Compare IndiaMART enquiries with assigned records. Compare approved proposals with sent ones, and won deals with project handovers.

For developer documentation, Zoho lists API versions 2 to 8. The Zoho CRM V8 API documentation is the newest version it shows. Salesforce publishes its REST API documentation. These pages describe the APIs. They do not settle edition, price or fit for solar.

Write a data dictionary before you build dashboards. Define lead, qualified lead, deal, win, loss, value, stage age and reply time. A conversion rate needs a top number, a bottom number, a group of deals and a period. Do not edit stage history to make reports look better.

Plan Migration, Security and Exit

Start with a list of sources: spreadsheets, an old CRM, phones, inboxes, messaging apps, proposal tools and accounting. Import only records that you need, that are lawful and that you trust. Match source fields to target fields and stable IDs. Keep source and consent proof. Remove duplicates. Run a trial load and reconcile counts and key totals. Then plan the freeze, the cutover and the rollback.

For security, ask where data is hosted and how it is encrypted. Ask about single sign-on (one login for many apps), multi-factor login, roles, audit logs and backups. Also ask about subcontractors, incident notices, mobile controls and API keys. Ask for current proof, not a generic security badge.

Test the export before you buy. Export accounts, contacts, deals, activities, notes, attachments, consent, proposal references, audit history and custom fields, with their links intact. Record the format, the fees, the time taken and what is missing. Agree on help after termination, a read-only period and proof of deletion.

Launch in stages. Start with the data model and rules. Then add lead capture, stages and proposal references. Then add one integration at a time with monitoring. After launch, keep a change register for fields, stages, routing, permissions, automations and integrations. Review access and territories whenever staff, branches or dealers change.

Score a Pilot

Run residential, C&I, repeat-customer, dealer, duplicate, lost, won, service and integration-failure cases. Include a user with limited access, a manager, an administrator, a mobile user and a user who is leaving.

Mark each area pass, conditional pass or fail. Add the evidence, an owner and a retest date. Do not average a serious security or export failure into a high feature score.

Here is a useful test record. Take one company with two sites and one shared contact. Import the same enquiry twice with its original source ID. Then send a revised design and proposal for only one site. Check that no duplicate is created. Check that both site histories survive. Check that the earlier proposal stays available. Then break the connector, replay the failed event, remove the assigned user and export everything.

Where QuickEstimate Fits

QuickEstimate’s pages describe an India-focused solar CRM. It has lead capture, a solar pipeline, WhatsApp follow-up and quotations that apply PM Surya Ghar subsidy figures. PM Surya Ghar: Muft Bijli Yojana is an Indian government scheme that gives central financial assistance for household rooftop solar. QuickEstimate also states its limits. Free is one user and 10 proposals a month. Pro has a three-user minimum and yearly billing only.

Zoho CRM and Salesforce are general-purpose CRMs with published APIs. In either one, you set up the solar stages (survey, design, quote, install) and the quote documents yourself, or with a partner. The right pick depends on your size, your other systems and who will run it. Test every candidate against the same scorecard.

Checklist Before You Sign

Before signing, ask for:

• Your approved selling models: residential, C&I, dealer and group
• A data model for accounts, contacts, sites, deals, projects, equipment and service
• A system-of-record and field-ownership table
• Rules for consent, source, duplicates, routing, reply times and opt-outs
• Controls for survey, design, estimate, proposal, approval, contract, payment and handover
• Stage definitions, required fields, forecast groups and loss reasons
• Roles, territories, permissions, audit log, mobile use and the process for users who leave
• Integration field matches, stable IDs, retries, alerts, replay and reconciliation
• A reporting dictionary, history, exception lists and export
• Proof for migration, security, retention, backup, incidents, data location and deletion
• Contract terms for price, renewal, limits, support, termination, export and deletion

To go deeper on one topic, read the solar sales CRM guide and the solar CRM software India guide. Also see the SurgePV CRM partnership overview. You can also read the CRM versus spreadsheet comparison, the mobile CRM guide and the solar customer management guide.

A CRM holds the relationship, and the design and proposal sit beside it. SurgePV covers the design, BOM and proposal side, so book a demo with your CRM setup and we will show where the project handoff happens.

Frequently Asked Questions

What is the best CRM for a solar company?

No single CRM is best for everyone. Match it to how you sell: residential, C&I (commercial and industrial), dealer or a mix, then run the same test on every candidate. Test lead capture, duplicates, quote handoff, permissions and data export. The table on this page compares OpenSolar, QuickEstimate, Salesforce and Zoho CRM using each vendor’s published features and prices.

How much does a CRM for a solar company cost?

Among the four compared here, list prices run from free to US$550 per user per month. Free means the OpenSolar core app, Zoho CRM Free for up to 3 users, and QuickEstimate Free for 1 user. US$550 is Salesforce Sales Cloud Max billed annually, Salesforce Starter Suite is US$25 and Pro Suite is US$100. QuickEstimate Pro is ₹6,999 per user per year with a three-user minimum, and Zoho Standard is US$14 per user per month on its annual setting. Plans, units and billing periods differ, so check each vendor’s page.

What should a solar company track in its CRM?

Track the legal account and contacts, lead source, consent proof, duplicate status, owner, territory, stage and next action. Track site and survey references, design and estimate versions, proposal approval and delivery, and contract and payment status. Track the handover to the install team, installed equipment, service, warranty, referrals and the reason for any lost deal. Keep an audit history of changes.

Does a solar CRM replace design or accounting software?

No. The CRM usually owns the relationship, consent, deal, activity, stage and next-action records. Solar design software should own the geometry, equipment, electrical checks, yield and technical outputs. Accounting should own tax, invoices, receipts and financial records. Agree on shared IDs, handoffs and which system wins a conflict.

How should WhatsApp, IndiaMART and Meta leads enter a solar CRM?

Use each platform’s own route. For paid sellers, IndiaMART documents a Push API that sends leads in real time to a webhook URL, and a Pull API that fetches them every 5 minutes. Meta documents webhook and bulk-read retrieval for lead ads, and you need the lead retrieval permission for full lead data. Zoho’s WhatsApp guide lists a verified business and a WhatsApp Business account as prerequisites. Then match source IDs and consent, remove duplicates, route the leads, and compare platform totals with CRM records.

How should a solar company migrate CRM data?

List your data sources and define the target model first. Clean the data, remove duplicates and match stable IDs, consent and owners. Keep the history you need. Run a trial migration and reconcile counts and values. Get user sign-off, freeze changes, cut over, and keep a rollback plan. Keep source exports under an approved retention policy.

How should a solar company pilot CRM software?

Run real residential and C&I records through the whole path, from lead capture and consent to handover and service. Cover duplicates, assignment, survey, estimate, proposal versions and approvals, plus reporting, export, integration failure and user removal. Score the evidence, task time, errors, audit trail, recovery, admin effort and exit quality.