How to Choose a Software Partner You Won't Regret
Every software partner's proposal promises senior engineers, agile process, transparent communication, and on-time delivery. The words have been photocopied so many times they carry no information. After twenty years of winning deals — and occasionally losing them to vendors clients later regretted — here's where we'd tell a friend to look for actual signal.
Signals that matter
- Who shows up to the sales call: if you can't meet the engineers before signing, the A-team is a brochure photo.
- What they ask you: strong partners interrogate your business problem; weak ones demo their process slides.
- How they talk about a failure: ask for a project that went sideways and what they did. Vendors with no such story are either new or lying.
- The ownership paragraph: code, accounts, and documentation in your name from day one — in the contract, not the conversation.
- Reference calls they don't chaperone: current clients, your industry, no minders on the line.
The pricing tell
Be suspicious of the lowest bid — someone eats that gap later, and it's usually you, via change orders or juniors learning on your dime. Equally suspicious: day-one certainty about an 18-month price. Honest firms estimate in ranges, narrow them as discovery reduces risk, and tell you what would move the number. Precision theater is a sales tactic; calibrated uncertainty is engineering.
The test drive
Whatever you conclude from proposals, verify it with a small paid engagement first — a discovery sprint or prototype with real deliverables. Four weeks of working together reveals more than forty pages of RFP responses. Any partner confident in their delivery will welcome the audition. The ones who insist on the big contract up front just told you why.