Digital transformation 5 min read
A digital transformation playbook for Indian SMEs moving off spreadsheets and WhatsApp
A phased, practical plan for a mid-sized Indian business moving from Excel and WhatsApp to an ERP: data clean-up, roles, rollout order and what to avoid.
Most mid-sized Indian businesses run on a combination that works surprisingly well until it suddenly does not: Excel for estimates and stock, Tally or a CA for accounts, and WhatsApp groups for everything else. Orders are confirmed in a chat, drawings are forwarded three times, approvals are a thumbs-up emoji, and the owner is the only person who knows the full picture.
The breaking point usually comes with growth. A second factory shift, a few more sites, a new sales team, a large customer who wants proper documentation. At that point the question is not whether to move to a system, but how to do it without disrupting the business that pays the bills.
This playbook sets out a phased approach that suits a business of a few dozen to a hundred or so people.
Be clear about why you are doing it
“Going digital” is not a goal. Write down the three or four problems you actually want to fix, in plain language. For example:
- We cannot see which orders are late until the customer calls.
- Quotations take too long and are priced on old rates.
- We do not know what is in stock without walking to the store.
- Retention and outstanding payments are tracked in someone’s notebook.
These become your measure of success. Every decision during the rollout can be tested against them.
Phase 0: choose a system that fits your work
A general-purpose system will need heavy configuration to fit a panel shop or a contractor. An industry system starts closer to how you work. When evaluating, look at:
- Does it follow your actual business flow, from enquiry to payment?
- Is it built for GST, INR and Indian document conventions?
- Can it import your existing data from Excel?
- Does it run in a browser on the phones and laptops you already have?
- Is the vendor clear about what it does not do?
Phase 1: clean the data before you move it
The most common reason ERP projects stall is bad data carried over from spreadsheets. Do this clean-up first, and do it with the people who use the data.
Customers and suppliers
- Remove duplicates (“ABC Pvt Ltd”, “A.B.C. Private Limited”, “ABC”).
- Verify GSTINs and state codes, because they drive the CGST/SGST or IGST split.
- Record billing and site addresses separately where they differ.
Products and items
- Agree one naming convention and stick to it.
- Fill in HSN codes and units of measure.
- Retire items nobody has bought or sold in years.
Prices and opening balances
- Collect current supplier price lists.
- Count stock physically, close to the go-live date.
- Agree opening receivables and payables with accounts.
A practical rule: if nobody can confirm a piece of data is correct, do not import it. Start that record fresh.
Phase 2: define roles before you create users
Decide who does what in the new system before anyone logs in. For each role, write down what they create, what they approve and what they only view.
| Role | Creates | Approves | Views |
|---|---|---|---|
| Sales | Leads, quotations | — | Customers, stock availability |
| Purchase | Requisitions, POs | — | Vendors, price lists |
| Stores | GRNs, issues | — | Stock |
| Manager or owner | — | POs above a value, quotations | Everything |
| Accounts | Invoices, payments | — | Financial reports |
Separating “creates” from “approves” is the single most valuable control you will add. It replaces the thumbs-up in the WhatsApp group with an approval that is recorded.
Also decide who should not see financial figures. Site and shop-floor staff often need operational screens without margins and costs.
Phase 3: roll out in the order money flows
Do not switch everything on at once. A sensible order is:
- Sales and quotations. Quick wins, visible to customers and easy for the team to see the benefit.
- Purchase and stores. Requisitions, POs and GRNs. Insist that stock enters only through a GRN from day one of this phase.
- Operations. Production work orders and QC for manufacturers; daily progress reports, labour and plant for contractors.
- Billing and payments. GST invoices, receipts and payment links.
- Reports and AI. Once the records are reliable, dashboards, briefings and agents become trustworthy.
Run each phase for a few weeks before starting the next. Keep the old method available as a fallback during the first phase only, and then retire it deliberately.
Phase 4: move conversations, not just data
WhatsApp will not disappear, and it should not. Customers and suppliers use it. The aim is that WhatsApp becomes a delivery channel for documents that live in the system, rather than the place the documents live.
- Send quotations, POs and invoices from the system so there is a record of what was sent.
- Keep approvals in the system, not in chat groups.
- Attach drawings and supplier documents to the relevant lead, order or project.
Change management that actually works
- Name an owner for the rollout, with time set aside for it.
- Train by role, using your own data, not generic demos.
- Pick champions in each team who learn first and help others.
- Fix small annoyances quickly. Early frustration spreads faster than early wins.
- Hold a short weekly review during rollout to check against the problems you wrote down at the start.
Mistakes to avoid
- Importing every old record “just in case”.
- Customising heavily before you have used the standard flow.
- Leaving approvals optional.
- Turning on AI agents before the masters they depend on are clean.
- Running the old and new systems in parallel indefinitely.
Where Zaptiz fits
Zaptiz has two industry products built for this kind of move. Zaptiz Electrical has a guided onboarding wizard, CSV import of customers with duplicate merge, supplier price list import from PDF, Excel or a photo, six job roles, email user invitations and module switches per company so you can turn workflows on in phases. Zaptiz Construction walks you through company, tax and finance settings, imports BOQs from Excel with saved column mappings, and has nine company roles, project-team access, maker-checker rules and per-member control over financial visibility.
Both run in a browser on computers, tablets and phones, send documents by email and through your own WhatsApp Business number, and can push records to Zoho Books. See the features page for detail, the FAQ for common questions, or book a demo to plan your rollout with us.
Keep reading
Business automation 5 min read
Automating procure-to-pay: requisition to PO to GRN to 3-way match
A practical guide to the procure-to-pay chain for Indian manufacturers and contractors: requisitions, approved POs, goods receipt and 3-way invoice matching.
CRM 4 min read
CRM follow-up discipline for B2B manufacturers and contractors
Most B2B deals are lost to silence, not to price. How pipelines, a next step on every deal and daily follow-up lists keep manufacturers and contractors winning.
AI 5 min read
AI agents that draft, people who decide: practical, safe AI in business software
What AI agents in an ERP should and should not do, why drafts beat automation for business records, and the safeguards to look for before you switch one on.