Choosing a Software Partner: Checks You Can Verify
By Mudabbir Hasan, Co-founder · Published · Last updated
Check what you can verify yourself first: that the company on the proposal is the one that will sign, that its past products are live and open to inspect, and that the named people exist. Then make the vendor produce what only they hold: reference calls on similar projects, the named team before signing, clauses on code and data ownership, and a handover plan. Score evidence, not confidence.
Why do most vendor checklists not help you decide?
They list criteria such as technical capability, communication and pricing transparency, and leave you to judge each one on the vendor's word. All three guides we read are written by software firms or a vendor directory, and each steers you to its own services or directory. The useful idea in them is narrower: score evidence, not sales confidence. Brandligo, a software-company directory, says to score each area from 1 to 5 on evidence and warns that a high total should not hide a failure on a mandatory requirement.
A practical way to apply that is to split the checks in two: the ones you can run yourself without asking the vendor anything, and the ones where the vendor has to produce proof.
What can you verify yourself in an hour?
- Does the company name on the proposal match the legal entity that will sign the contract and take payment? Brandligo lists matching the contracting entity to the proposal as a basic check.
- Can you open what they say they built? A live website, or an App Store or Play Store listing, is stronger evidence than a screenshot. Brandligo calls a portfolio screenshot weak evidence.
- Do the named people exist? Look at the team's public profiles and compare them with the people who appear in the proposal. The Competenza advises looking at the actual developers, not sales presentations.
- Do the case studies describe a problem and a result, or only a logo? Brandligo's advice is to get references on projects that resemble yours, including what happened after launch.
Who produces the proof?
You can check alone
- The company on the proposal is the one that signs
- Live products and store listings you can open
- The named people exist in public
- Case studies describe a problem and a result
Make the vendor produce
- The team, by name, before you sign
- Two reference calls on similar projects
- Ownership clauses for code and data
- A handover and data-export process
What should you make the vendor produce?
- The team, by name, before you sign. Brandligo lists a vendor that will not name the team before signature as a red flag.
- Two reference calls on projects similar to yours, including what happened after launch. Brandligo's red flag here is references that cannot be contacted or do not resemble your project.
- Ownership in the contract: code, data and IP, with repositories and cloud accounts you control. Production infrastructure that must stay in the vendor's accounts is another red flag on the same list.
- A termination, handover and data-export process, in writing.
- A change-request process with an approval step and a price, so scope changes do not arrive as a surprise invoice.
Red flags
Will not name the team before signature
References that cannot be contacted
Ambiguous code or IP ownership
Production infrastructure in the vendor's accounts
No termination or handover process
What about AI claims?
Talk Think Do, a software firm, treats AI maturity as a top-tier criterion in 2026. Its red flags are useful whoever you hire: a vague "we are AI-first" with no evidence, being unable to name the tools used, AI-generated code shipped without human review, and an unclear position on who owns it. Its own speed claims are self-reported and link to its own pages, so verify any figure a vendor quotes about faster delivery.
Is a small paid trial a better test than a sales call?
Both Talk Think Do and The Competenza recommend starting with a discovery phase, which lets you see how a vendor reasons, communicates and handles risk before committing to a build. It also gives you a document you can compare. If you want to run it, our guide to paid technical discovery explains what it produces and when to skip it.
Read: Paid technical discovery, what you get and when to skip it
How does MetaBuf measure up to its own checklist?
You can apply the same checks to us. Our case pages link to the live products where one exists, for example the Tooting Fish & Kebab ordering app on the App Store. Each team member has a page that links to their LinkedIn profile. Some of our AI work is confidential. Those case pages say so and describe only what the client allows. By the standards above, confidential work is weaker evidence than a product you can open yourself, so weigh it that way.
What should you do before you shortlist?
- Pick the three checks you can run alone and run them on every candidate.
- Send each shortlisted vendor the same request, so the answers are comparable.
- Score what you actually saw, and mark verbal assurance as exactly that.
- Ask for the contract's ownership and exit clauses before you negotiate price.
If you want to test us on any of this, ask for it in the free project call.
Shortlisting in four steps
- 1
Run the solo checks on every candidate
- 2
Send each shortlisted vendor the same request
- 3
Score what you saw
Mark verbal assurance as exactly that.
- 4
Ask for ownership and exit clauses before price
Sources
- Software Vendor Due Diligence Checklist (2026): 25 Checks, Brandligo (accessed 2026-10-10)
- Choosing a Software Development Partner, Talk Think Do (accessed 2026-10-10)
- How to Evaluate Software Development Partner in 2026, The Competenza (accessed 2026-10-10)
Related guides
Talk to an engineer about your project
Start with a free project call. We learn what you are building and recommend the right next step, with no pitch.
Book a call