Buying Committee Mapping: SPICED Language by Persona

On-demand reference for the sales-methodology skill.

Different personas in the DMU care about different SPICED elements. Tailor your conversation.

Chief Revenue Officer (Economic Buyer, Executive Sponsor)

• Cares most about: Impact (revenue upside, forecast accuracy, growth targets), Critical Event (board cycle, capital efficiency), Decision (process, speed to implement)
• SPICED language: "You're aiming for 50% growth. Today your forecast is ±30%, which makes planning risky. If we get to ±10%, you can confidently hire and budget. Board meets in May — 12-week window to show improvement."
• Key question: "If you could choose one thing to fix in your GTM in the next quarter, what would it be?"
• Objection handler: Never lead with features. Lead with business outcomes. "This solves your forecast problem because we embed qualification discipline at each stage."

VP Sales (Champion, User Buyer)

• Cares most about: Situation (how it fits their team's workflow), Pain (rep experience, pipeline quality), Decision (ease of adoption, rep buy-in)
• SPICED language: "Your reps are working low-quality pipeline because there's no shared qualification standard. SPICED gives them a framework that actually works — helps them disqualify faster and focus on winnable deals."
• Key question: "What does a bad rep experience look like in your current process? Where do reps get stuck?"
• Objection handler: Address adoption head-on. "We know reps won't use a framework that feels like extra work. SPICED lives in your CRM; it's how deals move through stages. Reps adopt it because it makes their job easier, not harder."

Sales Operations / Enablement (Technical Buyer, Process Owner)

• Cares most about: Situation (system integration, data hygiene), Pain (manual processes, reporting, data quality), Decision (implementation effort, ongoing support)
• SPICED language: "You're spending 15 hours/week reconciling forecast data because there's no clear qualification definition. SPICED standardises the language. Once reps consistently score deals in your CRM, forecasting becomes automatic."
• Key question: "What's your biggest pain point in CRM today? What data is unreliable?"
• Objection handler: Be prescriptive. "Here's how we implement this: Day 1, create 5 custom fields in your CRM. Week 2, train reps on scoring. Week 4, we lock stage gates so deals can't move without minimum scores. Within 8 weeks, you're running from clean data."

CFO / Finance (Economic Buyer, Fiscal Gatekeeper)

• Cares most about: Impact (ROI, payback period, reference customers), Pain (quantified savings or revenue), Decision (contract terms, risk, implementation timeline)
• SPICED language: "You identified €300K/year in wasted AE capacity due to poor qualification. SPICED reduces that by at least 50%, saving €150K. Implementation is 8 weeks, zero disruption. ROI = 1.2x in year one."
• Key question: "What's your approval threshold for new software? What does the business case need to show?"
• Objection handler: Show the math. "If we free up 15% of AE time and redeploy it to new business at 30% close rate, that's 6 deals/AE × 12 AEs × €80K ACV × 30% = €1.7M incremental ARR. Software costs €80K/year. That's 21x ROI."

CTO / Head of IT (Technical Buyer, Gatekeeper)

• Cares most about: Situation (system integration, data architecture), Pain (integration debt, security, compliance), Decision (implementation burden, ongoing support)
• SPICED language: "This integrates with your HubSpot via API. No custom integration needed. Security: SOC 2 Type II, GDPR-ready, on-premise or cloud options. 4-week implementation."
• Key question: "What systems does this need to integrate with? Any compliance or security requirements we need to know?"
• Objection handler: Be technical, not marketing. "Here's our API docs. Here's our security whitepaper. Here's the data that flows: deal stage + SPICED scores sync to your BI tool every 4 hours. No data lives in our system; we're a processing layer on top of your HubSpot."