MEDDPICC in a real deal: how I qualified and closed a US$1.2M contract in APAC

MEDDPICC is an enterprise sales qualification framework — Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition. Most reps treat it as CRM admin to fill in after the calls. Used properly, it isn't paperwork about the deal. It is the deal.

Here is what each letter looked like inside a real one: a US$1.2M total-contract-value, 18-month, greenfield pursuit with a large bank in APAC — won against two established vendors and an internal build option, through a procurement-led RFP, with nine distinct stakeholder groups at the table.

This is a real deal from my own pipeline. Out of respect for confidentiality, the institution, the individuals, the vendors, and certain specifics are deliberately unnamed or generalized. The lessons are exact.

For context: I lead enterprise sales in APAC for one of the leading assured integrated reporting platforms. The buyer was the finance office of a large bank — an organization whose annual and interim reporting ran on manual processes, version-controlled chaos, and a quiet, institution-wide lack of trust in its own numbers. They had lived with it so long it felt normal. That detail matters; we'll come back to it.

MMetrics

The deal didn't start with a metric. It started with adjectives — "complex reporting," "slow decisions." Adjectives don't get budget. So we co-built the number with the customer: a 35%+ finance productivity and efficiency target, modeled into a full ROI case, pressure-tested by their own business-case team and validated against independent third-party economic research.

The discipline here: the metric must be the customer's number, in their model, defensible in their boardroom without you in the room.

EEconomic Buyer

Budget authority sat in the finance controller's office, two levels above our day-to-day contacts. The mistake most reps make is asking their champion for an introduction and accepting "I'll represent you upward" as a yes.

We earned separate access instead: a dedicated executive connect with our regional leadership, and — the move that mattered most — hosting the controller at our Singapore office, on our turf, peer to peer. The economic buyer doesn't attend your demos. Either you build your own line to them, or your E is a name in a CRM field.

DDecision Criteria

By the time evaluation criteria appear in an RFP document, someone has already written them — and if it wasn't you, it was a competitor. We engaged before the specs were locked, sharing banking best-practice templates and shaping the criteria conversation around what actually predicts success in this category: functional depth, technical fit, information-security readiness, and future-readiness — would the platform still be the right answer five years out?

DDecision Process

Eighteen months sounds like one long sale. It isn't. It's a sequence of gates, each with its own owner and exit criteria: an art-of-the-possible workshop to expand their sense of what was achievable → a proof-of-value on their own annual-report data (we scored 4.3/5; generic demos would have scored generic) → RFI → RFP → joint business case → approval. We mapped every gate, and where we could help the customer move faster, we did — including drafting the skeleton of their internal direct-sourcing approval letter so their team could adapt it rather than start from blank.

You're not selling a product through this process. You're project-managing a decision the customer has never made before, on rails they've never run.

PPaper Process

Here's the embarrassing part: we missed their budget cycle. In an institution that plans annually, that's not a delay — it's a season. The recovery was a work-back plan, institutionalized with the champion, that mapped backwards from the next funding window through legal, infosec, and procurement, with named owners and dates.

We also pushed our master services agreement as the base template (banks redline less when the paper already reflects how institutions like them buy), ran a standing legal-review cadence, and treated information-security clearance as its own parallel workstream rather than a final-mile surprise.

IIdentify Pain

Early on, a senior stakeholder told us, in so many words: "We don't have any problem." And from where they sat, that was true. Manual consolidation, late nights before board reporting, static numbers in a moving world — it had all been normal for years. Pain that's been normalized stops registering as pain.

The unlock was before-and-after scenario mapping and an honest accounting of the cost of doing nothing: decisions slowed by data nobody fully trusted, risk and penalty exposure, and a finance team spending its talent on assembly instead of analysis. We never argued they had a problem. We built the mirror and let them look.

CChampion

We developed two champions: an assistant controller who led the evaluation, and a senior change manager driving the business case. Then, mid-deal, the change manager changed roles. In a single reorganization announcement, half my champion coverage evaporated — the scariest week of the cycle, compounded by a classic IT-versus-Finance standoff over who owned the decision.

What saved the deal wasn't a heroic recovery. It was boring, early multi-threading: because we already had relationships across nine stakeholder groups, we remapped the committee within days and developed a new internal voice — a data architect on the business-case team — while an internal coach helped us navigate the politics. We ran explicit gives-and-gets with our champions: what the deal would do for the institution, and what it would do for them.

CCompetition

On paper we faced two established vendors — a financial-close specialist and a corporate performance management platform. In reality, the most dangerous competitor was the third option: build it internally. Status quo with an engineering budget.

The compete strategy had three legs: a custom demonstration on their own reporting data, so the comparison was concrete rather than feature-list theater; reference checks with peer institutions already live on our platform, including one in the same sector; and reframing build-versus-buy around total cost of ownership — not the build cost, but the decade of maintenance, attrition, and audit risk that follows it.

The three moments this deal nearly died

Month two: "We don't have any problem." Survived by refusing to pitch and building the cost-of-doing-nothing case instead.

The missed budget cycle. Survived by converting embarrassment into structure — the work-back plan that ran the deal from then on.

The champion reorganization. Survived only because multi-threading had started twelve months before it was needed.

Notice what all three have in common: none were closed with a clever line in a meeting. All three were closed by work done earlier, quietly, when nothing seemed wrong. That's what qualification actually is — not a stage you pass, but a discipline you run continuously for eighteen months.