15 questions you really need to ask before signing. Plus red flags we ignored from our clients' previous vendors.
Over 10 years of running a software house, I've talked to hundreds of companies that came to us after failed collaborations with other vendors. The stories are similar: exceeded budget, delays, code no one wants to touch, and ghosting when problems start.
I've compiled these experiences into a guide that will help you avoid our mistakes... and theirs.
Before you start looking: preparation
The most common mistake? Sending "I need a mobile app" to 20 companies and comparing prices. It's like asking "how much does a house cost?" without specifying size, location, and standard.
15 questions you must ask
"Show me 3 projects similar to mine and let me talk to those clients."
Red flag: "We have NDAs on all projects" - sounds professional, but every software house has clients who will agree to references.
"Who specifically will work on my project?"
Red flag: "We'll assign the best team" - without names and CVs. Large firms often sell with seniors and deliver with juniors.
Contract must-haves
- Code ownership - must transfer to you after payment
- Escape clause - ability to exit contract with specified notice period
- Definition of done - clear acceptance criteria for each phase
- Bug warranty - minimum 3 months, standard is 6
- Support SLA - response time for critical issues
Looking for a vendor for your project?
We're happy to answer these 15 questions. And the next 15 that come to your mind.