A $4,000 unlacquered brass faucet sits on the edge of a marble island in a kitchen that cost more than my first three cars combined. It is a beautiful object. It is heavy, cold to the touch, and designed to patina over time, gaining character as it interacts with the oils of human hands.

But if you don’t install the right filtration system three rooms away, or if you ignore the slow buildup of calcium in the pipes, that faucet eventually becomes a very expensive paperweight. It represents the obsession with the “finish” while the “flow” is left to rot. We treat the surface as the asset and the infrastructure as a nuisance.

I started a diet at 4:00 PM today. It is currently 6:14 PM, and I am already convinced that the world is primarily composed of things I cannot have. This deprivation makes me irritable, and when I am irritable, I have very little patience for the way we budget for the internet. I’ve spent years in the orbit of “online reputation management,” and I’ve seen the same pattern repeat until it feels like a glitch in the simulation.

We budget for websites like we budget for kitchen renovations. We save up, we agonize over the color of the cabinets-or the hero section-and then we have a “Launch Day” where we cut a ribbon and assume the work is finished for the next five years. This is a fundamental misunderstanding of the medium. A kitchen is a static arrangement of wood and stone. A website is a living, breathing software environment that is being actively corroded by the salt air of the internet every single second.

The Ritual of Launch Day

The scene usually goes like this: It’s budget season. The CMO sits at a mahogany table or a Zoom grid and asks for $180,000 for a total site rebuild. She explains that the current site is “embarrassing.” It’s slow, the mobile menu jitters like a caffeinated squirrel, and the brand has moved three steps to the left since the last launch. The board or the CEO looks at the numbers, grunts about the cost, and then approves it in nine minutes. It is a Capital Expense. It is a project. It has a beginning, a middle, and a triumphant end.

Then, she asks for $2,500 a month to keep the site healthy-to optimize the schema markup for AI answer engines, to tweak the conversion funnels based on actual user heatmaps, and to ensure the GSAP animations don’t start breaking as Chrome updates its rendering engine.

“Find it in your existing operating line.”

– The CFO’s Response

The room goes silent. They treat the request for continuous improvement as if she’s asking for a gold-plated stapler. To the CFO, the $180,000 was a “fix.” To suggest it needs more money next month feels like admitting the fix didn’t work.

The Accounting Paradox

We would rather pay full price for a car crash every three years than pay for the oil changes that prevent it.

This is the tragedy of the accounting category. Capital projects get ceremony; maintenance gets the axe. And because nothing continuous happens, the site begins to decay the moment the developers hand over the keys. By year two, the visual drift is palpable. By year three, the site is a slow-motion car crash of broken links and outdated content.

Everyone agrees it is embarrassing, and the cycle restarts at full price. We would rather pay $180,000 every three years than $30,000 a year to keep the original investment from dying.

Lessons from the Forth Bridge

There is an industrial precedent for this kind of madness, and it’s found in the history of the Forth Bridge in Scotland. For over a century, “painting the Forth Bridge” was a literal idiom for a task that never ends. Because the bridge is made of steel and sits in the middle of a salt-heavy estuary, the moment the painters finished one end, the other end had already started to rust.

They didn’t paint it because they liked the aesthetic of “International Orange.” They painted it because if they stopped, the bridge would eventually fall into the Firth of Forth. In 2002, they finally applied a new, sophisticated glass-flake epoxy coating that lasts for decades, but the principle remained for 120 years: maintenance is the only thing standing between a masterpiece and a pile of scrap metal.

Digital infrastructure is exactly like that salt air. The “salt” in our world is the constant evolution of browser standards, the shifting algorithms of search engines, and the way users change their behavior. If you aren’t painting your bridge every day, you are just waiting for the collapse.

I’m currently staring at a glass of water and wishing it was a steak. This is probably why I’m thinking about how much we waste by being “efficient” with our budgets.

We think we are being fiscally responsible by refusing retainers. We think we are “buying back our time” by not having to manage a vendor month-to-month. But the “Three-Year Rebuild” is a deferred tax. You are paying for the decay; you’re just paying for it all at once, with interest, while losing three years of potential revenue because your site was underperforming for 75% of its lifespan.

