The NoCode CTO
Technology Strategy

How to make a technology decision you won't regret in 18 months

The technology decisions you regret rarely look risky on the day; they look sensible. Four questions asked up front protect you from the choice that traps you eighteen months later.

· 2 min read min read

Eighteen months ago it was the obvious choice. Everyone in the sector used it, the demo was slick, the price was fair, and the team liked it. Now you're the one paying to get out — migrating your data at three times the cost of getting in, discovering that the thing you built your operations on can't do the one thing you now need. The decision felt safe at the time. Most regretted ones do.

The decisions you regret rarely look risky on the day. They look sensible. What separates them from the good ones isn't luck; it's a handful of questions the buyer didn't think to ask, because everything seemed fine. Ask them up front and you protect yourself from the version of this that shows up a year and a half later.

The questions that protect you

Start with getting out. Before you commit, ask how you'd leave. Can you export your data in a usable form, or does it come out as a mess you'd have to rebuild? A tool you can leave cheaply is a tool that has to keep earning your business. A tool you can't leave owns you the moment you sign.

Then ask who holds the knowledge. When you configure a system around how you work, that setup is real value, and it lives somewhere: in your team, in documentation, or only in the vendor's head. If it's the last one, you haven't bought a tool, you've rented a dependency, and the rent goes up.

Next, ask what you're now dependent on. Every choice creates a reliance on something: a supplier, a format, a way of working, a single person who understands it. Naming that reliance out loud is uncomfortable, which is exactly why it's worth doing. You want to choose your dependencies deliberately, not discover them when one of them fails.

Last, ask how reversible it is. Some decisions are easy to undo, and you can make those quickly and move on. Others are load-bearing; they shape years of work and are painful to reverse. The mistake is treating both the same. Spend your care where the decision is hard to walk back, and stop agonising over the ones that aren't.

Slower on the few that matter

None of this means turning every purchase into a committee. Most tools are cheap, easy to swap, and not worth a week of deliberation; buy them and get on. The discipline is knowing which decisions are the load-bearing ones, and slowing down only for those. A regret you can undo in an afternoon isn't a regret. The ones that cost you eighteen months are the ones worth an extra hour today.


Facing a decision you'll be living with for years? Book a call and we'll pressure-test it with you before you sign, not after.

Robin Carswell

More on

Worth a conversation.

No pitch deck. No commitment. Just a conversation about what technology is and isn't doing for your business — and whether we can help.

Book a conversation →