What MIQL is.

A simple inspection layer for the revenue function, built on the premise that most pipeline reviews are stories, not assessments.

MIQL stands for the five pillars of evidence in any deal: Outcome, Maps, Insight, Quantify, Leadership. For each pillar, you ask whether it's a 2 (evidence confirmed by the buyer in their words), a 1 (the work happened but the buyer hasn't adopted it), or a 0 (none).

The total maps to a forecast category. 8 or higher is Commit. 7 is Most Likely. 5-6 is Best Case. Below 5, the deal is Pipeline regardless of close date.

That's the framework in one paragraph. Everything else in this manual is the practical work of running it on real deals, in real reviews, with real teams.

If you only read one section in this manual, this is the section. The rest is application.

The five pillars.

Each pillar is a question you ask the deal. Not the rep. The deal.

Notice what these questions are not. They are not asking what the seller did. They are asking what the buyer adopted. The seller did the value exercise is a 1. The buyer validated the dollar figure in their own data is a 2. The difference is everything.

Why these five

Other frameworks add pillars (paper process, decision criteria, champion, competition). They're fine. MIQL is deliberately five because five is what fits in a pipeline review without compressing the conversation. If you can't get five right, adding three more won't save you.

The 2 / 1 / 0 logic.

Three states per pillar. No half-points. No partial credit. The simplicity is the point.

2 means evidence confirmed. The buyer adopted it. They said the words. They wrote the email. They validated the number. They put their name on the milestone. There is a record of the buyer doing the thing, in their voice or their data.

1 means the work happened but adoption didn't. You ran the workshop. You sent the value calculator. You drafted the MAP. The buyer went along. They didn't push back. But they also didn't own it. If the deal stalls, no one on the buyer side is going to defend it.

0 means none. Not started. Not attempted. Not present. A 0 is honest. A 1 is sometimes a 0 in a nicer suit.

The math

Add the five pillar scores. Maximum is 10. The total maps to a forecast category:

• 0 to 4: Pipeline. Deal exists. Not commit-eligible.
• 5 to 6: Best Case. Some structural pillars confirmed. Useful for upside math.
• 7: Most Likely. Defensible in a forecast call but with documented gaps.
• 8 or higher: Commit. The forecast survives a board read.

The forecast category follows the score. Not the close date. Not the AE's confidence. Not the relationship. The score.

Two structural blockers.

Some pillar scores break the math. They're not deductions, they're caps.

O at 0 caps the deal at Pipeline

If the buyer hasn't articulated an outcome, you don't have a deal. You have a relationship. The forecast is Pipeline regardless of what every other pillar scores. There is no exception. Even a 9 with O at 0 forecasts as Pipeline.

This sounds harsh. It is the most common forecast disaster in B2B sales: deals categorized as Commit because the rep felt good and the close date was imminent, with no validated outcome anywhere in the deal record. They slip every quarter, and the rollup eats the variance.

M at 0 caps the deal at Best Case

Without a Mutually Agreed Plan that has buyer-side owners, the deal is being shopped or held at arm's length. Forecasting confidently on M at 0 is fiction. One exception: if O is at 2 and L is at 2, the deal qualifies as Executive-Led. The leader is carrying the deal in lieu of a formal MAP.

The Executive-Led path

When O is 2, M is 0, and L is 2, the deal is on a different track. It forecasts on the leader's word, not on the MAP's milestones. Tag it as Executive-Led. If it slips, the postmortem belongs to leadership, not the AE.

What this changes.

Not a methodology, not a process change. An inspection layer that sits on top of whatever you already do.

MIQL doesn't replace MEDDPICC, MEDDIC, BANT, Challenger, SPIN, or whatever methodology your team already uses. It doesn't replace your CRM. It doesn't replace your deal sheet. It is the evidence layer that asks whether the boxes already getting checked have anything behind them.

Used weekly, MIQL changes three things in measurable ways within a quarter:

