7 questions to ask before you have your own software built
· 7 min read · Your Own Software
"Let's have a program built just for us" is something most businesses say one day. It is a good idea; asked the wrong way, it is an expensive one. Before asking for a quote, answer these seven questions yourself, then ask the same questions of the developer.
1. Which process are we solving — not all of them?
The most common mistake: asking for "a system that does everything". The start should be a single critical process — appointments, portfolio, orders, document tracking. Once that works, it is extended. A system that does everything does nothing well, and is never finished.
Ask the developer: What exactly will be in the first version, and what will not?
2. Who will own the code?
If the quote does not say so, it is probably not yours. The contract should state clearly that the source code, the database and the domain belong to the business. If the word "licence" appears, be careful: a licence is rent, not ownership.
Ask the developer: Do we get the source code on delivery? If we stopped working with you tomorrow, would the system stay with us?
3. Where will the data live?
The system is yours, but if the data is in someone else's cloud, ownership is only half. The database should be in your own account (or on your own server), and the access keys should be with you.
Ask the developer: Which account is the database in? Who holds the backups? How does export work?
4. Who maintains it, and how?
Software does not end at delivery. Updates, bugs and new needs come. The maintenance agreement should be clear from the start: monthly or hourly, and what does it cover? Can the party doing maintenance change?
Ask the developer: What does the maintenance contract include? Can someone else maintain it too, or only you?
5. How will our existing data get in?
If there are 3,000 customers in Excel, they are not typed into the new system by hand. The import should be planned from the start: which file, which format, how many rows, what happens to faulty records?
Ask the developer: Can we import our Excel in one go? Is there a preview?
6. How long does it take, and when do we start using it?
"Three months" is not a sufficient answer. When is the first usable version? When is the team trained? Is there a period of running in parallel with the old system? No schedule, no timeline.
Ask the developer: When do we see the first working version? How is weekly progress shared?
7. What is the total cost — not today, but over five years?
Custom software costs more to start than a subscription; its five-year total is usually lower. The comparison should be made properly: subscription × 60 months + migration cost + lost flexibility, against setup + maintenance × 60 months.
Ask the developer: Setup fee, yearly maintenance, hourly rate for additional development — what is each one, separately?
A note: does it make sense for a small business?
Yes, if the process is critical. A single-branch dry cleaner, a real estate office with 5 agents, a clinic with 2 doctors — we have built systems for all of them. It is not the scale that decides, but how important the process is.
If the answers to the seven questions are clear, you are ready to ask for quotes. If they are not, one conversation is enough to clarify them first.