Article Software

Questions to ask a software development company before you sign

Twenty-four questions that show how a software vendor really works, what good answers sound like, and the red flags worth walking away from.

In this note

The questions that reveal how a software vendor scopes, builds, tests and hands over work, with what good answers sound like.

7 min read
A client and a software agency team shake hands across a meeting table with laptops and notes after a discussion.

Published by

VSN Editorial

Date

Oct 14, 2026

Read time

7 min read

Choosing a software partner is mostly a judgment about how they work, and a portfolio or a polished sales call tells you very little about that. The quickest way to find out is to ask specific questions and listen to how they are answered.

Below are the questions to ask a software development company before you sign, grouped by topic. For each group we describe what a good answer tends to sound like. You do not need to ask all of them in one meeting. Pick the ones that matter most for your project and send the rest in writing.

A useful habit: ask every shortlisted vendor the same questions, and write their answers down side by side. Differences that sound small in conversation often look large on paper.

Understanding your problem

The first questions test whether the vendor is interested in your business or only in the build.

  1. What else do you need to know about our users and workflow before you can estimate?
  2. Which part of our brief do you think is riskiest or least clear?
  3. Is there anything in our request you would advise us not to build yet?
  4. Would you recommend a discovery phase, and what would it produce?

What good sounds like: specific follow-up questions about your process, honest comments on risk, and a willingness to suggest a smaller first release. A vendor who agrees to everything in your brief without a single question has not thought about it yet.

Scope and estimate

  1. What exactly is included in this proposal, and what is excluded?
  2. Which assumptions affect the estimate most?
  3. How do you handle change requests, and how are they priced and approved?
  4. Is the price fixed per milestone, or based on time spent?

What good sounds like: a written list of deliverables, assumptions and exclusions, and a clear change process. For background on what moves an estimate, see our guide to custom software development cost.

The team and the process

  1. Who will actually work on the project, and what are their roles?
  2. Who is our day-to-day contact, and who makes technical decisions?
  3. How often will we see working software, not just status reports?
  4. How will decisions and feedback be recorded?

What good sounds like: named roles, a regular demonstration rhythm, and a shared place where decisions are written down. Be cautious if the people in the sales meeting will disappear once the contract is signed and nobody can tell you who replaces them.

Technology choices

  1. Which technologies do you recommend for this project, and why?
  2. What would make you choose a different stack?
  3. Which third-party services, libraries or paid platforms will the system depend on?

What good sounds like: a recommendation tied to your requirements, integrations, hosting and future maintenance, not to whatever the vendor happens to use for everything. Ask whether another developer could reasonably pick up the code later.

A good vendor explains trade-offs. A risky one only explains features.

— VSN Editorial

Testing, quality and security

  1. What testing is included, and who performs it?
  2. Which browsers, devices or environments will be tested?
  3. How do you handle security for the parts of the system you build?
  4. What happens if we find a defect after launch?

What good sounds like: testing activities described in the proposal, such as API, integration, browser or regression checks, and a warranty or defect process with clear limits. Be wary of anyone who calls software “fully secure” or “bug-free”. Security work can be scoped and reviewed; it cannot be guaranteed.

Ownership and handover

  1. Who owns the source code and any reusable components?
  2. Which accounts (hosting, domains, app stores, third-party services) will be in our name?
  3. What documentation and access will we receive at handover?

What good sounds like: ownership and licence terms written into the agreement, client-owned accounts wherever practical, and a defined handover package. If accounts are created in the vendor’s name “for convenience”, ask how and when they will be transferred.

After launch

  1. What support do you offer after release, and what does it cover?
  2. What are your response targets, service hours and exclusions?

What good sounds like: a separate support scope with a stated service window, response targets and what counts as a change versus a fix. It is reasonable to ask how issues are logged and reported, and to see an anonymised example of a support report or ticket history.

Questions a good vendor will ask you

Listen to the questions coming back, too. A vendor that understands software delivery will want to know things like:

  • Who decides on scope and signs off each milestone?
  • What happens today, step by step, and where does it go wrong?
  • Which systems hold the data now, and who owns those accounts?
  • What is the budget range and the date that really matters?
  • Who on your side will test, and how much time can they give?
  • What should happen when something fails, such as a payment, an import or an integration?

If a vendor asks none of these, they are estimating from assumptions. That is where surprises later in the project usually come from.

Red flags and what they usually mean

What you hearWhat it often meansWhat to ask next
“We can start tomorrow at a fixed price” (with no questions)The scope has not been understood yet“What assumptions is that price based on?”
“Everything is included”Exclusions have not been thought through“Please list what is not included.”
“We’ll host it on our account to keep it simple”You may not control your own system“When and how do accounts transfer to us?”
“Our software has no bugs”Testing and warranty terms are vague“What is your defect process after launch?”
“We’ll figure out the details as we go”Budget and timing risk sits with you“How are changes estimated and approved?”

How to use the answers

Put the answers in a simple table, one column per vendor. Score each group on clarity and honesty, not just on price. Then ask your top choice for one thing more: a short conversation with someone from their delivery team, not only sales.

If you have not prepared your brief yet, start with the software requirements checklist. Clear requirements make every one of these questions easier to answer.

Key takeaways

  • Ask every vendor the same questions and compare written answers side by side.
  • Good vendors ask questions back and point out risk; that is a positive sign.
  • Insist on written deliverables, assumptions, exclusions and a change process.
  • Confirm code ownership, account ownership and handover before signing.
  • Treat guarantees of “no bugs” or “fully secure” as warning signs.

FAQ: questions to ask a software development company

How many software companies should I talk to?

Enough to compare approaches, which for most projects means a short list of two to four. Talking to more takes time and rarely improves the decision if your questions are consistent.

Should I choose the cheapest proposal?

Only if it covers the same scope, assumptions, testing and support as the others. A low price with vague exclusions often becomes the most expensive option once changes start.

Is it a problem if a vendor recommends a paid discovery phase?

Usually not. For larger or uncertain projects it is a sign they want to reduce risk before committing to a fixed build. Ask what the discovery will produce and whether you own the outputs.

Can I ask a vendor to work with my in-house developers?

Yes. Many projects split work between an internal team and an external vendor. Agree access, code ownership, review responsibilities and how decisions are made before work starts.

VSN is happy to answer every question on this list in writing. If you are comparing partners for a software or SaaS project, see how we approach custom software and SaaS development or ask us directly.

Filed under Software

Keep reading

Related notes