Blog

Over the last few months I've been to a handful of networking events and talked with startup founders who are excited about a new reality: you can vibe code an MVP without recruiting a team of expensive developers. The energy is real, and the productivity gains are real. But every one of these MVPs works fine until it doesn't, and "doesn't" can be devastating. Small bugs repel the early adopters who would have become your champions. Lost momentum is hard to get back.

I've spent close to thirty years writing software, and a lot of that time has been cleaning up systems that were fine until they weren't. Here is my honest take for non-technical solopreneurs using tools like Replit, Lovable, or Cursor to ship their first product.

I needed a CRM. Not just any CRM. I wanted one that could actually work the way I work. I tried several existing tools. They either missed features I cared about, forced me into workflows that didn't fit, or wanted a monthly fee that didn't make sense for a one-person consultancy. So I did what any developer would do: I decided to build my own.

But this time, I had a plan. I was going to build it with AI and use the project as a clean experiment to measure how much more productive AI actually makes me. This is not really a story about the CRM, though. It is a story about what happened when I built it using Claude Code, and what I did not expect along the way.

There is a conversation happening in boardrooms and leadership meetings right now, and it goes something like this:

"The market is moving fast. Customers expect results in weeks. We need to modernize."

Everyone nods. The meeting ends. Then it gets handed to the technology team, and that is where things quietly fall apart.

It was December 2024 when Satya Nadella dropped a bombshell on the BG2 podcast: "SaaS is dead." The tech world reacted the way it always does - half panic, half eye-rolling. But here we are, over a year later, and it turns out Nadella wasn't entirely wrong. He was just early. And maybe a little dramatic.

The software industry in 2025 didn't collapse. SaaS didn't vanish overnight.

There's no escaping it. Every conference keynote, every LinkedIn feed, every vendor pitch deck. AI is everywhere. And if you're running a small or medium-sized business, you're probably feeling a familiar mix of excitement and anxiety. The big players are pouring billions into AI. Your competitors are name-dropping ChatGPT in meetings. And somewhere in the back of your mind, a voice is asking: Are we falling behind?

The short answer is no, not yet.

When I speak with potential clients about technology choices and system structure, I often hear:

"This is more than I need to know."

"I don't really care how it's built, as long as it works and is up and running by next month."

These responses make sense. Your job is to run your business, not to manage technical details. Software development is a supporting activity, and naturally you want to delegate it.

If you compare applications from the 90s, 2000s, and modern ones, you may notice an interesting trend: modern applications seem simpler, with fewer elements per square inch. Early applications, especially in the enterprise world, were packed with buttons, toolbars, edit fields, and icons.

Why has the trend shifted toward presenting less?

In this article, we will dive into how user interface design impacts employee productivity and the hidden cost of bad user experience (UX).

This article is written for small and mid-sized business owners and operators who are trying to decide whether to keep using standard SaaS tools or invest in a custom software solution. If you rely heavily on spreadsheets, manual workarounds, or disconnected systems, and you feel your software no longer matches how your business actually works, this article is for you.