The 3 Questions I Ask Every Client Before Touching Any Code

Most web projects go sideways before a single line of code is written. Not because the developers were bad. Not because the design was off. Because nobody asked the right questions at the start.

Before I open any tool, look at any platform, or suggest any approach, I ask three questions. They are not technical. They are about the business. And the answers change everything.

Question 1: Where Is Your Business Right Now?

Not where you want it to be. Where it actually is today.

A business launching its first product is in a completely different position than one that has been running for five years and is changing direction. Both might need a website. But what that website needs to do, and how much it needs to do it right now, are entirely different things.

A first launch needs speed and clarity. A pivot needs to communicate change without losing trust. A scaling operation needs infrastructure, not just a new coat of paint. Same category of project, completely different execution.

When I understand where you actually are, I can tell you what is appropriate for this stage. Not what would be impressive. What would be useful.

Question 2: What Does Success Look Like in Six Months?

Not "a beautiful website." Not "more leads." Something specific.

Is it closing your first ten clients? Is it proving that a new offer can sell before you build the full product? Is it getting off a platform that stopped working for you?

This question matters because it determines what the project actually needs to accomplish. A website built to prove a concept looks nothing like a website built to scale an existing operation. If you cannot answer this clearly, that is useful information too. It usually means the project scope needs work before anyone starts building anything.

The six-month horizon is intentional. Long enough to be meaningful, short enough to stay honest. Most technology decisions have a real shelf life, and the right choice for now is not always the right choice forever.

Question 3: What Are You Trying to Avoid?

This one surprises people. But it is often where the most important information lives.

Some clients want to avoid complexity. They have been burned by projects that grew out of control and they want something they can actually manage. Some are trying to avoid vendor lock-in. Some have a hard budget ceiling and need to know upfront whether we are working within it or not. Some need to avoid a long timeline because there is a launch date that cannot move.

Knowing what someone is trying to avoid tells me what tradeoffs they will and will not make. It also tells me where the real constraints are, which is often different from where people think the constraints are.

Why These Three Questions Change the Outcome

They frame everything that comes after. Platform choice, architecture, scope, timeline: all of those decisions become clearer when you know where the business is, what it needs to accomplish, and what it cannot afford to get wrong.

Without them, you are making technical decisions in a vacuum. And technical decisions made in a vacuum tend to be optimized for the wrong things.

These questions are not a discovery call format. They are a mindset. The answers are rarely complete on the first pass. But asking them, seriously, at the start, is what separates a web project that works from one that just ships.

If you want to go through them before your next project, let's talk.

More from Rainmakers

• What Is Web Consulting, the honest conversation before execution starts.
• What Happens in a Web Consulting Session, a walkthrough of what we cover.
• Web Consulting at Rainmakers, how we approach consulting projects.