Hiring a software development company is a bit like hiring a builder. Everyone's portfolio looks good, everyone promises to finish on time, and you only discover the difference halfway through the project, when changing course is painful and expensive.
We've taken over plenty of projects from other agencies over the years. In almost every case, the problems could have been spotted with a few direct questions before the contract was signed. Here are the twelve we'd ask if we were in your shoes, including a few that might feel awkward to ask us.
Understanding how they work
1. “Can you walk me through a similar project, from start to finish?”
Not the polished case study, but the real story. What went wrong? What would they do differently? A team that can talk honestly about challenges has learned from them. A team that claims every project was flawless is either inexperienced or not being straight with you.
2. “What happens in the first two weeks?”
Good partners spend the start of a project understanding your business: users, processes, goals and constraints. If the answer is “we start coding straight away”, be cautious. Skipping discovery is the most common cause of software that technically works but doesn't fit how your business operates.
3. “When will I see something working?”
You should see designs or a prototype within weeks, and working software regularly after that. Long silent periods are a red flag. Ask how often you'll get demos and whether you can try builds yourself.
4. “Who will actually work on my project?”
Sometimes the senior people you meet in sales calls aren't the ones building your product. Ask who your day-to-day contact will be, who's on the team and how much of their time is allocated to you.
Protecting yourself
5. “Who owns the code, designs and accounts?”
The answer should be simple: you do, once the work is paid for. Make sure the contract says so, and that hosting, domains, app store accounts and third-party services are registered in your name or transferred to you at handover.
6. “How do you handle changes to scope?”
Requirements always evolve. A good partner has a clear, fair process: small changes are absorbed, larger ones are quoted before work starts, and nothing appears on an invoice that you didn't approve.
7. “How do you test before release?”
Ask about their quality assurance process. Who tests? On which devices and browsers? Is there a staging environment where you can review changes before they go live? Testing that's “done by the developers as they go” often means bugs are found by your customers instead.
8. “How do you keep our data and systems secure?”
Look for specific answers: role-based access, encrypted connections, regular backups, secure handling of passwords and API keys, and a plan for applying security updates. Vague reassurance isn't enough.
Looking beyond launch
9. “What happens after the project goes live?”
Software needs ongoing care: bug fixes, security updates, operating system changes and new features. Ask what support looks like after launch, how quickly they respond to urgent issues and how ongoing work is priced.
10. “Could another team take over this code later?”
This is a great test of quality. Well-built software uses mainstream technologies, has clear documentation and follows common conventions, so any competent team could continue the work. If the answer is hesitant, you may be locked in.
11. “What would make you advise us not to build this?”
A partner worth hiring will tell you when an off-the-shelf tool would do the job, when a smaller first version makes more sense, or when your timeline is unrealistic. Willingness to say no is a sign they care about your outcome, not just the contract.
12. “How will we communicate day to day?”
Agree the channels (email, Slack, WhatsApp), meeting rhythm, response times and time-zone overlap upfront. Many project problems are really communication problems in disguise.
Warning signs to take seriously
- They agree with everything you say and ask very few questions
- The quote arrives within hours of a short conversation, with no breakdown
- They can't explain their process in plain language
- Payment is mostly upfront, with little tied to delivered milestones
- Past clients are hard to reach or reluctant to talk
Making the final decision
Price matters, but it's rarely the best deciding factor on its own. The cheapest quote often becomes the most expensive project once delays, rework and missing features are counted. Look for the team that understands your business best, communicates clearly and has a believable plan.
“You're not just buying software. You're choosing the people you'll be solving problems with for the next year or more. Choose people you trust.”
We're always happy to answer every one of these questions about how we work, including the awkward ones. If you're comparing partners for an upcoming project, get in touch and put us to the test.
How we can help
Software & SaaS Solutions
ERP, CRM and custom systems built around how you work.