The Age of Answer Engines

A website built today has to do things a website built eighteen months ago didn’t have to worry about. We’ve moved past the era where “SEO” just meant keywords and backlinks. We are now in the age of AEO-Answer Engine Optimization.

If your site architecture isn’t being constantly updated with the specific schema markup that LLMs like Perplexity or ChatGPT use to cite sources, you aren’t just losing rank on Google; you are becoming invisible to the next generation of discovery.

Most internal teams aren’t equipped for this. They are busy. They are trying to get the newsletter out or planning the next event. The website is just a thing they “update” when they have a new PDF to upload. This is why the agency model has to change from “The Build” to “The Partnership.”

You need a team that stays in the code long after the launch party is over. You need engineers who treat a website like a performance vehicle that needs a pit crew, not a statue that needs a dusting.

They aren’t interested in the “rebuild and disappear” model. Their focus is on the long-term ownership of results-ensuring that the branding, the motion work, and the technical SEO are integrated into a system that actually grows over time.

When you have the same team that defined the brand writing the schema markup, you stop having the “visual drift” that kills so many enterprise projects. I remember a client once who spent a quarter of a million dollars on a headless CMS build. It was a marvel of modern engineering. They fired the agency three months later because they “didn’t need them anymore.” They had the tool. They had the faucet.

Two years later, I looked at their site. The GSAP animations were stuttering because of a conflict with a new version of Safari. The images weren’t being served in WebP format because someone had disabled a plugin they didn’t understand. Their “contact us” form had a three-second delay. They had spent $250,000 on a Ferrari and then refused to change the oil. They were shocked when the engine seized.

From CapEx to Humility

We have to stop treating the website as a “thing we did” and start treating it as a “thing we are doing.” The shift from CapEx to OpEx in the digital world isn’t just about accounting; it’s about humility. It’s about admitting that we don’t know what the internet will look like in eighteen months.

It’s about having a team like Coherent Agency on your side that can pivot the strategy as the ground moves. If you wait for the three-year rebuild, you are basically saying you’re comfortable being wrong for two and a half years.

I’ve made this mistake myself. I once convinced a small firm to blow their entire marketing budget on a massive launch, thinking the “momentum” would carry them. It didn’t. Momentum is a fiction in a world where everyone else is sprinting. Without a budget for the “after,” the site became a relic within six months. I felt like a fraud, and quite frankly, I was one. I sold them a renovation when they needed a gardener.

Breaking the Cycle

The diet is still happening. I am currently contemplating the nutritional value of the ice cubes in my glass. But the hunger gives me a certain clarity about what’s necessary versus what’s just “nice to have.” A big, expensive rebuild is a “nice to have” if you don’t have the foundation to maintain it. It’s a vanity project disguised as a business necessity.

If you want to break the cycle, you have to change how you talk to the person with the checkbook. You have to explain that the $180,000 is the entry fee, not the total cost of ownership. You have to advocate for the “boring” work-the constant testing, the structural tweaks, the performance monitoring. You have to convince them that the bridge needs to be painted while it still looks perfect, not when the rust is visible from the shore.

Because once the rust is visible, the price of the repair isn’t just the paint. It’s the cost of the steel you have to replace. And in the digital world, that steel is your brand’s reputation, your search ranking, and the trust of your users.

It’s time to stop budgeting for the brass and start budgeting for the water. The best websites aren’t the ones that were launched most recently; they are the ones that have been loved most consistently. If you’re tired of the three-year rebuild, stop treating your site like a renovation. Start treating it like a bridge. Find the people who will help you paint it, every single day, so it never has the chance to decay.

Now, if you’ll excuse me, I’m going to see if there’s any caloric value in a stick of gum. Probably not. But then again, I’ve always been one for structural neglect when it comes to my own “maintenance.” Don’t be like me. Be like the Forth Bridge. Stay coated. Stay intact.