A construction company with a four-billion-euro annual turnover signed up for BauGPT last quarter. Their procurement process took eleven weeks. The actual onboarding took ninety minutes.
I want to sit with that asymmetry for a second, because I think it says something important about how B2B software has been built for the last decade.
The 90 minutes
Here is what happens in those ninety minutes, broken down:
15 minutes: IT connects SSO. One call, one configuration, done. We do not ask them to maintain a user list or provision accounts manually. They point their identity provider at us, we trust it.
5 minutes: They tell us where their documents live. A SharePoint folder. A network drive. A handful of PDFs their specs team uploaded last year. We start indexing in the background. This part takes thirty-six hours on our end. On their end, it takes five minutes.
10 minutes: They give us a list of twelve project managers for the pilot. Names, email addresses. Nothing else.
45 minutes: We answer three real questions. Questions they actually have, from projects they are actually running. Not demo questions we prepared. Not "ask me about DIN 18195." Their questions. We answer them live, with citations from their documents, and we let them verify the citations themselves.
15 minutes: Admin dashboard handover. Two screens. One shows who is using the system. One lets them remove a user. That is the entire admin surface.
The COO told us afterward: "If this had needed a workshop or a six-week rollout, we would have lost it in an internal review."
What we removed to get here
The ninety minutes did not happen by accident. It happened because we made a series of decisions that felt wrong at the time.
We stopped letting customers customize the system prompt. Every enterprise customer wants to customize the system prompt. They have a procurement checklist, and "configurable AI behavior" is on it. We said no. Their wins come from their indexed documents, not from prompt engineering. When we let them tune the prompt, they spent weeks on it and the answers got worse. We removed the option.
We stripped the admin dashboard. The first version had eighteen tabs. Analytics, user management, billing, document management, feedback review, integration settings, API keys, audit logs. All of it. We cut it down to two screens because every additional tab is a question during onboarding and a support ticket six months later.
We always demo on their actual documents. This is the one that makes the sales team nervous. If their documents are messy, if the specs are outdated, if nothing is properly named, we see it in minute sixty. They see us see it. It is uncomfortable. It is also when trust actually gets built, because they realize we are not showing them a controlled demo. We are showing them the real thing.
The German enterprise procurement paradox
Eleven weeks is not slow by German enterprise standards. It is approximately normal. There are legal reviews, IT security assessments, data processing agreements, internal budget approvals, reference calls, and a final sign-off that requires a specific title in the org chart. None of this is irrational. German enterprises run on process because process is what lets them operate at scale without constant surprises.
We cannot change any of that. We have no leverage over procurement timelines.
What we can change is everything that comes after the signature.
Most B2B SaaS treats onboarding as an opportunity to demonstrate depth. Long implementation projects signal enterprise-grade software. A dedicated customer success manager makes the customer feel important. A data migration phase means they are fully committed.
The construction industry does not have appetite for implementations. They have appetite for tools that work on Tuesday.
The question worth asking
The gap between "signed contract" and "first real answer" is a choice. In most products, it is a long one. It does not have to be.
The question is not "how long does onboarding take?" The question is: what are you making the customer do during that time, and is any of it actually for them?
In our case, the SSO connection is for them. The document indexing is for them. The pilot user list is for them. The live demo on their documents is for them.
The custom system prompt configuration, the multi-tab admin dashboard, the implementation workshop: those were for us. They made the product feel comprehensive. They made us feel like a serious enterprise vendor.
We got rid of them. Onboarding got ninety minutes faster.
What in your onboarding exists because it makes you feel like a real company, rather than because it helps the customer get to their first real answer?