When a Client Wants to Pause the Project Mid-Build
- A client asking to pause is not cancelling, and it is usually not about you. Budgets get frozen, a key person goes on leave, priorities shift. Your job is to make the pause easy to say yes to and easy to come back from, without carrying the cost of it yourself.
- Use the Profit Room's Clean Pause method: invoice the work done to date, leave the build in a documented, working state, write a one-page pause note covering what is done, what is next, and what restarts the project, and agree a check-in date.
- Release your calendar during the pause. Restarting means rebooking into your next open slot, and a long pause is a reason to re-confirm scope and price before work resumes.
The Short Answer
When a client wants to pause the project mid-build, agree to the pause and make it clean. Send an invoice for the work completed so far, get the build into a stable state with notes on where everything is, write down what has to happen for the project to restart, and set a date to check in. Then stop holding time for them. A pause handled this way protects your income, keeps the relationship warm, and makes the restart quick.
That is the Clean Pause method. It works because a pause has two risks. For you, it is unpaid work and a calendar gap you did not plan for. For the client, it is coming back in two months to a half-finished build nobody can explain. A clean pause removes both. It is also the opposite of a cancellation, which is covered in [when a client cancels a Claude Code project mid-build](/blog/client-cancels-a-claude-code-project-mid-build). Treat the two differently: a pause assumes you are coming back.
Why Clients Pause Projects
Before you react, find out what is behind the request. 'Can we put this on hold?' usually means one of four things, and each one changes what you say next.
- Money. A budget was frozen or a payment from their own customer is late. Ask whether they can pay for the work already done. If they cannot, that is a payment problem, not a pause, and [handling a client who pays late](/blog/how-to-handle-a-client-who-pays-late) applies.
- People. The person approving the work is leaving, on leave, or swamped. If the contact is leaving for good, [when your client contact leaves mid-project](/blog/client-contact-leaves-mid-project) covers how to find the new owner.
- Priorities. Something more urgent landed on their desk. The project still matters, just not this month.
- Doubt. They are not sure the build is right anymore. This one is worth a direct conversation, because a pause that is really doubt often turns into a quiet cancellation.
Ask one question first: 'What would need to be true for us to pick this back up?' The answer tells you which of the four you are dealing with, and it becomes the restart condition in your pause note. If they cannot answer at all, treat the pause as likely to be long, and plan your calendar that way.
Run the Clean Pause
Work through these in order. Most of it fits in one call and one email.
- Invoice the work done. Bill for completed milestones and any work in progress up to the pause date, using the terms in your contract. If you were paid by milestone, this is where [structuring client payments in milestones](/blog/structure-client-payments-milestones) pays off, because there is a clear line to bill against.
- Get the build to a stable point. Finish or roll back the change you are in the middle of, so nothing is left half-done. Make sure the code is saved in the client's repository or wherever your contract says it lives.
- Write the pause note. One page: what is finished, what is half-built, what the next three steps are, which accounts and keys the build uses, and any costs still running, like hosting or subscriptions. In the Claude Code desktop app you can ask Claude to read the project and draft a summary of the current state, then check and edit it yourself before you send it.
- Stop or hand over running costs. Anything billed to you on the client's behalf gets switched to their account or turned off with their okay, so you are not paying for a paused project.
- Agree the restart terms. A check-in date, what restarts the work, how much notice you need, and what happens to price and scope if the pause runs long. Put it in the email.
| Item | What to do | Why it matters |
|---|---|---|
| Work done so far | Invoice up to the pause date | You are not funding their pause |
| The build itself | Stable state, saved where the contract says | Anyone can pick it up later |
| Pause note | Done, half-done, next steps, accounts used | The restart takes days, not weeks |
| Running costs | Move to the client or switch off | No surprise bills on either side |
| Your calendar | Release the held time | You can book other work |
| Restart terms | Check-in date, notice period, re-scope rule | No argument when they come back |
Clean Pause: what to settle before you stop
What to Say
Notice what the message does. It opens with yes, so the client does not feel they have to argue for the pause. It settles money in the same breath, as a normal step rather than a demand. It promises something useful to them, the pause note, and it sets a check-in date so the project does not quietly drift away. The notice period is stated calmly, which tells them your time will go to other clients in the meantime without making it a threat.
If the pause is really doubt, say so gently: 'Before we pause, is there anything about the build itself you are unsure about? I would rather hear it now than in two months.' Sometimes the honest answer is a smaller scope, and a [change order](/blog/change-order-template-for-a-claude-code-project) keeps the project alive instead of on hold.
When the Pause Gets Long
Keep the check-in short and friendly: one email on the agreed date asking whether anything has changed. If the pause keeps rolling, say plainly that after a set point you will treat the project as closed, hand over the pause note and the code, and quote fresh if they come back. That is not a punishment. Requirements, tools, and your rates all move over months, and a new quote protects both sides from building against a plan that no longer fits. [Offboarding a client](/blog/how-to-offboard-a-claude-code-client) covers how to close it out cleanly.
To make future pauses painless, put a pause clause in your [scope of work](/blog/scope-of-work-that-prevents-scope-creep): work done is billed at the pause date, restarts need notice, and a pause beyond an agreed length means re-scoping. Mention it in your [expectations conversation](/blog/set-client-expectations-before-a-claude-code-build) so nobody is surprised when it applies.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
Should I agree when a client wants to pause the project?
Usually yes. Agree to the pause, invoice the work done so far, leave the build in a stable, documented state, and agree a check-in date and restart terms in writing.
Should the client pay for work done before the pause?
Yes. Bill for completed milestones and work in progress up to the pause date under your contract terms. A pause is not a reason for you to carry unpaid work.
Do I have to hold my schedule open during a pause?
No. Release the time and book other work. When the client is ready, they restart in your next open slot after the notice period you agreed.
What should a pause note include?
What is finished, what is half-built, the next few steps, which accounts and keys the build uses, and any costs still running. It should let anyone pick the project back up quickly.
What if the pause turns into months?
Check in on the agreed dates. Past a set point, close the project, hand over the code and the pause note, and quote fresh if the client comes back, since scope and prices may have changed.
Last reviewed November 12, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →
