Sophie J. was elbow-deep in a CSS override that hadn’t been touched since 2017, a digital archaeologist trying to find the foundation of a marketing page that had, at some point, decided to stop respecting the laws of physics. She wasn’t just fixing a margin; she was excavating a layer of intent that had long since been abandoned. The site was built on a stack that looked like a Jenga tower during a minor earthquake. Marketing had their Webflow setup for the main site, Sales was churning out Unbounce pages for every localized campaign, and the Product team-bless their hearts-had just migrated their entire documentation to Framer because the animations felt ‘more organic.’ Meanwhile, the CEO’s pet project, a micro-site for a charity auction, was sitting on a Carrd account tied to a personal Gmail address that no one in the 107-person company had the password for.

It felt a bit like the time I found a $20 bill in my old jeans last Tuesday. For about 7 minutes, you feel like the world is rewarding you for nothing. It’s a small, unearned win. You think about buying a fancy coffee or a notebook you don’t need. But then you realize that $20 was only there because you were disorganized enough to lose it in the first place. You didn’t find money; you just recovered a tiny fraction of your own previous negligence. No-code is the same. We found this ‘free’ productivity in the pockets of our departments, and we celebrated it as a revolution. We told ourselves that democratizing creation meant everyone could be an architect. What we didn’t realize is that if everyone is an architect but no one is a city planner, you don’t get a city. You get a digital favela.

Sophie J. often says that the most dangerous thing you can give a creative director is a tool that doesn’t require a ticket to the engineering team. In the old days-let’s call them the ‘Dark Ages of 2007’-if you wanted to change a hero image, you had to beg a developer. It was slow. It was agonizing. But it was governed. There was a single source of truth, a repository that lived in one place, and a deployment pipeline that ensured the brand didn’t look like a ransom note. Today, the velocity is intoxicating. A marketing manager can spin up a site in 47 minutes. They can add a tracking pixel with a click. They can integrate a form that sends data to a random Google Sheet that isn’t HIPAA compliant because ‘we just needed to test it.’

The Cost of Speed

This is the democratization trap. We traded coherence for speed, and now we are paying the interest on that debt. The analytics are scattered across 7 different dashboards. The brand identity is a suggestion rather than a rule, with 17 different shades of ‘company blue’ appearing across various subdomains. IT security is currently staring at a backlog of 237 unsanctioned SaaS tools, most of which were signed up for with a corporate credit card and a ‘trial’ that never ended.

The Ghost Stack

[The architecture of a company is not measured by the tools it uses, but by the spaces between them.]

We talk about ‘moving fast and breaking things,’ but we rarely talk about who has to sweep up the glass. Sophie J. is the one sweeping. She finds these rogue sites when a customer complains that the ‘Contact Us’ button on a landing page from three years ago is sending emails to a former employee who left in 2017. It’s functional locally-the page looks great, the form works, the data goes *somewhere*-but it’s unstable collectively. It doesn’t scale. It’s a shed built on top of a porch built on top of a basement that was never meant to hold that much weight.

I remember sitting in a meeting where the Head of Growth was bragging about how they had bypassed the dev queue by using a third-party builder. They saved $7,777 in internal billing. Everyone cheered. But six months later, when the company underwent a rebrand, that ‘saved’ money was spent tenfold trying to find all the places that growth team had hidden their custom pages. It was like finding that $20 bill again, only to realize you had used it to pay for a subscription that cost $207.

There is a specific kind of vertigo that comes from realizing your company’s digital presence is held together by Zapier tasks and good intentions. We’ve reached a point where the tools are so good at empowering the individual that they’ve become experts at undermining the collective. The centralization of infrastructure is often seen as a bottleneck, but in reality, it’s the only thing that keeps the favela from collapsing. We need a way to connect these disparate islands of productivity without stifling the creativity that birthed them. We need a way to ensure that when a developer makes a change to the core API, 47 different landing pages don’t suddenly go dark.

Towards a Digital City

This is where the conversation shifts from ‘how do we build’ to ‘how do we manage.’ The promise of no-code was never meant to be a license for chaos. It was meant to be a liberation of the logic, not an abandonment of the structure. When you look at the way

Hilvy

approaches the problem, you start to see the possibility of a middle ground. It’s not about taking the tools away from the Marketing or Sales teams; it’s about giving them a foundation that is actually connected to the rest of the organization. It’s about building on a platform that understands that a web presence is an ecosystem, not a series of one-off experiments.

Sophie J. recently showed me a spreadsheet she uses to track what she calls ‘The Ghost Stack.’ It’s a list of 37 URLs that the company owns but hasn’t officially updated in years. Some of them still have the ‘Built with…’ badges on them. Some of them are using fonts that haven’t been licensed since the late 2010s. She treats it with a mix of humor and exhaustion. She knows that as long as the democratization of tools is conflated with the abandonment of standards, her job will always exist. She will always be digging through the strata of forgotten experiments.

I found myself thinking about that $20 bill again while I was watching her work. It’s a distraction. A small, pleasant surprise that masks a larger problem of fiscal or digital awareness. We feel productive because we are busy building, but building isn’t the same as growing. Growing requires a root system. It requires a shared language. If the Marketing team is speaking Webflow and the Product team is speaking Framer and the IT team is speaking ‘Please Stop,’ the result isn’t a conversation; it’s a cacophony.

We need to stop praising the speed of the individual at the expense of the integrity of the whole. The local optimization of a single landing page is worthless if it creates a global incoherence that confuses the customer and terrifies the security team. We are currently living through the ‘Favela Phase’ of the internet, where we are building faster than we can plan. It’s exciting, sure. It’s vibrant and chaotic. But eventually, you want to live in a house that won’t fall down when the wind changes.

[Governance is the only thing that turns a collection of tools into a platform.]

Sophie J. finally found the bug. It wasn’t in the CSS. It was a script being pulled from a CDN that had been deprecated 7 years ago, hidden inside a custom code block on a ‘fast’ landing page. It took her 47 minutes to find it and 7 seconds to fix it. The irony wasn’t lost on her. The tool that was supposed to save time ended up costing more in the long run because it was built in a vacuum.

I think we’re starting to see a shift, though. People are getting tired of the fragmentation. They’re getting tired of having to log into 17 different accounts to change a logo. There’s a growing appetite for platforms that offer the ease of no-code with the rigor of enterprise architecture. We want the $20 in our pocket, but we also want a bank account that we actually track.

Democratization is a beautiful word, but it’s a heavy responsibility. If we are going to give everyone the power to build, we have to give them the framework to build responsibly. Otherwise, we’re just handing out hammers in a glass house. The future isn’t about choosing between speed and stability; it’s about finding the tools that allow them to coexist. It’s about building a digital city that actually makes sense, where every building, no matter how small or specialized, is part of the same map.

As Sophie J. closed her laptop, she looked at me and asked if I still had that $20. I did. I bought her a coffee. It was the least I could do for the person tasked with keeping our digital favela from burning down for one more day. We need more city planners and fewer accidental archaeologists. We need to start building like we plan to stay here for more than 7 minutes.