The onboarding bottleneck that automated itself away

Every new customer arrived with their own data, in their own format. Bringing them on meant an engineer sitting down and mapping that customer’s files into the company’s internal system — by hand, from scratch, every single time. It was slow, manual engineering work for every customer.

It was slow and error-prone, but the real cost was subtler: it put growth on a leash. The more customers the business won, the more engineering it burned just to onboard them. Success made the bottleneck worse.

What I built

As the platform’s technical lead, I drove the architecture and much of the build of an integration platform that automated the file-mapping. Instead of an engineer translating each new customer’s data by hand, the platform did the first pass itself — taking customer files in whatever shape they arrived and producing a mapping into the internal model that an engineer reviews instead of building from scratch.

Onboarding stopped being a from-scratch engineering project and became a review.

The result

The hand-mapping that had eaten engineering time on every customer became a review step, freeing the engineering team to build product instead of doing data translation by hand. The company projected the savings in the millions of dollars a year in onboarding time alone. And because onboarding no longer scaled with headcount, growth stopped being throttled by it.

Why this matters for a business like yours

Most businesses have a smaller version of this exact problem: data arriving in one shape that someone re-keys into another, over and over — invoices into the accounting system, orders into the CRM, spreadsheets into a database. That re-keying is usually the first thing worth automating. This was that same problem at fintech scale, but the principle is identical whether it’s customer files or the ones landing in your inbox this week.