You are looking at the pricing page and the number is wrong. It is Tuesday afternoon and the sun is low and the light hits the dust on your monitor. The price says forty-nine dollars and it has said forty-nine dollars for three weeks. The price should be fifty-nine dollars. You feel a small heat in your neck and you click the mouse. You highlight the four and you try to type a five but the screen does not change. You are in a browser and the browser is a window but the window is locked. You cannot reach through the glass.

Priya sits in the chair across from the window and she sees the same number. She is the head of marketing and she knows the math. Every person who clicks the buy button is seeing a ghost. They are seeing a price that does not exist in the bank. She opens the Slack channel and she finds Marcus. Marcus is the lead developer and his icon is a gray circle. She types the message and she says the price is wrong on the landing page. She adds an exclamation mark and then she deletes it. She puts the exclamation mark back because the error is costing money and the money is real. She hits the enter key and she waits.

Line One Hundred and Twelve

Marcus sees the notification and he sighs. He is deep in a database migration and the migration is delicate. He has a spice rack at home and he spent Sunday morning alphabetizing it because order is the only thing that keeps the world from breaking. He likes order and he likes clean code. He looks at the landing page and he sees the forty-nine. He knows exactly where that number lives. It lives in a file called PricingTable.js on line one hundred and twelve. It is tucked between a div tag and a closing bracket. It is a string of text and the text is hard-coded.

He does not change the number. He cannot just change the number and hit save. He types a reply and he gives a thumbs-up emoji. He pastes a link to a Jira ticket. The ticket is number thirty-four on the board. The board is full of cards and the cards represent the life of the product team. There is a bug in the payment gateway and there is a slow load time on the dashboard. The typo is now a ticket and the ticket is at the bottom. It is tagged with the word ‘website’ and it waits.

This is the moment the machine stops. The stutter is not a person and it is not a lack of effort. The stutter is the architecture. Months ago a developer wrote the code for the pricing page and they were in a hurry. They did not create a field in the content management system. They did not make the price a variable that a human could edit. They wrote the four and the nine into the script and they pushed it to the repository. They built a house and they bricked up the windows.

The Maintenance Diver’s View

I spend my mornings as an aquarium maintenance diver and I see this in the water. People build beautiful tanks and they fill them with life but they forget that life creates waste. They put the filters in places where no hand can reach. They hide the pumps behind heavy rocks. When the algae grows and the glass turns green the owner must drain the whole tank just to scrub a stone. A website is a tank. If you have to break the glass to change the water then the design is a failure.

The Heavy Weight of Deployment

A build pipeline is a heavy thing and you should understand how it works. When Marcus eventually decides to fix the four characters he must create a new branch in the version control system. He changes the four to a five and he saves the file. He pushes that change to a server in the cloud. A robot starts to run. The robot checks the code for errors and the robot builds a preview version of the site. Marcus looks at the preview and he sees the fifty-nine.

He asks another developer to look at the change. The other developer is busy but eventually they click a button to approve it. Then the robot runs again and it merges the change into the main code. It deploys the site to the live servers. This process takes twenty minutes of machine time and two hours of human focus. It requires a deployment cycle. This is why the typo takes eleven days.

Priya is waiting and the days go by. She is a professional but she feels the friction. She wants to test a new headline and she wants to add a disclaimer about the holiday shipping. She cannot do these things. She must ask Marcus and Marcus must ask the robot. The marketing team is a driver who cannot turn the steering wheel. They must send a letter to the engine room and the engine room is busy shoveling coal.

The Taste of Copper

The cost of this delay is invisible but it is heavy. A customer reads the forty-nine dollars and they click the button. They get to the checkout and the price becomes fifty-nine dollars. They feel a small sting of betrayal and they close the tab. A salesperson gets a lead and the lead mentions the lower price. The salesperson must apologize and the apology tastes like copper. The brand is a collection of promises and the promises are drifting out of sync.

The problem is not that Marcus is mean or that Priya is demanding. The problem is a modeling decision made in a meeting that nobody attended. When you treat language as an engineering artifact you commit to engineering speeds. You decide that a comma is as heavy as a database schema. You decide that the person who knows the customer best should have the least amount of power over the words the customer reads.

The Five-Second Standard

We see this at Coherent Agency and we build against it. A site should be a tool for the people who use it to grow the business. It should not be a hostage situation. We use Webflow to build the front end and we build the CMS with intention. We find every price and every headline and every image. We turn them into fields. We give the keys to the people who own the strategy.

When the price changes the marketing lead opens the dashboard and they type the new number and they hit publish. The change is live in five seconds. There is no Jira ticket. There is no deployment cycle. There is only the work.

The Architect and the Smudge

Marcus wants to work on the app. He wants to solve the logic of the database and he wants to optimize the API. He does not want to change a four to a five. Every time he has to open the website code to fix a typo he loses his flow. He loses the thread of the complex problem he was hired to solve. He is an architect who is being asked to come over and wipe a smudge off the window. It is a waste of his mind and it is a waste of the company’s money.

The wall between the code and the content is where the arguments live. When you decouple the two you remove the friction. You allow the developers to move fast on the product and you allow the marketers to move fast on the message. You create a system where the site can evolve as quickly as the conversation.

You are still looking at the screen and it is Friday now. The forty-nine is still there. You have alphabetized your spice rack and you have checked the Jira board. The ticket is now number twenty-eight. It has moved up six spots in four days. You realize that at this rate the price will be correct by next Thursday. By then the promotion will be over and the price will need to change again. You will open another ticket and Marcus will give you another thumbs-up and the cycle will begin again.

If you want to change the world you have to be able to change the words. If the words are buried in the engine you will never be able to speak clearly. You will always be shouting through a wall. You deserve a site that listens to you. You deserve a system where a four can become a five without a meeting or a sprint or a eleven-day wait.

You deserve to own your own voice.