The Client Question That Predicts a Six-Month Project Better Than Any Spec

I run a small WordPress studio — webmaster.co.ua, 18 years, 235+ projects. There's one question I now ask on every discovery call that I used to skip, and skipping it cost me more time than almost anything else in the business: "What happens if this project runs a month over?"

The answer tells you who actually controls the timeline. Some clients say "no problem, take the time you need." Others visibly flinch — there's an event, an investor update, a seasonal deadline they hadn't mentioned. Learning that in week one changes how you sequence the work. Learning it in week six, when the deadline suddenly becomes urgent, means you're renegotiating scope under pressure instead of planning around it from the start.

Silence on this question is its own answer. A client who can't articulate any consequence to slipping usually hasn't thought about the timeline at all — which means the deadline they gave you was arbitrary, not load-bearing. That's useful too: it tells you there's room to push back on scope without real cost to them, versus a client where every week genuinely matters.

It surfaces hidden dependencies you'd otherwise find out about late. More than once, the honest answer revealed that the site launch was gated on something else entirely — a rebrand not yet finalized, a product not yet ready, an investor deck that needed the URL before anything else did. Building against a deadline without knowing what's actually driving it means you can hit your date and still fail the client's real goal.

It's a five-second question that most intake processes skip entirely. Most discovery calls are structured around what the client wants built. Almost none ask what breaks if it's late. That single gap is why so many "urgent" projects turn out not to be urgent at all, and so many quiet ones turn out to have a hard, unstated deadline underneath.

If your intake process covers scope and budget but not consequence, it's worth adding — it costs one question and tells you more about how to sequence a project than the brief itself usually does.