10 Questions to Ask When Choosing a Software Company
Comparing proposals on price alone is misleading. Ten questions you need to clarify before signing a contract with a software company, and what to look out for in each.
Alp3 min read
In software projects, the price difference between two proposals most often stems from differences in scope, quality and responsibility. The questions below help you compare proposals on the same footing and avoid surprises down the road.
1. Have you done a similar project before?
The industry does not have to be the same; what matters is that a job of similar complexity has been completed. If possible, see the working product and ask what proved difficult in the project. An honest answer is worth more than a flawless presentation.
2. Who will work on the project?
Find out who makes up the team, whether part of the work will be subcontracted and who will communicate with you. It matters whether the people sitting across from you in the meeting are the same people who will do the work.
3. How will the process work?
How often will you see progress? Will interim versions be shared? How will change requests be handled? In projects with regular demos, misunderstandings surface early.
4. Which model is the price based on?
- Fixed price: Predictable if the scope is clear; additional cost arises as the scope changes.
- Time and materials: You pay for the effort spent; it is flexible but requires regular reporting.
Whichever is chosen, ask for the proposal to be explained item by item and for what is out of scope to be put in writing.
5. Who will own the source code and the intellectual property rights?
This matter must be stated explicitly in the contract. Under Turkish law, the transfer of economic rights must be made in writing, and the rights transferred must be specified individually. Also clarify which repository the code will be kept in and when you will be given access.
6. What do you base your technology choice on?
A good answer is grounded in your project's needs: scale, how easy it is to find a team, maintenance cost. Widely used and well-documented technologies make the transition easier if you need to work with another team in the future.
7. How do you assure quality?
Is code review carried out? Are there automated tests? Is a separate test environment set up? Which checks are carried out before release? The answers to these questions give an idea of the number of bugs that will come up after delivery.
8. How are security and personal data handled?
Authorization, encryption, backups and access logs should be part of the architecture. If the system will process personal data, set out in the contract the obligations under the KVKK (the Turkish Personal Data Protection Law) and the company's role in this process.
9. What happens after delivery?
Is there a warranty period, and which bugs does it cover? Can a separate agreement be made for maintenance and support? What are the response times? Software requires updates and monitoring after it goes live, too.
10. In whose name will the accounts and access be opened?
The domain name, server, cloud accounts, app store accounts and code repository should be opened in the name of your business. Otherwise, when you part ways with the company, you may have difficulty accessing your own product.
When comparing proposals
Look not only at the total amount but also at how detailed the scope definition is, the out-of-scope items, the schedule and the post-delivery terms. The lowest proposal may be low because one of these headings has been left out.
A good software partner is not the one who says “yes” to every request, but the one who tells you plainly what is necessary and what is risky.
You can ask us these questions, too: take a look at our approach to custom software development or tell us about your project.