# Questions to ask a software company before you sign

Two quotes for the same project can differ several times over, and the cheapest one is not always the risk you think. This checklist helps you compare software teams on what decides how a project goes: whether they understood your problem, whether they can show real working software, how you will see progress, who owns the code and the data, what it costs after launch, and the warning signs to walk away from. Use it in your first calls with each team, including NOVA. A good team will be glad you asked.

## How to use it

1. Send every team the same brief first, so you compare answers to the same question.
2. Ask the questions in a call, not only by email: how they answer matters as much as what they say.
3. Write each team's answers next to each other, section by section.
4. Weigh the red flags first, then the price.

## Did they understand your problem?

- [ ] They asked how the work happens today before talking about features.
- [ ] They can explain your problem back to you in your own words.
- [ ] They suggested a smaller first version, not everything at once.

## Proof of work

- [ ] They showed working software, not only designs or screenshots.
  - Tip: Ask them to click through a real system in the call.
- [ ] Their past work is close to yours in size and type.
- [ ] They can tell you what went wrong on a past project and what they changed.

## How they work

- [ ] Work is split into milestones, each with something you can see and try.
- [ ] You know who you will talk to every week.
- [ ] Changes to scope are written down and priced before they are built.
- [ ] You will see progress regularly, for example a weekly demo.

## Quality and security

- [ ] They explain how they test before each release.
- [ ] Logins, permissions and backups are part of the plan, not extras.
- [ ] They can show Arabic right-to-left screens they built, if you need Arabic.

## Ownership and handover

- [ ] You own the source code and the data, in writing.
- [ ] Hosting and domain accounts are in your company's name.
- [ ] Documentation is included, so another team could continue the work.

## Cost and contract

- [ ] What is included and what is not is written in the proposal.
- [ ] Payments are tied to milestones you can check.
- [ ] Running costs after launch are clear: hosting, support, licences.
- [ ] There is a period after launch in which bugs are fixed at no extra cost.

## Warning signs

- [ ] A fixed price before anyone asked how your work happens today.
- [ ] No written scope, only a total and a date.
- [ ] Everything promised in the first version.
- [ ] Vague answers about who owns the code and the data.

---

From NOVA Solutions · novasolutions.bassemhazem.com
https://www.nova-solutions.co/en/resources/vendor-evaluation-checklist
