Quick answer: choose a software development partner by testing how they think, not how they present. Ask about similar projects, who will do the work, how they plan, how they handle change and failure, how they secure your data, what you will own and what happens after launch. Clear, specific, honest answers matter more than a polished pitch.

Open the websites of ten software companies and you will read the same promises: quality, innovation, transparency, passionate teams. Words are free. The question is how to tell which company will still behave well in month five, when a deadline slips and a feature turns out harder than anyone thought.

The good news is that you can learn a lot in two or three conversations, if you ask questions that are hard to answer with a slogan. These are the ten we would ask if we were in your seat.

The ten questions

1. "Show me something you built that is similar to my project, and tell me what went wrong."

Everyone shows successes. Teams worth hiring will also describe a difficulty and what they learned. Honesty here predicts honesty later.

2. "Who exactly will work on my project?"

Ask for names, roles and experience. Beware the classic switch where senior people join the sales call and juniors do the work. Request a call with the lead engineer.

3. "How will you turn my idea into a plan?"

A strong answer includes discovery, user journeys, prioritisation and a phased roadmap. A weak answer jumps straight to a price. See our thoughts on estimates that hold up.

4. "What are the three biggest risks in my project?"

Experienced teams spot risks immediately: an integration, regulation, scale, data quality. A team that sees none is either inexperienced or selling.

5. "How will I see progress?"

Look for weekly demos of working software, a shared task board and regular written updates. Status reports with percentages and no working screens are a warning.

6. "What happens when I change my mind?"

You will. Ask how changes are estimated, approved and scheduled. The best answer treats change as normal and keeps it transparent, not punitive.

7. "How do you handle quality and security?"

Listen for code review, automated tests, security checks and monitoring, not only "our QA team tests everything". Ask how they would protect your data and whether they follow practices like those in our security checklist.

8. "What will I own, and how do I get it?"

You should own the code, designs, data and accounts. Confirm that repositories and cloud accounts are in your name, and that documentation and deployment steps are part of the delivery.

9. "What happens after launch?"

Software needs hosting, updates, fixes and improvements. Ask about support terms, response times, monitoring and how new features are handled. A partner who disappears after launch leaves you stranded.

10. "What would make you say this project is not a good fit?"

The most revealing question. Good partners will turn down work that does not suit them, or tell you to start smaller. Someone who says yes to everything is optimising for the contract.

Green flags

  • They ask more questions than they answer in the first meeting.
  • They suggest a smaller first release.
  • They give ranges and explain assumptions.
  • Their references speak warmly and specifically.
  • They are open about their process, tools and team.
  • They disagree with you politely, with reasons.

Red flags

  • A fixed price quoted after one short call.
  • Reluctance to let you talk to the engineers or past clients.
  • Vague contracts about ownership and exit.
  • Pressure to sign quickly with a "limited time" discount.
  • Portfolio items with no detail or that they cannot discuss.
  • No clear plan for testing, security or support.

A simple scoring method

Create a table with your shortlist across the top and these criteria down the side: relevant experience, team quality, process clarity, communication, security approach, ownership terms, post launch support and price. Score each from 1 to 5, weigh the ones that matter most to you and treat price as one factor among eight. The final number is less important than the conversation it prompts.

Try before you commit

If possible, begin with a small paid piece of work such as a discovery sprint or a prototype. It costs little, shows how the team communicates and produces something useful even if you part ways.

What we hope you will notice about us

We are a product company that also works as a technical partner for founders. We would rather tell you honestly when a project is not right than sell you something that does not work. Read how we think in our approach, explore our custom software development service, or talk to our team. We are happy to be asked these ten questions.

Frequently Asked Questions

How do I choose a software development company?

Shortlist a few with relevant experience, speak to the engineers, ask how they plan, handle change and secure data, check references and compare on value, not only price.

What should be in a software development contract?

Scope and deliverables, payment terms, ownership of code and data, confidentiality, change handling, warranties, support after launch and clear termination and handover terms.

Should I choose a local or offshore software company?

Choose the team that fits your needs best. Both can work well with clear communication, overlapping hours and good process. Location matters less than capability and trust.

How long does it take to choose a development partner?

Plan for three to six weeks to define requirements, meet shortlisted teams, check references and run a small paid trial if possible. Rushing this step costs more later.