Est. reading time: 12 minutes

Getting a new website built is one of the most expensive and consequential decisions a business owner makes, and it’s one of the decisions they’re least equipped to evaluate. You know your business. You probably don’t know web development. That knowledge gap is where the most costly mistakes happen, not after the site launches, but months earlier, in the planning and decision-making process.

We’ve worked with businesses on the marketing side who just finished a website build and are now trying to drive traffic to it. Some of those sites are excellent. Many of them have fundamental problems that limit performance from day one, problems that could have been avoided if someone had asked the right questions before the project started.

This post isn’t about design trends or platform comparisons. It’s about the decisions that determine whether your website becomes a business asset or an expensive disappointment.

You’re Probably Solving the Wrong Problem

Most website projects start with a feeling. The current site looks dated, or a competitor’s site looks better, or someone on the team is embarrassed to share the URL. So the business decides it needs a new website.

That instinct might be right. But “we need a new website” is a solution, not a problem statement. And jumping to the solution before defining the problem is how businesses end up spending $15,000 to $50,000 on a site that looks great but doesn’t actually perform any better than what it replaced.

Before you engage a developer or agency, get specific about what’s actually wrong. Is the site not converting visitors into leads or customers? That might be a design and UX problem, or it might be a messaging problem that a new design won’t fix. Is the site slow? That might require a rebuild, or it might require optimization of the existing site at a fraction of the cost. Is the site difficult to update? That’s a platform or CMS problem. Is the site not ranking in search? That could be technical SEO issues that a developer can fix without rebuilding everything.

The business owners who get the best outcomes from website projects are the ones who can articulate specifically what the current site fails to do. “It doesn’t look modern” is a preference. “We get 3,000 visitors a month and only 12 contact form submissions” is a problem with a measurable solution.

If you can’t clearly define the business problem the new website needs to solve, you’re not ready to start building. You’re ready to start diagnosing.

The Design Phase Gets Too Much Attention

This is going to sound counterintuitive, but most website projects spend too much time on visual design and not enough time on structure, messaging, and conversion strategy.

The typical process goes something like this: the business picks a developer or agency, they have a kickoff meeting, and within a few weeks they’re reviewing homepage mockups. What color should the buttons be? Do we like this font? Should the hero image be a photo or an illustration? These conversations feel productive because they’re tangible and everyone has an opinion.

Meanwhile, the questions that actually determine whether the site performs get glossed over or skipped entirely. What’s the primary action we want visitors to take on each page? What objections do visitors have, and where do we address them? What’s the information hierarchy, meaning what do visitors need to see first, second, and third? How does the site structure map to the way people actually search for and evaluate our services?

A beautifully designed website with unclear messaging, buried calls to action, and a structure that doesn’t match how customers think will underperform a plain-looking site that nails those fundamentals. We’ve seen it repeatedly. The businesses that invest in messaging strategy, site architecture, and conversion planning before the first pixel gets pushed produce better-performing websites. The ones that jump straight to visual design produce websites that look good in a portfolio and underdeliver in practice.

If your developer starts the project by asking about your color preferences instead of your customer journey, that’s a red flag.

Your Homepage Is Not Your Most Important Page

Business owners tend to obsess over the homepage. It gets the most design attention, the most revision cycles, and the most internal opinions. The homepage becomes the canvas for everything the business wants to say about itself.

For most businesses, the homepage isn’t where the majority of conversions happen. It’s not even where the majority of traffic lands.

If you’re running paid ads, that traffic should be landing on purpose-built pages, not the homepage. If you’re getting organic search traffic, people are landing on the specific pages that rank for their queries: service pages, product pages, blog posts, location pages. The homepage is often an orientation point for people who arrive through direct navigation or branded search, but it’s rarely the page doing the heaviest conversion work.

The pages that deserve the most strategic attention are your service or product pages, your contact or conversion pages, and any landing pages built for specific campaigns or audiences. These are the pages where visitors make decisions. They should have clear messaging, obvious next steps, trust signals positioned where hesitation happens, and content that matches the intent of the person who landed there.

This doesn’t mean the homepage doesn’t matter. It means the homepage shouldn’t consume 60% of the project’s creative energy while the pages that actually generate revenue get templated and filled in as an afterthought. We’ve seen website builds where the homepage went through five rounds of revision and the service pages, the ones that rank in Google and receive the most qualified traffic, were essentially the same template with different header images and swapped-out copy.

Allocate your attention proportional to where the business impact lives, not where the internal opinions are loudest.

Content Is the Part Most Businesses Underinvest In

The dirty secret of website development is that the most common reason for project delays and underwhelming results is content. Not design. Not development. Content.

Here’s how it usually plays out. The developer builds the site structure and designs the pages with placeholder text. Then they ask the business to provide the content for each page. The business owner, who’s been focused on the visual side of the project, suddenly realizes they need to write 15 to 30 pages of clear, compelling copy that accurately represents their business and speaks to their target audience. This was not what they expected to spend their time on.

So one of two things happens. The copy gets rushed, pulled together from the old website, internal documents, and hastily written paragraphs that nobody edits carefully. Or the project stalls for weeks or months while the business tries to find time to write content that should have been developed before design began.

Either way, the result is a well-designed site with mediocre content. And content is what actually does the selling. Visitors don’t convert because the layout is nice. They convert because the words on the page convinced them that this business understands their problem and can solve it.

