August 12, 2026 · by David Gilbert · 3 min read · Business & Marketing
Across web work, repairs, consulting, and marketing jobs, there's one question I've learned to ask early, almost always in the first five minutes, regardless of what the client thinks they're actually asking me for: "what does success on this actually look like to you, specifically?" It sounds almost too simple to matter. It's saved me from more wasted, misaligned projects than any other single habit I've built.
Why the Obvious Question Isn't Actually Obvious
People come to me with a request framed as a task — "fix my laptop," "build me a website," "help with my marketing" — and it's tempting to just take the task at face value and get moving. But the actual underlying goal behind that task varies enormously from person to person, and assuming I already know it is exactly how a technically successful project ends up feeling like a disappointing one to the client anyway.
A Real Example of Why This Matters
Two different clients can ask for what sounds like an identical website redesign and mean completely different things by "success." One genuinely just wants it to look more current for credibility's sake. Another specifically wants more phone enquiries from a particular service page. Building the same beautiful, modern site for both, without knowing which goal each client actually has, might fully satisfy the first client while completely missing the second client's actual underlying need.
What Changes Once I Actually Know the Answer
Every subsequent decision gets a genuine, concrete filter to run through. Design choices, feature priorities, even how I structure a quote — all of it gets easier and more confident once I know specifically what outcome we're actually building toward, rather than guessing at an unstated goal and hoping it happens to line up with what the client actually wanted.
The Answers That Surprise Me Most
Sometimes the honest answer has very little to do with the literal task at all — someone wants a website redesign mainly to feel proud of their business again after a rough year, more than for any specific measurable metric. That's a completely legitimate goal, and it changes how I'd approach the project just as much as a metrics-driven goal would, just in a different direction entirely.
Why I Ask It Even When the Answer Seems Obvious
Even when a goal seems self-evident from the initial request, asking directly surfaces nuance that guessing never would. Someone who says they want "more customers" might actually mean "more of a specific, more profitable type of customer," which is a meaningfully different brief that changes real decisions, not just word choice in how I describe the project afterwards.
How This Plays Out at the End of a Project
Projects built around a clearly stated goal get evaluated against that actual goal, honestly, rather than against vague, unspoken expectations that were never discussed and were always going to be impossible to fully satisfy. Clients leave knowing specifically whether we hit the target we both agreed on, rather than vaguely wondering if they got what they actually wanted but never quite said out loud.
The One Habit I'd Tell Any Freelancer to Build
Ask the success question early, specifically, and actually wait for a real, considered answer rather than accepting the first vague response and moving straight on. It adds maybe five genuinely worthwhile minutes to the very start of a project. It's saved me, conservatively, dozens of hours of rework and misalignment across the years I've been doing this — which is about as good a return on five minutes as I've found anywhere in business.