12 Red Flags to Watch for Before Buying a

Choosing a CRM is one of the most consequential software decisions a solar EPC owner or operations lead will make. Get it right and the tool becomes the backbone of your sales operation, every lead tracked, every proposal consistent, every follow-up on time. Get it wrong and you spend six months with a tool that the team hates, a migration nightmare, and the same broken processes as before, just more expensive.

The challenge in India is that the solar CRM market is full of tools that look right on a demo screen but are not built for Indian solar operations. Many are generic sales CRMs with a solar-sounding landing page. Some are Indian-built tools that solve only the easiest problems. A few are genuinely excellent products that will serve your team for years.

This guide gives you the twelve red flags that separate a CRM that will genuinely serve an Indian solar EPC, with PM Surya Ghar subsidy, WhatsApp communication, DISCOM paperwork, and field-heavy operations, from one that only looks good in a Zoom demo.

Why Generic CRM Evaluation Frameworks Fail for Solar

Standard CRM evaluation guides ask about integrations, pricing tiers, API access, and customer support hours. These matter, but they miss the solar-specific requirements that determine whether a team in Ahmedabad, Hyderabad, or Lucknow will actually use the tool day-to-day.

An Indian solar EPC has needs that no generic B2B SaaS tool is designed for:

• Subsidy calculations that change when the government updates PM Surya Ghar slabs
• DISCOM-specific net metering application tracking with different timelines per state
• WhatsApp as the primary customer communication channel, not email
• Android-first field usage by installation supervisors and survey technicians
• Proposal PDFs that carry your company brand, not the CRM vendor's watermark
• Compliance with India's emerging data privacy landscape under the DPDP Act 2023

The twelve red flags below are specifically calibrated to these requirements. Use them as a structured evaluation checklist in every vendor demo. Our full solar CRM buyer's guide covers the positive requirements in detail, this post focuses on the warning signs.

---

The 12 Red Flags

Red Flag 1: No PM Surya Ghar Subsidy Calculator

Why it matters: As of June 2026, PM Surya Ghar Muft Bijli Yojana is the primary purchase driver for residential solar in India. The subsidy structure, ₹30,000 for 1 kW, ₹60,000 for 2 kW, ₹78,000 for 3 kW and above, determines the customer's net cost and ROI calculation. A CRM with no built-in subsidy calculator forces your sales rep to open a separate spreadsheet, calculate manually, and copy the number into the proposal. This three-step process introduces errors and slows down the proposal timeline.

More critically, subsidy slabs are updated periodically. A CRM with a static subsidy field that your admin has to manually update every time the government changes the rate is a compliance and accuracy liability.

What to ask the vendor: "Show me how the subsidy calculator updates when government rates change. Is it automatic or manual? Can it handle state-level top-up subsidies alongside the central subsidy?"

A CRM that cannot answer this confidently is not built for Indian solar.

Red Flag 2: No Mobile Android App (or an App That Requires Internet)

Why it matters: In India, 78% of solar site surveys happen in residential neighbourhoods, rooftops, and semi-urban areas where internet connectivity is inconsistent. A CRM that only works via desktop browser, or a mobile app that cannot function offline, means your field team either skips logging data until they get back to the office (by which time the details are fuzzy) or cannot use the tool at all.

The Android requirement specifically matters because the Indian solar sales team is almost entirely Android-based. An iOS-first app with a half-built Android version is a signal that the vendor does not understand their Indian customer.

What to ask the vendor: "Does your Android app work fully offline? Which features are available without internet? Can a sales rep complete a site survey form, take photos, and generate a proposal draft without a network connection?" Ask to see this demonstrated in flight mode, not described.

Red Flag 3: Built for Generic Sales, Not Solar

Why it matters: A solar EPC's sales pipeline has stages that are fundamentally different from a generic B2B or retail sales process: Site Survey Scheduled, Shadow Analysis Complete, DISCOM Application Filed, Net Metering Approved, Commissioning Done. If a CRM's default pipeline stages are "Prospect, Qualified Lead, Proposal, Negotiation, Closed Won", the vocabulary of SaaS or real-estate sales, it is telling you something important about who it was built for.

The mismatch goes deeper than stage names. Solar deals involve technical parameters (system size in kWp, panel type, inverter brand, shadow-free area) that should live natively on the deal card, not in a custom text field you have to create yourself. A proposal tool that does not understand kilowatt-peak is not a solar proposal tool.

