
You are mid-discovery and you know the buyer has a shortlist, but you do not yet know the full set of rules they will use to pick a winner.
Every buying committee member carries a different scorecard in their head. The IT lead cares about security and integrations. The CFO cares about payback. Legal cares about data residency. If you only surface one stakeholder's criteria, you are qualifying against a partial picture. Deals get lost late because a criterion you never heard of - held by someone you never spoke to - tips the vote.
You build the whole deal around the champion's priorities, then procurement sends an RFP with fifteen requirements you have never discussed. You scramble, your demo looks generic, and a competitor who did the work earlier looks purpose-built for the job.
You can map the three categories of decision criteria - technical, business, and cultural or legal - to the right stakeholders, and run discovery questions that surface the full list before the formal evaluation begins.
Map the buying committee by category first. Who owns technical requirements (IT, security, architecture)? Who owns business or economic ones (CFO, VP Ops, line-of-business)? Who owns legal or vendor-fit ones (legal, procurement, HR)? List them before your next call.
Ask broad context questions to open the conversation: 'When you have bought tools like this before, what ended up mattering most?' or 'How will you know in 12 months that you made the right call?'
Narrow to specifics for each category. Technical: 'Which integrations or security requirements are non-negotiable versus nice to have?' Business: 'What financial or operational outcome does this need to deliver to get approved?' Cultural or legal: 'Are there compliance, data residency, or vendor-fit criteria that could stop this from moving forward?'
Ask the disqualifier question: 'What would immediately rule a vendor out?' This often surfaces the highest-weight criterion faster than any other question.
Use your champion to pressure-test the list: 'Is there anyone else whose requirements we have not covered yet?' Run this check after every new stakeholder conversation.
Rep asks the champion: 'So what are you looking for in a solution?' Champion says 'ease of use and good support.' Rep notes it down and moves on. Three weeks later, the security team sends a 40-question vendor assessment the rep has never seen.
Rep maps the committee before the call: champion is VP Sales, economic buyer is CFO, IT security has a sign-off role. On the discovery call the rep asks: 'Beyond what you need from a sales perspective, what will IT need to see to approve this, and what will finance need to see to release budget?' Champion names three technical requirements and a payback threshold. Rep books a separate 30-minute call with the IT lead to cover the security criteria directly.
You can map the three categories of decision criteria - technical, business, and cultural or legal - to the right stakeholders, and run discovery questions that
You have got it when you can list at least two criteria per category for a live deal, name the stakeholder who owns each one, and confirm there is no one left whose requirements you have not asked about.
Every buying committee member carries a different scorecard in their head. The IT lead cares about security and integrations. You can map the three categories of decision criteria - technical, business, and cultural or legal - to the right stakeholders, and run discovery questions that surface the full li
You build the whole deal around the champion's priorities, then procurement sends an RFP with fifteen requirements you have never discussed. You scramble, your demo looks generic, and a competitor who did the work earlier looks purpose-built for the job.
£7-10k flat fee. The methodology, delivered.
See Hire with Assessment