Software Engineering UKSoftware Engineering UK
How to Vet a Development Partner's Logic
Software Engineering UK

How to Vet a Development Partner's Logic

Omar EvansWords by Omar Evans

Further up the stream

Vetting a development partner became a discipline of its own at the point where businesses stopped buying software as a finished artefact and started commissioning a process that would keep producing software. When the engagement is a process, the supplier's reasoning is the product being bought, and the first release is its earliest output.

A proposal states intent. The logic underneath it decides what happens when that intent meets an unlisted integration, a priority change halfway through the build, or the departure of the engineer who understood the payment flow. TechRound's guide to choosing a UK software development partner puts the problem directly: a polished proposal can make a project look simpler than it is, and the questions that matter arrive after the estimate, in who checks the code, how a change reaches the budget, and who keeps the system running once launch is behind you. Its argument is that solid answers on those points give a firmer basis for a decision than the pitch or the headline price.

Treat the questions as instruments. A checklist records whether an answer existed. An instrument shows how the answer was reached, which is what you will actually be relying on for the life of the relationship.

Write the brief first, then grade the questions that come back

One page, written before any supplier sees it: who will use the system, what they must be able to do with it, which existing systems it has to work with, and which outcome you intend to measure. Add the constraints that could wreck a delivery plan, such as a date the business cannot move, the engineering hours you can spare for decisions and testing, and a dependency on a supplier who is not in the room. Keep it short, keep the constraints visible, and send the same page to every candidate.

The reply is the first real evidence. A partner that turns that page into a price without asking a single question has decided that understanding your problem is not part of its job. A partner that comes back with questions you cannot answer immediately is telling you something more useful, which is where the uncertainty in your own plan sits. TechRound makes the same point in its own terms, that a constructive challenge to an unclear requirement may say more about a supplier than an immediate quotation does.

Ask for an artefact. Algorithmic's account of evaluating a software partner argues that presentations state intent while artefacts show operating discipline, and proposes that every shortlisted team receives the same limited brief and returns a small discovery pack. The shape of that pack is the instrument:

  • a design document that names the chosen architecture, the options it rejected, and the evidence that would reopen the decision
  • a reproducible development environment, with pinned runtimes, migration steps and seed data that a new engineer can run unaided
  • pipeline logs from a real project, including one failed build and how the failure was remediated
  • an ownership checklist that names roles, decision rights, accounts and handover timing
  • failure assumptions written down beside the test that would falsify each one
  • a release and rollback path that shows how code reaches production and how it is pulled back

The same artefacts from every candidate, compared side by side, produce more usable information than a week of presentations. What you are reading is not the polish of the answer. You are reading whether the team can hold a decision in writing, because that is the mechanism you will depend on when you are no longer in the room.

Read the work backwards, through the evidence it left

The strongest single test of engineering judgement is a walk through a real pull request, anonymised if necessary. Stack Seekers' technical checklist for founders sets out what the sample should contain: comments from a second engineer, requests for change, tests inside the diff, a plain-English statement of intent, and a change small enough to hold in one reading. A firm that cannot produce one is not being coy about client confidentiality. It is describing its process.

Ask the same question of the people. Active Logic Insights' vetting guide calls this the question most buyers never put plainly: who writes the code? Its author separates the sales team, the account manager and the senior architect on the kickoff call from whoever is actually architecting, testing and deploying. The guide recommends asking where those developers are, whether you can meet them before work starts, and what the balance of project managers to engineers looks like, because coordination overhead is not engineering output. It also asks who carries technical accountability, and insists that the person answerable for quality should not be the person answerable for billing.

Accelerance's description of a software partner audit widens the scope beyond code. Its audit model covers pricing and contract compliance, delivery performance and code quality, communication and client satisfaction, management practice and risk mitigation, and security around data and intellectual property. That breadth matters because a partner can pass a code review and still fail an engagement on the commercial or operational side. Assemblysoft's supplier questionnaire guidance adds a test of a different kind: the answers should already exist in writing, dated and published, before you ask for them. A partner composing due-diligence answers from scratch for your questionnaire has never been asked them by anyone.

Evidence What it establishes What it cannot tell you
Reviewed pull request That peer review is a live practice with substance in it Whether the reviewer will still be there in a year
Pipeline logs with failures That release discipline survives a bad day How the team behaves when the client is the cause
Design document with rejected options That decisions are reasoned and recorded Whether the reasoning holds under real load
Ownership checklist Who holds accounts, rights and decision authority Whether the handover will ever be exercised
Reference call with hard questions How the partner behaves when a project goes wrong Anything about a project unlike your own

Price the exit before you price the build

Commercial control is a technical property. Under the Copyright, Designs and Patents Act 1988, code commissioned from an outside company belongs to that company unless it is assigned in writing, which Tulip Tech's UK buyer's guide sets out as a contractual point. The assignment should be present-tense and total: source code, design assets, documentation, and the accounts that make the system run.

Ask which parts of the deliverable are new and which are reused. A library the partner brought to the project carries different terms from work created for you, and those terms belong in the agreement. Ask who controls the repository during development, what your team can see of it, and what an incoming team would receive on the day the relationship ended: deployment instructions, architecture records, secrets rotation, monitoring access, third-party accounts and billing authority. Assemblysoft's guidance extends the same reasoning one level down, to the subprocessors and hosting providers behind the partner, since controls held by your supplier say nothing about a firm it quietly subcontracts to.

Then price the period after launch. Tulip Tech reports that annual maintenance typically runs 15 to 25 percent of the build cost, which makes support a line in the budget. Separate fixing defects from adding features, establish who decides severity, and name who receives alerts.

Engagement models carry different risks, and the model should follow the certainty of the brief.

Model Who carries scope risk What it rewards What it hides
Fixed price The supplier A brief that is genuinely complete The cost of every change you will later request
Time and materials You Iteration and honest discovery Weak reporting on progress and spend
Capped milestone Shared Defined stages with a ceiling The assumptions sitting behind the cap
Paid trial sprint Shared, briefly Evidence about the actual team Nothing, if the real people are staffed on it

Codebrand's nearshore vetting checklist treats the trial sprint as the best single instrument available, provided the people in the trial carry into the engagement and the work is real but not critical. That condition is the whole value of it. A trial staffed by the firm's strongest engineer and followed by a different team has told you about the pitch.

Close with a decision record. Put every candidate's answers beside the same written brief, note where they diverge, and ask what each divergence would cost you across the following year. Bring in the people who will live with the result: an operations colleague spots a handover dependency that a founder reads past. Before signing, send the preferred partner the outstanding points in writing and ask for written answers in the proposal or the agreement. The partner worth choosing is the one whose reasoning your team can follow, question and manage long after the launch is forgotten.

Sources

Source: How To Choose a UK Software Development Partner in 2026, TechRound

The usual questions

How should I brief potential software partners?

Write a single page detailing users, required actions, system integrations, and intended outcomes. Include constraints like fixed dates and available engineering hours.

What artefacts should a development partner provide?

They should provide a design document, a reproducible development environment, pipeline logs, an ownership checklist, and a rollback path.

Why should I review a partner's pull requests?

Reviewing an anonymised pull request tests engineering judgement. It shows if the team uses peer reviews, includes tests in diffs, and maintains small changes.

Who should be accountable for software quality?

Technical accountability should be separate from financial accountability. The person answerable for quality must not be the person answerable for billing.

Filed so far