How many layers of permission do you think you can survive before you stop being a builder and start being a person who manages the waiting?

You sit there and you look at the ticket and you know the code is right and the logic is sound and the message is honest. You only want to tell a human being that their package is on the way or that their password has been reset or that their food is getting cold on a porch. But the system says you cannot talk to them yet and it says you must ask for leave to speak and it says you must wait for a stranger to read your words.

The stranger does not know your business and the stranger does not care about your customer and the stranger only knows the rules in a book that you cannot see. You find yourself in a room where the light is too bright and you are staring at a shared spreadsheet that has nineteen rows and each row is a failure.

Column E: Where the Pain Lives

Column A holds the text you wrote and you thought it was simple and you thought it was clear. You wrote that the order is confirmed and you thought that was a good thing to say to someone who just gave you money. Column D holds the rejection reason and it is never a sentence but it is always a code like 1004 or 4002 or a string of letters that look like a cat walked across a keyboard.

Column E is the place where the pain lives and it is the column added by a developer in week three and it holds the guesses about what the codes actually mean. We think 1004 means the word confirm is too strong and we think 4002 means the greeting is too friendly or perhaps it is not friendly enough and nobody knows for sure. You spend your Tuesday changing words and you spend your Thursday waiting for a reply and by the time Friday comes the silence is the only answer you get.

I sent an email last week and I forgot to put the attachment on it and I felt like a fool but at least I felt like a human who was trying to move fast. The system does not move fast and the system does not feel like a fool even when it stops you from doing your job for a month. We submitted fourteen versions of a simple message and nine of them came back as junk and one of them finally went through after we deleted the word confirm.

Nobody at the company can tell us why that word was the enemy and the legal team had a meeting about it but they just talked about risk and they talked about surface area and they did not talk about the customer who was wondering where their shoes were. Thirty-one days passed from the moment we opened the ticket to the moment the first message landed on a phone and in those thirty-one days the world changed and the customer got angry and the developer started looking for a new job.

Survival of the Wealthiest

This is not a mistake in the design of the world and it is not a bug that needs a patch and it is actually the way the system is supposed to work. When you make it hard to do a simple thing then you are not just checking for safety but you are checking for who has the most money and who has the most time.

Compliance is a cost that stays the same whether you are a team of two or a team of two thousand and that means the big team can pay it without blinking and the small team dies in the queue. It is a way to make sure the only people who get to talk to customers are the people who can afford to hire three lawyers to argue about the word confirm.

The Mortar and the Brick

Ruby P.K. is a mason and she spends her days looking at old walls and she knows that the mortar is the most important part of the building. She told me once that you cannot put hard cement into an old brick wall because the old bricks are soft and they need to move and they need to breathe when the sun hits them.

“If you put that hard modern cement in the joints then the brick has nowhere to go and it will crush itself and the face of the brick will just pop off and fall into the street.”

– Ruby P.K., Mason

The gatekeeping process is like that hard cement and it is too stiff for a small business and it is too heavy for a fast team and it crushes the very thing it is supposed to hold up. You try to follow the rules and you try to match the strength of the system but your business is the soft brick and the system is the cement that does not move.

We think of these queues as bad luck or as a slow week but they are a tax on your patience and they are a tax on your soul. You start to write messages that sound like they were written by a robot because you are afraid that any hint of life will trigger a rejection code. You stop trying to be helpful and you start trying to be invisible and that is how the gatekeepers win.

They want a world where every message looks the same and every interaction is flat and every company is too tired to try something new. When you spend thirty-one days waiting for a green light you lose the fire that made you want to build the thing in the beginning and you start to think that maybe the spreadsheet is the real product.

The Machine in the Middle

If you are a developer then you know the feeling of the blinking cursor and the empty screen but the feeling of the waiting room is much worse. You have the code and you have the data and you have the permission of the customer but you do not have the permission of the machine in the middle.

You are caught in a loop where you change a comma and you wait four days and you change a greeting and you wait four more days and the clock just keeps ticking. It is a slow motion car crash where nobody gets hurt but everyone loses their mind and everyone forgets why they were even trying to send a message.

Stop Asking for Permission

The answer is to find a way around the gate or to find a way to make the gate disappear and that is why people look for a better

whatsapp api

that does not treat them like a criminal for wanting to talk to a client.

You need a tool that lets you connect in five minutes and not thirty days and you need a tool that does not have a legal team sitting between your server and the phone in the pocket of your customer. You want to see the message arrive and you want to get back to the actual work of building your business. The gatekeepers will tell you that the waiting is for your own good but they are the ones who built the gate and they are the ones who hold the key.

We have to decide if we are going to be the people who wait or if we are going to be the people who build. The spreadsheet with the nineteen rows is a monument to wasted time and it is a map of a place where innovation goes to die in a pile of reason codes. You can spend your life trying to guess what 1004 means or you can find a path that does not require a secret decoder ring and a month of your life.

The market looks like it is full of quality outcomes but it is actually just full of the people who were wealthy enough to survive the silence. I would rather be the person who sends the message and makes a mistake than the person who waits a month to say nothing at all and I think most developers feel the same way when they are honest with themselves.

The next time you see a rejection code do not ask what you did wrong and instead ask why you are asking for permission from a machine that does not know your name. There are ways to talk to the world that do not involve a thirty-one day delay and there are tools that treat you like an adult who knows how to conduct a business.

You do not have to be the soft brick that gets crushed by the hard cement and you do not have to be the row in a spreadsheet that nobody ever reads. You can just send the message and you can just do the work and you can leave the waiting room to the people who have nothing better to do with their time.

The world is moving fast and the customers are waiting and the only thing standing in the way is a gate that you can choose to walk around if you are brave enough to try.