MEDDIC without the homework

Every rep I know agrees with MEDDIC. Almost none of them fill it in. The framework was never the problem. The form is.

MEDDIC is six questions you should answer before you pour a quarter into a deal. What is the quantified value. Who controls the budget. What will they judge you on. What are the steps to a yes. What pain is driving this. Who is your champion on the inside. Get them right and you stop chasing deals that were never going to close.

Then the call ends, three more meetings happen, and nobody writes any of it down. What survives is a deal sitting at a stage with no reason attached. The discipline dies in the gap between the conversation and the CRM, and it dies for the same reason every CRM habit dies: someone has to type it in.

The answers are already in the email

Here is what most tools miss. By the time a deal reaches you, most of the MEDDIC answers are already sitting in the thread. The prospect told you what they are trying to fix. Their signature carries their title. The CC line shows you who else is in the room, and one of them writes like the person who signs. The moment they ask for a quote, the deal has a size.

The thinking was never the work. The typing was.

So Blake does the typing. You forward a thread to your workspace address, the same forward that is Blake's whole interface, and Blake reads it, researches the company, and files the opportunity with the qualification already attached. The buying committee gets pulled out of the thread and labelled, champion and economic buyer included, with titles and seniority filled from the web. Metrics land as the value, the deal type, and the contract length, with TCV computed for the forecast. The decision process is the pipeline stage and the next step. The pain is the stated interest and the urgency in that first message, written down in plain language.

You open the deal to a readout, not a blank form.

What an email will not tell you

Two of the six resist this, and it is worth being straight about which. Decision criteria and the live competitive picture are rarely spelled out in an inbound email. Blake surfaces what it can infer from the thread and your own context note, and asks you to confirm the rest. It does not guess them confidently and call it done. A scorecard that bluffs is worse than one that flags what is still open.

And Blake never turns the framework into a gate. There is no rule that freezes a deal until six fields go green. The point of qualifying is to make the next move obvious, not to put a checklist between you and the reply.

You do not need a RevOps team to run it

MEDDIC has a reputation as enterprise machinery, the thing you adopt once you have hired a VP of Sales and someone to make everyone use it. That reputation is mostly about who pays to enforce it. The discipline itself is just as useful to three reps closing deals over email, and it is the same instinct behind the four piles Blake already sorts every lead into. Cadillac, steak knives, coffee, cold, each with the reason written out. You can override it. You cannot pretend the question was not asked.

Take the capture away and the framework is free. A small team gets the upside of qualifying well without hiring anyone to police it.

That is the whole idea. Forward the thread, let the scorecard fill itself in, and go spend your week on the Cadillacs.