What should you ask before you hire a company to build software?

By Ranjit Bhinge, founder of Blur Studio · Updated · 7 min read

Short answer: Ask who will do the work, who owns the code, data and accounts when it is finished, what exactly is in and out of the price, how you will see progress, how security is handled, and what happens after launch. For each question, a good company gives a specific answer in writing. A warning sign is a vague answer, a promise with no detail, or "we will sort that out later". A software development company is a business that designs, builds and sometimes runs software for other businesses.

Ranjit Bhinge

You are about to hire someone to build software for your business, and you want to know what to ask and which answers should worry you.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

How to use this list

Most lists online give you 20 or 40 questions and stop there. That is not much help if you cannot tell a good answer from a smooth one. So each question below comes with the answer to listen for, the answer that should worry you, and why it matters.

You do not need to ask all of them. Pick the ones in bold first. They are the ones that cause the most pain when they go wrong. Ask by email if you can. A written answer is easy to point back to later.

Who does the work

1. Who will actually build my software?

  • Good answer: Names the people, says whether they are employees or contractors, and says who you can speak to directly.
  • Warning answer: "Our team" with no names, or a sales person who cannot say who writes the code.
  • Why it matters: Some firms sell the project, then hand it to someone you never meet. Quality depends on that person.

2. Do you use AI tools to write code, and how is the result checked?

  • Good answer: Yes or no, plainly. If yes, a person reviews every change, tests it, and is responsible for it.
  • Warning answer: Evasion, or "the AI handles it".
  • Why it matters: AI-written code can be fast and fine, or fast and full of holes. Review is the difference. If you are weighing AI builders against a human, read AI app builder versus hiring a developer.

3. Have you built something like this before, and can I talk to someone you built it for?

  • Good answer: A similar project explained in plain words, and a client who agrees to talk. Or an honest "not exactly the same, but close to this one".
  • Warning answer: Only logos, screenshots or "under NDA" for everything.
  • Why it matters: A reference call takes 15 minutes and tells you more than a portfolio.

Ownership

4. Who owns the code, the data and the accounts when we finish?

  • Good answer: You own all of it. The code sits in a repository (the place code is stored and tracked) under your account, or is transferred to you. The hosting and domain accounts are in your name.
  • Warning answer: "You get a licence to use it", or the code lives only in the company's own account.
  • Why it matters: Ownership is not automatic. The US Copyright Office explains that a commissioned work counts as a "work made for hire" only if it falls into specific categories and there is a signed written agreement. Check whether your project fits those categories rather than assuming it does. Get ownership or assignment in the contract, and ask a lawyer to read it.

GitHub, a popular service for storing code, documents that a repository can be transferred to another owner with its history, issues and settings moving with it. Ask the company if that is how they will hand over.

5. What exactly do I get at the end?

  • Good answer: A list: the code, a simple guide to how it works, how to run and update it, passwords and keys, and a short walkthrough call.
  • Warning answer: "The finished app" and nothing more.
  • Why it matters: If the person who built it leaves, a new developer needs this to take over.

Scope and price

6. What is in the price, and what is not?

  • Good answer: A written list of what is included, what is excluded, and a pass or fail check for each feature. Hosting and paid services are shown separately.
  • Warning answer: One number, no breakdown, "everything you need" with no list.
  • Why it matters: The gap between what you pictured and what they priced is where budgets blow up. My step-by-step on how to scope a small business software project shows what the list should look like.

7. How do you handle changes once we start?

  • Good answer: Every change is written down and priced before it starts. You can swap items of equal size. New ideas go on a later list.
  • Warning answer: "We are flexible, don't worry about it." Flexible usually means a surprise invoice.
  • Why it matters: Changes are normal. Unpriced changes are the problem.

8. Can we start with a smaller first phase?

  • Good answer: Yes, with a fixed price for phase 1 that is useful on its own, and a rough guess for later.
  • Warning answer: Only an all-or-nothing contract, or a large upfront payment for the whole build.
  • Why it matters: A small start limits your risk. Basecamp's book Shape Up describes the same idea: fix the time you will spend, and let the scope bend to fit. See MVP development companies for how small first versions work, and custom software development cost for how prices are built.

Working together

9. How will I see progress along the way?

  • Good answer: A working version you can click through every week or two, not just status reports. A named person who answers your messages, with a stated reply time.
  • Warning answer: "You will see it at the end" or only slide decks.
  • Why it matters: Working software shows problems early, while they are cheap to fix.

