Guide · Updated October 2026
How to choose a software development company: a checklist
Most failed software projects are decided before the first line of code: the wrong partner, a vague scope or a contract that leaves the code with the vendor. This checklist is what we would use ourselves if we were hiring a development company — including the questions that make vendors like us uncomfortable.
Guide
1. Define the job before you compare vendors
- Write one page: the problem, who will use the system, what they do today, and what “done” looks like in numbers (hours saved, orders processed, launch date).
- List the systems it must connect to: accounting, CRM, telephony, payments, identity.
- Decide your deadline and priorities honestly. A vendor can only propose a sensible scope if it knows the constraints.
- Check whether an off-the-shelf product already covers 80–90% of the need. If it does, buy it; a good vendor will tell you the same.
2. Shortlist on relevant evidence, not on size
- Similar systems built. Ask for two or three projects close to yours in type (CRM, SaaS, mobile, integrations) — not just in industry.
- Who actually builds it. Ask for the names and seniority of the engineers who will work on your project, and whether they are employees or subcontractors.
- Independent reviews. Clutch, GoodFirms and G2 reviews are verified to different degrees; read the negative ones and how the vendor responded.
- Fit of size. A 1,000-person firm and a small senior team both deliver good software; what matters is whether your project is important to them.
3. Compare engagement models
| Model | Works best when | Watch out for |
|---|---|---|
| Fixed scope | Requirements are clear after discovery | Slow change requests; vendor padding the estimate |
| Time and materials | Scope will evolve, long-running product | Open-ended — insist on weekly reporting and agreed limits |
| Dedicated team / engineer | Ongoing development of your own product | You manage priorities; quality depends on the people |
| Freelancers | Small, well-defined tasks | Continuity and code quality on larger systems |
4. Questions to ask every vendor
- Who owns the source code, repositories, cloud accounts and domains — from day one, not only at the end of the project?
- What exactly is delivered at the end of discovery, and can we take it to another vendor?
- How often will we see working software, and can we open a staging environment at any time?
- How are scope changes estimated and approved?
- What happens if a key engineer leaves?
- What does support after launch include, and what is the response time?
- Which parts would you recommend we buy rather than build?
5. Contract essentials
- Intellectual property assigned to you; source code in your repository throughout the project.
- NDA and data processing terms if personal or customer data is involved.
- Milestones tied to working, demonstrable software — not to hours or documents.
- Acceptance criteria, warranty period for defects and a clear termination clause with handover.
Red flags
- A precise fixed scope after a 20-minute call, with no discovery.
- Code hosted only in the vendor’s accounts until the end of the project.
- You never talk to an engineer before signing.
- No questions about your business process — only about features and screens.
- Reviews that are all five stars with no detail, or case studies with no description of what was actually built.
How SilentCore answers these questions
Code, cloud accounts and data are created in your name from the first commit; discovery produces a written specification you keep; you see a working demo every Friday; scope changes are agreed before they are built. See how we work, case studies or get a quote. For a neutral shortlist, read custom software development companies for small and mid-size businesses.
FAQ
Questions we are asked most
How do I choose a software development company?
Write a one-page brief, shortlist vendors with similar systems built, talk to the engineers who will do the work, compare proposals for the same written scope, and make sure the code and accounts belong to you from day one.
Should I choose fixed scope or time and materials?
Fixed scope after discovery works well for a defined first release. Time and materials with weekly reporting suits evolving products. Avoid a fixed scope given without discovery.
What questions should I ask a software development company?
Who owns the code and accounts, who exactly will build it, how often you will see working software, how changes are agreed, what support includes and what they would recommend you buy instead of build.
Is it safe to hire an offshore or remote development team?
Yes, if ownership, communication and quality are controlled: code in your repository, regular demos, overlap with your business hours, an NDA and milestones tied to working software.
Contact
Talk to the people who will build it
Planning a project like this? Describe the system in two minutes — we reply within one business day and send a written scope after a short call.
More guides
Services