Before signing with a software development company, ask who owns the code, what the price excludes, who writes it, how it is tested and what happens after launch. A portfolio answers none of these. For each of the twelve questions below we have included what a good answer sounds like, so you can tell the difference between a clear answer and a smooth one.
Ownership and access
Start here, because these answers decide how easy it is to leave.
- Who owns the code, and from when? You should own it from the first commit, in a repository you control. Be wary of ownership that only transfers on final payment.
- Do we get repository and cloud access from day one? Yes, as the account owner. If the vendor hosts everything in its own accounts, leaving will be slow and expensive.
- Could another team take over this codebase? Yes, and they should be able to show you the documentation a new engineer would start from.
Money and scope
Disputes with development companies are often about things that were never written down.
- Is this fixed price, or time and materials? A clear answer for your scope, with the reason. Neither model is wrong. Vagueness is.
- What happens when the scope changes? Changes are written up with their cost and their effect on the timeline, and you approve them before work starts.
- What is not included in this quote? A specific list. Hosting, third-party licences, app store fees and support after launch are the usual gaps.
People
The people in the sales meeting are often not the people who write the code.
- Who will write our code? Named engineers you can meet before you sign.
- How much do our working hours overlap? A stated daily window, and a description of how questions are handled outside it.
Quality
You do not need to read code to check these.
- How do you test? Automated tests that run on every change, and a staging environment that mirrors production. Ask to see a recent test run.
- Do you use AI to write code, and who reviews it? Yes is a fine answer, provided every change is read by an engineer and passes the same tests as hand-written code.
After launch
Software needs attention after it ships. Agree how before it does.
- What does support after launch look like? A defined arrangement with a price, or a clean handover with documentation and a walkthrough.
- When are you not the right choice? A real answer. A company that is right for every project has not thought about the question.
What buyers say they want to see
When the review platform Clutch surveyed 451 business buyers, the most valued thing on a service provider's website was transparent cost information, chosen by 25%, followed by case studies and testimonials at 23%. The survey is from 2020, so treat it as a guide to what buyers ask for, not a current measurement: buyers want to know what it will cost and whether it has worked before.
If a company cannot answer the twelve questions above in writing, the proposal is not finished.
The short version
Ask all twelve, in writing, of every company you are considering, and compare the answers side by side. Specific answers are a good sign. So is a company that tells you where it is not the right fit.