Website projects go sideways when the brief is really a wish list

Before you kick off a website project, the smartest questions aren’t about colours, page counts, or which platform is “best”. They’re about how the site will make money, how it’ll be looked after, and what has to be true for the project to count as a win. Most of the pricey clean ups we get called into started with those conversations being skipped, then big decisions getting locked in far too early.

If you’ve built a few sites before, you know the fundamentals. The gap between an average rebuild and a great one is whether you’re willing to ask the awkward questions while it’s still cheap to change direction.

What job is the website actually doing in the business?

“Marketing” isn’t a job. Neither is “credibility”. A website usually has to do one hard, specific job, generate qualified leads, take payments, reduce admin load, support a sales team, or make recruitment easier. Some sites do a few of these, but there’s almost always a primary job that should drive the decisions.

When that primary job is fuzzy, the build turns into a negotiation between internal opinions. You end up with something that looks fine, but no one can explain what success is beyond “more traffic”.

The simplest way to pin it down is to identify the highest value action you want a visitor to take, then work backwards. If the money is made on phone calls, the site needs to generate calls from the right people, not just clicks. If the money is made on booked consultations, the booking flow isn’t an add on, it’s part of the product.

What does a qualified conversion look like, and how will we measure it?

Good businesses define conversions in business terms, not vanity metrics. A lead you can’t service profitably is noise. A form fill with no context is often dead weight for sales. If you’re at the decision stage, you’ll get more value from agreeing on what “qualified” means than arguing about whether the homepage needs a video.

This is where measurement stops being theoretical. If you can’t reliably track enquiries, calls, bookings, purchases, or quote requests, you can’t improve the site after launch. So ask early, what events are we tracking, where do leads land, CRM, inbox, job management software, and who is actually going to look at the data each week?

GA4 is useful for behavioural trends, but it won’t magically tell you lead quality. Most teams need a simple, disciplined measurement stack, clear conversion events, consistent naming, call tracking if calls matter, and a way to tie leads back to source. If you’re running Google Ads, this isn’t optional, conversion data affects bidding and cost per lead.

Who are we building for, and what do they need to decide?

“Our customers” is too broad to be useful. The buyer might be the business owner, the researcher might be an office manager, and the end user might be a technician. They’re looking for different proof, and they have different concerns. The site has to answer the questions that stall the deal.

For service businesses, it usually comes down to a handful of decision blockers, whether you service their area, whether you handle their specific situation, what the process looks like, what it costs, or at least how pricing works, and whether you’re trustworthy enough to invite in. If your content doesn’t deal with those blockers quickly, people don’t leave because the design is “wrong”. They leave because the site didn’t reduce uncertainty.

What content do we already have that’s worth keeping, and what’s holding us back?

Most rebuilds should start with a content and performance audit, not a sitemap workshop. You need to know what’s currently driving leads, which pages rank and why, what’s outdated but salvageable, and what should be deleted or redirected.

A common mistake is deciding “we’ll rewrite everything”, then running out of time. The new site goes live with thin copy and missing detail, exactly where buyers needed reassurance. A better approach is triage, keep and improve what’s already working, rewrite what’s wrong or unclear, and create new pages only where there’s a genuine gap in the buyer journey or search demand.

If local SEO matters, the structure of your service pages isn’t an aesthetic preference. It affects how Google reads relevance and how users self qualify. If you’re unsure how to organise that properly, How Service Area Pages Should Be Structured for SEO is a solid reference point.

What’s the real scope, and what are we deliberately not doing?

Scope creep usually isn’t about “difficult clients”. It’s about decisions not being made clearly. A strong scope forces the trade offs into the open, what’s in, what’s out, and what gets handled later.

If you want a website that also works as a quoting tool, a client portal, a learning platform, and a booking engine, that’s not a “website project”. That’s product development, and it needs different planning, budget, and testing. Plenty of businesses can build those things, but pretending they’re just extra pages is how timelines blow out and quality slips.

Good teams will make you prioritise. If they don’t, you’ll be prioritising under pressure two days before launch.

Who owns what after launch?

This is one of the most telling questions you can put to an agency or developer, what do we own, and what are we renting?

At minimum, you should have clear ownership of your domain, access to hosting, or at least the ability to move, analytics properties, ad accounts, and key third party tools. If the site is built in a system where you can’t export content or move without rebuilding, you want to know that upfront, not when the relationship goes sour.