10. What do you need from me, and how fast?

  • Good answer: A clear list: who makes decisions, how many hours a week, what content or data they need.
  • Warning answer: "Nothing, we will take care of it all."
  • Why it matters: Every build needs an owner on your side. A company that says otherwise has not done this much.

11. What happens if we disagree, or if one of us wants to stop?

  • Good answer: A written way out: you pay for work done, and you receive the code built so far.
  • Warning answer: No exit terms, or you lose everything if you stop.
  • Why it matters: It is much easier to agree on this before you are annoyed.

Quality and security

12. How do you handle security and my customers' data?

  • Good answer: They can name what they do: each user only sees what their role allows, passwords are never stored in plain text, data is backed up, and keys are kept out of the code. They mention a standard such as OWASP's Top 10 or NIST's Secure Software Development Framework.
  • Warning answer: "It's very secure" with no detail.
  • Why it matters: OWASP, a nonprofit that publishes software security guidance, ranks Broken Access Control, meaning people seeing things they should not, first in its 2021 Top 10. NIST, the US standards agency, publishes a framework for secure development practices (SP 800-218). You do not need to read them, but a good company knows them. If you handle health, payment or children's data, ask a lawyer about extra rules.

13. How do you test before you hand it to me?

  • Good answer: They test against the "done when" checks you agreed, and you get to try it with real examples.
  • Warning answer: "We test internally" and nothing you can see.
  • Why it matters: A pass or fail check removes arguments at the end.

After launch

14. What happens after launch? Who fixes bugs, and what does support cost?

  • Good answer: A stated period where bugs are fixed free, then clear options for ongoing support with a price and a reply time.
  • Warning answer: No mention of support, or a lock-in where only they can maintain it.
  • Why it matters: Software needs updates. A system nobody maintains slowly breaks.

15. What will it cost to run each month, and whose account is it in?

  • Good answer: A monthly estimate for hosting and paid services, billed to your own accounts.
  • Warning answer: A bundled fee with no breakdown that makes it impossible to move.
  • Why it matters: This is the cost that continues for years.

Quick red flags

  • They will not put anything in writing.
  • They promise a fixed price and date before asking a single question about your business.
  • Pressure to sign this week because of a "special rate".
  • No questions back to you. A good builder asks as many as you do.
  • Unusually low price with no explanation. Cheap quotes often skip testing, security or handover.

Is a company even the right choice?

Not always. Depending on your size, a single freelancer, a part-time technical lead or an AI builder may fit better. See how to choose a custom software development company, fractional CTO versus development agency, and, if you started with an AI builder and got stuck, hiring a developer for a Lovable, Bolt, Replit or Cursor app. If the project is mainly about AI, use questions to ask an AI consultant before hiring.

How I'd approach this

I would shortlist two or three companies, send each the same one-page description of the process I want built, and ask the bold questions by email. Then I would compare the written answers side by side. The company that answers specifically, admits what it does not know and asks me good questions back is usually the right one, even if the price is not the lowest.

I would not pay for a full build before seeing a small first phase working. And I would not sign anything until ownership, handover and exit are written down. That one page of terms protects you more than any amount of trust.

Print this list and bring it to your first call, mine or anyone else's. If a company is annoyed by these questions, you have learned something useful.

Questions people ask

What are the most important questions to ask a software development company?

Who will do the work, who owns the code, data and accounts at the end, what is in and out of the price, how you see progress, how security is handled, and what happens after launch. These are the bold questions above. Written answers are best.

How do I choose a software development partner?

Send two or three companies the same one-page brief, compare written answers, and talk to a past client. Pick on specific answers and clear terms, not the lowest price. My guide to choosing a custom software development company goes deeper.

What are red flags when hiring a software developer?

No written terms, vague ownership, a single price with no breakdown, pressure to sign fast, no questions back to you, and no plan for support after launch. A price far below the others is also a warning, because testing, security and handover are often skipped.

Will I own the software if a company builds it for me?

Not automatically. The US Copyright Office says a commissioned work is a work made for hire only if it fits listed categories and there is a signed written agreement. Get ownership or assignment in the contract, and ask a lawyer to check it.

Should I hire a company, a freelancer or use an AI builder?

It depends on size, risk and how much you can manage. See AI app builder versus hiring a developer and fractional CTO versus development agency for the trade-offs.

How much should I expect to pay?

It depends on how much is in scope, so ask for a breakdown, not a single number. I explain the main cost drivers in custom software development cost. A smaller first phase keeps the first bill small.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…