The customer has signed. Your team is pleased. Then the first week passes while everyone waits for information, access or an available person to begin the work.
From inside the business, the sale is complete and onboarding is underway. From the customer’s side, they have made a commitment and are still waiting to see it pay off.
If this happens repeatedly, adding more leads can increase the queue at the same weak point. Before pushing harder for new business, make the start of the relationship dependable.
Separate a signed customer from a ready customer
A signature does not necessarily mean delivery can begin. Imagine a small agency that can start two new customer projects each week.
For the agency, a customer is ready when the agreed files have arrived, one person on their side can approve the work and both sides know what the first piece of work is. The agency, in turn, is ready when the right team member is booked.
Keep those conditions to things that really block the first useful work. If the first piece of work depends on the customer’s files, it waits for them, but a detail needed for a later stage should not hold up the start. Both sides should be able to tell whether the start conditions have been met.
Sometimes a customer wants to begin before an essential input arrives. If a limited first step is useful and safe, explain what can happen now and what still depends on the missing information. A quick start built on guesses can create rework and end up slower than a clear, short wait.
Promise a start you can actually support
Now suppose the agency has a busy sales week. It signs six new customers, and each one hears that work will begin the following Monday.
The team may be capable of serving all six over time. The immediate problem is that it has promised three weeks of starts in one week. No improvement to the welcome email changes that arithmetic.
The agency has several honest options. It can offer different start dates, arrange additional qualified capacity or reduce the initial work to a scope it can deliver. The customer should understand which option they are buying before being left in a queue.
Whether to take on six at once is a capacity question to settle before anyone signs.
Sales and delivery need to share the same meaning of “start.” If a kickoff call only introduces the relationship and real work begins later, say so. A reassuring date loses value when each side reads it differently.
Identify the first useful result
An onboarding checklist can become a tour of the company: introductions, forms, credentials, instructions and another call. Some steps may be necessary, but the customer is waiting for something useful to happen.
Name that result. For the agency, it might be the first draft the customer can react to, not a kickoff call or a form that is easy to mark complete.
Work backward from it. Ask which information the draft needs, who has to act, which steps can wait and which customer decision could hold everything up.
This gives the team a reason to collect each input. It also makes the customer’s part easier to explain: “We need these files to start your first draft” is more useful than another unexplained form request.
Make waiting visible
A small readiness table shows why each start has not happened yet.
| Customer | Start agreed | What blocks the first result | Next action |
|---|---|---|---|
| Cedar | Tuesday | Nothing; inputs and capacity confirmed | Begin the agreed first task |
| Orchard | Thursday | Customer has not chosen a final approver | Ask for one named approver today |
| Harbor | Next Monday | Internal specialist slot is not confirmed | Confirm capacity before reaffirming the date |
A missing customer input and an internal capacity problem need different responses. Sending another reminder to Harbor would accomplish nothing if your own specialist is the constraint.
Give the customer one clear route to understand the next step. They should not have to contact three people to find out whether you are waiting on them or whether they are waiting on you.
Review the last five starts
For five recent customers, compare five dates: signing, the promised start, essential inputs ready, actual start and the first useful result. The promised and actual starts show whether you kept the start promise. The other gaps show whether the time went to waiting for inputs or to producing the first result.
Then identify the largest avoidable delay in each case. Do not aim to make every gap zero, because some services need careful preparation. The useful question is whether the waiting was necessary, explained and consistent with the promise made.
If slow starts keep recurring, fix the largest avoidable delay alongside your next sales push. That might mean clearer sales language, a smaller initial information request or a firmer limit on new starts each week. The aim is to win business on terms the team can deliver from the beginning.
