“So… how long is this going to take?”
It sounds like a simple question about dates. It isn’t.
Whenever a client asks you for a timeline they are asking you almost NEVER for a calendar. They’re asking about money. They’re asking about risk. They’re asking if they can trust the person sitting across the table.
Feed them the incorrect answer and you give away a date you cannot make. Feed them the correct answer and you have half of a sale before someone even puts pen to paper.
Here’s the problem:
The majority of teams respond to the question posed, rather than answering the question intended.
Let’s fix that.
What you’ll walk away with:
- Why every timeline question is really a budget question
- The 4 hidden questions buried inside “how long?”
- How to answer without boxing yourself in
- What to do when the dates start slipping
Why “How Long?” Always Means “How Much?”
Time is project material. Each additional week equals additional salaries, additional software licences, additional rent on equipment doing nothing in your yard.
So when a client hears “six months,” their brain immediately starts doing sums…
Six months worth of payroll. Six months before you start seeing any return on investment. Six months where you have your employees stuck in status meetings rather than working.
This is why project cost estimating and scheduling will never be separated. A date without a number behind it is worthless. And a number without a date attached is simply a guess dressed in a business suit.
It’s why this link lies at the heart of professional project training. Project managers studying a Master’s in Project Management devote significant time to cost estimating, resource planning & forecasting techniques. After all, those are the skills that help you transform a schedule from rough sketches to defensible. The date your client sees is only the tip of the iceberg when it comes to the cost calculation beneath.
The 4 Questions Hiding Inside “How Long Will This Take?”
Ask a client what they really want to know and you’ll hear the same four things every time.
“What Is This Going To Cost Me?”
Duration is it. This is your client’s euphemism for price. If anything gets billed hourly or by the sprint, duration is your enemy.
When they talk about more time, they don’t mean a shorter wait. They mean you pay more. You know that too.
“When Do I Start Seeing A Return?”
Nobody buys a project. They buy the thing the project produces.
The whole warehouse build doesn’t even pay for itself until month three. All they care about is “when do we start saving money”. When someone sells you a date they are typically back-solving for when expenditures cease.
“How Badly Could This Go Sideways?”
Clients have been burned before. Almost all of them.
The statistics agree. A study from McKinsey & Company and Oxford University involving over 5,400 large-scale IT ventures showed they run 45% over budget and 7% over schedule, on average. McKinsey also found that each additional year added to a project’s schedule increases the cost overrun by approximately 15%.
Long projects don’t just cost more. They cost more per year.
“Do You Actually Know What You’re Doing?”
He’s the silent partner. Round numbers sound ignorant. Too-specific sounds like a sales job.
Confidence comes from showing your working, not from sounding certain.
How To Answer Without Painting Yourself Into A Corner
Ok, here’s the good news. There is a repeatable method to approach this conversation that preserves both the schedule and the relationship.
Give A Range, Then Explain The Range
Don’t ever deliver one date. Deliver a best case and a worst case. Simply explain what the difference is between them.
Somewhere between fourteen and eighteen weeks. Fourteen of the product data arrives by the end of the month. Eighteen if it comes late.
The client now knows that the timeline wasn’t your word alone, but a shared responsibility.
Attach A Cost To Every Date
This is where good project cost estimating pays off. There should be a number next to every milestone in the plan for the client to see exactly what a delay costs and what it buys.
As soon as someone asks for two more weeks of testing, the answer is no longer an argument over feelings. Two weeks, this many dollars, protects you from this.
Say Your Assumptions Out Loud
All estimates are based on assumptions. Most teams keep them mental. That’s where arguments start.
Write them down. All of them:
- Who is providing what, and when
- How many rounds of feedback are included
- Which approvals are needed and who gives them
- What is explicitly not in scope
That last bullet is the one that saves projects.
Agree The Change Process Before You Need It
Scope changes are not negotiable. According to PMI’s Pulse of the Profession research, 52% of projects suffer from scope creep. That’s a significant increase from prior years.
Build the door before there is a fire. Determine how a change will be requested, costed and approved before starting the project. That two line change form signed at project kickoff can prevent a nasty discussion half way through the project.
What To Do When The Dates Start Slipping
They will slip. That is not failure, it’s arithmetic.
What matters is how quickly the client hears about it.
Pick up a slip the week it shows, not the week you find out about it. A three-day slip reported quickly is just a scheduling footnote. Three days unreported for a month reeks of cover-up.
Bring three things to that conversation:
- What moved and why
- What it costs in time and money
- Two or three options for handling it
Options are what turn bad news into a solution. Clients don’t lose faith because of a delay. They lose faith because of surprises.
And here’s the part most people miss…
A revised estimate is far more believable than the original. It’s based on facts, not guesses. Tell them that and your credibility increases, rather than decreases.
Bringing It All Home
When a client asks you how long something will take, remember that they are also asking you about cost, payback, risk and if you are the right team to work with – all in one question.
Answer all four and the conversation changes completely.
To recap:
- Treat timelines and budgets as one conversation, never two
- Give ranges with clear reasons behind each end of them
- Put a cost beside every milestone
- Write down every assumption, especially the exclusions
- Agree the change process before anything changes
- Report slips early, and always bring options
Good project cost estimating doesn’t make a project magically execute itself. It does, however, create a realistic timeline. An honest timeline is what your clients recall long after the work is completed.