• Forecast accuracy lifts. Commit deals close at the rate Commit deals should close. The 70-percent-forecast / 50-percent-close gap closes.
• Deal review duration drops. Story-led reviews ran 60 minutes. Score-led reviews run 25.
• Coaching becomes specific. Instead of work the deal, you're coaching get Q to 2 by Friday. That conversation has a different relationship with skill development.

That's why this manual exists. The framework is small. The discipline is the work.

Find your motion.

The framework is the same across the revenue function. The application is different. Pick your motion below. For each, there is an IC guide and a manager guide.

The IC guide is the audit itself. Open the Audit tab, pick your role, and the five questions calibrated to your motion are right there. Score a real deal in three minutes. The audit is the IC's daily tool.

The manager guide is the meeting template. How to run weekly deal reviews under MIQL. The five inspection questions in inspection voice. The forecast bar. Three coaching plays. The Monday-ready meeting structure.

Cross-team coordination

When MIQL operates across Sales, SE, and Customer Success simultaneously, the score becomes a shared language. Sales runs deal reviews on it. SE uses it as the POV approval filter. CS uses it on renewal forecasts. Same five pillars, three different uses, three different team owners.

The cross-team operating agreement is one page. Co-signable by VP Sales, VP SE, VP CS. Locks MIQL in as the shared inspection layer so it doesn't get tagged as belonging to one team.

The 90-day install.

If you own enablement, training, or sales operations, this is the program. The full Enabler's Brief is downloadable below. This page is the orientation.

Most sales methodologies fail at install, not at design. The framework gets introduced in a kickoff workshop, the team nods, the wallpaper goes up in the war room, and within six weeks the team is back to story-led reviews. Nothing changed.

MIQL installs differently because it doesn't require a methodology change. It is an inspection layer that sits on top of what the team already does. The work is making sure managers actually use it weekly, not making sure reps memorize five new acronyms.

The arc

• Weeks 1-2: Calibration. Managers run the audit on their three biggest deals before any rep training. Score reveals where the org actually is.
• Weeks 3-6: Manager-led adoption. Managers bring MIQL into weekly deal reviews. Reps learn by doing, not by training. Light coaching, heavy modeling.
• Weeks 7-10: Operational integration. CRM fields get added (Outcome captured verbatim, MAP completion rate, EB engagement decay). Pipeline reports reflect MIQL scores.
• Weeks 11-13: Cross-functional handoff. Sales, SE, and CS sign the Operating Agreement. MIQL becomes the shared language, not a sales-only tool.

What you, the enabler, actually do

The Enabler's Brief details the program week by week. The summary version: you are not training reps, you are coaching managers. Managers run the new review format with you observing for three weeks. You correct the inspection-voice questions. You catch when they revert to story. You hold the line on score-driven forecasting until it's muscle memory.

The reps will learn from the manager modeling it. That's the only training that sticks.

The complete library.

Every document in the Field Manual, available in one place. Use these as leave-behinds, training materials, or co-signable artifacts.

• One-Pager · Universal two-minute read. Generic.
• Manager's Card · Two-page reference for sales managers running deal reviews.
• Enabler's Brief · The 90-day install plan.
• SDR/BDR Leader Guide · Pipeline reviews, MIQL-style. For SDR managers.
• AE/SE Leader Guide · Deal reviews, MIQL-style. For sales managers and RDs.
• SE One-Pager + SE Operating Guide · For the SE org. Partnership in stages 1-2, gate at stage 3.
• Renewals One-Pager + Renewals Leader Guide · For the CSM org. Cost of switching, sponsor decay, expansion signal.
• RevOps Leader Guide · For the RevOps director. Five system inspections, three operating moves.
• Cross-Team Operating Agreement · One page. Co-signed by VP Sales, VP SE, VP CS.

If you're running the install as the lead enabler, work backward from the Operating Agreement. That's the artifact you're trying to get co-signed at the end of week thirteen. Everything else exists to get you there.