Tridasoft

12 questions to ask before hiring a software company

Questions for the first meeting so you can compare quotes on ownership, process, security and maintenance, not just on price.

Author:
Ahmet Serdar Tunçay · Founder
Published:
Updated:
7 min read

There are many teams building web, mobile and business software, and the price gap between quotes is often large. That gap usually comes from differences in scope, ownership and maintenance terms, and those rarely appear clearly in the quote. The questions below cover what you should settle in the first meeting, whichever company you choose. We are a software company too; we wrote this list so that you can compare fairly, not to praise ourselves.

Ownership and hand-over

  1. Who will own the source code, and how will it be delivered? The contract should state clearly that ownership of the code and design files passes to you, and delivery should be access to a code repository.
  2. In whose name will the server, domain, email and app store accounts be opened? If they are not in your name, access to your own system becomes a negotiation when you part ways with the vendor.
  3. Which documentation comes with delivery? Setup steps, environment variables, the database schema and restore-from-backup instructions are the minimum another team needs to take over.

Process and communication

  1. Who will you talk to during the project? How many layers sit between the person in the sales meeting and the team writing the code, and who answers a technical question?
  2. How will the scope be put in writing, and how will changes be priced? A good quote lists the screens and rules included and states what is out of scope.
  3. How often will you see working versions? A single delivery after months of seeing nothing means problems surface at the latest and most expensive moment.

Quality and security

  1. How is testing done, and whose approval ends the acceptance test? Ask how the bug list is kept and what counts as "closed" before release.
  2. How will personal data be handled? Which data is collected, who can access it, where it is stored and how privacy notices fit into the flow should be discussed at the design stage. The final legal wording should be approved by your own legal adviser.
  3. What is the backup and recovery plan? Ask how often backups are taken and when a restore was last tested; an untested backup is not a backup.

After launch

  1. What does maintenance cover? Security updates, small changes, monitoring and backup checks should each be written down; "we provide support" on its own is not a commitment.
  2. Why this technology? Ask whether the chosen language and platform are common enough that another team could pick them up later.
  3. Can the references be verified? Open the live address of the work they show you and, if possible, ask for a short call with that business. A company that does not share client names without permission should still be able to describe its work in detail, anonymously.

The real benefit of a local partner is that discovery and training can happen on site; being nearby is not a quality signal on its own. The answers to the questions above matter more than the address.

Putting quotes side by side

Put the quotes into a table: these 12 questions as rows, the companies as columns. Every cell with an unclear answer can come back later in the project as extra cost or delay. The lowest price is often the quote with the most empty cells.

Let's answer these questions for your project.

Tell us what you need; we reply within one business day and set up a short discovery call.