Skip to content
Skandava

8 Questions to Ask Before Hiring a Software Company

Before you sign a software development contract, ask these eight questions. Each comes with what a good answer sounds like and which answers are warning signs.

Hiring a software company is one of the biggest decisions a growing business makes, and it is hard to judge from a sales presentation. These eight questions cut through the pitch. For each one you will see what a good answer sounds like and what should make you pause.

1. Who will own the code when we are finished?

A good answer: “You do, once the project is paid for. You will get the source code, the accounts and the documentation.”

A warning sign: vague replies, or “we license it to you”. Ownership should be written into the contract before work starts.

2. Who will actually work on my project?

A good answer: names, roles and how many people, plus a straight answer on whether any work is passed to outside freelancers.

A warning sign: the team you meet in the sales call is not the team that builds it, and nobody will say who is.

3. How do you estimate, and what happens if the scope changes?

A good answer: an explanation of whether the price is fixed or based on time, what is included, and how a change is priced before anyone starts on it.

A warning sign: a very low price with no written scope. The cost usually returns later as “extras”.

4. How will I see progress?

A good answer: short cycles, regular demos of working software you can click through, and one person who answers your questions.

A warning sign: silence for weeks, then a “big reveal”. By then it is expensive to change direction.

5. What happens after launch?

A good answer: a clear plan for bug fixes, hosting, monitoring and small changes, with a stated response time and cost.

A warning sign: “we will figure that out later”. Software needs looking after, and a launch is the start of that, not the end.

6. What will I receive at handover?

A good answer: a list: the code repository, login details for every account, deployment instructions and short notes on how the system works.

A warning sign: no list at all. If a new developer could not take over from what you were given, the handover is incomplete.

7. Can I speak to a past client?

A good answer: two or three references you can actually call or email, ideally for a project similar to yours.

A warning sign: only logos on a slide, or reference customers who cannot be reached.

8. How is payment tied to progress?

A good answer: payments linked to delivered milestones, not a large amount paid before anything exists.

A warning sign: most of the price due up front, or payments that continue regardless of what has been delivered.

What to do with the answers

You do not need every answer to be perfect. You are looking for a company that answers plainly, puts things in writing and is comfortable being asked. Pay attention to how the questions land. A team that welcomes them is usually a team that is easy to work with later.

Ask the same questions of every company you talk to and write the answers side by side. The differences are usually obvious within an hour.

Want this solved for your team?

Tell us what you are dealing with and we will reply with an honest view of the options.