Back to Insights

You won the client. Now you are chasing them

TL;DR

  • The hardest part is not winning the client. It is getting the details you need to start.

  • Logos, prices, photos, and approvals arrive in bits, across chats, over weeks.

  • While you wait, the job sits idle, and the client starts wondering why nothing is moving.

  • The fix is a short checklist, sent on day one, with one place to send everything.

  • If the checklist is not complete, the start date moves. That rule protects both sides.

You celebrate the yes. Then Monday comes, and the work does not start. Not because you are lazy, and not because the client changed their mind. Because you need six things from the client, and you have one of them. The logo is in an old chat. The price list is a photo of a notebook page. The approval for the draft is still pending, because the person who must approve it has not seen your message.

So you chase. You send a polite reminder on Tuesday. You send another on Thursday, a little less polite. The client replies with two of the six items, and promises the rest soon. Soon stretches to next week. Meanwhile your team has nothing to build, your calendar has a hole in it, and the client, who was excited last week, starts to feel that your firm is slow.

This is the quiet gap after the win that won the client, then chaos began describes from the other side. There, the job starts in chaos. Here, the job never starts at all. Both cost you the same thing: the energy of the yes, spent on chasing instead of building.

Why does work stall after the client says yes?

Because "yes" is not the same as "ready".

Signing means the client trusts you enough to start. It does not mean they have gathered what you need. Most small business clients have never been asked for a clean handover before. They run their business the same way you do, from memory, chat, and a spreadsheet that only they understand. When you ask for the details, you are asking them to do a job they did not expect, in the middle of their own busy week.

So the details arrive the way their business runs: in bits. One item by voice note. One item forwarded from a staff member. One item promised for tomorrow. Nobody is trying to slow you down. The client simply has no single place where all of it already sits, ready to send.

That is also why the brief changed in chat keeps happening. When details live in chat, every new message can quietly change the job. A start that depends on chat will always be a start that depends on the last message sent, not on a complete picture.

Why does chasing details eat the founder's week?

Because chasing looks like follow-up, but it is really project management without a project.

Each chase is small. A message here, a call there, a search through old chats to check whether the client already sent the price list last month. Added up, it is hours of work that produces nothing the client can see. The client sees no design, no draft, no progress. They only see reminders. You look nagging. They feel nagged. The relationship starts with friction, before any real work exists.

The research backs the shape of this, even if the numbers come from larger firms. An analysis of more than 16,000 onboarding tasks at marketing agencies found 85.2 percent of the tasks were assigned to the client, not the agency, which means the timeline stalls until the client acts. Read the client onboarding statistics. A separate onboarding benchmark report puts the median completion time for top firms at 4.8 days, against 12.3 days for middle firms and 23.7 days for the weakest, with the weakest relying on scattered email and manual chasing. Read the client onboarding benchmarks.

Your firm is smaller than those surveyed, but the pattern matches what you live every week. When the client holds most of the inputs, and there is no checklist and no single place to send them, the start date is not a date. It is a hope.

Why do clients go quiet after signing?

Because nobody told them exactly what to do next, or by when.

Put yourself in the client's chair for a minute. They signed, they paid the advance, and then they got a long message asking for ten things, with no order, no deadline, and no sense of what blocks what. They mean to reply. Then their own work takes over. Your message sinks. A week later your reminder arrives, and now replying feels like admitting they dropped the ball. So they put it off again.

Silence after signing is rarely a lost client. It is usually a confused one. The client does not know which item matters first, so they wait until they can send everything at once. Everything at once never comes, so nothing comes.

This is close to the enquiry that never got a reply, except the roles are reversed. There, you were the one who did not reply. Here, the client is. The cause is the same: no clear next step, owned by one person, with a date on it.

What does a clean start actually look like?

It looks like a short checklist, sent the same day as the yes, with one place to send it all.

Keep the list short. Five to eight items, no more. Each item in plain words: the logo file, the price list, three photos, the name of the person who approves drafts, the date the client wants to launch. Put a tick box next to each one. Tell the client which three items block the start, and which ones can follow later. Give one date for the first three, and say plainly: work starts when those three arrive.

| What you ask for | Why it blocks the start | What to accept |

| Logo and brand details | Without them, no design can begin | The original file, not a screenshot from a chat |

| Price list or service list | Without it, every page is a guess | One document, even a photo of a clean list |

| Photos of the work or shop | Without them, the site looks empty | Phone photos are fine, if they are clear |

| The approver's name | Without it, drafts wait for nobody in particular | One named person, not "the team" |

| The launch date the client wants | Without it, there is no schedule to protect | One date, agreed in writing |

Notice what the checklist does. It moves the work out of chat and into one list that both sides can see. The client can see what is left. You can see what is left. Nobody has to search old messages to find out whether the logo already arrived. And when the client sends an item, you tick it off in front of them, so progress is visible even before the build starts.

The second rule matters as much as the first: if the blocking items are not in by the date, the start date moves, and you say so on day one. This is not a threat. It is honesty. A start date that moves quietly, without anyone saying so, turns into clients keep asking for updates. A start date that moves openly, with the reason named, keeps trust intact.

How do you start this on your next win?

Do it before the celebration fades, while the client is still excited.

First, write your standard checklist once, and reuse it for every client. Do not write a fresh list for each job, because a fresh list is where items get forgotten. Second, send it within hours of the yes, not next week, with the three blocking items marked and one date on them. Third, keep one rule for yourself: no chasing in chat. When an item arrives, tick it off on the list and reply on the list, so the list stays the single truth. When an item is late, send one reminder that names exactly what is missing and what it blocks, not a general "please send the details".

Then watch what changes. The client stops feeling nagged, because they can see the list shrinking. Your team stops waiting in the dark, because they can see when the start is real. And you stop spending your week on polite reminders, because the list does the reminding for you.

That also fixes a quieter problem. When you answer the same question ten times, it is because answers live only in your head. When a job stalls waiting for details, it is because inputs live only in the client's head. Both are the same disease: the business runs on memory, not on a list anyone can see. Write the list, and the business starts to run on paper instead.

And once jobs start on time, the next leak becomes visible: work that starts clean but drifts, because nobody owns the follow-up. One leak at a time, in the order the money actually flows. First get the details in. Then get the job done. Then get paid without chasing that too.

Frequently Asked Questions

My clients are busy people. Won't a checklist feel pushy?

No, if it is short and it helps them. A checklist tells a busy client exactly what to do, in what order, instead of leaving them to guess. Pushy is ten scattered messages asking for ten things. A single list with three blocking items is the opposite: it respects their time by asking once, clearly.

What if the client sends half the items and goes quiet?

Work with what blocks the start, and say so. If the three blocking items are in, start. If they are not, send one reminder naming the missing items and the new start date. Do not start half a job and fill the gaps from memory, because that is how wrong prices and wrong photos end up live.

Should I refuse to start until everything arrives?

No. Refusing to start until everything arrives is as bad as starting with nothing. Start when the blocking items arrive, and let the rest follow. The rule is about the items that block real work, not about a perfect file. Perfect is the enemy of started.

My work is custom each time. Can one checklist fit every client?

Yes, if the checklist covers the inputs every job needs, not the job itself. Logo, prices, photos, approver, launch date: those five show up in almost every job. Add two job-specific items at the bottom. A standard spine with a custom tail beats a fresh list every time.

Does this mean I need new software to collect client details?

No. A document, a form, or a single page your client can open all work. Software helps only after the habit exists. Start with the list, sent the same day as the yes. Buy the tool later, if the list outgrows it.