Most website projects start with a list. A new look, smoother animations, a page for every service, a form that finally works on mobile. The list gets built, the site goes live, and six months later the phone rings about as often as it did before.
The list wasn't the problem. The site was built without a website strategy: a clear answer to what the website has to achieve for the business, for whom, and what a visitor should do once they arrive. Design, platform, and features all follow from that answer. When the answer is missing, they follow from taste. A website consultation exists to get that answer before any money is spent.
This post explains what a website consultation should cover, why it comes before a quote, how the options you receive afterward should be structured, and how to prepare so the call is worth your time. It's written for owners and decision-makers planning a new website, a redesign, or a marketing push that depends on the website working. If you need a single fix on a site that otherwise does its job, you don't need this process; you need a good developer.
What a website strategy is, in plain terms
A website strategy is the set of decisions you make before anyone opens a design tool. Five questions cover most of it:
- What does your business do, in the words your customers use?
- What problem should the website solve? More inquiries, better-qualified inquiries, fewer support emails, bookings without phone calls, credibility with a new market?
- Who is the website for? Not "everyone" but the customer you want more of.
- What should a visitor do? Call, book, request a quote, download, buy.
- Who else is competing for that visitor, and what do their websites do well or badly?
None of these questions is about color, layout, or platform. That's the point. A website that answers them can look many different ways and still work. A website that skips them can look excellent and still fail.
Why "impressive" is the wrong brief
In our experience, most people evaluating a website are impressed by animations, graphics, and their own taste. That's normal. You look at your website more than anyone, so it's natural to want it to look the way you like.
Your customers look at it once, for a few seconds, with a question in mind. They want to know whether you do the thing they need, whether they can trust you, and what to do next. An animation that delays that answer works against you. A layout you love but your customers find confusing costs inquiries you don't hear about.
This is why a strategy call spends its time on your customers and your goals, and why a good partner will sometimes steer you away from the feature you came in asking for. Not because it's wrong in itself, but because it doesn't move the needle.
What a website consultation covers
Providers call it different things: a website consultation, a discovery call, a web design consultation. At Lavender Giraffe we call it a strategy call, because the name says what the 30 minutes are for. It's a conversation with the person who will run your project, not a sales team. It covers the five questions above, plus what already exists: the current site, what works on it, what doesn't, and what you've tried.
You should leave a website consultation with three things. A clearer statement of the problem than you arrived with. An honest view of whether a website is the right fix, or whether something smaller or different comes first. And a sense of what a realistic scope looks like.
What happens next depends on one thing: whether you have a fixed budget.
If you have a budget, say so on the call
If you know what you can spend, share it. There's nothing to gain from hiding it. We assess whether what you want can be achieved within that budget, and we meet again to discuss what can be done. No quote goes out in between, because the question isn't "how much does this cost" but "what's the best use of this amount." Sometimes the answer is a smaller site that does one thing well. Sometimes it's a phased plan.
If you don't have a fixed budget, you get a range first
If the budget is open, you receive a rough quote range after the call: within hours for a small site, a couple of days for a larger or more complicated project. The range lets you decide whether to continue before anyone invests more time. If you do, a discovery stage looks deeper at your needs, your market, and your current site, and the result is a Proposal of Services.
Why you should be offered options, not one number
For larger projects, the Proposal of Services usually includes two or three packages to choose from. A small site gets one clear scope and price. Each is a fixed price for a defined scope, so you're choosing between complete solutions rather than negotiating line items.
This matters for two reasons. First, it puts the trade-off in your hands. One option might cover the core problem with a lean site. Another might add the content, languages, or integrations that make the site work harder from day one. You see what each level buys and decide what the business needs now. Second, a fixed price for a fixed scope removes the most common source of friction in web projects: the invoice that grows because nobody defined where the project ended.
Search engine optimization (SEO) isn't a separate line in any of the options. It's built in from the first wireframe, because a site that can't be found doesn't solve anyone's problem, however good it looks. You can read more about how we work on the process page.
Who does the work, and who is accountable
A boutique agency doesn't do everything in-house, and it shouldn't. Specialist work needs specialists: copywriting, Google Business Profile setup, app development or complex builds, domain name system (DNS) records, and email configuration. What matters to you is how those specialists are chosen and who answers for the result.
Our contractors are selected on experience and results, and we know them personally. None are sourced from freelance platforms. You talk to one person throughout, and that person is accountable for the whole outcome, including the parts a specialist delivered. If something isn't right, there's no handoff and no "that was the other supplier."
When you're comparing providers, ask this directly: who will I speak to, who does each part of the work, and who is responsible if a part fails? A clear answer is a good sign. A vague one usually means you'll be managing the contractors yourself later.
Two examples of the strategy call changing the answer
A marketing request that turned into a website. A client came to us for marketing. Their website was a year old, built by someone else, and looked fine. On review, its Core Web Vitals were poor and its SEO was a mess: the metadata and structure had been carried over from a previous website in a completely different sector. The site was invisible to Google and to AI tools. Spending on marketing would have sent traffic to a site search engines couldn't make sense of. The strategy call changed the order: fix the foundation, then market. We built a new website first. If your own site has similar symptoms, the post on why your Google ranking dropped covers what to check.
A new website the owner hated. Another client had recently paid for a new website. It worked well enough, but they disliked the design, and they'd been given no chance to approve it before launch. The site went live as the designer had decided it should look. We started from what their business needed the site to do, then designed it with them, with a review stage before anything went live. They're happy with the result and have sent us many referrals since. The lesson isn't that design taste doesn't matter. It's that the process has to include you at the points where it counts: goals first, then design you've seen and agreed to, then launch.
How to prepare for a strategy call
You don't need a brief, a sitemap, or a mood board. You need answers to a few questions, even rough ones:
- The problem in one sentence. "We get inquiries, but the wrong ones." "Nobody finds us." "The site embarrasses us in front of larger clients."
- The customer you want more of. One or two types, described the way you'd describe them to a colleague.
- The action a visitor should take. Pick one primary action.
- Two or three competitors, and what you think their websites get right.
- Your budget, if it's fixed. If it isn't, that's fine too.
- What exists: your current site, whether you own the domain and hosting, and whether you have access to Google Analytics and Search Console.
If you've already written a formal brief, bring it. The post on why the quote you choose rarely matches your website brief explains how to score proposals against it once they arrive.
Common mistakes worth avoiding
- Asking for a quote from an email. A price without a conversation is a price for something the provider guessed. It will be either padded to cover the unknowns or low because the unknowns were ignored.
- Judging proposals by the mockup. A polished visual in a proposal shows design taste. It doesn't show whether the provider understood the problem. Read the scope before you look at the pictures.
- Spending on marketing before the site can be found. Ads and social campaigns send people to the website. If the site is slow, misconfigured, or invisible to search engines, that spend leaks.
- Buying features instead of outcomes. A chatbot, a blog, a members' area. Each is worth having if it serves the goal. Each is a maintenance cost if it doesn't.
- Choosing the biggest package by default. More scope isn't more safety. Choose the option that solves the problem you named on the call, and plan the rest as a next phase.
The decision in one sentence
Decide what the website has to achieve and for whom before you decide how it should look, and choose a partner whose website consultation asks those questions before quoting.
If you'd like to talk through what your website needs to do, book a strategy call. It's 30 minutes with the person who would plan and run your project, not a salesperson, and you leave with a clearer picture whether or not you continue. You can also see what Lavender Giraffe builds and for whom.
Frequently asked questions
What is a website strategy?
A website strategy is the set of decisions about what your website must achieve for your business, who it serves, what visitors should do, and how it compares with competitors. It's made before design and platform choices so that those choices have something to serve. It doesn't need to be a long document; a page of clear answers is enough for most businesses.
Is a web design consultation free?
It depends on the provider and on what the session includes. A first web design consultation that covers goals, audience, and a rough range is often free, because it's how both sides decide whether to work together. Deeper discovery work, such as audits, market research, and competitor analysis, is real work and is often a paid stage. Ask upfront what is included at each step so there are no surprises.
What happens after a strategy call?
If you shared a fixed budget, the next meeting covers what can be achieved within it. If the budget is open, you receive a rough quote range, usually within hours for a small site, and a discovery stage follows if you want to continue. The outcome is a Proposal of Services with a fixed price, and for larger projects two or three packages to choose from.
Do I still need a strategy call if I already have a brief?
Yes, and it will be a shorter one. A brief tells a provider what you want. The call checks whether what you want solves the problem you have, and it's where a good provider will tell you if it doesn't. Bringing a brief makes the call more precise, not redundant.
