From Scores to Shortlist: How to Run Vendor Demos and Make the Final Call

You've scored the responses. The spreadsheet (or comparison matrix, if you've moved past spreadsheets) shows a ranked list of vendors with weighted totals. Five vendors responded. Three scored well. Two are close at the top.

Now what?

This is the gap where most procurement processes stall. The scoring is done, but the decision isn't. There are demos to schedule, references to check, pricing to negotiate, and a final selection to make that the entire organization can stand behind.

Here's how to move from scores to a signed contract without losing momentum, objectivity, or your team's confidence in the outcome.

Narrowing the field: from scored list to shortlist

Not every vendor who submitted a response deserves a demo. The purpose of scoring is to create separation, and the shortlist should reflect that separation clearly.

Use the data, not the politics

Pull the weighted totals from your evaluation. Look for natural breaks in the scores. If vendors 1-3 scored between 82 and 90, and vendors 4-5 scored below 70, the shortlist draws itself. If the field is tightly clustered, focus on the section-level breakdowns to find meaningful differences.

Two to three finalists is the right number for most procurements. Fewer than two eliminates your negotiation leverage and contingency option. More than three burns time on demos for vendors who are statistically unlikely to win.

Notify non-finalists early

Once the shortlist is set, inform vendors who didn't make the cut. Don't wait until the process is over. A prompt, professional notification respects their time and preserves the relationship for future procurements. Offer brief feedback if your organization's policy allows it.

Structuring vendor demos that actually help

Most vendor demos are sales presentations disguised as product demonstrations. The vendor controls the agenda, shows their best features, glosses over limitations, and leaves your team impressed but not informed.

Flip the dynamic. Your demo, your agenda.

Send the demo agenda in advance

Provide each finalist with a structured agenda that covers the scenarios you care about most. This does two things: it forces vendors to prepare for your use cases (not their standard pitch), and it ensures you can compare demos consistently across vendors.

Focus on your weak spots, not their highlights

The best demo questions target areas where the vendor's written response was vague, incomplete, or concerning. If Vendor A scored a 3 on implementation approach because their timeline was unclear, the demo is your chance to get specifics. Prepare 3-5 targeted questions per vendor based on their proposal gaps.

A sample demo structure

Keep demos to 75 minutes maximum. Longer sessions lead to fatigue and diminishing signal.

Demo scorecards

Treat demos like you treated written responses: score them. Create a simple scorecard with 5-8 criteria that map to your must-haves. Have each evaluator score independently during or immediately after the demo. Waiting a day to score means scoring from memory, which is unreliable.

Sample demo scorecard criteria:

• Solution addressed our primary use case
• User interface was intuitive for non-technical users
• Vendor answered gap questions with specifics, not generalities
• Implementation timeline and approach were realistic
• Team demonstrated deep knowledge of our industry

Score each criterion on the same 1-5 scale you used for the written evaluation. Add demo scores to the overall vendor profile, but keep them separate from written scores so you can see both dimensions.

Best-and-final-offer (BAFO) rounds

A BAFO round invites shortlisted vendors to submit their best pricing and terms after seeing the competitive landscape (without disclosing competitors' actual numbers).

When to use a BAFO

BAFO rounds are appropriate when:

• Two or more finalists are close in scoring and you need a commercial differentiator
• Initial pricing came in above your budget range, but the vendors are otherwise strong
• You want to give vendors a chance to sharpen their offer based on your refined scope

BAFO rounds are not appropriate when one vendor is the clear leader on both score and price. Running a BAFO in that case just delays the decision and signals indecision to your top pick.

How to structure a BAFO

Send a concise request (1-2 pages) that includes:

• Confirmation of the scope (or any scope changes since the original RFP)
• Specific areas where you want vendors to improve their offer (pricing structure, SLA commitments, implementation timeline)
• Submission deadline (typically 5-7 business days)
• Clarification that this is the final opportunity to adjust their proposal

Do not reveal other vendors' pricing. Do not promise the contract to the lowest bidder. The BAFO is about getting each vendor's best offer, not about starting an auction.

Reference checks: asking the right questions

"Can you provide three references?" is the most common and least useful reference request in procurement. Every vendor provides references who will say positive things. The value of reference checks comes from asking specific, experience-based questions that reveal what working with the vendor is actually like.

Questions that surface real information

On implementation: "Was the project delivered on time and within the original budget? If not, what changed and how did the vendor handle it?"

On surprises: "What surprised you after signing the contract? What wasn't apparent during the sales process?"

On support: "When something breaks or goes wrong, how responsive is the vendor? Can you give a specific example?"

On value: "Knowing what you know now, would you choose this vendor again? Why or why not?"

On team: "Is the team you work with today the same team from the sales process? How has the relationship evolved?"

Talk to references the vendor didn't provide

If possible, find customers through your network, industry forums, or review platforms who the vendor didn't hand-pick. Unprompted references give a more balanced picture than curated ones.

Keep reference notes in the evaluation record

Document reference conversations and include them in the final evaluation packet. When someone asks six months later why you chose Vendor B over Vendor A, reference notes add critical context that scores alone can't provide.

Making the final decision defensible

Procurement decisions get questioned. By leadership, by unsuccessful vendors, by auditors, by the team that has to live with the choice. A defensible decision isn't just the right decision. It's a documented decision with a clear trail from requirements to selection.

Document the rationale

Write a 1-2 page selection summary that covers:

• Number of vendors invited and responded
• Evaluation methodology (weighted scoring, criteria, evaluators)
• Shortlist rationale (why these 2-3 vendors)
• Demo and reference findings
• Final ranking with scores
• Recommendation and reasoning (including any trade-offs)

This document protects you if the decision is challenged. It also serves as a template for future procurements.

Address the trade-offs explicitly

Rarely does one vendor win every category. If your top scorer has a higher price than the runner-up, acknowledge it and explain why the quality, capability, or risk profile justifies the difference. Pretending trade-offs don't exist undermines trust in the process.

Get sign-off before announcement

Circulate the selection summary to key stakeholders for approval before notifying the winning vendor. This is not about consensus. It's about ensuring no one with authority to block the decision is surprised by it.

How Strutter streamlines shortlisting

The gap between "we have scores" and "we have a winner" is where manual processes break down. Evaluators scored in different spreadsheets. Demo notes live in someone's notebook. Reference check results are in an email thread. Pulling it all together for a decision brief takes days.

Strutter AI keeps everything in one place:

Comparison matrix. All vendors, all questions, all scores in a single view. Filter by section, sort by weighted total, and click any score to read the vendor's full response. No spreadsheet required.

AI vendor recommendation. After all responses are scored, Strutter analyzes the data and generates a recommendation that includes the top vendor, key strengths and weaknesses, trade-offs between finalists, and areas where human review is especially important.

Audit trail. Every score, override, and recommendation is logged. When the decision is questioned, the trail is already built.

The scoring and comparison matrix feed directly into your shortlisting decision. You spend less time compiling data and more time on the judgment calls that actually matter: which vendor to demo, which references to call, and which trade-offs to accept.

The finish line

Moving from scores to a signed contract takes discipline, structure, and documentation. Shortlist based on data. Run demos on your terms. Ask references the hard questions. Document the rationale. And award the RFP with confidence.

If you're evaluating red flags in vendor responses or still building your scoring framework, start there. For the full buyer-side workflow from start to finish, see the Buyer RFP Guide.

Try Strutter AI free and see how AI-powered scoring and comparison get you from responses to a shortlist in hours, not weeks.