Rohit has been here before. Two years ago, a CRM vendor spent 45 minutes showing him a beautiful dashboard, dark mode, drag-and-drop cards, a pipeline that looked like something from a startup brochure. He signed up. Within six weeks, his reps had gone back to WhatsApp. The CRM could not generate a PM Surya Ghar-compliant proposal. It had no Android app worth using in the field. Customer support was available over email with a 48-hour response window.
The problem was not the demo. The demo was excellent. The problem was that Rohit did not know what questions to ask during the demo, so the vendor showed him everything impressive and skipped everything critical.
If you are evaluating solar CRM software in 2026, this guide gives you a structured way to avoid that mistake. The 7-Category Solar CRM Demo Scorecard lets you rate each vendor during the demo itself, so you walk out with a number rather than a feeling.
Key takeaway
Score every CRM vendor 0–3 across 7 categories (Lead Management, Proposal Automation, WhatsApp Integration, PM Surya Ghar Subsidy Calculation, Pipeline Dashboard, Mobile App, Pricing and Implementation) during the demo itself. A solar-specific CRM should score 17 or above out of 21. Below 14, walk away regardless of the price. The scoring takes under 20 minutes if you have the right questions ready before the call starts.
You can compare this scorecard against the full Solar CRM Buyer's Guide and the feature-level breakdown in solar CRM features to look for. If you are still deciding whether you need a CRM at all, the 6-signal CRM readiness test resolves that question first.
Why Most Solar CRM Demos Are Designed to Impress, Not Inform
A vendor-led demo has one goal: move you toward a purchase decision. That is not a criticism, it is just the incentive structure. The sales rep will open with the cleanest pipeline view, show the fastest proposal creation flow, and demonstrate integrations you will never use. They will not volunteer that their Android app crashes on Samsung Galaxy A-series phones, that PM Surya Ghar subsidy slabs require a manual configuration update every time MNRE revises them, or that "WhatsApp integration" means copy-pasting a link into a chat.
Indian solar EPCs have a specific set of requirements that differ from generic B2B sales CRMs. According to JMK Research, India added over 14 GW of rooftop solar capacity in 2024–25, with the residential segment growing fastest, driven almost entirely by PM Surya Ghar subsidies. Your CRM has to operate in that context, not in a generic sales context.
The gap between what demos show and what the field requires is widest in three areas:
Mobile-first reality. Most of your reps are on Android phones with variable connectivity. A CRM demo runs on a MacBook with a fibre connection. These are different products.
Subsidy complexity. The PM Surya Ghar scheme has multi-slab CFA structures that change. A generic CRM has no concept of this. A solar-specific CRM should pre-load these slabs, auto-calculate them per system size, and update them when MNRE revises the rates.
WhatsApp as the primary channel. Enterprise CRMs are built for email. Indian solar sales happen on WhatsApp. A CRM that does not natively integrate with WhatsApp Business API forces your reps to context-switch 30–40 times a day.
The 7-Category Scorecard below forces vendors to demonstrate each of these dimensions live, not in a slide deck.
The 7-Category Solar CRM Demo Scorecard
Score each category from 0 to 3 during the demo. Do not score from memory after the call, write the number in real time.
Scoring legend:
- 0, Feature is absent or requires a third-party workaround
- 1, Feature exists but is generic (not solar-specific)
- 2, Feature is functional and reasonably solar-aware
- 3, Feature is solar-specific, Indian-market-ready, and works on mobile without issues
-
1
Lead Management, max 3 pts
Does the CRM capture leads from multiple sources (IndiaMart, JustDial, Facebook, Google Ads, site form) and assign them automatically? Can a manager see every rep's lead count and last activity from one view?
-
2
Proposal Automation, max 3 pts
Can a rep generate a branded PDF proposal with subsidy auto-calculated on an Android phone in under 60 seconds? Is the proposal layout editable without code?
-
3
WhatsApp Integration, max 3 pts
Is WhatsApp Business API natively integrated, not just a send-link button? Can reps send follow-up messages from inside the CRM without switching apps? Are message templates pre-built for solar sales stages?
-
4
PM Surya Ghar Subsidy Calculation, max 3 pts
Does the CRM automatically apply CFA slabs (₹30,000/kW up to 2 kW; ₹18,000/kW for 2–3 kW) without manual input? Does it handle state top-up subsidies? Does it flag when a customer's system size crosses a slab boundary?
-
5
Pipeline Dashboard, max 3 pts
Can the owner see the full pipeline by stage, by rep, and by deal value on a phone in under 30 seconds? Does the dashboard update in real time without manual refresh? Are solar-specific stages pre-configured (Survey Scheduled, Proposal Sent, Net Metering Applied, Installed)?
-
6
Mobile App, max 3 pts
Is there a dedicated Android app (not a mobile web wrapper)? Does it work on 4G with intermittent connectivity? Can reps do site notes, photo uploads, and status updates without a desktop browser?
-
7
Pricing and Implementation, max 3 pts
Is pricing per-seat transparent with no hidden onboarding fees? Is the implementation timeline under two weeks for a 10-person team? Is support available in Hindi over phone or WhatsApp, not just email?
Total possible: 21 points. Use the scoring table at the end of this article during the demo.
Category 1: Lead Management, 7 Questions to Ask During the Demo
Lead capture and routing is where most generic CRMs fail Indian solar EPCs first. A solar EPC in 2026 gets leads from IndiaMart, JustDial, Facebook, Google, walk-ins, and referrals, often simultaneously. Ask these seven questions before you let the vendor move on to a different screen.
-
1
Show me how a lead from IndiaMart enters the CRM automatically.
If the answer is "we have a Zapier integration you set up yourself," that is a 1 out of 3, not a 3. Native connectors with zero-configuration setup matter because your reps will not maintain a Zapier workflow when it breaks at 9 PM.
-
2
How does the system prevent two reps from contacting the same lead?
Duplicate lead management is non-negotiable at any EPC with more than two reps. Watch for deduplication by phone number, the most reliable identifier in Indian solar sales since customers give different names in different contexts.
-
3
Can I see which rep called a lead and what was said, from my phone right now?
Ask the vendor to demonstrate this on an actual phone, not a browser. If the mobile view is a stripped-down version of the web app with key data missing, that is what your reps will see in the field.
-
4
What happens to a lead that has not been followed up in 3 days?
The system should have an automatic alert, to the rep and to you. If the vendor says "you can set up a reminder manually," that is a 1. If the system surfaces stale leads automatically on the dashboard every morning, that is a 3.
-
5
Can I filter leads by pincode, system size interest, or subsidy eligibility?
These are solar-specific filters that generic CRMs do not have. If you run targeted campaigns or service specific pincodes, you need to segment your lead list by these parameters. A generic CRM gives you name, email, phone, nothing else pre-built.
-
6
Does the system record the lead source automatically, and does that data appear in your reports?
Lead source tracking matters for your marketing budget. If you spend ₹20,000 per month on IndiaMart and ₹15,000 on Facebook ads, you need to know which channel closes more deals. A CRM that does not track source-to-close makes every marketing decision a guess.
-
7
If I import my existing 500-lead Excel sheet today, how long does it take, and what breaks?
Ask about this directly. Most CRM vendors will show you a clean import flow on tidy sample data. Ask what happens with messy data, duplicate numbers, missing fields, non-standard date formats. The answer tells you how much manual cleanup you will be doing during CRM implementation.
Category 2: Proposal Automation, What 60 Seconds Actually Means
Sixty seconds is not a marketing claim, it is a specific workflow benchmark. When a rep is sitting across from a customer at their home after a site survey, the customer is at peak interest. If the rep has to say "I will send you a quote tomorrow," that interest drops. According to QuickEstimate platform data, proposals sent within 10 minutes of a site visit close at 2.3× the rate of proposals sent the next day.
60seconds
Target proposal creation time on Android
Source: QuickEstimate platform benchmark, 2025
2.3×close rate
Proposals sent in under 10 minutes vs next-day
Source: QuickEstimate platform data, 2025
During the demo, ask the vendor to generate a proposal live, not from a saved template with pre-filled data, but by entering a customer name, address, electricity bill amount, and system size from scratch on an Android phone. Time it. If it takes more than 3 minutes on their own demo device, it will take longer in the field.
Demo script. Say: "Can you open a new lead right now, enter a 3 kW system in Ahmedabad with a ₹3,500 monthly bill, generate a proposal with PM Surya Ghar subsidy, and send it to a WhatsApp number, all from your phone?" The entire sequence should take under 90 seconds in a solar-first CRM. Read more on what this looks like in the proposal generator feature overview.
Also check whether the proposal tracking feature shows when the customer opened the proposal and for how long, this tells your rep when to follow up rather than guessing.
Category 3: WhatsApp Integration, The Feature That Separates Indian Solar CRMs from Global Ones
Indian solar sales run on WhatsApp. A customer who would not answer a phone call will respond to a WhatsApp message in 4 minutes. According to CEEW research on solar adoption patterns, over 70% of post-survey customer communication happens on WhatsApp in Indian residential solar markets. Your CRM's WhatsApp integration is not a nice-to-have, it is the primary communication channel.
There are three levels of WhatsApp integration that vendors call "WhatsApp integration":
Level 1, A button that opens WhatsApp. This is not integration. This is a tel: link with a different protocol. Clicking it opens WhatsApp on the rep's phone and switches context. No message history is stored in the CRM. Score: 0.
Level 2, WhatsApp Business API connection via a third-party service. Messages can be sent from the CRM interface, but templates require approval, setup takes a week, and support is split between two vendors when something breaks. Score: 1–2 depending on reliability.
Level 3, Native WhatsApp Business API integration with solar-stage message templates pre-loaded. Templates for "proposal sent," "follow-up reminder," "site survey confirmation," and "subsidy application status" are built in. Message history syncs back to the lead record. Score: 3.
Test this during the demo. Ask the vendor to send a pre-approved WhatsApp template message to a test number from inside the CRM interface without touching the phone's WhatsApp app. If they cannot do it in the demo, they cannot do it in production. QuickEstimate's WhatsApp follow-up feature handles this natively with solar-specific templates pre-approved on the WhatsApp Business API.
Also ask: if a customer replies on WhatsApp, does the reply appear in the CRM lead record automatically? This is the difference between an integration and a one-way broadcast tool.
Category 4: PM Surya Ghar Subsidy Auto-Calculation, The Non-Negotiable Feature
The PM Surya Ghar Muft Bijli Yojana has specific Central Financial Assistance (CFA) slabs: ₹30,000 per kW for systems up to 2 kW, and ₹18,000 per kW for the 2–3 kW range, subject to MNRE guidelines. Several states add top-up subsidies on top of this. A proposal that quotes the wrong subsidy is not just embarrassing, it creates a contractual problem when the customer's actual payout differs from what was promised.
This table shows the functional difference between a CRM that has built-in subsidy calculation and one that does not:
| Capability | Has subsidy auto-calc | No subsidy auto-calc |
|---|---|---|
| Subsidy in proposal | Auto-populated from system size | Rep manually enters, error-prone |
| State top-up subsidies | Configured per state, auto-applied | Not tracked; rep must know from memory |
| Slab boundary alerts | Flags when system crosses 2 kW or 3 kW | No alert; wrong slab applied silently |
| Rate updates when MNRE revises | Vendor updates; auto-applies to new proposals | Rep continues using old rates until informed |
| Net-of-subsidy price in proposal | Auto-calculated, shown prominently | Must be manually computed; often omitted |
| Consistency across reps | Every rep quotes identical subsidy for same size | Different reps quote different amounts for same system |
Scoring tip. If subsidy calculation is fully automatic and handles state top-ups, score 3. If it auto-calculates central CFA only and requires manual state entry, score 2. If the rep must type in the subsidy amount from a reference sheet, score 1. If the CRM has no subsidy field at all, score 0, and seriously reconsider this vendor for Indian residential solar.
Category 5 and 6: Pipeline Dashboard and Mobile-First Android App
These two categories are linked because the pipeline is only useful if your team can update it in the field without friction. An owner who can see their sales pipeline from a phone gets two critical benefits: they do not need daily team calls to know deal status, and they can intervene on a stalled deal before it goes cold.
Pipeline Dashboard, Pros and Cons by Implementation Type
Solar-specific pipeline
- Pre-configured stages (New Lead, Survey Done, Proposal Sent, Net Metering Applied, Installed, Lost)
- Deal value auto-calculated from system size and component prices
- Owner sees full pipeline in one screen without setup
- Stage-specific automation triggers (e.g., auto-send survey confirmation when stage changes)
Generic pipeline
- Stages must be configured from scratch, takes 1–2 days to get right
- Deal value is a freeform text field with no ₹ formatting or subsidy logic
- Dashboard is desktop-first; mobile view is a truncated table
- No automation without paying for the top-tier plan
Mobile App, the Android-first test
India's solar field sales run on Android. According to Mercom India's market data, over 85% of Indian smartphone users are on Android, with the Galaxy A-series and Redmi devices dominating among field sales teams. A CRM app that was designed for iOS and ported to Android will show it, slower load times, broken layouts, and missing features that "will be added in the next release."
During the demo, ask the vendor to open their Android app and demonstrate:
- Adding a new lead from scratch
- Updating a lead stage
- Generating and sending a proposal
- Viewing the pipeline dashboard
If any of these require switching to a browser, mark the Mobile App category down by 1 point per step that fails on native Android.
Connectivity test. Ask the vendor: "What happens in your app when the phone drops to 2G for 30 seconds?" A properly built Android-first app caches unsaved entries locally and syncs when connectivity returns. If the answer is "you will lose your data," that is a field disaster waiting to happen on a site visit in a basement or a rural location.
Category 7: Pricing, Implementation, and Support, What to Negotiate
Pricing is the final category in the scorecard but often the first thing vendors want to discuss. Reverse this in your demo. Get the functionality score first, then discuss pricing as a function of value delivered, not as a starting point.
When you do reach pricing, ask about these specific line items before you accept any quote:
Per-seat vs per-company pricing. Some CRMs charge per user seat. If you have 8 reps, that compounds fast. Solar EPCs with large field teams should negotiate a company-wide seat with unlimited users, or at least a cap on seat cost as you scale. Read the detailed breakdown in the solar CRM pricing guide.
Implementation fees. A CRM vendor who charges ₹15,000–₹40,000 in onboarding fees for a tool with a 2-week implementation timeline is pricing in complexity they create. A solar-specific CRM should be live in under two weeks for a team of under 15 people, without a paid onboarding package. Check the typical timeline benchmarks from CRM implementation in India.
Support language and channel. Enterprise CRM support runs Monday–Friday over email in English. Your reps are in the field on Saturday. Your site supervisor speaks Hindi. Ask specifically: "Is there a Hindi-language support option? Is WhatsApp or phone support available?" If the answer is email-only, that is a 1 in this category.
Contract length and exit clauses. Ask for a 3-month pilot before committing to an annual contract. Any vendor confident in their product will agree. A vendor who pushes back on a 3-month pilot is telling you something about their churn rate. Also check the scalability questions before signing anything longer than 12 months.
Red Flags: 8 Things That Should Kill a Deal During a Solar CRM Demo
These eight behaviours during a vendor demo should stop your evaluation entirely, regardless of how good the rest of the product looks.
-
!
They demo on a laptop and refuse to demo on mobile
If the vendor cannot demo the CRM on an Android phone, your reps cannot use it in the field. There is no exception to this rule in 2026.
-
!
PM Surya Ghar subsidy is "coming soon" or "available with custom configuration"
This scheme has been the primary driver of Indian residential solar for two years. If it is not already built in, the vendor is not tracking the Indian market closely enough to be trusted with your sales pipeline.
-
!
WhatsApp integration is a third-party Zapier zap they ask you to set up yourself
You are not a developer. When the zap breaks at 11 PM on a Monday, you will not be fixing it. Zapier-based integrations are maintenance burdens, not features.
-
!
The vendor cannot name three Indian solar EPCs using their product right now
Industry-specific CRMs build their product around their customers' specific workflows. If the vendor cannot name existing solar EPC clients, they are building a generic CRM and calling it solar.
-
!
Data export is buried, locked behind a plan upgrade, or requires a support ticket
You own your lead data. Any CRM that makes exporting it difficult is creating a hostage situation. Ask the vendor to show you the data export function right now, during the demo. It should be a one-click CSV download.
-
!
Support is email-only with a 48-hour SLA
When a rep cannot send a proposal before a customer meeting in 3 hours, a 48-hour email response is not support. Ask specifically for the after-hours contact method and test it by messaging them outside business hours before you sign.
-
!
The demo uses a pre-built demo account, they will not create a fresh account with your data
A polished demo account hides setup complexity. Ask the vendor to start from a blank account and configure it for your business during the call. If they refuse, the setup experience is probably terrible.
-
!
The pricing changes between the demo and the actual contract
Get the pricing in writing before the demo ends, not in a follow-up email. Verbal pricing that changes is a negotiation tactic. A solar EPC should compare vendors on a level field with identical pricing terms in hand. See how different vendors compare in top solar CRM alternatives in India.
How QuickEstimate Fits
QuickEstimate is built specifically for Indian solar EPCs, not a generic CRM with a solar skin on top. Here is what that means in the context of the 7-Category Scorecard:
- Lead Management (Category 1): Native connectors for IndiaMart, JustDial, Facebook Lead Ads, and Google Ads. Leads route to the right rep automatically based on pincode or system size. Stale lead alerts surface on the manager dashboard every morning without any setup. See the lead capture feature in detail.
- Proposal Automation (Category 2): A rep can generate a branded PDF proposal on Android in under 60 seconds, enter system size, the subsidy calculates automatically, the net-of-subsidy price appears, and the PDF goes to the customer via WhatsApp in one tap. The proposal generator handles this end-to-end.
- WhatsApp Integration (Category 3): Native WhatsApp Business API, send follow-ups, proposals, and subsidy update messages from inside the CRM. Customer replies sync back to the lead record automatically. See the WhatsApp follow-up feature.
- PM Surya Ghar (Category 4): CFA slabs are pre-loaded and update automatically when MNRE revises rates. State top-up subsidies are configurable per state. Slab boundary warnings appear when a system size crosses 2 kW or 3 kW.
- Pipeline and Mobile (Categories 5 and 6): Solar-specific pipeline stages are pre-configured. The pipeline management view loads in under 3 seconds on a 4G connection. The Android app works offline and syncs when connectivity returns. Sales reports show stage-by-stage conversion rates without manual calculation.
- Pricing and Support (Category 7): Transparent per-company pricing, no per-seat charges for field reps. Implementation takes under one week for most EPCs. Support is available in Hindi over WhatsApp with a 4-hour response window on weekdays. Book a live demo to see QuickEstimate scored against the 7-Category Scorecard in real time.
If you want a structured walk-through of how to choose a CRM vendor before booking a demo, the how to choose the right solar CRM guide covers the decision framework from scratch. The QuickEstimate masterclass also covers pipeline setup and lead management in depth for Indian EPCs.
The Scoring Table: Bring This to Your Next Demo
Print this or open it on your second screen during the demo. Fill in the score for each category in real time.
| # | Category | What 3/3 looks like | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|---|
| 1 | Lead Management | Native multi-source capture, dedup by phone, stale-lead alerts auto-on | __ | __ | __ |
| 2 | Proposal Automation | Branded PDF on Android in under 60 sec, subsidy auto-applied, WhatsApp send in one tap | __ | __ | __ |
| 3 | WhatsApp Integration | Native API, solar templates pre-loaded, replies sync to lead record | __ | __ | __ |
| 4 | PM Surya Ghar Subsidy | CFA slabs pre-loaded, state top-ups configurable, slab boundary alerts | __ | __ | __ |
| 5 | Pipeline Dashboard | Solar stages pre-set, real-time on phone, conversion rates auto-calculated | __ | __ | __ |
| 6 | Mobile App (Android) | Native Android, offline-capable, full feature parity with desktop | __ | __ | __ |
| 7 | Pricing and Implementation | Transparent pricing, live in under 2 weeks, Hindi phone or WhatsApp support | __ | __ | __ |
| Total Score (max 21) | 17+ = strong | __ | __ | __ | |
Score interpretation:
- 17–21: Proceed to a 3-month pilot. Negotiate contract terms.
- 14–16: Acceptable if the gaps are in Category 7 (pricing/support), not in Categories 2–4. Negotiate hard on the missing features as a product roadmap commitment.
- Below 14: Walk away. The missing features in core categories will not be fixed during your subscription. The vendor is selling a roadmap, not a product.
You can use this same framework when reading reviews on third-party sites, apply the scorecard mentally to what other EPCs describe and see how the scores hold up. The best solar CRM software in India comparison covers the major vendors with this lens applied.
FAQ
What is the most important feature to test in a solar CRM demo?
Proposal automation on an Android phone is the single most important feature to test. Ask the vendor to generate a PM Surya Ghar-compliant proposal from a fresh lead on an Android phone in under 90 seconds. If they cannot do this, your reps will not use the CRM consistently in the field, which means the pipeline data will always be incomplete.
How long should a solar CRM demo last?
A productive solar CRM demo takes 45–60 minutes. The first 10 minutes should be your questions about their existing solar EPC clients and their roadmap. The next 30 minutes should be live feature demonstrations across the 7 categories in the scorecard. The final 10–15 minutes should cover pricing and implementation timeline. Any demo shorter than 40 minutes is a pitch, not an evaluation.
Should I negotiate pricing during the demo?
Score the product first, then negotiate. If you raise pricing early, the vendor will anchor on a number before you know whether the product is worth it. Complete the 7-Category Scorecard during the demo, then use the score as negotiating power: a vendor scoring 14 out of 21 should not be priced the same as one scoring 19.
What does PM Surya Ghar auto-calculation mean in a CRM?
The CRM automatically applies the correct CFA slab based on the system size entered for a customer. The net-of-subsidy price appears in the proposal without any manual calculation. The best implementations also handle state top-up subsidies and alert the rep when the system size crosses a slab boundary. More detail at the PM Surya Ghar national portal.
Is WhatsApp integration important in a solar CRM?
Yes, it is the primary communication channel for Indian solar sales. Over 70% of post-survey customer communication happens on WhatsApp in Indian residential solar markets, according to CEEW solar adoption research. A CRM that does not integrate natively with WhatsApp Business API forces your reps to context-switch between tools 30–40 times a day.
How do I evaluate a CRM's mobile app during a demo?
Ask the vendor to demonstrate four tasks on an Android phone: adding a new lead, updating a lead stage, generating and sending a proposal, and viewing the pipeline dashboard. Each task that requires switching to a browser should reduce your mobile score by 1 point. Also ask what happens when the phone drops to 2G, a field-ready app caches data locally and syncs when connectivity returns.
What is a good score on the 7-Category Solar CRM Demo Scorecard?
17 or above out of 21 is strong. A score of 14–16 is acceptable if the gaps are in Category 7 only. Below 14 means the product has fundamental gaps for Indian solar sales workflows. Do not let a low-scoring vendor talk you into a trial, the gaps you see in the demo will be the same gaps your reps encounter in the field. Refer to the detailed breakdown in solar CRM features to look for for the full feature checklist.
Should I ask for a trial before signing a solar CRM contract?
Always ask for a 3-month pilot before committing to an annual contract. A vendor confident in their product will agree. If the vendor refuses or heavily discounts only the annual option, treat that as a red flag. Confirm data export is available at any point during the trial so you are not locked in if the product does not deliver. The 8 CRM scalability questions checklist helps you evaluate long-term fit before you commit.
Want to put this into practice?
QuickEstimate gives you everything in this article, proposal automation, lead capture, WhatsApp follow-up, built for Indian solar EPCs.
Start free