Most B2B teams price a deal carefully and then improvise the onboarding. The hours go unlogged, the client's data arrives as four different Excel files, and the first invoice slips by a month. The people who feel it are ops and finance leads at Indian SMBs and mid-market firms, where the same two or three people handle sales, delivery and support.
What does a customer onboarding process for B2B services cost?
A typical Indian B2B deal spends roughly ₹40,000 to ₹3,00,000 of internal time on onboarding, which usually works out to 10-20% of the first-year contract value. A small rollout — under 10 users, no integration, one location — tends to take 30-50 person-hours. A mid-market rollout with data migration, one integration and training for 25-50 users typically runs 120-250 hours. At a blended internal cost of ₹800-1,200 an hour, mixing an implementation engineer, a project owner and some founder time, you land in the range above. If you have never measured this, the real number is almost always higher than the quote assumed.
Where the onboarding budget actually goes
Data migration and cleanup is usually the largest single line, ahead of configuration and training. For a 150-hour onboarding, a realistic split looks like this:
- Discovery, scoping and kickoff: 6-10 hours
- Data migration, deduplication and cleanup: 40-60 hours
- Configuration, custom fields and one integration: 20-40 hours
- Training across two or three sessions: 8-15 hours
- Project management, status calls and follow-ups: 15-25 hours
- Post-go-live support in the first 30 days: 10-20 hours
Project management alone is often a sixth of the total, and it is the line most likely to be missing from a proposal. Track it anyway — it is real salary being spent.
A worked example: a 40-user CRM rollout
A mid-market equipment manufacturer in Pune signs a ₹9.6 lakh annual contract for a CRM rollout across 40 users in three branches. The onboarding consumes about 180 person-hours: 10 on discovery, 55 on migrating and cleaning the customer master and open pipeline, 30 on configuration, 12 on four training sessions, 25 on project management, 18 on first-month support, and roughly 30 on internal review and rework. At a blended ₹1,000 an hour, that is ₹1,80,000 — about 19% of year one. Go-live then slips three weeks because the item master has duplicate SKUs, which pushes the first invoice out by roughly ₹80,000 and adds 20 hours of rework. Similar patterns show up across our case studies.
What pushes onboarding cost up or down
Three variables move the number more than anything else: data quality, the number of client-side approvers, and whether the client names one internal owner. Dirty master data can double the migration line. Every additional approver — procurement, IT, finance, the plant head — typically adds a week of calendar time and 5-8 hours of chasing. A single owner with authority to sign off cuts both. On the tooling side, configuration instead of custom code keeps effort predictable. When you control the stack end to end, as we do with our self-hosted CRM, you script the data import once and reuse it for every customer — that is where the savings compound.
How to cut onboarding cost without losing the client
Charge for implementation and write the number into the contract, because free and unlimited onboarding is exactly what makes the cost invisible. Common Indian SMB practice is a one-time implementation fee of ₹15,000-₹75,000 depending on scope, sometimes credited against year one to keep the deal warm. After that:
- Send a fixed data template on day one and do not start migration until it comes back filled
- Reuse one checklist and one scope document across every deal, and publish what is included and what is extra with the same discipline you apply to pricing
- Record the training session once and send the video instead of repeating it per batch
- Cap free support hours for the first 30 days and state the boundary in writing
Where to start
Pick one onboarding that closed last quarter and rebuild the hours from calendars and timesheets rather than memory. Compare that number to the contract value. If it is above 20%, you have a pricing or scoping problem before you have a delivery problem — fix the template and the fee first. That kind of scoping work is part of what we do at Maysan Labs, alongside the web platforms, dashboards and internal tools themselves, but the arithmetic above holds whether or not you ever talk to us.
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
Storefront we build and run ourselves
We needed a storefront we could sell and run, not only build: stock, orders, payments and customers in one place.
Written by Sanjay Mandal at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn