How to Get a Website Budget Approved Internally

The website is seven years old, barely usable on a cell phone, and a nightmare to work with on the backend. Everyone in marketing knows this. The agency’s proposal is on the table. And then the management team says the one thing that brings the project to a halt: “Do we really need this right now?”

We encounter this situation regularly. Not when it comes to deciding which agency to choose, but much earlier. Marketing managers come up with a solid concept and a well-put-together proposal, and yet nothing happens for months.

The reason is rarely the amount. It’s because the proposal is written in a language that sounds convincing in marketing but doesn’t resonate with management.

Why Good Arguments Don’t Work

The typical reasons given for a relaunch are technically sound. The site isn’t responsive, the load times are slow, the design looks outdated, and the CMS is cumbersome. Every single point is accurate.

From a CEO’s perspective, however, they all describe the same thing: a situation that has existed for a long time and that the company has managed to cope with so far. A situation is not a reason. If you’ve been putting up with a bad website for seven years, you can certainly put up with it for an eighth year as well.

What’s missing is the cost of this situation. As long as the old website seems to cost nothing, any investment in a new one is purely an expense. As soon as it has a cost, it becomes a comparison between two amounts. And comparisons are something we decide on.

The Cost of Doing Nothing

The most significant figure in any website proposal isn’t the asking price. It’s the amount the existing site burns through each year.

This can be reliably estimated in three ways. The first is lost leads. If your site has 2,000 visitors per month and generates twelve leads, the conversion rate is 0.6 percent. A solid B2B rate is between one and two percent. That difference amounts to eight to fourteen inquiries per month that simply aren’t being generated. Your sales team knows how much each acquired inquiry is worth to you. When you add these two figures together, the result is usually a number greater than the entire project budget. This is exactly where conversion optimization comes in.

The second area is sales. Ask two or three colleagues how often they have to send documents via email because the website doesn’t provide them. Calculate the total number of hours. This figure regularly surprises company presidents because it doesn’t appear in any report.

The third area is job applications. Anyone looking for a job today checks out the website before applying. The HR department can tell you how much it costs to leave a specialized position unfilled for a year. A single missed hire often weighs more heavily than a complete website relaunch.

Three numbers you’ll need beforehand

A proposal without numbers is just an opinion. That’s why there are three metrics you should know before going into the meeting: the number of inquiries received through the website, the average value of a new contract, and the load time of your most important pages.

You can get the first two from Sales and Analytics and Tracking; the third one takes five minutes using PageSpeed Insights. By the way, if you don’t have the first number because nothing is being measured properly, that in itself is already a valid point. A company that doesn’t know how many requests its website generates is making all decisions about it blindly.

The Comparison You Don’t Have to Fear

Take your three main competitors and put their websites side by side with yours. Not as a screenshot in a presentation, but live during the meeting, on your phone.

This moment has a stronger impact than any line of reasoning. CEOs rarely visit their own company’s website and almost never visit a competitor’s. The direct comparison answers the question of urgency without a single adjective. It also shows that web design isn’t about taste, but about who a prospective client trusts to solve their problem.

Steps Instead of All-or-Nothing

A request for 80,000 euros is reviewed. A request for 5,000 euros is approved. This isn’t a tactic—it’s a matter of approval thresholds, and you can take advantage of them.

A website audit at the outset costs a fraction of the project’s total cost and provides exactly what the proposal is missing: concrete findings instead of estimates. Afterward, everyone is on the same page regarding the facts. “The marketing department wants a new website” becomes “We have a quantified problem and know what it will cost.”

Then break the project down into sections that work on their own. Start with the concept and structure, then move on to design and implementation, followed by content and visibility. Each section has its own deliverable, and after each one, management can reassess the project. This makes the project feel less overwhelming without actually making it any smaller.

The business should be included in the same application

A mistake we often see: The application covers only the project. A year later, the next one comes along—this time for website maintenance, hosting, and upkeep. This makes you look like someone who didn’t think things through, and the second application is much more difficult to process.

Be upfront about the ongoing costs from the very beginning. As a rule of thumb, they’ll amount to roughly the project budget over three years. This openness may cost you a bit of buy-in during the first meeting, but it will save you a lot of explaining later on.

Conclusion: Let the other side do the math

A website budget isn’t approved because the old site is bad. It’s approved because someone calculated how much it costs.