What to ask the vendor: "Show me the default pipeline stages for a solar EPC. What solar-specific fields are on the deal card out of the box? Can I track system size, roof type, and subsidy eligibility on the lead record without custom development?"

Compare the answers to what a purpose-built solar CRM offers vs. a generic tool in our guide to buying your first solar CRM.

Red Flag 4: No WhatsApp Integration

Why it matters: Indian solar buyers communicate almost exclusively via WhatsApp. The sales process from first enquiry to signed contract typically involves eight to fifteen WhatsApp messages, shared images of electricity bills, and a proposal PDF sent via WhatsApp chat. A CRM with no WhatsApp integration forces your team to switch between apps for every customer interaction, and the CRM record is always incomplete because half the conversation is locked in WhatsApp.

The integration should be two-way: messages sent by the customer appear inside the CRM deal record, and the rep can reply from within the CRM without leaving the interface. One-way integrations (where only outgoing messages are logged) miss half the conversation context.

What to ask the vendor: "Show me a live demo of a WhatsApp conversation being logged in a deal record. Can I reply from the CRM? Are incoming messages visible? Does this work with a regular WhatsApp Business number or does it require the WhatsApp Business API (which costs ₹2,000–5,000/month extra)?"

Our detailed breakdown of WhatsApp CRM features covers exactly what the integration should include.

Red Flag 5: Proposal PDF Is Not Brandable

Why it matters: Your proposal is the most high-stakes document in your sales process. It represents your company's professionalism, builds customer trust, and differentiates you from competitors offering handwritten or generic Excel printouts. A proposal with the CRM vendor's watermark, logo, or default template at the bottom is telling your customer: "We use someone else's software and we couldn't customise it."

In a market where customers are spending ₹1.5–8 lakh on a single purchase, brand trust matters. Our analysis of solar sales best practices consistently finds that branded, visual proposals close 18–25% better than plain-text equivalents.

Brandability goes beyond just adding your logo. The font, colour scheme, header layout, section order, and custom terms and conditions should all be configurable. Your proposal in Rajasthan (desert climate, high irradiation) should be able to look different from your proposal in Kerala (monsoon, shading considerations).

What to ask the vendor: "Show me a proposal generated with our logo and brand colours. Can I change the template layout? Can I add custom pages or sections? Is there a watermark or vendor branding on the free or base plan that I cannot remove?"

Red Flag 6: No Pipeline Stage Customisation

Why it matters: Every solar EPC has a slightly different sales process. A residential-focused EPC in Gujarat with a thirty-day average deal cycle has different stage requirements than a commercial-focused EPC in Maharashtra with a ninety-day cycle. A CRM that forces you to use fixed, generic pipeline stages, with no ability to add, rename, or reorder stages, is a tool that will never feel right for your process.

The customisation requirement extends to stage-specific automations. When a deal moves from "Site Survey Done" to "Proposal Sent," the CRM should automatically: send a WhatsApp acknowledgement to the customer, schedule a Day-3 follow-up reminder for the rep, and notify the back-office coordinator to begin the net metering paperwork. If stages cannot be customised, these automations cannot be properly configured either.

What to ask the vendor: "Can I add custom pipeline stages? Can I build stage-specific automations? Is there a limit to the number of stages I can create? Can I have different pipelines for residential and commercial projects?"

Red Flag 7: No Offline Mode

Why it matters: Site surveys happen on rooftops, in villages, in industrial estates with poor connectivity. Installation supervisors need to mark project progress checkpoints from sites that have no mobile data. If your CRM requires a live internet connection for every action, your field team will either skip using it entirely or create a shadow system (WhatsApp, paper) that defeats the purpose of having a CRM.

Offline mode should store data locally and sync automatically when connectivity is restored, not just "remember the last page you viewed."

What to ask the vendor: "What specifically happens when a field rep loses internet? Can they add lead notes, complete site survey forms, update project status, and take photos? How long does unsaved data persist? Does it sync automatically or do they have to manually trigger a sync?"

Red Flag 8: Per-User Pricing That Becomes Unaffordable at Scale

Why it matters: A solar EPC that starts with four users at ₹800/user/month pays ₹3,200/month, manageable. The same tool at fifty users costs ₹40,000/month, or ₹4.8 lakh per year, on CRM software alone. Per-user pricing that looks reasonable at Stage 1 becomes a growth penalty at Stage 3 and Stage 4.

