Tool Evaluation
Part of Marketing technology procurement
Scoring vendors against agreed business requirements
Use agreed criteria, evidence labels and clear rating anchors to compare marketing software offers without hiding essential conditions.
A vendor scorecard is useful when it shows how each proposed offer meets agreed requirements and what evidence supports each rating. Set the comparison basis before reviewing offers. Keep essential conditions visible outside the total: a strong result elsewhere does not establish that a required condition is met.
Fix the comparison basis
For each requirement, name the user, required outcome and reason it matters. Decide whether it is an essential condition or a trade-off to weigh. Ask suppliers for evidence of the same outcome while allowing different ways to deliver it. Record the edition, services and configuration proposed; a feature in another plan does not describe the offer under review.
Agree on criteria and rating anchors before responses are assessed. Record any authorised change to the comparison approach rather than changing it silently after seeing an offer.
Rate the evidence, not the pitch
A short scale can help reviewers apply the same terms. For example, 0 could mean the observed outcome failed. 1 could mean a route was described but remains unproven. 2 could mean the outcome was shown with a material condition; 3 that it was shown in the proposed setup without that condition.
These are suggested anchors, not a required standard. Mark missing evidence unassessed rather than treating it as an observed failure.
| Requirement | Importance | Evidence and setting | Rating and reason | Open condition |
|---|---|---|---|---|
| Corrected enquiry reaches sales | Essential | Receiving record in the proposed route | Record what was observed | Confirm any production dependency |
| Ordinary user maintains the workflow | Weighted trade-off | Walkthrough with the intended role | Record steps and help needed | Identify administrator work |
| Supplier supports the service | Weighted trade-off | Proposed support terms and route | Record what is included | Confirm escalation owner |
A written response, presentation, live demonstration and proof of concept offer different levels of evidence. A slide claim should remain labelled as a claim. A failed demonstration may reflect missing setup; record the explanation and decide whether a comparable follow-up is warranted.
Resolve differences between reviewers
Have reviewers write a short reason for each rating before discussing it. Resolve disagreements by returning to the agreed outcome, offer and evidence. Keep any material dissent about an essential task visible. A numerical average should not hide a specific failure in a critical hand-off.
Recommend with the conditions attached
Show essential-condition results, any weighted result, operational and cost concerns, and the evidence still needed. Explain why an option with a lower total might be preferred, or why a high-scoring offer cannot proceed. Scores support a judgement about the proposed offer; they do not replace that judgement. Give every unresolved approval condition an owner and due point.
