The 0→1 Craft

When Enterprise Onboarding Becomes An Unintended Consulting Gig

MR
Mrinal Rai
5 min read

The Invisible Trap of Customer Success

In the early days at Intugine, we convinced ourselves that manual onboarding was simply 'being helpful.' We spent hours cleaning client CSVs, mapping their erratic logistics data, and manually configuring API webhooks for them. We called it 'white-glove service.' The reality was that we were building an expensive, low-margin consultancy practice hidden inside a SaaS company.

You start with a pilot. You tell yourself, 'Just this once, we will build this custom module for this Tier-1 logistics firm, and then we will productize it.' But the product team doesn't build it for the roadmap; they build it to patch a hole in the current deployment. Two years later, you have fifteen bespoke versions of your software, and your support team has doubled in size just to manage the technical debt of your 'onboarding.'

Identifying Necessary Pilot Friction

There is a fine line between necessary pilot friction and operational debt. Necessary friction occurs when you need to understand the client's data structure to refine your product's core intelligence. If you are manually onboarding because your product doesn't yet know how to ingest messy ERP data, that is valid R&D. You are building a smarter parser.

However, if you are doing it because the client simply doesn't want to follow your standardized input processes, that is a red flag. If the 'friction' is moving from the client's plate to your engineering team's plate, you have failed the product test.

If your engineering team knows the customer's proprietary workflow better than the customer's own project manager, you are not a SaaS company anymore.

The Three-Step Audit for Onboarding

Before you commit to another custom deployment, run these three checks. If you fail any of them, stop.

  • The Repetition Metric: Is this specific request something we can automate for the next five customers? If the answer is no, it is a bespoke service, not a feature.
  • The Cost of Maintenance: Will this code require a dedicated developer to update whenever we change our core backend architecture? If yes, it is an anchor, not an engine.
  • The Margin Threshold: If we strip out the hours spent on this 'manual onboarding,' does the ARR still justify the infrastructure costs?

When to Say No

Learning to say no to enterprise clients in the Indian market is particularly difficult. We have a culture of saying 'yes' to build relationships. But true enterprise scale is not built on being a developer-for-hire. It is built on the opinionated structure you impose on the market. If you cannot get the client to adapt to the logic of your platform, you aren't leading the market; you are being led by the client's inefficiencies.

Ultimately, a successful product scales when you stop solving problems with people and start solving them with code. If your onboarding process is still a human-in-the-loop operation after twelve months, you don't have a product-market fit—you have a service-market fit, and that is a much harder business to exit.

b2b-saasproduct-managemententrepreneurshipscalingscheduled30
Join the Chronicle
Get essays, reflections, and builder wisdom — delivered rarely, crafted carefully.
Continue Reading