Does custom software lock you into one supplier?

This is one of the most common worries I hear when we talk about a system built for the company. There's a lot of truth in it - except that lock-in depends on the specific terms of the agreement, whether the software is custom-built or off-the-shelf. Below I break it down and give you questions worth asking any supplier.

Where lock-in really comes from

It has three layers. Technical: what format the data sits in and whether you can get it out of the system. Contractual: what the agreement says about licences, penalties and termination. Knowledge-based: whether what is known about the system is written down, or lives in one person's head. Any of them can lock you in - and each applies to custom and off-the-shelf software alike.

Off-the-shelf software can lock you in too

Worth saying plainly, because lock-in is mostly associated with bespoke systems. With an off-the-shelf subscription you hand your process to someone else's product, in someone else's cloud and format, and the price and direction of development are set by the supplier. A price rise, or the withdrawal of a feature you rely on, is often outside your control - and migrating to another tool can cost more than the switch itself.

How I build so the system stays yours

I stick to a few principles that directly limit dependence. The code, database schema and documentation stay with you. The Claris platform licence is yours, so the system doesn't vanish along with me. The data sits in a standard format and can be exported, and integrations run through open APIs. So if you ever want to hand development to someone else, they have something to build on.

What to ask every supplier

Before you sign anything, ask five questions: will I get the code and documentation; what format is my data in and can I export it myself; does the system have an open API; can I hand further development to another person or firm; what exactly happens to the system and data when we end the collaboration. Clear answers to those five questions are the best safeguard you can give yourself.

A dependence that is natural

Some dependence always remains - on the partner who knows your system best, or on the knowledge built up over years of working together. That's normal and healthy in itself. The difference between good collaboration and shackles is that you can leave the former in reasonable time and on a reasonable budget, because the data and code are on your side.

If you'd like to talk through your own situation - let's take thirty minutes. I'll show you what the contract and handover of the system look like with me, so you can compare them with other offers.