Blog
What to ask a software studio before you sign
6 min read
Short answer
Before signing, get five things in writing: how the price is calculated and what a change costs, who owns the code, whose account the system runs on and where the data sits, what you receive at handover, and what happens if the relationship ends. References tell you whether the supplier can program. These answers tell you whether you can part ways years later without damage. Have a lawyer read the contract; what follows is only a list of things to ask.
01Price: fixed or by the hour
A fixed price suits a tightly bounded scope where you can write down in advance what done means. With an unclear scope it is either padded with a reserve or leads to arguments over every change. An hourly rate is fairer for things still being discovered, but it needs a cap or a regular statement of hours.
In practice a fixed price for the first bounded part and an estimate for the rest works well. Also ask what a change you cannot foresee costs and how it gets decided.
02Who owns the code
Ask directly: does ownership of the code pass to us once we have paid, or do we get only a licence to use it? Both are possible and both make sense, but you must know which one you have. With a licence you may find that you cannot develop the system further without the supplier.
Check the third-party libraries too. Nearly all software uses them and open licences are common, which is fine. What matters is that the contract does not bind you to something you cannot meet without the supplier.
03Hosting, accounts and data
- 01Whose account does the system run on? Ideally yours: the domain, hosting, database and code repository should belong to you, with the supplier having administrator access.
- 02Where is the data physically and who can reach it? With personal data this is not a formality.
- 03Is it backed up, how often, and has a restore been tried? A backup nobody has ever restored is an assumption, not a backup.
- 04What is the monthly cost of running it? For a company system of this size it is tens of euros, not hundreds.
04Handover, maintenance and leaving
What exactly do you receive at the end: the source code, a description of how the system is deployed, a list of access credentials and brief documentation that another developer could take over from? Also ask what handing over to a different firm would look like, and the answer shows how the supplier thinks about departure.
Maintenance is usually calculated at 10–20% of the build cost per year. Check what is in it and what is not, how fast they respond to a fault, and whether the agreement can be terminated without a penalty.
Finally: who will actually build it, and will it be the same person you are talking to now? A contract with a small studio can also be written to protect you if its situation changes.
Frequently asked
- Is a fixed price or an hourly rate better?
- Fixed for a tightly bounded scope, hourly for things still being discovered, ideally with a cap. A fixed price for the first part and an estimate for the rest is a practical combination.
- Who owns software a company has paid for?
- It depends on the contract. Either ownership of the code passes to you, or you only get a licence to use it. Ask directly and have it written down.
- What should I watch for at handover?
- That you receive the code, access credentials, a description of the deployment and documentation, and that the domain, hosting and database are on your account. Then another firm can take the system over.