Est. reading time: 10 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 costly mistakes happen, not after launch, but months earlier, in the planning and decision-making that shapes everything the developer eventually builds.
We see the results from the marketing side constantly: businesses that just finished a build and now want traffic driven to it. Some of those sites are excellent. Many have fundamental problems that cap performance from day one, problems that a few right questions before the project started would have prevented. This post is about those questions, not design trends, not platform wars, the decisions that determine whether the 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, a competitor’s looks better, someone on the team is embarrassed to share the URL, so the business decides it needs a new website. The 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 spend $15,000 to $50,000 on a site that looks great and performs no better than what it replaced.
Before engaging anyone, get specific about what’s actually wrong. A site that doesn’t convert visitors might have a design problem, or a messaging problem no redesign will touch. A slow site might need a rebuild, or might need optimization at a tenth of the cost. A site that’s painful to update has a CMS problem. A site that doesn’t rank might have technical SEO issues fixable without rebuilding anything. Each diagnosis points at a different project with a different budget, and the feeling points at all of them equally.
The owners who get the best outcomes are the ones who can articulate what the current site specifically fails to do. “It doesn’t look modern” is a preference. “We get 3,000 visitors a month and 12 contact form submissions” is a problem with a measurable solution. If you can’t define the business problem the new site needs to solve, you’re not ready to build. You’re ready to diagnose.
The design phase gets too much attention
This sounds counterintuitive, but most website projects spend too much time on visual design and not enough on structure, messaging, and conversion strategy. The typical arc: kickoff meeting, then homepage mockups within weeks, then months of conversations about button colors, fonts, and hero images. Those conversations feel productive because they’re tangible and everyone has an opinion.
Meanwhile the questions that determine performance get glossed over. What’s the primary action visitors should take on each page? What objections do they arrive with, and where do we answer them? What’s the information hierarchy, what must be seen first, second, third? How does the site structure map to how people actually search for and evaluate this kind of business?
A beautifully designed site with unclear messaging, buried calls to action, and a structure that fights how customers think will lose to a plain site that nails those fundamentals, and we’ve watched it happen repeatedly. The businesses that invest in messaging strategy, architecture, and conversion planning before the first pixel gets pushed produce sites that perform. The ones that jump straight to visuals produce sites that look good in a portfolio and underdeliver in the wild. If your developer’s first questions are about color preferences rather than customer journeys, that’s a red flag worth heeding.
Your homepage is not your most important page
Business owners obsess over the homepage. It gets the most design attention, the most revision cycles, and the most internal opinions, becoming the canvas for everything the business wants to say about itself. But for most businesses, the homepage is neither where most conversions happen nor where most traffic lands.
Paid traffic should be landing on purpose-built pages. Organic traffic lands on whatever ranks for the query, service pages, product pages, blog posts, location pages. The homepage mostly orients people arriving from direct navigation or branded search, useful work, but rarely the heaviest conversion work. The pages that deserve the strategic attention are the service or product pages, the contact and conversion pages, and campaign landing pages, because those are where visitors make decisions, and they need clear messaging, obvious next steps, trust signals positioned where hesitation happens, and content matched to arrival intent.
None of which means the homepage doesn’t matter, and when it’s the page in question, it has its own discipline, one we detailed in building a homepage that keeps visitors scrolling and clicking. It means the homepage shouldn’t consume 60 percent of the project’s creative energy while the revenue pages get templated as an afterthought. We’ve seen builds where the homepage survived five revision rounds and the service pages, the ones ranking in Google and receiving the qualified traffic, shipped as one template with swapped header images. Allocate attention proportional to where the business impact lives, not where the internal opinions are loudest.
Content is the part most businesses underinvest in
The quiet truth of website development is that the most common cause of project delays and underwhelming results is content. Not design, not development. Content. The usual sequence: the developer builds the structure with placeholder text, then asks the business for the real copy, and the owner, who’s been focused on visuals, suddenly discovers they owe 15 to 30 pages of clear, persuasive writing they never planned to produce.
Two outcomes follow. The copy gets rushed, scraped from the old site and internal documents into paragraphs nobody edits carefully, or the project stalls for months while the business hunts for time to write. Either way the result is a well-designed site with mediocre content, and content is what does the selling. Visitors don’t convert because the layout is pleasant. They convert because the words convinced them this business understands their problem and can solve it.
If the budget doesn’t include professional copywriting or a dedicated content phase, the most important layer of the site is being treated as a gap-filler. The best projects we’ve seen treat content as a deliverable that precedes design, shaping the wireframes rather than squeezing into them.
The platform choice is a long-term decision disguised as a technical one
WordPress, Shopify, Squarespace, Webflow, custom, the platform decision usually gets made on developer preference or vague impressions of which is “best,” and it carries operational consequences most owners never evaluate at the time. Four questions do the real work.
Who maintains the site after launch? If it’s your team, the platform must let non-technical people change content, add pages, and update information without calling a developer. If it’s hired help as needed, you need an ecosystem big enough that you’re never locked to one person or agency.
What must the site do beyond displaying information? Ecommerce points hard at Shopify, since retrofitting stores onto WordPress creates complexity nobody enjoys. Complex integrations, CRMs, booking systems, custom workflows, favor WordPress or custom builds. A straightforward professional presence might be best served by Squarespace or Webflow at a fraction of the maintenance burden.
What are the ongoing costs? The build price is one number; hosting, plugins, security, platform fees, and maintenance are another. A $5,000 WordPress site carrying $200 a month in upkeep has a very different five-year cost than a $5,000 Squarespace site at $30 a month, and five-year cost is the honest comparison.
And how does the platform handle SEO fundamentals? Speed, mobile behavior, URL structure, metadata control, schema capability. Every major platform is adequate for most businesses, but the margins differ, and if organic search is central to your growth plan, those margins deserve real evaluation. There’s no universally correct answer, only the right one for your team and trajectory, so be skeptical of anyone who insists one platform wins regardless of context.
Speed and performance are not optional features
A slow website is a revenue problem, full stop, and it applies to new builds exactly as it does to existing sites. If the new site isn’t fast on mobile over a mediocre cellular connection, it underperforms for the majority of your visitors from launch day, and this is not a nice-to-have that gets optimized later, it’s a core requirement that has to be baked into development.
The failures we find on newly launched sites are depressingly consistent: full-resolution images uploaded without compression, too many plugins and third-party scripts loading everywhere, animations and video backgrounds that impress on the developer’s machine and crawl on a real phone, and hosting underpowered for the traffic. Every one is preventable during the build and expensive to fix after it. So make speed a deliverable with targets, not an aspiration: Largest Contentful Paint under 2.5 seconds and Cumulative Layout Shift under 0.1 are reasonable baselines a competent developer can commit to and verify, on real devices at throttled speeds, before launch.
How to evaluate a developer or agency
The market runs from $2,000 freelancers to $100,000 agencies, and price alone tells you little. Here’s what does. Do they ask about your business before your aesthetics, your customers, conversion goals, and competitive landscape, or your design inspiration? Both approaches have value; the first produces business outcomes. Can they show results rather than portfolios, load times, conversion improvements, “lead submissions rose 40 percent after the rebuild,” instead of screenshots? How do they handle content, is copywriting in scope or quietly outsourced to you? What happens after launch, support, training, performance monitoring, or does the relationship end at the handoff? And what does the contract say about who owns the design files, code, and content, what happens if you leave, and what triggers each payment, because surprises in web development contracts are almost always expensive ones.
The website is the foundation, not the finish line
A website doesn’t generate business on its own. It’s the infrastructure every other marketing effort depends on, ads drive traffic to it, SEO brings visitors to it, email sends people back to it, and if it converts well, every marketing dollar works harder, while if it doesn’t, every marketing dollar is partly wasted. That’s why the decisions before and during the build matter so much: a site built on clear conversion goals, strong messaging, fast performance, and honest structure is a foundation that lasts years, and one built around visual preferences will need rebuilding long before it should.
Define the problem before commissioning the solution. Invest in content and conversion strategy before design. Choose the platform on operational reality. Hold the developer accountable for performance, not just aesthetics. The businesses that treat the website as a strategic investment rather than a creative project get more from every channel that touches it, and eventually, every channel does. It’s the same order of operations we run in our own web development work, structure and strategy decided before anything gets designed.
