To vet outsourced development partner candidates properly, collect evidence rather than promises: look at relevant delivered work, run a short paid trial task, question their security habits, read the contract for IP and exit terms, and test how they communicate. Score each supplier against the same checklist so the decision rests on facts.
What it means to vet outsourced development partner options
Vetting answers one question: if we hand this team our project, how likely is it to arrive working, on time, and in a form we can own and maintain? A polished sales pitch tells you little about that. Evidence does. This article is a procedure for the late stage, once you have a shortlist of two or three. If you are still deciding whether to outsource at all, read in-house versus outsourced development for a UK SME first.
Evidence of delivery
Ask for proof that is specific and checkable.
- Two or three examples of work similar to yours in type and complexity, not just the best-looking one.
- Permission to speak to a past customer, and the questions you will ask: were they on time, how were problems handled, would they hire again?
- A walkthrough of a live product, including what went wrong during the build.
- Sample documentation, such as a handover note or technical readme.
- Who actually did the work: the people on your project, not just the company.
Be cautious of references that are all logos and no detail. Also remember that a supplier may be constrained by confidentiality from showing some work; a good one will explain that and offer an alternative.
The paid trial task
The strongest signal available is watching the team do real work. Pay for a small, self-contained piece of the actual project, so both sides take it seriously and you avoid free spec work.
A good trial task is:
- Small: something that fits within a short, fixed window and a modest, pre-agreed budget.
- Representative: it touches the real stack and some real ambiguity, such as one screen with a form, validation and a database write.
- Checkable: you can run it, read the code and compare it with the other candidate on the same brief.
- Independent: it does not depend on information you only have in your head.
Judge more than the output. Did they ask sensible questions? Did they flag a risk in the brief? Is the code readable, with sensible commit messages and a note on how to run it? Did they deliver when they said they would? The way someone handles a small task previews how they will handle a large one.
Security and data handling
Whoever you hire will probably touch your code, servers and perhaps customer data. Ask practical questions and expect specific answers.
- How do you manage access to our repository, servers and accounts, and how is access removed when someone leaves the project?
- Do developers work on personal or company-managed devices, and how are those protected?
- How are secrets and credentials stored and shared?
- Will any personal data be used for development or testing, and if so, how is it protected? Can test data be anonymised?
- Do you follow a secure coding checklist, such as the OWASP guidance?
- Where will our data and backups be stored, and which sub-suppliers will see it?
- What is your process if you discover a security incident?
If personal data is involved, your obligations under UK data-protection law apply, including having a suitable written agreement with a supplier that processes data for you. Confirm current requirements with the ICO or a qualified adviser.
Contract and IP terms
Read the contract before you commit, and have a solicitor review it; this section lists what to look for, not legal advice.
- Ownership: that the intellectual property in code written for you is assigned to you, and when that happens (on payment, for example).
- Third-party and open-source components: what is included and under which licences.
- Payment terms: milestones tied to deliverables you can accept, rather than large payments upfront.
- Acceptance: how you test and approve work, and what happens to defects found after delivery.
- Exit: notice terms, handover of code, documentation and accounts, and whether you can hire someone else to continue.
- Confidentiality and liability clauses that match the risk of the project.
Financial and legal diligence goes further than this; see our software vendor due diligence checklist for the contract and company-health side. Keep this article for the trial and evidence process.
Communication fit
Many projects fail on communication, not code. During the trial, note response times, clarity of written updates, willingness to say "I don't know" or "that will take longer", and overlap with UK working hours if your team is in a different time zone. Agree up front on the channel, the weekly update, who attends demos and who can make decisions on each side.
Scorecard
Score each candidate from 1 to 5 on each row, weight the rows that matter most to you, and compare totals. A low score on a critical row can outweigh a high total.
| Area | What good looks like | Candidate A | Candidate B |
|---|---|---|---|
| Delivery evidence | Relevant work, a reachable reference, named team | ||
| Trial task | On time, readable code, good questions | ||
| Security | Specific answers on access, secrets and data | ||
| Contract and IP | Clear assignment, fair acceptance and exit terms | ||
| Communication | Prompt, plain updates and candid about risk | ||
| Fit for your size | Your project matters to them |
Next step
Pick your two finalists, write one brief for a paid trial, and score both on the table above. If you are still deciding which type of supplier suits you, our comparison of agencies, freelancers and development companies helps. You can also talk to our UK software development team; we work remotely.
Frequently asked questions
What is a good trial task?
Choose a small, paid, self-contained piece of your real project that can be finished in a short fixed window, such as one form with validation and a database write. It should be checkable, use your actual stack and be given to each finalist on the same brief so you can compare fairly.
How should IP be assigned?
The contract should say that intellectual property in code written for you transfers to you, and state when, commonly on payment. It should also list third-party and open-source components and their licences. Have a solicitor review the wording, since the right terms depend on your project.
What security questions matter?
Ask how repository and server access is granted and removed, how credentials are stored, whether real personal data is used in testing, which devices developers use, where data and backups sit, who the sub-suppliers are, and what happens if there is an incident. Look for specific answers, not general reassurance.