Start here: you may not need a custom CRM
A small Coimbatore team losing leads in a WhatsApp group should set up a free CRM tier properly and spend the money elsewhere. HubSpot free or Zoho Bigin will do it, and saying so costs me a project I did not deserve. Read the free CRM comparison first if that describes you.
The businesses that genuinely need a custom CRM here have one of three things: a sales process a pipeline does not model, enquiries arriving in a format no CRM ingests, or an integration requirement - Tally, GST invoicing, an existing ERP - that is the actual point of the project rather than a nice-to-have.
Export enquiries do not fit a standard pipeline
A Coimbatore exporter selling pumps, castings, components or knitwear does not run a lead-to-close pipeline. An enquiry arrives from a buyer or an agent with a specification, sometimes a drawing, often in an email thread with six attachments. It becomes a sample, then a costing, then a revised costing after the buyer changes a tolerance, then a proforma invoice, then an order that ships in parts.
Standard CRMs collapse that into one deal record with a value and a close date, which loses exactly the information you need - which revision the buyer approved, which sample went out, what the costing assumed. Modelling enquiry, sample, costing revision and order as distinct linked records is the difference between a CRM the export desk uses and one it works around.
Dealer and distributor networks
Wet grinder, pump, appliance and auto-component businesses sell through dealers, and a dealer is not a lead. It is a recurring account with a credit limit, an order history, a territory, a price list that differs from retail, and a claim or scheme balance. Sales staff visiting dealers need the last three orders and the outstanding on their phone at the counter, not after they get back.
The CRM that works for this is closer to an order and account management system than to a sales pipeline. Route plans for field staff, visit logging with location, order capture on the spot, and outstanding visible to the person having the conversation. Where a generic CRM is used for this, the field team almost always ends up calling the office to ask what the dealer owes, which is the thing the software was bought to prevent.
Quotations, follow-up and the thing that actually loses deals
Most lost business in this market is not lost to a competitor price. It is lost to a quotation nobody followed up, because the person who sent it was busy and there was no system holding a next action with a date on it.
So the quotation record is the centre of the design: version history, what changed between revisions, who approved it, and an automatic follow-up task that exists whether or not anybody remembers. Tie that to the enquiry it came from and the order it becomes, and you can finally answer how many enquiries turn into quotes and how many quotes turn into orders - which is the number that tells you whether to hire another salesperson.
WhatsApp, because that is where the conversation is
For most Coimbatore businesses the customer conversation happens on WhatsApp, and a CRM that does not contain those messages contains half the story. Messages logged against the enquiry record automatically, quotations sent as PDFs from the system, order status replies handled without someone re-typing them, and payment reminders that go out on schedule.
The detail worth checking in any CRM, mine or a vendor, is whether messages attach to the record by themselves or whether somebody has to paste them in. The second one stops happening in week three.
Billing, GST and the handover to accounts
A CRM that stops at the order hands the accounts team a re-typing job. Quotation to proforma to invoice should carry the same line items through, with GST slabs and HSN codes correct at the first entry rather than corrected later, and the output should land in Tally without an intermediate spreadsheet.
Where an ERP already exists, the CRM should write to it rather than duplicate it. Two systems holding customer master data always diverge, and the divergence is discovered during an audit.
Frequently asked questions
Should we buy Zoho or build a custom CRM?
Buy if your sales process is a normal pipeline and your integrations are standard - Zoho and HubSpot are cheaper and faster than anything custom. Build when export enquiries, dealer accounts or Tally and GST integration are the actual requirement rather than an add-on.
Can the CRM handle export enquiries with drawings and samples?
Yes, and that is a common reason for the project. Enquiry, sample, costing revision and order are modelled as linked records rather than collapsed into one deal, so you retain which revision the buyer approved and what each costing assumed.
Can field staff see dealer outstanding on their phone?
Yes. Dealer account view with last orders, credit limit and outstanding, plus visit logging and on-the-spot order capture, built mobile-first for mid-range Android. That is usually the highest-value screen in the whole system.
Does WhatsApp integration log messages automatically?
With the WhatsApp Business API, yes - messages attach to the enquiry record without anyone pasting them. Worth checking in any CRM you evaluate, because manual logging quietly stops within a few weeks.
Will it connect to our existing ERP or Tally?
Yes. Where an ERP exists the CRM writes to it rather than keeping a second customer master, since two masters always diverge. Tally-compatible export is standard for the billing side.
How long does a custom CRM take to build?
A focused CRM covering enquiry, quotation and follow-up is typically four to six weeks. Dealer management, WhatsApp integration and billing add to that and are usually delivered as later stages that each go live.
Map your sales process
Tell me what you need and you get a written scope, a fixed quote and a delivery timeline before any work starts — no obligation.
Ananth N · Madurai, Tamil Nadu · serving Madurai, Coimbatore, Chennai and clients across India · remote-first.
Request a free CRM blueprint WhatsApp Email