Most project conversations start with a feature list. A booking form, a blog, an online store, a members area. Feature lists feel productive, but on their own they don't tell us much about what actually needs to get built or why. Instead, we start every first call with four questions that matter far more.
1. What should this site accomplish?
Not "what pages should it have," but what result are you actually after. More booked calls, more online orders, more trust from people finding you for the first time. The answer shapes everything from layout to copy to which features are worth the effort.
2. Who is actually going to land on this site?
A site built for someone comparing five options on their phone during a lunch break needs a different structure than one built for a client who was already referred to you and just needs reassurance before booking a call.
3. What happens after someone takes the action you want?
A contact form that lands in an inbox nobody checks isn't much better than no form at all. We ask what your actual process looks like after a booking or inquiry comes in, so the backend supports how you really work rather than an assumption of how it should work.
4. What does this need to still be doing in a year?
This is the question that separates a quick fix from a real investment. A site that only needs to hold up for a few months can be built differently than one that needs to scale with a growing business.
Features are the how. These four questions are the why, and the why is what actually determines the how.
Once we have honest answers to these four questions, the feature list tends to sort itself out. Some things clients originally asked for turn out to be unnecessary, and some things they hadn't thought to ask for turn out to matter a great deal.