Most software projects that go wrong do so because of something nobody agreed at the start. These are the questions we’d ask if we were on your side of the table. Ask them of us, and of anyone else you’re talking to.
1. Who owns the code?
Agree it in writing before the build. If it’s yours, you can take it elsewhere. If it’s licensed, know what that licence lets you do.
2. Who runs it after launch?
Software needs hosting, updates and someone to call when it breaks. Find out who does that, and what it costs each year.
3. How will we see progress?
Working software you can use beats status reports. Ask how often you’ll get something real to try.
4. What happens to our data?
Where it’s stored, who can see it, how it’s backed up, and how you get all of it back.
5. What’s in the estimate, and what isn’t?
Training, moving data from the old system and changes after launch are often left out. Ask.
6. Who will we actually speak to?
At a small company, it should be the people building it. If there are layers in between, find out who they are.
7. What would make you say no?
A good supplier will tell you when software isn’t the answer, or when they aren’t the right people for it. If nothing would make them say no, be careful.
Trunkfield Software, Lichfield