Sector05 Skill Depot

Shards0/0

05 // Skill Depot

PlaybookPlaybookGong

Sales Methodology Gong Skill

Value Proposition: Translates your sales methodology into Gong — Smart Trackers, stage-specific scorecards, AI Call Reviewer instructions, and Initiative Boards. Methodology-selectable on the card.
#Enablement#Gong#Call Intelligence#SPICED#MEDDIC#Smart Trackers#Scorecards

A Gong-specific implementation playbook for sales methodology. No download — Gong doesn't accept skill file uploads. Methodology setup happens through Admin Center → Agent Studio (Smart Trackers, AI Call Reviewer scorecards, Initiative Boards). This playbook walks the build, methodology by methodology, and tells you exactly which Smart Trackers to create, how to split scorecards by stage, and how to wire it all to a coaching initiative.


For Best Results

  1. Enable AI Call Reviewer at the company level first. A Tech Admin has to flip it on in Admin Center → General Settings before any auto-scoring works.
  2. Build Smart Trackers before scorecards. Scorecards can use Smart Trackers as their AI source.
  3. One scorecard per stage, not one scorecard per methodology.
  4. Use Range (0-3) and Yes/No question types only. They're the only types Gong weights.
  5. Run scorecards in manual-suggest mode for 30 days before flipping to full auto-scoring.

Read This First Why You Can't Just Build One MEDDIC Scorecard

A Gong scorecard scores one call. SPICED and MEDDIC are deal-level frameworks that build across multiple calls. A first discovery call legitimately can't score Critical Event or Decision — those conversations haven't happened yet. Scoring them as "0" punishes the rep for following the process.

The right architecture:

  1. Smart Trackers detect methodology concepts across every call in the deal (Champion identified, Economic Buyer engaged, Critical Event mentioned, Competitor named, Pricing objection raised).
  2. Stage-specific scorecards evaluate behaviors expected at that stage (Discovery scorecard checks for situation depth + pain quantification; Demo scorecard checks for impact framing + decision process probing).
  3. Initiative Board rolls up tracker signals across the team so managers see methodology adoption over time.
  4. CRM owns the deal-level total score (via the RevOps Skill). Gong is the coaching and signal layer, not the system of record for qualification.

Skip this architecture and you end up with a 30-question MEDDPICC monster scorecard that managers fill out manually, reps resent, and the AI scores poorly.


Build Steps by Methodology

Use the dropdown to select your methodology. The Smart Trackers, scorecards, and Initiative Board pattern for that framework will appear — Gong-specific menu paths and exact question phrasings, ready to copy into Admin Center → Agent Studio.


Make This Skill Yours

The dropdown above covers SPICED, MEDDIC, MEDDPICC, BANT, and PACCT. For a methodology not listed (CHAMP, FAINT, NEAT, GPCT, Sandler, custom), use the prompt below to generate the same build pattern for your framework.

Generate a Gong implementation plan for [YOUR METHODOLOGY].

1. List the canonical elements of [YOUR METHODOLOGY]. Search the web for the
   official definition and the version most commonly used in practice.
2. For each element, design one Smart Tracker in Gong:
   - Tracker name: "[YOUR METHODOLOGY] – [Element] [Behavior]"
   - Description: what the tracker should detect (a concept, not a keyword)
   - 3-5 suggested phrasings the tracker should fire on
3. Decide which elements belong on which stage scorecards:
   - Discovery: elements surfaced in first 1-2 calls
   - Demo / Proposal: elements that emerge as the deal advances
   - Negotiation: elements that only matter at close (procurement, competition)
4. Write each scorecard question as Range 0-3 or Yes/No (Gong only weights those types).
5. For each question, specify the AI Source: "Gong AI" or "Smart Tracker [name]."
6. Paste the 0-3 rubric language from the Enablement skill into each question's
   "Add details or examples" field.
7. Define one Initiative Board including all trackers, with a manager review cadence.
8. Output the full plan in a checklist format I can take into Gong Admin Center
   and execute in order.

Cross-methodology teams: if SDRs run PACCT and AEs run MEDDIC, build the SDR scorecard and AE scorecards separately and use different Call Type filters. Create a hand-off scorecard that scores how completely the SDR's PACCT trackers fired before the AE's first call.


Chaining Workflows Pairs With the Enablement and RevOps Skills

This is the third leg of the methodology stack. The three skills compose:

  • Sales Methodology Enablement Skill owns the conversation — what reps say, the 0-3 rubric, persona-tailored language, coaching prompts.
  • Sales Methodology RevOps Skill owns the CRM — fields, validation rules, stage gates, forecast logic, deal-level total score.
  • This skill owns the call intelligence — what Gong detects, what scorecards measure, what Initiative Boards surface to managers.

The workflow:

  1. Enablement defines the methodology and rubric.
  2. RevOps wires it into Salesforce or HubSpot.
  3. This skill wires it into Gong.
  4. Reps run the methodology in conversation (Enablement), CRM enforces stage gates (RevOps), Gong measures behavior in real calls (this skill).
  5. Adoption gaps surfaced in Gong feed back to Enablement for targeted coaching.

Keep all three in sync. A methodology change touches all three skills. If you swap SPICED for MEDDIC, you update the Enablement coaching prompts, the RevOps field schema, AND the Gong trackers + scorecards. Skipping any one of them breaks the loop.

Also pairs with: Salesforce Data Hygiene or HubSpot Data Hygiene — Gong's CRM sync is only as good as the underlying field hygiene.