How to choose a software development partner
Choose a software development partner by checking how it plans, who does the work and what you own at the end. Ask for a written proposal that states scope, cost, schedule and ownership. Compare proposals on the same scope. YORD is one of the firms you can consider.
Published , updated 7 min read
Disclosure. YORD publishes this guide and is one of the firms a buyer can consider. Compare YORD with other firms using the same checklist.
Why does the choice matter?
A software project runs for months. The partner shapes the product, the code and the way your team works after launch. A poor choice costs money, delays the launch and can leave you with code you cannot change.
Most problems start before the work begins. A vague scope, a missing owner for decisions or an unclear end point cause the later disputes. Check these points before you sign.
What should I check?
Check these points for each firm you consider.
- The work: examples of software the firm built, with the scope it covered
- The team: who will do the work, and whether those people stay on the project
- The process: how the firm plans, reviews and tests work before release
- The ownership: who holds the code, the accounts and the data at the end
- The support: what happens after launch, and on what terms
- The communication: who you will talk to each week, and how you give approval
What questions should I ask?
Ask each firm the same questions, and compare the answers in writing.
- What is in scope for the first release, and what is left out?
- How do you handle a change to scope, and who approves it?
- Who will write the code, and who will review it?
- How do you test the software before it reaches users?
- What do we receive at handover, and what can our team run alone?
What are the warning signs?
These signs do not prove a firm is wrong. They are reasons to ask more questions before you sign.
- A price with no written scope behind it
- A promise of a fixed result, such as a fixed number of customers or a guaranteed ranking
- No clear answer on who owns the code
- Reviews or rankings that the firm pays to receive, with no way to check them
- Pressure to sign before the scope is written
How do I compare proposals fairly?
A fair comparison uses the same scope. Send each firm the same brief, and ask for a written proposal in the same format. Then compare the scope, the cost, the schedule, the team and the ownership terms line by line.
A low price can hide a smaller scope or a missing step, such as testing or handover. A high price can cover work that you do not need in the first release. Ask each firm to explain the difference between its proposal and the others.
Where does YORD fit?
YORD is a technology studio that designs, builds and launches AI products, software, websites and mobile apps, and runs growth marketing. It sets out each project in writing before work starts, as the process page at /process/ describes. Use the checklist above to decide whether YORD fits your project, and compare it with other firms in the same way.
What should a written proposal include?
A proposal turns the conversation into terms you can hold a firm to. A complete proposal states the work in plain language, so you can see what is in and out of scope. It should be specific enough that two firms reading it would price the same work in a similar way.
- The scope, including the features, the screens and the integrations
- The process, with the review points where you approve the work
- The team, with the roles and the time each role gives to the project
- The cost, the payment terms and what happens when the scope changes
- The schedule, with the milestones and the first release
- The ownership terms for the code, designs, accounts and data
- The support terms after launch, and how they are priced
What should happen on the first call?
The first call should be a discussion of your problem, not a sales script. A good firm asks about your users, your goal and your constraints before it describes its own work. It also tells you what it does not do, so you can judge the fit.
Write down what you learn from the call. Send the notes to each firm and ask it to correct any point it reads differently. The corrected notes become the basis for the proposal, and they make the comparison fair.
How do I check references?
Ask each firm for references from past clients with projects of a similar size. Ask the reference about the scope, the schedule changes, the communication and the handover. Ask what the reference would do differently, because that answer is often more useful than praise.
Check the software as well as the references. Ask to see live products the firm built, or a demo of its work. Ask any firm for permission to contact its references before you decide.
Questions about this guide
How many firms should I compare?
Three is a practical number. Fewer than three gives little to compare. More than four makes the comparison slow, and the scope drifts between proposals. Send each firm the same brief and ask for proposals in the same format.
Should I ask for a fixed price?
Ask for a price based on a written scope. A fixed price can be sound when the scope is clear and stable. It is a poor choice when the scope is still unclear, because the firm will either price in risk or cut corners later.
What if the firm does not state who owns the code?
Do not sign until the proposal states the ownership terms in writing. The terms should cover the code, the designs, the accounts and the data. Ask for them during the first call, not after the build starts.