Sales closes a new client. Everyone’s happy. The client is excited to get started, and the business wants to show it moves fast.
So operations jumps in. And within a day, the questions start. What exactly did we promise? Who’s the main contact? Who gets the invoices? What are the payment terms? Where are the files supposed to go? Who on our side owns this client?
Some of those answers are in the salesperson’s head. Some are in an email thread. Some don’t exist yet. Work has started anyway, and now everyone’s backfilling.
What the owner thinks
“Operations needs to be faster.” Or, from the other direction, “Sales needs to send better notes.” Both are trying to solve the symptom. The real problem is that nobody designed what has to be true before work starts.
Tracing the trip
Here’s what has to happen between “they said yes” and “work starts smoothly,” and where it usually breaks:
- Agreement signed. Scope, price and terms are set. Usually solid, but exclusions and assumptions often live only in conversation.
- Sales hands off to delivery. This is the biggest break. What was promised? Any special circumstances? Schedule commitments? Without a defined list, the handoff is whatever the salesperson remembers to mention.
- Billing gets set up. Billing contact, terms, rates, how invoices are delivered. Often discovered at the first invoice, when it’s late.
- Files and systems get created. Client folder, project in the tool, access for the client if there’s a portal. Often done ad hoc, by whoever gets to it.
- An owner is named. Who on our side is responsible for this client? Often assumed, rarely stated.
- Work starts. Ideally after 1 through 5. Usually somewhere in the middle of them.
What I’d investigate
I’d go to each team that touches a new client after the sale and ask one question: what do you need before you can do your part well?
Delivery will say scope, promises, contacts, timeline. Billing will say contact, terms, rates, delivery method. Whoever sets up files and systems will say naming, access, who needs to be invited.
Then I’d look at the last few new clients and see when each of those things actually arrived. The gap between “needed” and “arrived” is the problem.
What’s underneath it
Intake was designed from the front. The sales process collects what sales needs to close. Nobody worked backward from what the people after the sale need to start.
What I’d change
- List every downstream need. One combined list, from delivery, billing and admin.
- Build intake backward from it. Some of it comes from the client, through one form, not ten emails. Some comes from sales, through a short required handoff.
- Create a “ready to start” check. Before work begins, the list is complete. Contacts, terms, scope, promises, files, owner.
- Name the owner at handoff. One person on your side owns the client from here.
If you need the same ten pieces of information every time, stop collecting them through ten emails.
What I’d leave alone
The sales conversation. I don’t want the salesperson filling out a long form in front of the client or slowing down a good close. The handoff can happen right after.
Watch the first invoice for each new client. If it’s late, wrong, or goes to the wrong person, that’s usually the clearest sign the intake missed something billing needed. It’s an easy, regular checkpoint for whether the backward design is working.
The tradeoff
A “ready to start” check can delay a start by a day or two while the last pieces come in. That can feel like losing momentum. In practice, starting with everything is usually faster than starting fast and stopping to chase.
The pattern
Client onboarding often feels like a delivery problem, but it usually starts in sales. The fix is designing intake from the end: what do the people after the sale need?
Try this: ask your delivery lead and your billing person to each list what they wish they had on day one of a new client. Compare it to what they actually get.
If the lists don’t match, that’s a good thing to work on in a Systems Fit Call.
