Home › Blog › Setting up MEDDPICC in HubSpot in under an hour

Setting up MEDDPICC in HubSpot in under an hour

Most teams that "tried MEDDPICC and it did not stick" never actually wired the eight letters into the deal record — they just put them on a slide. The rollout fails because the framework lives in enablement decks, not in the CRM, and reps treat it as something to remember rather than something to fill in. Doing it correctly in HubSpot takes under an hour and turns the framework from a slide into an operational discipline.

The 8 custom Deal properties

Open Settings → Objects → Deals → Manage Properties. Create eight custom properties under a new property group called "MEDDPICC Qualification." Each is a single-line text field, not a dropdown. The reason for text fields rather than picklists: the qualification answer is specific to each deal, and forcing reps to pick from a list trains them to game the picklist instead of writing a real answer.

• Metrics — what numerical outcome does the buyer want?
• Economic Buyer — first and last name, plus title.
• Decision Criteria — what they will evaluate vendors on.
• Decision Process — the literal steps from here to signature.
• Identified Pain — current state that is unacceptable enough to spend money.
• Champion — first and last name, plus a one-sentence why-they-care.
• Paper Process — procurement, legal, contract review path.
• Competition — named competitors, including do-nothing.

Naming convention matters. Use the full word in the property label ("Economic Buyer," not "EB"). Reps will encounter these fields in deal records every day, and full words communicate intent better than abbreviations. Also use the property description field — a short one-line prompt for each property that tells the rep what good looks like. "Decision Process" with the description "Bullet the literal steps. Example: 1. Demo with team. 2. Security review. 3. Procurement RFI. 4. Legal redlines. 5. Counter-sign." costs nothing to add and dramatically improves what reps put in the field.

Property dependency rules

Paper Process and Competition do not always matter. For a $20K transactional deal, they add ceremony without insight. For a $200K enterprise deal with multi-vendor evaluation, they are the two most predictive fields. HubSpot lets you conditionally show properties based on other field values — use it.

Set Paper Process and Competition to show only when Deal Type = New Business and Deal Amount > $50K. The threshold is yours to set; pick the number that maps to where your team needs procurement scrutiny. Below that, the two fields stay hidden and do not pollute the deal record. Above it, they are required (per the stage-gate rule below).

Stage requirements at Stage 3 and Stage 4

This is the part that actually drives adoption. Open Settings → Objects → Deals → Pipelines. For your default pipeline, configure stage progression rules. At Stage 3 (typically Proposal or equivalent), require four MEDDPICC fields to be non-empty: Economic Buyer, Identified Pain, Champion, Decision Process. At Stage 4 (typically Negotiation), require all eight where applicable (Paper Process and Competition only required if visible per the dependency rules above).

HubSpot enforces these as validation rules. The rep cannot advance the deal stage until the fields are populated. They will resist. That is the point. The friction at stage advancement is the entire reason the framework drives qualification depth instead of being a checkbox exercise.

One configuration note: the stage requirement in HubSpot is not natively a hard block — it is a warning. To make it a hard block, use a workflow that automatically reverts the stage change when the fields are empty. Set the workflow trigger: when Deal Stage = Stage 3 AND any of the four required fields is empty, revert stage to previous AND send the rep a notification. The notification text matters; write it as a coach, not a cop. "Deal moved back to Stage 2 — fill in Economic Buyer, Identified Pain, Champion, and Decision Process before advancing. Description prompts are in each field."

The MEDDPICC Health calculated property

Create one more property: a calculated property called "MEDDPICC Health." It is a number between 0 and 8 that counts how many of the eight fields are populated with non-trivial values. HubSpot calculated properties support this kind of formula — count non-empty fields in the property group.

Use the score on dashboards. Filter deals to MEDDPICC Health less than 6 at Stage 3+ and show that filtered count as a tile on the manager's dashboard. The tile becomes the first thing managers look at every morning. Reps who see their deals appearing in that tile clean up their qualification within a day. The score is a public accountability mechanism without needing a single meeting.

The completeness dashboard

One dashboard, five tiles, configured in 15 minutes:

• Average MEDDPICC Health by rep (bar chart, sorted descending).
• Count of Commit-tier deals with Health less than 6 (single number, red if greater than 5).
• Aging deals at Stage 3+ with empty Champion field (table).
• Deals where Decision Process is shorter than 50 characters (table — proxy for "they wrote 'TBD' or similar").
• Trend chart: average Health across the team over the last 12 weeks.

Save it as a shared dashboard. Send the manager a link. The dashboard does the inspection that no human wants to do every Friday afternoon.

A workflow that pings managers on incomplete commits

One more workflow worth setting up. Trigger: Deal Stage = Commit AND MEDDPICC Health less than 6. Action: send the manager a Slack notification ("Deal X is in Commit but Health is 4/8 — please review qualification with rep before Friday"). This catches the deals that slip through the validation rules because the rep populated the four required fields trivially. The workflow runs in HubSpot for free; the Slack integration is the standard one most teams already have.

The notification is calibrated to be a nudge, not an interruption. One ping per deal, per stage transition. Managers can choose to act or not. After two months, the notifications taper because reps stop letting deals reach Commit with thin qualification. The workflow becomes self-eliminating, which is the right outcome.

One trap: HubSpot's built-in BANT field

HubSpot ships with a built-in qualification framework called BANT (Budget, Authority, Need, Timeline). It is a property group on the Contact object. Do not use it as your qualification framework. BANT is from a different era, captures less information than MEDDPICC, and lives on the wrong object (Contact, not Deal). If you have it enabled for legacy reasons, hide the property group and ignore it. Your qualification lives on the Deal object in your MEDDPICC group, full stop.

The reason this is a trap: HubSpot occasionally surfaces BANT as a default suggestion in onboarding, and a new admin will turn it on alongside MEDDPICC because "why not." Two qualification frameworks confuse reps and create a debate about which is authoritative. Pick one. MEDDPICC.

Bonus: the same setup in Salesforce takes about 3 hours

If you are setting up MEDDPICC in Salesforce instead, the work is the same conceptually but takes longer because Salesforce's customization surface is wider and slower. Add the eight fields to the Opportunity object (15 min), configure page layouts per profile (45 min), build validation rules for stage progression (30 min), build the MEDDPICC Health formula field (15 min), build the dashboard (30 min), build the Flow that handles incomplete-Commit alerts (45 min). Three hours, end to end.

The Salesforce setup is the same logic; just more clicks. The discipline of using the framework after the setup is identical.

The 30-day adoption check

Thirty days after rollout, run the audit. Average MEDDPICC Health should be 5+ across the team. Commit-tier deals should be 7+. If you are not there, the validation rules are too soft or the manager cadence is too quiet. Tighten the rules. Loop in the CRO to read fields out loud during the next forecast call. Six weeks later, audit again. By the end of quarter two, the framework should be invisible — meaning it works without anyone needing to talk about it. That is the goal.