Also ask who is responsible for updates, backups, security, and uptime monitoring. WordPress sites don’t “set and forget”. Neither do Shopify apps, server environments, or headless setups. If you want a site that stays fast and stable, someone has to own ongoing care. If you’re weighing up whether to keep that in house or outsource it, What to Look for in a Long Term Website Partner covers the practical questions that matter.

What’s the plan for SEO and redirects on day one?

SEO migrations fail in very predictable ways, URLs change without redirects, internal links break, metadata disappears, and the new site launches with weaker content than the old one. Rankings drop, leads dip, and everyone blames Google.

A competent rebuild includes a redirect map, a plan to preserve or improve key pages, and a crawl of staging before launch. It also includes a post launch check to catch issues that only show up when the site is live, like blocked resources, indexation problems, or analytics misfires.

If your current site has any organic performance at all, treat the rebuild like an asset transfer, not a clean slate.

How fast does the site need to be in the real world, not in a demo?

Speed isn’t a vanity metric. It affects conversion rates and it affects SEO, especially on mobile. The trap is designing on a fast office connection, then shipping uncompressed images, heavy sliders, and a pile of third party scripts nobody has audited.

Ask what performance budget you’re building to. That can mean limits on font files, video usage, animation libraries, and tracking scripts. It also means deciding early how you’ll handle images, caching, and hosting. If your site relies on half a dozen marketing tools, you need someone who will test the impact and make trade offs, not just install everything that gets requested.

What’s the content production reality, and who signs it off?

Most website timelines are really content timelines. Design and development are fairly predictable. Content isn’t, because it needs input from busy people who often aren’t used to writing for buyers.

Get clear on who’s writing the copy, who’s supplying photos, whether you need new photography, and who has final approval. If approvals are split across three stakeholders, bake that into the plan. If you need a compliance review, schedule it early. If you’re in a regulated industry, agree on what you can and can’t claim before anyone starts writing headlines.

If you’re using AI to speed up drafts, treat it like a junior assistant. It can help with structure and first passes, but the final copy still needs real expertise, local nuance, and accuracy. Otherwise you publish generic content that doesn’t differentiate you, and doesn’t convert.

What integrations are business critical, and what’s the failure plan?

Websites rarely stand alone. They connect to CRMs, email marketing, booking systems, quoting tools, inventory, accounting, and live chat. Integrations are where “simple” projects quietly become complex.

Be specific about what must happen when someone submits a form or makes a booking. Where does the data go, who gets notified, how is it tagged, and what happens if an integration fails? If a lead disappears into the void for a week because an API key expired, that’s not a technical hiccup. That’s lost revenue.

For higher volume lead gen, it’s worth asking whether you need server side tracking, offline conversion imports, or at least a reliable way to match leads back to campaigns. Without that, you’re guessing with your ad spend.

What does “done” mean, and what happens after go live?

Launching is a milestone, not the finish line. Strong teams define what “done” looks like, acceptance criteria, testing requirements, handover documentation, training, and a post-launch support window.

Then they plan the next 90 days. Real gains come from watching how users behave, listening to sales feedback, and iterating. If your agency disappears at launch, you’re left living with whatever assumptions got baked into the build.

The question that saves the most money

Ask your team to walk you through the riskiest part of the project. Not the most exciting part, the riskiest. It might be a platform migration, complex forms, SEO retention, third party integrations, internal approvals, or simply the fact that nobody has time to provide content.

When that risk gets named early, you can design around it. When it’s ignored, it turns into a surprise invoice or a quiet performance drop that takes months to claw back.

About the Author

Nicholas McIntosh

Nicholas McIntosh is a digital strategist driven by one core belief: growth should be engineered, not improvised. 

As the founder of Tozamas Creatives, he works at the intersection of artificial intelligence, structured content, technical SEO, and performance marketing, helping businesses move beyond scattered tactics and into integrated, scalable digital systems. 

Nicholas approaches AI as leverage, not novelty. He designs content architectures that compound over time, implements technical frameworks that support sustainable visibility, and builds online infrastructures designed to evolve alongside emerging technologies. 

His work extends across the full marketing ecosystem: organic search builds authority, funnels create direction, email nurtures trust, social expands reach, and paid acquisition accelerates growth. Rather than treating these channels as isolated efforts, he engineers them to function as coordinated systems, attracting, converting, and retaining with precision. 

His approach is grounded in clarity, structure, and measurable performance, because in a rapidly shifting digital landscape, durable systems outperform short-term spikes. 


Nicholas is not trying to ride the AI wave. He builds architectured systems that form the shoreline, and shorelines outlast waves.

Connect On LinkedIn →