CRM Consultant, India

Mapping how an Indian business actually sells

Before discussing software, I draw the sales map. Indian companies rarely sell through one route, and each route leaves its information in a different place. A manufacturer might sell directly to a handful of large buyers, appoint distributors for each state, give dealers a scheme every quarter and still take inquiries from marketplace listings and its own website.

The questions I work through with your sales and accounts heads include:

• Who owns the end customer when a dealer or distributor sits in between, and does the business need visibility of secondary sales at all?
• Which inquiries are handled by inside sales over the phone, and which go to a field executive for a visit?
• How are government and PSU tenders tracked, and who watches submission and clarification dates?
• Which large accounts buy from several locations under different GSTINs, and how should those be grouped?
• Where do export inquiries go, and are they priced differently?

The answers become a channel map and an account structure: parent companies, branches, contacts and the partner or salesperson responsible for each. That structure matters more than any feature list. If a CRM is configured before it exists, dealers end up recorded as customers, branches as separate accounts and the same buyer appears several times under different spellings. Getting this right is the core of my CRM consulting approach, adapted here to Indian channel structures.

Designing pipelines, stages and lead routing

Once the channels are clear, I design pipelines that a sales review meeting can actually use. A project sale to an EPC contractor, a new dealer appointment and a repeat order from an existing distributor move through very different steps, so forcing them into one pipeline produces stages nobody believes. On the other hand, too many pipelines make management reporting difficult. I aim for the smallest number that reflects genuine differences.

Each stage is defined by something the buyer has done, such as sharing a drawing, approving a sample or issuing a purchase order, rather than by how hopeful the salesperson feels. For every stage I list the few fields that must be complete before the deal moves forward, and nothing more.

Routing gets the same care. Many Indian leads arrive with only a name and a mobile number, so the mobile number often becomes the main duplicate check. Rules then assign the inquiry by state, product line, customer type or preferred language, with an escalation path when nobody responds in the agreed time. Marketplace inquiries, IVR calls and web forms can all feed the same queue, provided the source is captured on arrival. That source field later lets you compare channels on closed revenue rather than on inquiry counts, which is where CRM work connects with lead generation.

WhatsApp, calls and consent under the DPDP Act

For many Indian buyers, WhatsApp is the main sales channel, not an extra one. That creates two problems a CRM design has to solve. First, conversations held on salespeople's personal numbers leave with them when they move on. Second, it becomes hard to show what a contact agreed to and when.

On the first point, I lay out the options and their trade-offs: a business messaging account connected to the CRM, shared team numbers, or a lighter rule that key conversations are summarized as activities on the deal. Each has different cost, setup and adoption implications, and the right choice depends on volume and how much the business relies on the channel.

On consent, India's Digital Personal Data Protection Act sets expectations for how personal data is collected, used and withdrawn, and the detailed rules have been rolling out in stages. The CRM design can support compliance by recording for each contact:

• the source and purpose for which the data was collected
• the notice shown and the consent given, where consent is the basis
• withdrawal requests and the date they were actioned
• who inside the business can view or export the record

I also ask each shortlisted vendor where data is stored and processed, because some buyers and group companies ask that question. Whether your process satisfies the Act is a judgment your lawyer makes; my part is making sure the CRM can store their decisions and enforce them.

From quotation to invoice: the handoff into the ERP or Tally

A CRM earns trust in the accounts department when won deals arrive complete. In India that handoff carries more detail than in many markets, because a sales order eventually becomes a tax invoice and, for many businesses, an e-invoice and e-way bill.

I design the handoff point by answering a short list of questions with sales and finance together:

• Is the quotation prepared in the CRM, in the ERP or in Tally, and which system holds the approved price list and dealer schemes?
• Who creates a new customer, and at what stage are the GSTIN, PAN, billing address and shipping addresses verified?
• Which system calculates GST on the quotation, so the figure the buyer sees matches the eventual invoice?
• What credit limit and overdue information should sales see before promising delivery?
• Which order, dispatch and payment statuses should flow back to the CRM?

My usual recommendation is that tax calculation and invoicing stay in the accounting or ERP system, with the CRM sending a clean order and receiving status updates. The tax treatment itself belongs with your chartered accountant. For the engineering of these links, including e-invoice and bank connections, see how I approach the work as a system integration consultant in India.

Choosing a CRM in India without vendor bias, and making it stick

Indian businesses have a wide choice of CRM products and implementers, and every demo looks good. I compare options against your written design rather than a generic checklist. Depending on the business, the shortlist might include Zoho CRM, Odoo CRM or ERPNext CRM where the ERP decision points that way, as well as HubSpot or Salesforce for teams with different needs. The country platform pages go deeper into each product; this page stays neutral.

Criteria that tend to decide the outcome in India include how the mobile app behaves on weak connections, licensing costs for large field teams, messaging integration, how easily the CRM connects to your accounting system, data location and whether a capable implementer is available for that product in your region.

Adoption is planned from the start. I keep mandatory fields to a minimum, give field executives a simple mobile view, and build the dashboards that management will use in its weekly review, so the meeting runs from the CRM instead of from a separate spreadsheet. After launch, I review usage and adjust what people are avoiding. The work is remote; for the wider picture see my India overview and ERP consultant page for India.