This matters especially for solar EPCs because the "team" includes roles that use the CRM lightly, installation supervisors who just update project status, back-office staff who only process DISCOM documents, drivers who need read-only access for delivery addresses. Paying full per-user rates for light users is economically irrational.

What to ask the vendor: "What is the pricing at 5 users, 15 users, and 50 users? Are there different tiers for light users vs. full users? Is there a flat-rate plan for unlimited users? What features are restricted at lower pricing tiers?"

Compare per-user CRM costs vs. flat pricing in the context of long-term CRM investment in our solar sales team KPIs guide, which covers the ROI calculation for sales tools.

Red Flag 9: No DISCOM or Net Metering Application Tracking

Why it matters: For Indian solar EPCs, the DISCOM net metering application is not a sales activity, it is a project milestone that directly affects cash collection. Many EPCs collect the final payment tranche only after commissioning, which requires DISCOM approval of the net metering application. A single missed DISCOM deadline can delay the final payment on a ₹5 lakh project by four to six weeks.

A solar CRM should track DISCOM application status as a first-class feature: application filed date, expected approval date, actual approval date, rejection reason (if rejected), and resubmission status. This is not a generic project management task, it is solar-specific compliance with financial consequences.

What to ask the vendor: "Does the CRM track DISCOM net metering applications? Can I log the application filing date, expected approval timeline, and approval/rejection status? Does it send reminders when an application is approaching its deadline? Can I filter my pipeline by DISCOM application status?"

See the complete DISCOM compliance requirements in our guide to the solar sales funnel in India.

Red Flag 10: No Indian Payment Gateway Integration

Why it matters: Solar EPC deals in India typically involve three to five payment milestones: advance on signing, payment on material delivery, payment on installation completion, and final payment on commissioning or DISCOM approval. Tracking these milestones, and sending automated payment reminders, is a core operational need, not a nice-to-have.

A CRM with no integration to Razorpay, PayU, or Cashfree means your team is managing payment tracking in a separate spreadsheet, manually reconciling with bank statements, and missing payment follow-ups when customers delay.

The integration should allow you to: generate a payment link directly from the CRM deal record, track which milestones have been paid, and automate a WhatsApp reminder when a milestone is due but not received.

What to ask the vendor: "Which Indian payment gateways do you integrate with? Can I generate a payment link from a deal record? Can I track partial payments against a milestone schedule? Does the system send automated reminders for overdue payments?"

Red Flag 11: Data Export Locked or Expensive

Why it matters: Your customer data, lead records, deal history, contact information, proposal archives, is your most valuable business asset. A CRM that makes it difficult, expensive, or technically complex to export your own data is using lock-in as a retention strategy. If you ever need to switch vendors, migrate to an ERP, or pull data for regulatory compliance, you should be able to do so without paying an exit fee or waiting for a vendor ticket.

This is especially important under India's Digital Personal Data Protection Act 2023, which gives data principals (your customers) rights over their data. If a customer requests their data or its deletion, you need to be able to fulfil that request from your CRM within a reasonable timeframe.

What to ask the vendor: "How do I export all my data? Is it a self-service export in CSV or Excel? Are there any charges for data export? Can I export all historical deal records, notes, and activity logs? What happens to my data if I cancel the subscription, is there a grace period to download it?"

Red Flag 12: No Indian Data Hosting or DPDP Compliance Posture

Why it matters: The Digital Personal Data Protection Act 2023 is India's first comprehensive data privacy law. While full enforcement timelines are still being finalised, the direction is clear: Indian businesses will be expected to demonstrate responsible handling of Indian citizens' personal data. A CRM that stores all your customer data on servers in the US or EU, with no Indian data residency option and no DPDP compliance statement, is a risk that will only grow over the next two to three years.

Beyond regulatory compliance, Indian data hosting offers a practical benefit: lower latency for your field team. A CRM hosted in Mumbai or Hyderabad loads 40–60% faster on mobile connections than one routed through AWS us-east-1.

What to ask the vendor: "Where is customer data physically stored? Is there an Indian data residency option? Do you have a DPDP compliance statement or data processing agreement? Are you ISO 27001 or SOC 2 certified? What is your data breach notification policy?"

---

Summary Comparison: Solar-Ready vs. Generic CRM

