Run MEDDPICC on a technical discovery call by starting with the engineer's current workaround. Ask what it costs in their own units. Cover the pain, the metrics and the decision criteria on the call. Leave with a champion candidate, a booked scoping session and the name of whoever approved the last comparable tool.

What can a first call with an engineer establish?

MEDDPICC began as MEDDIC at PTC in 1996 (MEDDICC). The letters stand for Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Implicate the Pain, Champion and Competition.

An engineer knows the system and its failures in detail. Budget and approvals usually sit elsewhere. After call one, expect this state:

  • Firm: Implicate the Pain, Metrics and Decision Criteria.
  • Partial: Champion (a candidate), Competition, Decision Process and Paper Process.
  • A lead only: Economic Buyer, as a name or a title.

What is the running order for the call?

Use this order for a 30-minute call. First, learn the problem:

  1. State your dated reason for calling in one sentence. Ask whether it matches what they see.
  2. Ask for a walk-through of the current system and the workaround. Listen for 10 minutes.
  3. Pick the failure they described with the most feeling. Ask how often it happens and how they measure it.
  4. Ask what a replacement must do on day one, and what would rule a product out.

Then test the deal:

  1. Show the one part of the product that answers the failure. Skip the tour.
  2. Ask what else competes for the same engineers this quarter.
  3. Ask who approved the last comparable tool, and what the vendor had to fill in.
  4. Book the scoping session before the call ends, with a solution architect on the invite.

Step 8 sets up technical scoping, stage 2 of the enterprise B2B sales cycle. A call that ends with "send me something" has not passed stage 1.

How do you get metrics from someone who does not own the budget?

Collect the numbers in engineering units first. Examples are hours lost per incident, incidents per month, or the share of requests that fail. On this call, get the inputs and their source.

Show the engineer one formula:

  • Engineer hours lost per month, multiplied by the loaded hourly cost.
  • Plus the revenue or volume lost during each failure, if customers feel it.
  • Plus the cost of the roadmap item the team cannot build while it maintains the workaround.

The buyer must be able to check the number against its own systems. Ask where it lives: a dashboard, a ticket queue or someone's memory. Confirm a number from memory before it goes in the pilot plan.

How do you tell whether the engineer is a champion?

Give them a task and see whether they do it. The framework's publisher describes a champion as someone with power, influence and credibility inside the buyer. A friendly engineer who likes your API may have none of those. Three tests work on a first call:

  • Access: ask them to bring a solution architect to scoping. A champion names the person and sends the invite.
  • Information: ask for the last vendor's security questionnaire. A champion finds it or names who holds it.
  • Self-interest: ask what a fix would do for them personally. A champion has an answer, such as ending on-call pages.

An engineer who passes one test is a useful coach. An engineer who passes all three is a champion candidate, and a sponsor above them must confirm it.

How do you find the Economic Buyer through an engineer?

Ask about the past. Engineers can usually say who approved the last tool in their category, but often not who holds the budget. The Economic Buyer has overall authority in the decision and usually enters at the MOU.

Get the name early, because the group is large. Forrester reports 13 internal stakeholders and nine external influencers in the typical buying decision (Forrester, January 2026). Procurement professionals are decision-makers in 53% of buying cycles.

Write the name in your notes with its source and date. Confirm it with a second person at scoping. That person signs the MOU or LOI, so a wrong name costs you the stages in between.

Why ask about the Paper Process on a technical call?

The Paper Process is the series of steps from decision to signature. The engineer who sat through the last vendor's security review can describe it from memory. Ask how long it took and what held it up. Then prepare the evidence pack in how B2B startups get through vendor due diligence faster.

Ask about Competition in the same part of the call. For a technical buyer, the strongest competitor is often an internal build or a roadmap item. Neither shows up on a vendor comparison.

What do you do in the hour after the call?

Score each letter as firm, partial, lead or unknown. Write the three facts that changed your view of the deal. Send the engineer a short recap with the failure in their words, the metric and its source, and the scoping date.

Ask them to correct it. A corrected recap is the first written proof that they will work with you.

To book discovery calls with engineers at companies that have a dated reason to act, get five named buyers, free.