Businesses pick a technology partner in different ways. Some compare prices. Some check portfolios. Some ask for referrals. Others go with the person who understood their business best in the first meeting.
All of those are reasonable. Most people skip the one question that decides how it ends: what happens if the team that built your system closes down or walks away?
The question that matters more than price or portfolio
We have seen this happen to a business that put tens of thousands of dollars into a custom system a few years back. The system ran their daily operations and did what it promised.
Then they needed one change. The team that built it was gone. There was little documentation and nobody left who understood how it worked. A change that should have taken a few weeks became close to impossible.
The system still worked, and it was frozen. Nobody could change it without breaking something nobody understood.
Owning and renting
That is the difference between owning software and renting a dependency you happen to pay for. It applies to a system that runs your operations and to an app your customers open every morning.
Ask one question. If a different team stepped in tomorrow, could they pick up where the last one left off? If the answer is no, you rent access, and the original team decides how long that lasts.
Documentation protects you more than the contract does. A well-documented system can pass to your own staff or to a different vendor, and the new team keeps building without starting from zero. A system that lives in one team's heads is yours in name only, until the day you need a change.
Nothing runs forever, and nobody promised it would. What matters is who picks the ending. You can plan it, because the business outgrew the system. Or it can be forced on you, because nobody left can touch the system and the vendor is gone. The first is a normal cost of business. The second is expensive and avoidable.
Three questions to ask before you sign
Ask any developer or agency these before you sign:
- Will you document my system and keep the documentation current as it changes?
- If I bring in a different team in a year, can they read what is there and continue, or do they start from zero?
- Whose servers does it run on, and who holds the code, you or me?
Vague answers are an answer.
How we work at Hoseh Digital
We are a Singapore team. Everyone working on your project is someone you can call, meet and sit across the table from. We keep documentation current while we build, and we do not leave it for the end of the project.
We do this on purpose. What we know about your system should not leave with a project or with a developer who moves on.
Stay with us for years or do not. Hand the system to your own team or to someone else. That choice belongs to you, and we should not control it by being the only people who understand what we built.
Not sure whether you own your system?
If a system already runs part of your business, try the three questions on it. If you are unsure of the answers, talk to us. We will walk through it with you for free and tell you where you stand.
