Most Indian B2B companies still onboard a new customer through an email thread, a shared spreadsheet, and one ops person's memory. The cost never appears on an invoice — it shows up as a three-week gap before the first invoice, a KYC document that arrives twice and a signed contract that arrives not at all. If you are weighing up customer onboarding automation, the decision gets easier once you put a rupee figure on the current mess.
What does customer onboarding automation actually cost?
For a typical Indian SMB signing 20–60 new B2B customers a month, plan for ₹1.5 lakh to ₹6 lakh in year one, with roughly 60% of that being one-time build and 40% tools plus running costs. A workflow-only setup that stitches your existing CRM to email, WhatsApp and a document folder usually lands between ₹40,000 and ₹1.2 lakh. A customer-facing portal with document upload, eSign and status tracking starts around ₹3 lakh and climbs with every integration. Most teams in that 20–60 band end up near ₹2–3.5 lakh. Budget another 10–15% of build cost each year for changes; the services page lists what a build of this size usually covers.
Where the budget goes: tools, build, and people
No single line item is frightening on its own — the bill is dominated by the build and by whoever owns the thing after launch. A realistic annual tool stack for 40 onboardings a month looks like this:
- Workflow layer: Zoho Flow ₹1,500–₹6,000/month, Make ₹900–₹4,000/month, or self-hosted n8n on a ₹1,000/month VPS if someone on your team can maintain it.
- CRM: existing Zoho or HubSpot seats, or a self-hosted CRM where the real cost is the server and the maintenance hours.
- WhatsApp Business API: roughly ₹0.10–₹0.80 per message depending on category, plus a provider platform fee of ₹2,000–₹10,000/month.
- Email: a transactional sender at a few hundred rupees a month at this volume, cheaper again if you already run one in-house.
- Verification and signature: GSTIN and KYC checks at ₹3–₹15 per call, eSign at ₹15–₹60 per document.
- Build: the largest line, and the one that varies most.
A worked example at 40 new clients a month
A B2B services firm onboarding 40 clients a month typically burns about 3.2 hours of ops time per client, which is roughly ₹4.6 lakh a year. That 3.2 hours is kickoff notes, contract back-and-forth, document collection, account setup, the welcome email and CRM hygiene. Forty clients at 3.2 hours is 128 hours a month; at a loaded cost of ₹300 an hour that is ₹38,400 a month, or ₹4.6 lakh a year. Automation usually takes the per-client time to about 1.1 hours, because only exceptions need a human. That saves ₹25,000 a month. Build at ₹2.2 lakh plus ₹2,400 a month in tools is ₹2.49 lakh in year one — payback in under ten months, before you count the faster first invoice.
Which costs are worth paying, and which you can skip
Spend on anything that removes a handoff between sales and delivery; skip anything that only looks good in a demo. Worth paying for early: a CRM record created automatically from the signed scope, document collection with automated reminders, self-serve kickoff scheduling, and one status view the customer can check without emailing you. Not worth paying for at 40 clients a month: an AI chatbot on the onboarding page, a fully bespoke customer portal, or a custom eSign integration when a ₹20-per-document vendor already works. The test is frequency — automate the step you repeat forty times a month, not the one you handle twice a quarter. Anything below ten onboardings a month should be a checklist and a ₹15,000 template, not a project.
How long before it pays for itself?
Most SMB onboarding automation pays back in 8–15 months, and it moves faster as average contract value rises. The three variables are volume, loaded hourly cost, and how much rework you quietly absorb today — the third is usually the biggest and the least measured. Below 100 clients a year, the honest answer is often "don't build, buy templates". Above 100, a proper portal starts to make sense, and the savings that never reach the spreadsheet are the useful ones: first invoices going out days earlier, fewer missing documents at GST filing time, and consent captured once and logged properly under the DPDP Act. A few of these builds are written up in the case studies.
Where to start
Start with a two-week audit of a single onboarding, timed in 15-minute blocks, before you talk to any vendor or sign up for a tool. You will usually find two steps eating most of the time — document collection and account setup are the usual culprits — and one of them can often be fixed with a form, a reminder sequence and a webhook. Automate that one step, measure for a month, and only then decide whether a portal is worth building. If you would rather have someone run the audit and the build together, Maysan Labs does exactly this for Indian B2B teams — but time the process yourself first; the numbers will make the conversation much shorter.
Buying software or a website?
Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.
Get the free checklistRelated case study
Full-Stack Ecommerce Platform
Needed a complete ecommerce platform built from scratch with inventory, orders, payments, and customer management.
Written by Sanjay Mandal at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn