Sixty-four percent of corporate digital footprints are actually just a collection of personal favors masquerading as infrastructure.

That number sounds high until you are the one sitting in the chair on a Tuesday morning, trying to figure out why the “Contact Us” form has stopped sending emails. You check the settings, and you see that the SMTP relay is tied to an account labeled “[email protected].”

Brian hasn’t worked for the company since the Obama administration. Brian is currently living his best life as a surf instructor in Costa Rica, and Brian’s old Gmail account was just deactivated for inactivity. Suddenly, your multi-million dollar lead generation engine is a silent engine because it was built on the back of one man’s private convenience.

The Agility Trap

I recently lost an argument about this. It was a heated, circular debate with a Director of Operations who insisted that requiring every single API key and login to be stored in a centralized, encrypted vault was “unnecessary friction.”

He told me that we needed to be “agile.” He said that the team needed to “move fast and break things.” I told him that what they were actually doing was “moving fast and leaving landmines for their future selves.” I was right, but I lost the argument anyway because “agility” is a sexier word than “governance.”

Now, Owen is living in the wreckage of that agility.

Owen’s Digital Archaeology

Owen is on day four of his new role as a Digital Product Manager. He has a browser window open with nine different tabs, all of them variants of the “Forgot Password” screen. He is trying to get into the DNS registrar because the SSL certificate is about to expire, and the site will be flagged as “Unsafe” by Chrome in forty-eight hours.

The registrar, a company with a user interface designed in 2004, informs him that a password reset link has been sent to an email address ending in @compuserve.com.

Owen stares at the screen. He doesn’t even know if the company ever had a CompuServe account. He finds a Slack message from March 2021-a digital fossil-where a developer named Marcus told a project manager that he had “put the domain on his personal card to save time” because the corporate procurement process took three weeks. Marcus is now a VP at a rival firm. Marcus is not answering his LinkedIn DMs.

This isn’t just a “bad handover.” This is the default state of the modern web. We like to think of institutions as monolithic entities that own their assets, but they aren’t. They are loose confederations of individuals who use their own accounts, their own credit cards, and their own memory to keep the lights on.

Every time someone leaves a company, they take a small piece of the organization’s brain with them. Sometimes, it’s just the password to the stock photo account. Other times, it’s the only login for the server that hosts the entire legacy product catalog.

Learning from the Infrastructure of Care

In my other life, I spend a lot of time around guys like Ian T.-M. Ian is a medical equipment installer. He handles C-arms and surgical imaging suites-machines that cost more than a suburban house and can accidentally cook a patient if they aren’t calibrated correctly.

“Infrastructure is not an opinion; it is a physical reality that demands documentation.”

– Ian T.-M., Medical Equipment Specialist

When Ian walks into a hospital to install a new imaging table, he expects a blueprint. He expects to know exactly where the lead shielding is in the walls and where the high-voltage lines are buried in the floor. If the hospital doesn’t have the map, Ian doesn’t drill. He waits until they find the map.

Web development has somehow escaped this rigor. We treat websites like they are ethereal, floating in a “cloud” that manages itself. But the cloud is just someone else’s computer, and you still need the keys to the front door.

The archaeology of a website usually begins with the “View Source” button, but it quickly moves into the realm of private detective work. You start looking at the billing history in the accounting software, trying to find a charge for $14.99 that repeats every year. You find the name of a vendor you’ve never heard of.

You call them, and they tell you they can’t talk to you because you aren’t an “authorized contact” on the account. The authorized contact is, of course, the surf instructor in Costa Rica.

Companies don’t rebuild because they want a new look; they rebuild because they have lost control of the old one. They are squatters on their own domain. They are paying a hosting fee to a company they can’t log into, for a site built on a CMS that hasn’t been updated in three years because the developer who knew the “super-admin” password moved to Berlin and changed his phone number.

When a team like

Coherent Agency

steps into a mess like this, the first task isn’t design. It isn’t even strategy. It’s a technical audit that looks more like a forensic crime scene investigation.

You have to map the dependencies. You have to find out where the GSAP animations are pulling from, why the Lottie files are hosted on a private Dropbox link, and who actually owns the Webflow account where the site lives.

The shift from “designer” to “engineer” happens when you realize that a pixel-perfect layout is worthless if the client doesn’t actually own the pixels. If the SEO strategy is built on a foundation of “someone’s cousin’s personal Google Search Console account,” then the strategy is a ghost. It exists only as long as the cousin stays friendly.

Digital Hostage-Taking vs. Managed Services

We see this most often with marketing leaders who inherit a site from a previous vendor who used a “black box” approach. The vendor says, “Don’t worry about the technical stuff, we handle it all.” What they really mean is, “We are going to make it impossible for you to ever leave us because we hold all the keys.”

It’s a form of digital hostage-taking that is often disguised as “managed services.” But let’s be honest: half the time, it isn’t malice. It’s just laziness. It’s easier to use your own GitHub account than to wait for IT to provision a corporate one.

It’s faster to use your own credit card for a $9-a-month plugin than to fill out an expense request. We trade institutional security for five minutes of personal convenience, and then we forget we ever made the trade.

Owen eventually finds a workaround. He spends six hours on the phone with the registrar’s “legal and brand protection” department. He has to provide a notarized letter on company stationery, a copy of the articles of incorporation, and a photo of his own driver’s license just to prove that the company actually owns the company name.

It’s a humiliating process. It makes him feel like a thief in his own office. And even after he gets the DNS back, he still doesn’t have the keys to the analytics.

Five years of traffic data, conversion metrics, and user behavior patterns are locked away in a “Property” that was created by an intern in 2018 using a personal Yahoo email. That data is gone. You can’t get it back. You just have to start over from zero, like a person who woke up with amnesia and has to be told their own name.

The Hidden Tax

The average cost of a “rescue” project because the old site is a black box no one can open.

This is the hidden tax of “moving fast.” We think we are saving money by skipping the documentation and the “friction” of centralized ownership. But the tax always comes due. It comes due in the form of Owen’s lost week. It comes due in the form of a $50,000 “rescue” project because the old site is a black box that no one can open.

The inbox is a cemetery where the only living things are the bills no one can pay.

I still think about that argument with the Director of Operations. I think about it every time I see a “Site Not Found” error or a broken API connection. We are obsessed with the “front end”-the colors, the fonts, the “vibe.” But the back end is where the power lives. Ownership is a technical requirement, not a legal suggestion.

Fragile Institutional Memory

If you don’t have a map of your digital assets, you don’t own them; you are just renting them from the past versions of your employees. And those people are moving on. They are getting married, moving to different cities, and forgetting the passwords they made up on a Tuesday afternoon three years ago.

Institutional memory is a fragile thing. It’s not held in the “culture” or the “mission statement.” It’s held in the .env files, the password managers, and the billing department’s spreadsheets.

If those things aren’t aligned, the institution isn’t an institution. It’s just a group of people standing in a room, hoping the lights stay on, while the guy who knows where the fuse box is just boarded a flight to San Jose.

We need to start treating our digital presence with the same gravity that Ian T.-M. treats a surgical suite. We need to stop “guessing” where the power lines are. We need to demand that our agencies and our internal teams provide not just a finished product, but a complete map of how that product exists in the world.

Because eventually, there will be another Owen. And he’s going to be sitting there with nine tabs open, wondering why no one cared enough to leave him the keys.

The goal isn’t just to build a website. The goal is to build something that the company can actually hold onto. Anything less isn’t engineering; it’s just a very expensive temporary installation.

And in a world where your website is your primary interface with the public, “temporary” is a very dangerous word to live by.