When a Client Sets an Unrealistic Deadline (How to Say What Is Possible Without Losing the Project)
- An unrealistic deadline is usually a real need with the wrong plan attached. Something is happening on that date - a launch, an event, a board meeting - and the client has assumed everything must be done by then. Find out what the date is actually for before you answer.
- Use the Profit Room's Three Levers method: a build has three levers - scope, time, and price. If the date is fixed, offer a smaller first version that hits the date. If the scope is fixed, offer a realistic date. If both are fixed, the only lever left is a rush price for clearing your calendar, and only if you can truly deliver.
- Say no to the impossible version early and in writing. A yes you cannot keep turns into a missed deadline, a rushed build, and an unhappy client. A clear 'here is what we can do by then' keeps the project and your reputation.
The Short Answer
When a client sets an unrealistic deadline, do not agree on the spot and do not just say no. Ask what is happening on that date, then come back with options: what you can deliver by the date, what date fits the full build, and what changes if they need both. Most clients do not need everything by the deadline. They need the one part that matters for whatever is happening that day.
That is the Three Levers method. Every build has three levers: scope, time, and price. A client can usually fix one or two of them, but not all three at once. Your job is to show which lever moves, in plain words, before any work starts. It is the other side of [telling a client you will miss a deadline](/blog/tell-a-client-you-will-miss-a-deadline): this time you catch the problem at the start, when it is cheap to fix, instead of at the end, when it is not.
Why Clients Set Unrealistic Deadlines
A tight date rarely comes from bad intent. Knowing where it comes from tells you how to answer.
- A real event. A launch, a trade show, a busy season, or a meeting where they promised to show something. The date is fixed, but the scope usually is not.
- They do not know how long builds take. Many clients have seen AI tools make something in minutes and assume a full build works the same way.
- Someone above them set it. Your contact may be passing on a date from their boss or their board and has never questioned it.
- Pressure as a tactic. Some clients set a tight date to push the price down or get more attention. This is less common, and usually shows up alongside other pushing.
- The project started late on their side. They waited to sign, and now the original date is still in their head even though the time has gone.
Ask one question to find out: 'What happens on that date, and what do you need working by then for it to go well?' The answer usually shrinks the must-have list straight away.
Run the Three Levers Method
Use these steps the moment a client gives you a date you cannot hit with the full build.
- Do not answer on the spot. Thank them for the date and say you will come back with a plan. A same-minute yes is a promise you have not checked.
- Find out what the date is for. Ask what happens on that day and what has to be working by then. Write down the real must-haves.
- Estimate honestly. Break the build into parts and estimate each one, with a buffer for testing and feedback. [How to estimate a Claude Code build](/blog/estimate-a-claude-code-build) covers this. Claude Code can make you fast, but review, testing, client feedback, and account access still take real time.
- Lay out the options. Give them two or three clear paths: a smaller first version by their date, the full build by a realistic date, and, only if you can truly do it, the full build by their date at a rush price.
- Let them choose. The client picks the lever. Your job is to make each option clear, not to decide for them.
- Put it in writing. Update the [scope of work](/blog/scope-of-work-that-prevents-scope-creep) with the agreed scope, date, and price, and note what the client needs to provide and by when for the date to hold.
What to Offer Instead of the Impossible Version
These are the options that usually keep the project and the client happy.
| What is fixed | What you offer | What you need from the client |
|---|---|---|
| The date | A smaller first version that hits the date, with the rest as phase two | Agreement on the must-haves for launch day |
| The scope | A realistic date for the full build | A clear sign-off on the new date |
| Both the date and the scope | A rush price for clearing your calendar, only if you can truly deliver | Fast feedback, early access, and payment terms that match |
| Nothing yet | A short paid planning step to break the build down and set the date together | Time with the person who set the deadline |
Three Levers: what to offer when the deadline does not fit
The smaller first version is usually the best answer, because it gets the client something real on their big day and gives you room to do the rest properly. [Shipping a client MVP in a weekend](/blog/ship-a-client-mvp-in-a-weekend) covers how to cut a build down to the part that matters. If the client chooses the rush option, [how to charge a rush fee without losing the client](/blog/charge-a-rush-fee-without-losing-the-client) covers how to price it and say it.
When to Walk Away
Sometimes the right answer is no. Walk away, politely, when even the smallest useful version cannot be done by the date, when the client refuses every option and still insists on everything, or when the deadline keeps moving earlier once you agree. A client who will not hear the truth about timing at the start rarely hears it later. [How to turn down a client project](/blog/how-to-turn-down-a-client-project) covers how to say no and leave the door open.
If you do take the project, keep the client close to the timeline as you go. [A weekly client update](/blog/weekly-client-update-prevents-fires) shows progress against the date every week, so nobody is surprised near the end.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
What should I do when a client sets an unrealistic deadline?
Do not agree on the spot. Ask what is happening on that date and what needs to be working by then, estimate the build honestly, and come back with options: a smaller first version by their date, the full build by a realistic date, or a rush price if you can truly deliver.
How do I tell a client their deadline is not realistic?
Lead with what you can do, not what you cannot. Say what you can deliver by their date, what the full build needs, and let them choose. A clear plan with options lands better than a flat no.
Should I charge more for a tight deadline?
If meeting the date means clearing other work or working outside your normal hours, a rush fee is fair. Only offer it if you can truly deliver the full build in time without cutting testing.
What if the client is slow with feedback or access after agreeing to a tight date?
Write down what the client needs to provide and by when as part of the agreement. If they are late, the date moves by the same amount, and they should know that from the start.
When should I turn down a project because of the deadline?
When even the smallest useful version cannot be done by the date, when the client refuses every option, or when the date keeps moving earlier. A client who will not accept honest timing at the start is likely to be a hard client throughout.
Last reviewed October 25, 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 →