Choosing a development partner is a multi-year decision wearing a quotation's clothes. These questions reveal how a vendor will behave when things get difficult — which is when it matters.
The ten questions
1. Who owns the code and documentation? 2. What exactly happens after launch? 3. Show us a scope document from a past project. 4. How do you handle changes mid-project? 5. What do you do when you disagree with our approach? 6. How is testing done and evidenced? 7. What access do we have during the build? 8. What are your response targets? 9. What happens if we part ways? 10. Can we speak to a long-term maintenance client?
Red flags
Fixed quote with no written scope. No mention of testing, documentation or handover. 'Unlimited revisions'. No maintenance offering (they don't expect to support what they build). Reluctance to let you speak to existing clients. Promises of timelines that never slip — honest engineers discuss risk.
The green flags that matter most
Written scopes with acceptance criteria. Staged delivery you can review. Plain-language reporting. A maintenance relationship they propose before you ask. Willingness to recommend a smaller solution than you requested. That's a partner, not just a vendor.