The system underneath the frameworks.
Every sales framework works — until the situation stops matching its assumptions. Then it has nothing left to say except "do it better."
Most revenue programmes hand a team one framework. MEDDPICC. SPICED. BANT. Each is built on a fixed set of assumptions about how a deal works, and inside those assumptions, each is genuinely useful.
The problem is what happens outside them. When the deal doesn't behave the way the framework expects — when the qualification looks clean but the deal still stalls, when the checklist is full but nobody can say what to do next — a single-framework team has no answer. The framework can't question its own assumptions. So the coaching collapses into "do it better," and nothing changes.
A revenue team doesn't need a better framework. It needs the layer above the frameworks: a shared way to read any situation correctly first, and decide what to do — before reaching for a tool.
Current → Ideal → Action.
The system runs on one logic, and the logic is a question — asked the same way at every level of the revenue team.
Current
What is actually true right now? Not what the CRM says, not what we hope. What is verified.
Ideal
Where does this need to get to? The specific state that counts as progress.
Action
What is the single next move that closes the gap?
That's CIA. It is not a framework competing with MEDDPICC. It is the diagnostic habit that sits above all of them — the thing that tells a rep or a manager which question they're actually facing before they pick a tool to answer it.
Most frameworks tell a team what to check. CIA tells a team how to read the situation and what to do next. That difference is the entire system.
One logic. Every level of the team.
Because CIA is a question, not a script, it works wherever a revenue team has to read a situation and act — and it means something specific at each level. The content changes; the logic doesn't.
Deal review.
A manager running a deal review uses CIA to stop rescuing deals and start coaching the rep who owns one. Current: what is actually verified about this deal — not what stage it sits in. Ideal: what would have to be true for it to be real and progressing. Action: the one move the rep makes on the next call to close that gap. The manager doesn't take the deal. They coach the next action and hand it back.
Client diagnosis.
A rep uses the same logic pointed at the customer instead of the deal: read the customer's current situation honestly, define where they need to get to, decide the next move in the conversation. The specifics — what "Current" means in discovery versus late-stage, for this team's funnel — are defined with the team, not handed down.
Expansion.
CS teams use CIA to move past relationship check-ins: the customer's current adoption and value, the next milestone that matters to them, the action that gets them there. Same logic, expansion content.
One logic across the team is what makes coaching consistent. A manager, a rep and a CS lead are all asking the same three questions — so a deal review, a discovery call and an expansion conversation are finally legible to each other.
What this looks like on a real deal.
Here is the gap a single-framework team lives with every week.
A rep runs a deal through MEDDPICC. Metrics: clear. Decision Criteria: clear. Champion: identified. But the Economic Buyer line is thin — the rep has a name, but no evidence that person has ever engaged. MEDDPICC has done its job. It has surfaced the gap accurately.
MEDDPICC tells the rep what is missing. It does not tell the rep what to do about it on Thursday's call. This is where most deal reviews end — a manager says "you need to get to the EB," the rep nods, and nothing concrete changes.
- Current
- Named Economic Buyer with zero verified engagement. Every assumption about this deal's velocity rests on a person who has never shown up.
- Ideal
- Direct, verified contact with the EB — a short conversation where they confirm the problem is worth solving and the timeline is real.
- Action
- On Thursday's call, the rep asks the champion to arrange a 15-minute conversation with the EB to confirm priority — framed as protecting the EB's time, not selling. If the champion can't or won't, that is the diagnosis.
MEDDPICC found the gap. CIA turned it into a move the rep can make this week — and into a coaching conversation the manager can actually run. That handoff, repeated across every deal, is the system.
You don't throw away MEDDPICC.
Nothing here replaces the frameworks a team has already invested in. MEDDPICC, SPICED and the rest still do real work — they sharpen the Current read on a deal, and the worked example above shows exactly how.
But they sit in a specific place. Specialist frameworks are layer-2 instruments: powerful, stage-specific, and best adopted once a team already shares the CIA logic and has the skill to use them well. Handed to a team on day one — before there's a shared way to read a situation — a specialist framework becomes a checklist nobody trusts. Handed to a team that already diagnoses well, it makes the diagnosis sharper.
CIA first, because it aligns the whole team. Specialist frameworks second, where each team is ready for them. That sequence is why the system sticks when framework training usually doesn't.
See the system in full.
The free playbook lays out the whole architecture: the CIA logic, how it works at each level of a revenue team, and the worked examples — including why no framework will save a team that can't diagnose, decide and act.
One email. Playbook back the same day.
Want to see how this maps to your team's actual pipeline? Book a free 45-minute session — we'll run your current revenue motion through CIA and pinpoint where execution is breaking.
Book a session →