How Much of Your Budget Should Actually Go to Your Website

"What should we budget for the website" is one of the most common early questions in any new project, and it's usually asked as if there's a standard answer — a percentage of revenue, a rule of thumb, a number that applies broadly across different businesses and situations. In practice, the honest answer depends heavily on what the site is actually being asked to do for the business, which varies enormously from one situation to the next.

Why a flat percentage rule doesn't hold up

Generic budgeting rules of thumb — "spend X percent of revenue on your website," "budget Y dollars per employee" — tend to break down quickly once you look closely, because they don't account for what's actually the determining factor: how directly the website is connected to revenue for this specific business. A business that generates the large majority of its new customers through its website is in a fundamentally different situation than a business where the website plays a smaller, supporting role alongside referrals, foot traffic, or an existing sales team. The first business is underinvesting if it applies the same modest budget the second business might reasonably use.

The more useful question to ask instead

Rather than starting from a percentage, start from a specific question: what is the website's job, concretely, in this business's actual customer journey? If the website is expected to be the primary way new customers find and evaluate the business — the case for most businesses relying heavily on search, ads, or social traffic — it deserves a level of investment proportional to that responsibility, because it's effectively functioning as the primary salesperson, available continuously, for every visitor who arrives without any other context about the business.

If the website plays a smaller, confirming role — most customers arrive through referral or an existing relationship and use the website mainly to verify legitimacy before committing — a more modest investment, focused on clarity and trustworthiness rather than elaborate functionality, is usually the right call.

A more useful framing than a percentage

Rather than asking "what percentage of revenue," it's often more productive to ask "what would it cost, in lost opportunities, if this specific page or site didn't exist or didn't work well." For a landing page that's the primary conversion point for paid advertising, that cost is direct and calculable — every visitor who arrives and doesn't convert due to a weak page is a specific, quantifiable loss on ad spend that already happened. For a supporting page that a small share of visitors check before an already-likely purchase, the cost of it being mediocre is real but smaller and harder to isolate precisely.

This framing tends to produce more sensible budget allocation than a flat percentage rule, because it directs resources toward the parts of the digital presence doing the most actual work, rather than spreading budget evenly across a site regardless of which pages matter most to the outcome.

Where businesses most commonly under- and over-invest

Under-investment shows up most often in the page or pages doing the heaviest conversion lifting — a primary landing page treated as a minor detail when it's actually the site's most consequential piece, simply because it's "just one page" rather than the whole site. Over-investment shows up most often in elaborate features and pages that see little real traffic or influence on the actual decision to buy — an ambitious members' portal or resource library built before there's any evidence customers want it, at the expense of the core pages that are already proven to matter.

A practical starting approach

Identify which specific page or pages in the digital presence are doing the most actual work in converting visitors into customers. Concentrate the available budget there first, funded properly rather than thinly spread. Expand into supporting pages and additional functionality only once there's real evidence — traffic, conversion data, direct customer feedback — that they'll be used and that they matter.

Comparing two businesses with the same revenue

A software consultancy and a neighborhood café might have comparable annual revenue, but their websites are doing entirely different amounts of work. For the consultancy, the website is very often the first and sometimes only touchpoint a prospective client has before deciding whether to reach out — it's functioning as the primary salesperson, and underinvesting in it directly caps how many of those prospects ever convert into a conversation at all.

For the café, most customers arrive through walking past, a friend's recommendation, or a delivery app listing — the website mainly needs to confirm hours, location, and menu clearly, a smaller and less consequential job. Applying the same budget logic to both businesses, purely because their revenue happens to be similar, would systematically underfund the consultancy's most important growth lever while potentially overspending on features the café's website doesn't actually need to do its comparatively modest job well.

Why cheaper options often cost more in the long run

A pattern worth naming directly: a business that treats the website budget purely as a cost to minimize, rather than an investment to size appropriately, often ends up spending more in total than a business that budgeted realistically from the start — just spread across multiple smaller, less effective attempts instead of one properly resourced one. A minimal initial build that doesn't actually convert well gets patched, then redesigned, then patched again, each round consuming budget and time without ever reaching the quality bar that would have made the first attempt work if it had been resourced properly from the outset.

This isn't an argument that more expensive automatically means better, or that every business needs a large website budget regardless of its actual situation — plenty of businesses are well served by a modest, focused investment, as discussed elsewhere. It's an argument against the specific pattern of chronic underinvestment followed by repeated, incremental fixes, which frequently costs more in total, in both money and lost opportunity during the underperforming periods, than a single properly scoped investment would have.

Revisiting the budget as the business changes

A website budget decided once, at launch, and never revisited is its own kind of mistake, independent of whether the original number was right. As a business grows, the website's role in the customer journey can shift substantially — a business that initially relied mostly on referrals may find, a few years in, that a growing share of new customers are arriving through search or social channels instead, meaning the website's importance in the overall customer journey has quietly increased without anyone deciding it should.

Revisiting the "what job is the website actually doing now" question periodically — not just once at launch — keeps the budget aligned with the website's actual current role, rather than a role it may have outgrown or shifted away from since the original decision was made.

The takeaway

There's no universal number that correctly answers "how much should a website cost" across every business. There is a reliable method: identify what the site is actually being asked to do in the business's specific customer journey, and let that — not a generic percentage — determine where the budget goes and how much of it a particular page or feature genuinely deserves.