When a client goes quiet in the middle of a project

The stall is more common than the cancellation

A project that stops is rarely cancelled outright. It goes quiet: feedback that was due does not arrive, a decision is postponed, the material you were waiting for stays unsent, and the messages get shorter and then stop.

This is one of the more expensive situations in a small business, because it consumes the schedule without producing revenue. The slot is reserved, the work cannot proceed, and the invoice can’t be issued.

Why clients disappear

The most frequent reason is that something else became more urgent. A project that mattered in March competes in May with whatever crisis has arrived since, and yours is not the only thing on their desk.

Sometimes the decision has moved upwards, or a budget is being reviewed, or the person you deal with has been told to wait and finds that awkward to relay. Occasionally somebody has left and nobody has picked the project up. Now and then it is genuinely about the work — they are unhappy and are avoiding the conversation.

From your side these all look identical, which is why guessing is unproductive. The useful assumption is the most likely one, which is that they are busy and the project has slipped down the list rather than off it.

Make it easy to restart

The most effective message is short, contains no reproach, and gives them a single simple action. What you are waiting for, what happens once it arrives, and a question that can be answered in one line.

Long messages summarising the history make things worse. Somebody who is behind on responding does not want a document that requires twenty minutes; they want a question they can answer between meetings.

Offering a specific alternative also helps — proposing a date to resume, or a reduced first step, or asking whether it would be easier to pause formally until a particular month. People find it much easier to accept a proposal than to construct one.

Say what a delay does, before it becomes an issue

A stalled project has consequences you should name early rather than announce later. Your availability changes. Costs may have been incurred. Anything already delivered may need revisiting if too much time passes.

Raising this as information rather than as a threat is straightforward: that the slot reserved for them can be held until a date, after which the next available time is later. That’s true, it is reasonable, and it gives the client a concrete reason to respond, which the polite reminders had not.

This is much easier when the agreement said something about it at the outset — how long a pause can run, what happens to the price and the schedule afterwards. A sentence in the brief prevents most of this from becoming a negotiation.

Bill for what has been done

Where the work is staged, the stage that was completed should be invoiced, whatever is happening with the remainder. That is the protection those stages were built for, and not using it is how a stall turns into a bad debt.

Where nothing has been invoiced and substantial work has been delivered, raising the invoice for the completed portion is entirely legitimate and often restarts communication immediately. It isn’t an escalation. It is billing for work done, which is what the arrangement always said would happen.

Closing it properly when it does not restart

After a reasonable number of attempts over a reasonable period, a final message that closes the matter is better than an open file. Say that you assume the project is not proceeding at present, that anything outstanding remains payable, and that they are welcome to be in touch if circumstances change.

That sounds like giving up and it is actually the most productive version of the outcome. It releases the schedule, it prompts a reply from anybody who did still intend to proceed, and it leaves the relationship intact for the not-uncommon case where they return several months later with the project revived and the budget approved.

The scheduling lesson underneath all this is worth stating separately. A stalled project holds a slot that produces nothing, so the protection isn’t to leave the slot empty while waiting. Having something else that can move into the gap — a smaller job, work on your own business, a client further down the list — turns a client’s delay into an inconvenience rather than an unpaid fortnight. That is easier to arrange when the possibility of a stall was expected than when it arrives as a surprise.