The One Client Conversation That Saves the Most Time — and Nobody Has It

I run a small WordPress studio — webmaster.co.ua, 18 years, 235+ projects. If I had to point to the single highest-leverage habit we built, it's not a tool or a stack decision. It's a five-minute conversation we now have before any scoping starts, that almost nobody in this business has by default.

We ask what "done" looks like, before we ask what they want built. Most intake calls jump straight to features — pages, sections, functionality. But "done" for a client is rarely a feature list. It's usually a business outcome: more calls, more bookings, credibility with a specific type of customer. Skipping this question means you can deliver every requested feature and still have an unhappy client, because you built the list without ever knowing the actual target.

We ask who else has to approve it. A huge share of painful revision cycles trace back to a stakeholder who never joined the calls — a business partner, a spouse, an investor — whose opinion arrives after "final" was already signed off. Asking this upfront doesn't eliminate the problem, but it turns a surprise into a known risk you can plan around.

We ask what happened with their last developer, if there was one. Not to gossip — to pattern-match. One bad story about a past freelancer is someone else's problem. A pattern across multiple past developers usually points at unclear scope or shifting requirements on the client's side, which is information worth having before you quote.

We ask what they'd cut if the budget got tighter. This tells you more about their real priorities than any wishlist does. A client who can name what's expendable understands tradeoffs — and clients who understand tradeoffs make faster, better decisions once the project is underway.

None of these questions are technical. But they predict project difficulty better than any spec review I've ever done, and they take less time than writing the proposal itself.