If your website budget doesn’t include professional copywriting or a dedicated content strategy phase, the most important layer of the site is being treated as an afterthought. The best website projects we’ve seen treat content as a deliverable that precedes design, not one that fills in the gaps after the wireframes are approved.

Choosing a Platform Is a Long-Term Decision Disguised as a Technical One

WordPress, Shopify, Squarespace, Webflow, Wix, custom-built. The platform decision often gets made based on developer preference, perceived cost differences, or vague impressions about which one is “best.”

This decision has long-term operational consequences that most business owners don’t fully evaluate at the time.

The questions that actually matter:

Who will maintain and update the site after it launches? If the answer is “our team,” the platform needs to be intuitive enough for non-technical people to make content changes, add pages, and update information without calling a developer. If the answer is “we’ll hire someone as needed,” you need a platform with a large enough developer ecosystem that you’re not locked into one person or agency.

What does the site need to do beyond displaying information? If you need ecommerce, Shopify is purpose-built for that and trying to retrofit ecommerce onto a WordPress site creates unnecessary complexity. If you need complex integrations with CRMs, booking systems, or custom workflows, WordPress or a custom build gives you more flexibility. If you need a simple, professional site that’s easy to maintain, Squarespace or Webflow might be the right fit at a lower cost.

What are the ongoing costs? The sticker price of building the site is one number. The ongoing costs of hosting, plugins, security updates, platform fees, and developer maintenance are another. A $5,000 WordPress site that requires $200/month in maintenance and plugin costs has a very different five-year total cost than a $5,000 Squarespace site with a $30/month subscription and minimal maintenance needs.

How does the platform handle SEO fundamentals? Site speed, mobile responsiveness, URL structure, metadata control, schema markup capability. Every major platform handles these adequately for most businesses, but there are meaningful differences at the margins. If organic search is a significant part of your growth strategy, the platform’s SEO capabilities deserve more evaluation than they typically get.

There’s no universally correct answer. There’s only the right answer for your specific business, team, and growth plan. Be skeptical of anyone who insists one platform is always the best choice regardless of context.

Speed and Performance Are Not Optional Features

This applies to existing sites and new builds equally. A slow website is a revenue problem, full stop.

We covered site speed in depth in our CRO post, but the short version for a website development context: if your new site isn’t fast on mobile over a mediocre cellular connection, you’ve built a site that underperforms for the majority of your visitors. This isn’t a nice-to-have that gets optimized later. It’s a core requirement that needs to be baked into the development process from the start.

The most common speed problems we see on newly launched sites: oversized images that were uploaded at full resolution without compression, too many plugins or third-party scripts loading on every page, heavy animations or video backgrounds that look impressive on the developer’s demo and crawl on a real user’s phone, and hosting that’s underpowered for the site’s traffic level.

Every one of these is preventable during the build process. None of them are easy to fix after launch without significant rework. If your developer isn’t proactively addressing performance during development, including testing on real devices at throttled speeds, performance will be a problem on launch day.

Make page speed a deliverable with specific targets, not an aspiration. A Largest Contentful Paint under 2.5 seconds and a Cumulative Layout Shift under 0.1 are reasonable baselines that your developer should be able to commit to and verify before the site goes live.

How to Evaluate a Website Developer or Agency

The market for web development ranges from freelancers charging $2,000 to agencies charging $100,000+. Price alone doesn’t tell you much about quality. Here’s what we’d look at.

Do they ask about your business before they talk about design? A developer who starts with questions about your customers, your conversion goals, your competitive landscape, and your growth strategy is approaching the project as a business tool. One who starts with design inspiration and visual preferences is approaching it as a creative project. Both have value, but the first approach produces better business outcomes.

Can they show you results, not just portfolios? Pretty screenshots don’t tell you whether the site performs. Ask about load times, conversion rates, and business outcomes for previous clients. A developer who can say “we rebuilt this site and the client’s lead form submissions increased by 40%” is telling you something much more meaningful than “look how nice this looks.”

How do they handle content? If the answer is “we’ll need you to provide all the copy,” the content layer is being outsourced to you regardless of your ability to produce it. Developers who either include copywriting in the scope or partner with a content strategist are setting the project up for a better outcome.

What happens after launch? A website isn’t a finished product on launch day. It’s a living tool that needs ongoing optimization. Ask about post-launch support, training for your team, and how performance will be monitored and improved over time. If the relationship ends on launch day, you’re on your own for everything that comes next.

What does the contract look like? Understand who owns the design files, the code, and the content. Understand what happens if you want to move to a different developer or platform later. Understand the payment structure and what triggers each payment milestone. Surprises in web development contracts are almost always expensive.

The Website Is the Foundation, Not the Finish Line

A new website doesn’t generate business on its own. It’s the infrastructure that every other marketing effort depends on. Paid ads drive traffic to it. SEO brings organic visitors to it. Email marketing sends people back to it. Social media directs attention to it. If the website converts well, every marketing dollar works harder. If it doesn’t, every marketing dollar is partially wasted.

That’s why the decisions you make before and during the build matter so much. A website that was built with clear conversion goals, strong messaging, fast performance, and a structure that serves both users and search engines gives you a foundation you can build on for years. One that was built around visual preferences without strategic planning will need to be rebuilt much sooner than it should.

Take the time to define the problem before you commission the solution. Invest in content and conversion strategy before you invest in design. Choose a platform based on your actual operational needs. Hold your developer accountable for performance, not just aesthetics.

The businesses that treat their website as a strategic investment rather than a creative project consistently get more out of every marketing channel that touches it. And eventually, every marketing channel does.