The Discovery Call Questions That Tell Us If a Project Will Go Well

After a few hundred discovery calls, a pattern shows up that has nothing to do with budget size or project complexity. The same handful of answers reliably predict whether a project goes smoothly or turns into a slog — and none of them are about how much money is on the table.

"Who makes the final call on decisions?"

Projects with one clear decision-maker move fast, even when that person changes their mind occasionally. Projects with three stakeholders who each need to individually approve every choice move slowly no matter how good the team is, because consensus-by-committee adds a review cycle to everything, including things that were never actually controversial.

"What have you tried before, and why didn't it work?"

A client who can answer this specifically — "we hired someone who didn't understand our industry" or "scope kept expanding and nobody pushed back" — has usually learned something real from a past attempt. A client who can't answer it, or blames the previous team entirely without any self-reflection, is more likely to repeat the same pattern with us.

"What does success actually look like in six months?"

This is the single best predictor we've found. A concrete answer — a number, a behavior, a specific outcome — means the brief is going to be clear and the project will have a real finish line. A vague answer ("just, you know, a better website") usually means scope will keep drifting because there's no fixed target to measure against.

Why we ask these instead of just quoting a price

A quote based on a vague brief is a guess wearing a number, which is exactly the trap we describe in how much a website or app should actually cost. These questions aren't a sales tactic — they're how we find out whether we can actually give you an honest, accurate answer instead of a comfortable one that falls apart three weeks into the project.