Before You Spend Money on a New Website, Do This First

We get a version of the same enquiry every few weeks. A business owner reaches out ready to move forward with a new website. They have a budget in mind, sometimes a rough deadline, and usually a Pinterest board or a competitor’s site they like the look of. What they often don’t have is a clear answer to a simple question: what is this website actually supposed to do for the business?

That’s not a criticism. Most business owners aren’t website people, and they shouldn’t have to be. But it’s the single biggest reason website projects go over budget, drag past deadlines, or launch to a shrug instead of results. The build itself usually isn’t the problem. The planning that should have happened before the build starts is.

If you’re about to spend money on a new website — whether that’s your first one or a redesign of something that’s underperforming — there’s a short list of things worth sorting out before you request a single quote. None of it costs money. All of it will save you some.

Get Specific About Why You Need a New Site

“Our website looks outdated” is a reason to want a new website. It’s not a reason a developer can actually design around. Before you talk to anyone about building anything, get specific about what you need the site to accomplish.

Is the goal more leads through a contact form? More phone calls? Online sales instead of in-person only? Better credibility when a prospect Googles you mid-negotiation? Fewer support questions because information is finally easy to find?

We worked with a client who initially described their goal as “a more professional-looking site.” A few questions in, it became clear the real issue was that 80% of their enquiries came from word-of-mouth, and their existing site actively lost the referrals who tried to look them up — no pricing guidance, no service area listed, no way to book a consultation. Aesthetics were part of the answer, but the actual goal was capturing warm referral traffic that was arriving and leaving with no next step. Every subsequent decision — structure, content, forms — got easier once that was named clearly.

Write your goal down in one sentence before you go any further. If you can’t, that’s worth sitting with before spending anything.

Audit What You Already Have

If you have an existing site, don’t treat it as a clean slate to throw away. It’s a source of information, even if it’s ugly or outdated.

Look at your analytics if you have them set up: which pages get the most traffic, where visitors are coming from, which pages people actually convert on. If a handful of blog posts or service pages are quietly ranking on Google and bringing in steady traffic, that’s something a redesign needs to protect, not accidentally delete. We’ve seen businesses relaunch a fresh, better-looking site and lose a chunk of their organic traffic within weeks, simply because well-ranking URLs were renamed or removed with no redirects in place.

Even without analytics, a basic audit is useful. Which pages get outdated fastest? What do people ask you that isn’t answered anywhere on the site? What do you personally find annoying about it? This isn’t wasted time before the “real” work starts — it’s information that shapes the real work.

Know Your Audience Better Than Your Competitors’ Websites

It’s tempting to start a website project by browsing competitor sites and collecting ones you like. There’s nothing wrong with reference points, but they can quietly steer you toward decisions that suit someone else’s audience, not yours.

Before you brief anyone, get clear on who’s actually supposed to use this site. A business selling premium custom furniture and a business selling fast, affordable moving services are both “local service businesses,” but their ideal customer arrives with completely different expectations, patience levels, and questions. One might browse slowly and want rich photography and a considered story. The other wants a quote and a phone number within ten seconds of landing.

If you serve more than one type of customer — say, both retail and wholesale, or both residential and commercial clients — decide upfront whether the new site needs to speak to both, and how it will separate those journeys instead of mashing them into one generic homepage.

Understand What the Budget Actually Needs to Cover

A common source of frustration later in a project is discovering that “the website” was never really one line item. Design and development are usually the biggest cost, but they’re rarely the only one.

Domain and hosting are ongoing, not one-time. Content — professional copywriting, photography, product descriptions — is often underestimated and delivered late, which stalls timelines more than almost anything else. SEO setup, whether basic technical foundations or a fuller strategy, is worth budgeting for separately if it matters to you. Ongoing maintenance, security updates, and small changes after launch add up over a year, even for a simple site. If you’re moving from an existing platform, migration work — especially preserving SEO value — can be its own line item.

None of this means a website has to be expensive. It means going in with a realistic picture of the full cost prevents the awkward moment three months in where “just add this one feature” turns into an unplanned invoice.

