Playbook: How to Evaluate a Strategy Partner in 3 Phases

Most procurement frameworks were built for software licenses, not strategic judgment. When the purchase is strategic clarity — not dashboard access, not a tool subscription — the standard RFP fails.

Gartner's 2025 Marketing Technology Survey found martech utilization has dropped to 49% — organizations pay for twice the capability they use. Poor vendor selection costs 15–25% of contract value in fixes and re-procurement. Applying a software procurement lens to strategy partners is measurable waste.

This playbook gives you a three-phase framework for evaluating partners who deliver outcomes, not access.

Phase 1: Define the Decision Architecture

Lock who decides, what matters, and how you'll weight it before sending a single RFI.

1.1 Build the RACI Matrix

Strategy partner evaluation crosses marketing, procurement, and often the CTO. Without explicit decision rights, the process drifts toward consensus-by-committee.

R = Responsible, A = Accountable, C = Consulted, I = Informed

Strategy leads own evaluation. Procurement structures the process. Finance validates the model.

1.2 Weight Criteria Before You See a Proposal

The most common failure: retrofitting criteria to justify a gut pick. Lock weights first.

What's absent: feature matrices, integration counts, platform architecture. Gartner's 2026 CMO Spend Survey found 70% of CMOs say their processes aren't mature enough to scale AI — yet 15.3% of budgets go to AI initiatives. The gap isn't technology. It's turning capability into decisions.

Phase 2: Pressure-Test the Partnership Model

Run every candidate through three filters.

Filter 1: Outcomes or Access?

Ask what you're buying. "A platform," "dashboards," "proprietary data" — that's access. You'll still need a team to operate it.

Ask a strategy partner: "Within 48 hours of your brief, a decision-ready assessment with prioritized recommendations." That's a finished outcome.

Filter 2: Generalist or Category-Fit?

"Works across industries" means generalist until proven otherwise. Press for evidence in your vertical: competitor dynamics, audience segments, regulatory context. Domain depth separates reusable templates from usable decisions.

Filter 3: Subscription or Project Model?

Project-based engagements: intense effort, then shelfware. Subscription models — continuous intelligence, on-demand delivery — produce compounding returns. Context doesn't reset between engagements.

Phase 3: Validate with Evidence

Demos are theater. Reference calls are managed. Test what happens when you hand a partner something real.

3.1 The Live Brief Test

Give each shortlisted partner the same real brief your team is wrestling with. Set a 48-hour clock. Evaluate:

The partner who asks the sharpest questions before delivering understands your business.

3.2 Reference Calls That Matter

Skip the three references they provide. Ask for a client who left. If they won't provide one, that's your answer.

To active references, ask one question: "What decision did this partner help you make that you wouldn't have made without them?" Dashboards or "great to work with" = vendor. A specific strategic choice with measurable impact = partner.

The One-Page Evaluation Summary

Three weeks from brief to decision. Not three months of RFP ping-pong.