---

How to Use These Red Flags in a Demo

The best way to evaluate a CRM is to run a structured demo that systematically tests each of the twelve points above. Here is a step-by-step protocol.

---

Red Flag Scorecard

Use this scoring grid during your evaluation. Award 1 point for each red flag that applies. A score of 0–2 is acceptable. A score of 5+ means the tool is not suitable for an Indian solar EPC operation without significant workarounds.

---

Stats: The Real Cost of Choosing the Wrong CRM

---

What Good Looks Like

For each of the twelve red flags above, a solar-purpose-built CRM should pass every test. The benchmarks to look for:

• PM Surya Ghar subsidy auto-calculated from system size with one-click update when government rates change
• Android app with full offline mode, site surveys, lead notes, photos, and proposal drafts all work without internet
• Default pipeline stages that match a solar EPC workflow, not a generic B2B sales workflow
• Two-way WhatsApp integration that works with a standard Business number, not just the expensive API
• Proposal PDFs with your logo, colours, and layout, zero vendor branding visible to customers
• DISCOM application tracking built into the project record, with deadline reminders and status filtering
• Flat-rate or volume-tier pricing that does not penalise team growth at 15 or 50 users
• Self-service CSV export, available immediately, with no additional cost or support ticket required
• Indian data hosting with a clear DPDP compliance statement and data processing agreement

For the broader evaluation framework, including positive requirements, feature weightings, and vendor comparison matrix, see our complete solar CRM buyer's guide, our guide to qualifying solar leads, and our breakdown of the solar sales team structure that the right CRM should support.

---

---

Frequently Asked Questions

Q1: What is the biggest red flag when choosing a solar CRM in India?

The three most critical red flags are: no PM Surya Ghar subsidy calculator, no offline Android app, and no WhatsApp integration. Any one of these means the tool is not designed for how Indian solar sales teams actually work. A CRM without these three capabilities will either be rejected by the team within sixty days or require expensive workarounds that defeat the purpose of a unified system.

Q2: Why does per-user CRM pricing matter for a growing solar EPC?

A per-user pricing model that costs ₹800/user/month at five users (₹4,000/month) costs ₹40,000/month at fifty users, that is ₹4.8 lakh per year on CRM software alone. For an EPC growing from ten to thirty people in eighteen months, this growth penalty is significant. Flat-rate or volume-tier pricing is more appropriate for an operations-heavy business that adds light users as it scales.

Q3: Does a solar CRM need to comply with India's DPDP Act?

Yes. Under the DPDP Act 2023, your solar EPC is a Data Fiduciary for your customers' personal information. Your CRM vendor is a Data Processor. You need a Data Processing Agreement with your vendor, clarity on where data is stored, and assurance that data can be exported or deleted on request. A vendor with no DPDP compliance posture creates a legal liability for your business.

Q4: How important is WhatsApp integration in a solar CRM?

Extremely important. Indian solar buyers communicate primarily via WhatsApp from first enquiry through deal closure. Without two-way WhatsApp integration, half your sales conversation is invisible in the CRM record, reps must manually log customer responses, and follow-up reminders cannot be triggered by customer replies. Look for integration that works with a standard WhatsApp Business number, not just the expensive WhatsApp Business API.

Q5: What questions should I ask about offline mode?

Ask: "What specifically can a field rep do without internet?" followed by a live flight-mode demonstration. The app should support adding lead notes, completing site survey forms, taking photos, and updating project status, all without a network connection. Data should sync automatically when connectivity is restored. If the vendor describes offline mode as "viewing cached data" rather than "creating and editing data," it is not a true offline mode.

Q6: Is it a red flag if a CRM does not have DISCOM tracking?

Yes, it is a significant red flag for Indian solar operations. DISCOM net metering applications directly affect commissioning timelines and final payment collection. A project delayed at DISCOM approval holds up the final payment tranche, affecting cash flow. A CRM without built-in DISCOM application tracking forces the operations team to manage this critical milestone in a separate spreadsheet.

Q7: How do I test proposal branding capabilities before buying?

During the demo, upload your logo and set your brand colour scheme, then generate a sample proposal PDF on the spot. Check: Is there any vendor logo or watermark? Can you change the font or header layout? Can you add custom terms and conditions? A CRM that cannot produce a fully branded proposal PDF during the demo will not do it in production either.