Planning toolVendor evaluation

Software Vendor Evaluation Checklist

Alpha ExpansionFree to use, nothing to sign up for
In short

This checklist records how one software company performed against the things that predict a good project: whether it understood the problem, what evidence it showed, how clear its commercial terms are and what you would hold at the end. You rate each line strong, fair, weak or unseen. Fill it in once per company, straight after each meeting or proposal, and you have records that can be laid side by side.

Key points
  • 01Rate each company the same way, on the same lines, straight after you meet.
  • 02Unseen is an answer: it tells you what to ask for before deciding.
  • 03The questions a company asks you are better evidence than its presentation.

Rate one company

Six parts. Fill it in for a single company, download the record, then clear the form and repeat for the next. Use unseen where you have no evidence yet, instead of guessing.

Where you are with them
Did they understand the problem?
  • Restated our problem correctly
  • Asked hard questions
  • Challenged part of our scope
  • Named risks and assumptions
  • Proposed what to build first
What did they show?
  • Comparable work shown in detail
  • References we could call
  • People who would do the work met
  • Sample deliverables shown
  • Process explained with examples
How clear is the offer?
  • Price broken down by stage
  • Assumptions and exclusions stated
  • Change handling explained
  • Payment tied to deliverables
  • Costs after launch included
What would you hold?
  • Rights to code stated in writing
  • Repository in our account
  • Accounts held by us
  • Documentation as a deliverable
  • Exit and handover terms
Where this company stands now
01

How to use it

  1. 01

    Fill it in the same day

    Rate the company within hours of the meeting or of reading the proposal. Impressions blur quickly, and after three companies they merge. A record made at once is the only fair basis for comparison.

  2. 02

    Use unseen honestly

    Where you have no evidence for a line, choose unseen and do not guess. The unseen lines become your list of requests, and how a company responds to them is evidence too.

  3. 03

    Write specifics in the notes

    In strengths and concerns, record what was said or shown. A note such as asked how refunds work is useful a fortnight later. A note such as seemed professional is not.

  4. 04

    Repeat for each company

    Download the record, clear the form and start again for the next company. With the same lines rated the same way, differences between proposals become obvious, and price finds its proper place among them.

02

What separates one software company from another

Proposals for the same project often look alike and differ little in price. The differences that matter show up in four areas, which is why the checklist gives each its own part.

PartWhat it settlesWhy it matters
UnderstandingWhether they grasped the problem and its risksA company that misunderstands the brief will build the wrong thing efficiently
EvidenceWhat they showed, and who you metClaims are free, while comparable work and reachable references are not
Commercial termsHow the price is built and what changes itAn unexplained total cannot be compared or controlled
Ownership and exitWhat you hold during and after the workIt decides whether you could ever change supplier
JudgementYour own strengths, concerns and next requestsTurns a rating into a decision and a list of things to ask
03

A worked example

Illustrative example

One company rated after its proposal

The example is invented: a leisure operator rating one of three companies. Load it to see the complete record. The ratings are mostly good, and the unseen and weak lines show what to do next.

  • Strong linesUnderstanding is the best part. The company restated the problem, asked about freezes and refunds and named the risks in moving old member data.
  • Weak and unseenThe developers were not met, running costs are missing, and neither references nor exit terms have been seen.
  • Next requestsFour concrete asks follow directly from those lines, and the verdict is proceed with conditions.

Nothing in the record says this is the wrong company. It says the decision is not ready, and it names the four things that would make it ready.

04

What this tool does not do

The checklist organizes your own observations. It adds no information about any company, and it cannot weigh the lines for you.

  • It does not produce a score, on purpose. A total would hide the one weak line that matters most to you.
  • It cannot verify what a company told you. References and sample documents do that.
  • It does not replace legal review of the contract, particularly the clauses on rights and exit.
  • Nothing you type leaves this browser. Each record exists only where you save it.
05

What to do with the finished document

Lay the records for your shortlisted companies side by side and look first at the weak and unseen lines. If we are one of the companies you are evaluating, send us the list of what you still need to see. Send it through the contact page or book a 30-minute call and bring it along.

06

Common questions

Why does the checklist not give each company a score?

Because a total invites the wrong comparison. A company can collect many strong marks and still be weak on the single line that matters most for your project, such as who holds the code. Reading the ratings line by line, and weighting them by your own priorities, leads to a better decision than adding them up.

How many companies should we evaluate?

Three or four is usually enough for a real comparison while leaving time to speak with each properly. Evaluating many more spreads your attention thin and discourages serious companies from investing effort in a proposal. Shortlist by relevant experience first, then use the checklist on those that remain.

What matters more, the proposal or the meeting?

They show different things. The proposal shows how a company structures work, prices it and handles terms. The meeting shows how it thinks: the questions asked, the assumptions challenged, the risks raised unprompted. Rate both. A polished document from a company that asked nothing should concern you.

Should price be on the checklist?

Price belongs in the comparison, after you have confirmed that the proposals describe the same scope. The checklist rates how clearly a price is built and explained, which tells you whether it can be compared at all. An unusually low total with unclear assumptions is a warning, not a saving.

Next

Where to go from here

Next step

Tell us about your project

Describe what you want to build and the systems it has to work with. We reply with how we would approach it and which decisions come first. The scoping conversation is free.

Response within 24 hoursFree consultation and scopingNDA available on request

Premium digital product and engineering studio. We build high-performance web platforms, SaaS applications, mobile apps, and 3D experiences for high-growth companies.

Alpha Expansion is a premium digital product and engineering studio specializing in React development, Next.js development, full-stack development, mobile app development, UI/UX design, and 3D interactive experiences.

We serve industries including SaaS, FinTech, Healthcare, E-commerce, Logistics, and Real Estate.