Choosing the wrong development partner can cost you months and thousands of dollars. Here's what to ask before signing anything.
1. Can you show me similar projects you've completed?
Not just a portfolio — actual case studies. What was the problem? What did you build? What were the results?
If they can't show you relevant work, that's a risk.
2. How do you handle scope changes?
Every project evolves. The question is whether changes trigger a nightmare or a conversation.
Good answer: "We document changes, discuss impact on timeline and budget, and get approval before proceeding."
Red flag: "We'll figure it out as we go."
3. What's your communication process?
How often will you hear from them? Who's your main point of contact? What happens if something goes wrong?
You shouldn't have to chase people down to get updates on your own project.
4. Who will actually build my software?
Sometimes the person in the sales meeting isn't the person doing the work. Ask:
- Is development in-house or outsourced?
- Who's the tech lead on my project?
- Can I meet them?
5. What's included in the price — and what's not?
Get specific. Does the quote include:
- Hosting setup?
- Testing?
- Documentation?
- Training?
- Post-launch support?
The cheapest quote often becomes the most expensive project.
6. What happens if we need to part ways?
Uncomfortable question, but important. Ask about:
- Code ownership
- Data export
- Transition support
- Contract terms
You should never be locked into a vendor because they control your data.
7. How do you handle bugs after launch?
Software has bugs. It's inevitable. What matters is the response.
Ask:
- What's covered under warranty?
- What's the response time for critical issues?
- What's the process for reporting problems?
8. Can I talk to past clients?
References matter. A company that can't provide them either doesn't have satisfied clients or hasn't been around long enough.
When you talk to references, ask:
- Would you hire them again?
- What surprised you about working with them?
- What would you do differently?
9. What technology will you use, and why?
You don't need to understand the tech deeply, but you should understand the reasoning. Are they choosing tools because they're right for your project, or because they're what the team already knows?
Also ask: What happens if I need to hire someone else to maintain this later?
10. What could go wrong?
This might be the most telling question. A good partner will be honest about risks:
- Integration challenges
- Timeline dependencies
- Technical unknowns
If they say "nothing," they're either inexperienced or not being straight with you.
The Meta-Question
Beyond all of these: Do you trust them?
Software projects require collaboration. You'll be working together for weeks or months. Technical skills matter, but so does the relationship.
If something feels off in the sales process, it probably won't get better once the contract is signed.
Before You Call Anyone
Do some homework first:
- Define your problem — not your solution
- Set a realistic budget range — even if rough
- Identify who will manage the project — someone needs to make decisions
- List your non-negotiables — timeline, features, integrations
The better prepared you are, the better conversations you'll have.
Need help thinking through your project? We're happy to chat — even if we're not the right fit. Contact us