All Insights

What 17 Years Running Infrastructure Taught Me About Business

Lessons from building systems in real markets, and why operational reliability still matters more than the next big idea.

Most of what I learned about business didn’t come from books or frameworks. It came from systems that broke at 2am, customers who needed a real answer, and infrastructure that had to keep running whether or not the trend of the month worked out.

I started a .ke domain registrar in 2005 and ran it for 17 years, until it was acquired in 2022. That kind of run teaches you a few things no MBA program covers.

Reliability is a feature, not a checkbox

When you sell uptime, you stop romanticizing speed. Shipping fast is great, but if the thing you shipped goes down on a Friday night, none of that speed matters. The businesses that lasted in our market weren’t the fastest, they were the ones whose customers stopped worrying about them.

That is what reliability buys you: customers who stop worrying. It doesn’t show up on a feature list. It shows up in renewals, referrals, and the phone that doesn’t ring in a panic.

Trust is built at 2am

Anyone can serve a customer when everything works. The business is really built in the other moments: the server that fails at night, the domain that expires on a weekend, the email that stops flowing on invoice day.

Customers don’t expect perfection. They expect a straight answer, a realistic timeline, and someone who stays until it’s fixed. Do that consistently for years and you have something competitors can’t copy with a bigger marketing budget.

More tools rarely fix the problem

Every year, a new wave of platforms promised to change how business runs. Some helped. Most just added another login, another subscription, another place for things to break.

The teams that ran cleanest weren’t the ones with the most software. They were the ones who understood their own workflow well enough to know what to keep simple. Understand the workflow first. Then, and only then, choose the tool.

Own the boring things

The assets that decide whether a business survives are unglamorous: the domain name, the DNS, the email, the backups. Nobody celebrates them. Everybody depends on them.

In 17 years I saw businesses lose access to their own domains because someone else had registered them and moved on. I saw companies discover, on the worst possible day, that their backups had never actually been tested. None of these were technology failures. They were ownership failures, and every one was preventable with an hour of attention.

A business that depends on you is not yet an asset

Selling the company taught me a final lesson. What a buyer pays for is not the founder’s talent. It’s the system: documented processes, clean records, infrastructure that runs without heroics, a team that knows what to do.

The discipline that makes a business sellable is the same discipline that makes it stable. Write things down. Remove yourself from the critical path. Build so the business would survive your absence. Even if you never sell, you’ll sleep better.

The principle underneath it all

Foundations first. Own what you depend on, protect it properly, and only then build the exciting things on top. Technology will keep changing. That order of operations won’t.

If you want to talk about any of this, reach out or connect on LinkedIn (opens in a new tab).

Want to talk this through?

If anything here connects to what you're building, get in touch.

Work With Me