Choosing a software company: the questions to ask.
Most bad software engagements are avoidable at the vetting stage. Before you sign, get clear answers on who owns the code, who actually builds it, how you're priced, what happens at handover, and how it's kept secure. A good studio answers all of these without flinching.
Ask every studio these.
If they dodge any of them, keep looking.
- Who owns the code and IP? It should be you, in writing, on payment. (why this matters)
- Who actually builds it — the seniors who pitched, or juniors after you sign?
- How am I priced — fixed, time-and-materials, or retainer? What's included?
- What happens at handover — do I get the full repo, docs and access?
- How is it kept secure and compliant (GDPR, and HIPAA/PCI if relevant)?
- What if I'm not happy — milestones, exit terms, and what I keep?
What a good answer sounds like.
- 'You own everything on payment' — no hostage code.
- A scoping step first — they de-risk before quoting.
- Senior, named people on your build, not a bait-and-switch.
- A managed plan for after launch, so the build doesn't rot.
Walk away from these.
A quote with no scoping. Vagueness on who owns the code. A fixed price that seems too clean (it hides a risk buffer). No answer on handover or maintenance. Pressure to sign before you've seen a plan. These are the tells of an engagement that ends badly.
Common questions.
What questions should I ask a custom software company?
Who owns the code and IP, who actually builds it, how you're priced, what happens at handover, how it's kept secure and compliant, and what happens if you're not happy. A good studio answers all of these clearly.
How do I choose the right software development company?
Vet on substance, not pitch: confirm you own the IP, that senior people build it, that pricing and scope are clear, that handover includes the full code and docs, and that there's a plan for after launch.
What are red flags when hiring a software studio?
A quote with no scoping step, vagueness about who owns the code, a suspiciously clean fixed price, no answer on handover or maintenance, and pressure to sign quickly.
Should I get a fixed price or time-and-materials?
Each has trade-offs — fixed price hides a risk buffer and can incentivise corner-cutting; time-and-materials needs trust. The safest setups scope first, then phase the work. See our page on fixed price vs time-and-materials.
Will senior developers actually work on my project?
Ask directly — some agencies win with seniors and deliver with juniors. A studio-led model keeps experienced people on the build the whole way.
What should handover include?
The full source code, documentation, and access to every account and environment — everything you'd need to take the system elsewhere. If you can't walk away with it, you don't really own it.
Keep reading
Related questions
Ask us all of these.
Book a call and put us through your own checklist — IP, team, pricing, handover, security. We'll answer every one straight.