The Flow Journal

Why I'd rather build you one thing that lasts than ten that impress

On the difference between a system built to demo well and a system built to run for years, and why the harder one to sell is the only one worth building.

A single brass lantern burning steadily on a worn wooden table on a lodge veranda at dusk, with a closed leather ledger beside it and the bush and last light beyond
Still doing its one job.

Early on, when I was still working out how any of this was meant to fit together, I built more than anyone needed.

Every new tool I found, I wanted a reason to use it. A dashboard here. An automation there, plugged into a notification that fired for something nobody was ever going to act on. If a piece of software could talk to another piece of software, I connected them, because it felt like progress. It felt like I was building something serious.

What I'd actually built was a machine that needed me constantly.

Every new connection was one more thing that could quietly break while I wasn't looking. One more login. One more place to check before I trusted the numbers on the screen. I remember sitting with it one evening, trying to work out why a simple enquiry had taken three days to reach anyone, and tracing it back through four different tools before I found the gap. Four tools, and the one job the client actually needed done still fell through the middle of them.

That was the evening I stopped being impressed by my own setup.

Here's what I hadn't understood yet. A system that looks impressive in a demo and a system that quietly does its job for two years are almost never the same system. The demo rewards more. More screens, more automations, more things happening at once, so it feels like you're getting your money's worth. The two-year version rewards the opposite. Fewer moving parts. Fewer places for something to go wrong while you're asleep or on a flight or simply not looking.

I understand why the sprawl is tempting, on both sides of the table. To the person selling it, more tools looks like more value. To the person buying it, more tools can feel like you're finally taking this seriously. Neither feeling has much to do with whether the enquiry actually gets answered.

So now, when I sit down to build something for someone, I ask a smaller question than I used to. Not what could this do. What does this business actually need to happen, on an ordinary Tuesday, and nothing more than that.

It's a less exciting pitch, if I'm honest. There's no screen full of dashboards to show off on the call. What you get instead is something built to fit how you already sell, tuned to your own voice, small enough that I can hold the whole thing in my head, and built to still be doing its one job quietly in two years without either of us thinking about it.

I'd rather hand you one thing you never have to worry about than ten things you'll eventually be afraid to touch.

I don't say that as some kind of principle I arrived at cleanly. It's just what tracing one enquiry through four very good tools taught me, the hard way, on an evening I'd rather have spent doing anything else.

The best compliment I get from a client isn't "look what it can do." It's the one I actually hear most, usually months in, almost as an aside.

I forgot it was even running.

That's the whole point. Not that it impresses you once. That it disappears into the background of a business that just works, and stays there, doing the one thing it was built to do, long after the demo would have worn off.