Solar Dealer Network Management Software for India (2026)

Somewhere in Rajkot, a solar EPC dealer has three site surveys pending in WhatsApp, a subsidy application that missed its DISCOM deadline, and an installer who showed up to the wrong address because the job sheet was a voice note. The dealer is not incompetent. He onboarded six months ago when PM Surya Ghar went live, hired two surveyors, and is trying to run a project-based field operation the same way his distributor cousin runs an FMCG beat — which doesn't work, because these are not the same thing.

That mismatch is where rooftop solar businesses are leaking margin, losing subsidy entitlements, and quietly burning customer trust. The pipeline from first enquiry to DISCOM-connected, subsidy-disbursed installation is eight to fourteen steps long, involves three or four different field roles, and produces documents that have a hard expiry. Managing it on spreadsheets and WhatsApp groups is not a bandwidth problem. It is a structural problem.

Why solar dealer ops look like real-estate, not FMCG

The instinct for most channel partner CRM deployments in India is to pick an FMCG-style order-capture tool — beat plan, outlet visit, invoice. That model works when the unit of work is a repeatable call to a known location. Solar EPC doesn't work that way.

Each residential or MSME rooftop customer is a one-time project with a unique site. The surveyor visits once to assess roof area, shadow patterns, structural load-bearing capacity, and existing wiring. The output is not an order — it is a site report that gates everything downstream: panel sizing, inverter selection, installation scheduling, net-metering application, and finally the subsidy claim to the National Portal for Rooftop Solar. If the site report is wrong or missing a field, the DISCOM rejects the net-metering application. The rejection notice arrives four to six weeks later and there is no easy undo.

This is closer to how a real-estate developer manages site inspections than how an FMCG RSM manages outlet calls. The workflow is linear, document-heavy, and deadline-sensitive. Any software that doesn't reflect that structure will be abandoned by field teams within three months — not because field teams are resistant to technology, but because the tool doesn't match the actual job.

The eight steps that need a system

The survey-to-installation pipeline for a typical PM Surya Ghar residential project runs roughly like this: lead capture → site survey scheduling → survey execution and report upload → technical design and proposal → customer sign-off → DISCOM net-metering application → installation scheduling → commissioning and subsidy claim submission.

Most dealers manage steps one and two adequately — WhatsApp enquiries land somewhere, surveyors get called. Steps three through eight is where things fall apart. Survey reports live in phone galleries. Proposals are PDFs in email threads. DISCOM application status is tracked by calling the utility office. Installer schedules are managed by the installation supervisor's personal judgment about who is free.

The consequence is predictable. A dealer with thirty active projects in different pipeline stages genuinely cannot tell you — without making four phone calls — how many are stuck at net-metering application, how many have a commissioning date, and how many have subsidy claims stuck past the official 30-working-day disbursement benchmark. That opacity is not a sign of a bad business. It is the natural result of running a project-based operation without project-based software.

The counterintuitive case against standalone solar CRMs

Here is where the advice gets slightly uncomfortable: the Indian market now has several tools marketed specifically as solar CRMs or solar installer tracking apps. Some are worth evaluating. Many of them solve the wrong problem elegantly — they make lead management and proposal generation look clean, and then leave the field execution layer entirely to WhatsApp.

The field execution layer is where the money goes. A surveyor who logs four visits in a day but only completes two proper site reports creates a backlog that is invisible until the proposal stage collapses. An installer who marks a job complete before the inverter is commissioned creates a subsidy claim problem that surfaces weeks later, once the DISCOM or the subsidy auditor cross-checks the commissioning record. These failures do not happen in the CRM's lead or proposal module. They happen in the field, between the first visit and the final photograph.

What the field execution layer needs is what good field force management software provides: geo-verified check-ins at the customer site, structured form capture for the survey report, photo upload with GPS tagging, and task assignment that the back office can monitor without calling anyone. The solar-specific vocabulary — shadow analysis checkbox, sanctioned load field, DISCOM jurisdiction dropdown — sits on top of that infrastructure. It does not replace the infrastructure.

A dealer who buys a beautiful solar CRM but has no field execution discipline will generate beautiful lead funnels and miss every DISCOM deadline. A dealer who has tight field execution can work with a generic tool and still operate a clean pipeline.

What good field execution looks like on a rooftop solar project

The survey stage is the highest-leverage point to get right. A structured survey form on a field force app should capture roof dimensions, shading obstructions, structural observations, existing meter details, consumer number, and at minimum four geo-tagged photographs — roof north, south, meter board, and access path. This takes twelve to fifteen minutes on-site and produces a record that the design team, the DISCOM application team, and eventually the subsidy auditor can all reference without calling the surveyor back.

With that record in the system, downstream scheduling becomes deterministic. The installation team knows the roof type before they load the truck. The net-metering application team has the consumer number and DISCOM jurisdiction without hunting for the surveyor's WhatsApp message. The subsidy claim team has the commissioning photograph already tagged to the correct project.

The numbers are not trivial. Under PM Surya Ghar, the Central Financial Assistance is ₹30,000/kW for the first 2kW plus ₹18,000 for the third kW, capped at ₹78,000 — so a 2kW system nets ₹60,000 and a 3kW-or-larger system nets the full ₹78,000. A rejected DISCOM application because of a missing field in the survey report can cost the customer that entire amount — and the dealer the customer relationship, the referral, and in some cases the recovery of installation cost if the customer ties payment to subsidy disbursement. Structured field capture pays for itself on the first claim it saves.

Managing a multi-dealer channel across Tier 2 and 3 markets

PM Surya Ghar's channel model is deliberately distributed. State nodal agencies and DISCOMs have empanelled thousands of vendors across smaller towns — Bhavnagar, Tumkur, Muzaffarpur, Gorakhpur — many of whom are electrical contractors or solar traders who have never run a structured field operation. The national EPC companies and larger regional players who manage these dealers as a channel face a different version of the same problem: visibility.

A renewable energy channel partner CRM for this layer needs to aggregate project status across fifty or a hundred dealer locations without requiring those dealers to adopt enterprise-grade software they cannot afford or support. The practical answer is a mobile-first, low-bandwidth app that the dealer's own surveyors and installers use in the field — and that rolls up project status to the managing company's dashboard automatically. Coverage here means field force tracking across geographies, not just in one city.

This is also where lead management becomes relevant at scale. A national solar brand running dealer-assisted sales in forty cities needs to know which dealer is converting inbound enquiries and which is letting them age past thirty days. That visibility does not require a complex CRM build. It requires lead assignment with timestamp, activity logging, and a pipeline stage that somebody updates when the status changes — preferably automatically from the field app, not by manual data entry at 6 PM.

Where Kinematic fits into this

Kinematic was built for field operations that don't fit the FMCG mould neatly — industries where the unit of work is a site visit with structured output rather than a repeatable outlet call. Solar EPC is one of those. The survey form, the installer job sheet, the geo-verified commissioning photo — these all run naturally on the same field force infrastructure that serves pharma MR teams and real-estate site visit workflows.

If you are managing a rooftop solar dealer network in India and your current answer to "how many projects are stuck at DISCOM application stage" is a phone call to your operations manager, it is worth looking at what structured field execution actually looks like. Or get in touch — we can walk through a survey-to-installation workflow on your actual project types, not a generic demo.

The subsidy money is real. Missing paperwork is expensive. The margin for pipeline opacity is smaller than most dealers think until the rejection letter arrives.