Get Your Content and Assets Together Before You Start

This is the step most commonly skipped, and it’s the one that quietly derails more timelines than anything technical. A developer can build a fast, well-structured site in weeks. What stalls projects for months is waiting on final copy, waiting on product photography, waiting on someone internally to approve the About page text.

Before development starts, try to have at least a working draft of your core content — what each main page needs to say, your logo and brand assets in usable formats, real photography rather than placeholders you’ll “swap later,” and any testimonials, certifications, or case studies you want featured. You don’t need it perfect. You need it started, so it isn’t the thing holding up launch.

Decide on Scope Before You Ask for Quotes

Vague scope produces vague quotes, and vague quotes are hard to compare fairly. Before reaching out to agencies or freelancers, get specific about what the site actually needs to do.

Does it need e-commerce, and if so, how many products, and what payment methods? Does it need booking or scheduling functionality? Multiple languages or currencies? Integration with a CRM, email marketing tool, or inventory system you already use? Roughly how many pages, and is there a blog component?

You don’t need to have this fully engineered — that’s what a good developer helps you refine — but arriving with a rough scope means every quote you receive is answering the same question, instead of three agencies pricing three different imagined projects.

Vet Who You’re Hiring, Not Just What They Charge

Price comparisons across agencies and freelancers are often comparing incomparable things. A quote that’s half the price of another is sometimes a legitimately better deal, and sometimes a sign that ongoing support, revisions, or basic SEO groundwork simply aren’t included.

Ask to see actual, similar work — not just a portfolio page, but a live site they built for a business in a comparable industry or with comparable complexity. Ask what happens after launch: is there a maintenance plan, who fixes something if it breaks, what a future content update costs. Ask how they handle SEO fundamentals, even if SEO isn’t the main service — a site that’s technically sound from day one saves you from paying someone else to fix it in six months.

A slightly higher quote from someone who asks good questions about your business goals is often the better investment than a lower one from someone who just wants a spec sheet.

Protect Your Existing SEO If You’re Redesigning

If you’re replacing an existing site rather than building a first one, this deserves its own line of attention. Search engines have indexed your current pages, and some of them are likely already generating traffic you don’t want to lose.

Before a redesign begins, get a list of your current URLs, especially any pages ranking well or bringing in steady traffic. Make sure your developer has a plan for 301 redirects from old URLs to their new equivalents, rather than letting old pages quietly 404 after launch. If page structure or navigation is changing significantly, flag which content absolutely needs to carry over versus what can be safely retired.

We’ve inherited more than one project where a previous redesign, done by a different provider, wiped out years of organic traffic simply because nobody thought to map old URLs to new ones. It’s a straightforward fix when planned for in advance, and a genuinely painful one to recover from afterward.

Set Goals You Can Actually Measure After Launch

Decide before launch how you’ll know if the new site is working. This sounds obvious, but it’s frequently skipped, which means three months after launch nobody can say with confidence whether the investment paid off.

Pick a small number of concrete things to track — form submissions, calls, online orders, newsletter signups, whatever maps to your actual business goal from step one. Make sure analytics and, if relevant, conversion tracking are set up before launch, not added as an afterthought once someone asks for a report. A website without a way to measure its own performance is much harder to improve later, because there’s no baseline to improve from.

The Real Cost of Skipping This

None of the steps above require a developer, a designer, or a budget. They require an hour or two of thinking clearly about your business before you hand a brief to someone else. Skip them, and the most common outcomes are a project that runs over budget because scope kept shifting, a launch that gets delayed because content wasn’t ready, or — most frustrating of all — a finished site that looks perfectly fine and still doesn’t move the numbers that mattered in the first place.

At Infyras, the projects that go smoothest and perform best almost always start with a client who’s done some version of this groundwork before the first design conversation. Our job is to translate clear goals into a site that’s fast, well-structured, and built to convert — but that translation works best when the goals are actually clear going in. If you’re still figuring out that part, it’s worth spending the time there first, before spending anything on the build itself.