zime-ai/zime-gtm-skills

41 skills

• adoption-leaderboard

  Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibration, prepping 1:1 coaching from real call evidence instead of impressions, or checking whether a specific behavior is actually landing across a book of calls.

  Self-containedActs undeclared1,210 words
• bant

  Audits a B2B sales call transcript against the BANT qualification framework (Budget, Authority, Need, Timeline), or sweeps a CRM export for deals missing BANT fields. Use when qualifying an early-stage lead, deciding whether to advance a deal past a first call, or checking a pipeline export for unqualified opportunities.

  Self-containedInstructions only710 words
• challenger

  Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when a rep leans on discovery-question skill but rarely brings a point of view, when prepping a rep for a competitive or status-quo-defending deal, or when a manager wants to know if a call taught the buyer something new rather than just restating their stated problem.

  Self-containedInstructions only900 words
• champion-tracker

  Tracks champion strength across a deal's call(s) — builds an action ledger, one row per named contact per cited quote, tagging each as either an act of internal selling (looping in a stakeholder, pushing back for the rep in a room the rep wasn't in) or mere positive sentiment (encouraging words, no action), then reads the trend across calls. Use when a rep or manager wants to know if a deal actually has a champion or just an enthusiastic contact, especially before a forecast call or a stalled deal review.

  Self-containedInstructions only870 words
• churn-prevention

  Audits a renewal-risk or check-in call transcript against a churn/retention-signal rubric, or sweeps a CRM export for at-risk accounts missing renewal-risk data. Use when reviewing a customer check-in or QBR before a renewal, coaching a CSM on retention conversations, or scanning an account list for churn risk.

  Self-containedInstructions only590 words
• competitor-battlecard

  Reads a single sales call transcript and writes a battlecard for whichever competitor (or status quo) the buyer actually named on that call — how they framed it, what they said it does better or differently, what the rep countered with, and what went unanswered, citing every line to the transcript. Use right after a call surfaces a competitive frame, to arm the rep for the next call or brief a manager on it — not to score how well the rep handled the objection (see challenger) or to write a post-close loss review (see win-loss-brief).

  Self-containedInstructions only659 words
• customer-success

  Audits a periodic QBR or account health-review call transcript against a rubric covering value delivered, usage breadth, open issues, and forward alignment, or sweeps a CRM export for accounts overdue for a health review. Use when reviewing a QBR or ongoing health check-in, distinct from a renewal-risk-triggered or expansion-triggered conversation.

  Self-containedInstructions only467 words
• deal-highlights

  Writes a short highlights digest of one sales call — the moments that actually matter (a commitment, an objection, a buying signal, a competitive mention, a risk, a number that matters), each citing the quote it came from. Use when a rep needs something to skim or forward to a manager right after a call, not a full rubric grade of it.

  Self-containedInstructions only592 words
• deal-risk-digest

  Reads a pipeline export (a whole book of business, not one call) and ranks deals by risk — a past-due close date paired with low probability, stage age, a blank or vague next step, and a single-threaded contact, with deal value breaking ties — citing the column values behind each call. Use when a sales manager or RevOps person wants a ranked risk view across a whole pipeline before a forecast call or pipeline review, not a single-call audit.

  Self-containedInstructions only627 words
• deep-discovery

  Audits an early-stage B2B sales discovery call transcript against a discovery-quality rubric, or sweeps a CRM deal export for missing discovery fields. Use when reviewing a discovery/early-stage sales call, coaching a rep on discovery quality, or checking a pipeline export for deals with thin discovery.

  Self-containedInstructions only768 words
• end-client-registration

  Audits a partner/reseller's end-client deal registration for completeness — partner identity, end-client entity kept distinct from the partner, engagement scope, conflict check against the direct pipeline, confirmed permission to engage the end-client contact, commercial terms, and an expiry window. Use when reviewing a channel/partner deal registration export or a partner registration-review call, before accepting the registration into the partner pipeline. Distinct from `new-business-registration` (sibling skill), which audits a direct new-logo opportunity with no partner involved.

  Self-containedInstructions only684 words
• evaluation-pipeline-check

  Sweeps a deal/pipeline export for technical evaluations running without defined success criteria, a technical champion, or an evaluation end date, and flags evaluations running long, stalled, or missing a security/procurement review relative to the export's own norms. Use when reviewing deals sitting in a technical evaluation stage, or auditing a pipeline export before a forecast call.

  Self-containedInstructions only645 words
• executive-briefing

  Writes the short brief a rep sends upward out of one deal — to their own exec or the buyer's exec sponsor — covering deal snapshot, status, what's at risk, and the ask, each claim cited to a quote or a CSV column/cell. Use when someone who will never read the transcript needs to act on one deal, not a call-by-call digest or a whole-pipeline sweep.

  Self-containedInstructions only858 words
• faint

  Audits a B2B sales call transcript against the FAINT qualification framework (Funds, Authority, Interest, Need, Timing), or sweeps a CRM export for deals missing FAINT fields. Use when a prospect hasn't articulated a clear need yet but shows financial capacity and curiosity, or when deciding whether a demand-driven lead is worth advancing before a formal need is on record.

  Self-containedInstructions only858 words
• first-call-rampup

  Audits a new rep's early sales call transcript against a foundational-skills rubric covering opening, open-ended questioning, pain uncovering, and pitch delivery. Use when coaching a newly ramped rep, reviewing their first calls, or building a rep-development plan from real call evidence.

  Self-containedInstructions only590 words
• follow-up-email-drafter

  Drafts the customer-facing follow-up email a rep sends after a sales call, grounding every recap, next step, and date in what was actually said, plus a separate grounding-notes section flagging which lines are heard-verbatim versus a proposal the rep should confirm before sending. Use right after a call when a rep wants a first-draft follow-up instead of writing one from scratch, or when a manager wants to sanity-check a drafted email against the transcript before it goes out.

  Self-containedInstructions only779 words
• improve-demo

  Audits a product demo call transcript against a rubric covering tailoring, stakeholder presence, engagement, and outcome clarity, or sweeps a CRM export for demos with no documented next step. Use when reviewing a demo call, coaching a rep on demo delivery, or checking pipeline for demos that didn't produce a clear next step.

  Self-containedInstructions only626 words
• meddicc

  Audits a B2B sales call transcript against the MEDDICC qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition), or sweeps a CRM export for deals missing MEDDICC fields. Use when qualifying an opportunity, prepping for a deal-review or forecast call, or checking whether a deal in the pipeline has real MEDDICC coverage.

  Self-containedInstructions only831 words
• meddpicc

  Audits a B2B sales call transcript against the MEDDPICC qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition), or sweeps a CRM export for deals missing MEDDPICC fields. Use when a deal is heading toward legal/procurement/security review and needs a read on the close-mechanics letter that MEDDICC doesn't cover, prepping for a late-stage forecast call, or checking whether a pipeline deal has a mapped signature path.

  Self-containedInstructions only955 words
• meeting-to-qualify

  Audits a qualification call transcript to assess whether a deal is real — authority, budget plausibility, urgency, and fit — or sweeps a CRM export for deals never properly qualified. Use when deciding whether to invest further in a deal, reviewing a qualification call, or checking pipeline for unqualified deals inflating forecast.

  Self-containedInstructions only662 words
• mutual-action-plan

  Writes a mutual action plan out of what was actually said on a call — milestones from today to signature, each with an owner on both sides and a date — or fills date/stage gaps from a CRM export row. Use when a rep needs a real MAP to send a prospect after a call, or a manager wants to check whether a deal's stated next steps actually hang together as a plan.

  Self-containedInstructions only766 words
• negotiation-closing

  Audits a late-stage negotiation call transcript against a rubric covering pricing sentiment, procurement momentum, contracting awareness, and closure timeline, or sweeps a CRM export for late-stage deals with no documented closing path. Use when reviewing a negotiation call, or checking pipeline for deals stuck in late stage with no clear path to close.

  Self-containedInstructions only454 words
• negotiation-pipeline-check

  Sweeps a deal/pipeline export for deals in negotiation with no paper process started, no named approver on a discount, no credible close date, or no named signature path. Use when reviewing forecast-stage negotiation deals for whether they have a real mechanical path to signature, not just a stated intent to close.

  Self-containedInstructions only751 words
• new-business-registration

  Audits a new-logo deal-registration record, or the call/checkpoint where a rep registers a brand-new opportunity into pipeline, against general deal-registration practice covering entity identification, duplicate/conflict checking, source attribution, and ICP fit. Use when reviewing a fresh deal registration before it's approved, or sweeping a registration export for records missing required fields. Not for partner-sourced end-client registrations — see end-client-registration.

  Self-containedInstructions only599 words
• next-step-commitment

  Checks whether a sales call ended with a real, dated, mutually-owned next step versus a vague "we'll circle back." Use when reviewing whether a call actually moved a deal forward, coaching a rep on closing calls out properly, or sweeping a CRM export for deals stuck without a next step.

  Self-containedInstructions only677 words
• onboarding-journey

  Audits a new-customer onboarding call transcript against a rubric covering onboarding experience, sentiment, and early expansion signal, or sweeps a CRM export for onboarding accounts with no documented health signal. Use when reviewing an onboarding check-in call, or checking a new-customer list for onboardings going quiet.

  Self-containedInstructions only452 words
• pain-finder

  Ranks the pain points surfaced in a sales call transcript by confidence and evidence, tagged by category. Use when a rep wants to know what a prospect's real pain points are and which to lead with in a follow-up, or when comparing pain points across multiple calls with the same account.

  Self-containedInstructions only646 words
• persona-based-discovery

  Audits whether a discovery call's questions and framing were actually tailored to the specific buyer persona in the room (technical evaluator, economic buyer, end user, etc.), or sweeps a CRM export for deals with no persona/role data attached to contacts. Use when checking that a rep adapted to who they were talking to rather than running a one-size-fits-all script, or when reviewing a pipeline export for deals missing contact-role fields.

  Self-containedInstructions only871 words
• pilot-to-conversion

  Audits a pilot/POC check-in call transcript against a rubric covering plan alignment, technical readiness, user engagement, and results against criteria, or sweeps a CRM export for pilots at risk of stalling before conversion. Use when reviewing a pilot check-in call, or checking pipeline for POCs that have run long without a documented result.

  Self-containedInstructions only484 words
• poc-pilot-pipeline-check

  Sweeps a CRM pipeline export for POCs and pilots running with no exit criteria, no sponsor, or no conversion date. Use when RevOps or a manager wants a pipeline-wide read on which POCs/pilots can actually convert versus which are drifting with nothing written down.

  Self-containedInstructions only643 words
• poc-success

  Audits a POC/pilot exit review — did the pilot actually meet its agreed success criteria, and is that decision documented with evidence and sign-off — or sweeps a CRM export for deals past their POC end date with no recorded outcome. Use when a pilot has just wrapped and you need a structured read on whether it genuinely passed, or when checking pipeline for POCs that ran out the clock with no outcome written down.

  Self-containedInstructions only727 words
• prospect-pipeline-check

  Sweeps a CRM pipeline export for prospect-stage deals with no real two-way engagement from the prospect side — the earliest "is this even a deal" gate, before budget, buyer, or pain are even in scope. Use when auditing a prospect-stage pipeline for zombie deals a rep is carrying forward on outbound activity alone, or before a pipeline review to separate real opportunities from unanswered outreach.

  Self-containedInstructions only694 words
• qualify-pipeline-check

  Sweeps a CRM/pipeline export for deals that advanced past the Qualify stage without the facts that stage is supposed to establish — economic buyer, pain, budget signal, a close date consistent with the procurement cycle, a next step, and a qualification-framework record. Use when RevOps or a manager wants to audit the Qualify pipeline for deals advanced on hope rather than evidence. Does not read call transcripts — that's `meeting-to-qualify` (audits the qualification call itself) or `sql-to-qualify` (audits the SQL handoff call); this one only asks whether the CRM record itself can prove qualification happened.

  Self-containedInstructions only722 words
• qualify-to-poc

  Audits the call/checkpoint that moves a qualified deal into POC/pilot kickoff — the go/no-go gate before pilot work starts — against five dimensions covering success criteria, technical scope, stakeholder commitment, timeline/exit criteria, and resourcing. Or sweeps a CRM export for deals entering pilot stage without those fields set. Use when deciding whether a deal is actually ready to start a POC, reviewing a POC-kickoff call, or checking pipeline for pilots that started without a real plan.

  Self-containedInstructions only781 words
• sandler

  Audits a B2B sales call transcript against the Sandler Selling System submarine (Bonding & Rapport, Up-Front Contract, Pain, Budget, Decision, Fulfillment, Post-Sell), or sweeps a CRM export for deals missing Sandler-relevant fields. Use when checking whether a rep pitched before earning the right to, whether a close was actually agreed to or just assumed, or auditing a pipeline for deals that skipped a submarine compartment.

  Self-containedInstructions only1,047 words
• sell-the-dream

  Audits a B2B sales call transcript for future-state vision selling — does the rep name the world change and stakes before pitching product, or lead with features and bolt a "vision" on afterward. Scored against Andy Raskin's publicly published "5 Elements of a Great Sales Narrative," corroborated by Corporate Visions, Force Management, and Challenger's convergent "vision before product" pattern. "Sell the dream" is the colloquial name for this behavior, not a citation to a named methodology. Use when a rep pitches features early and a deal stalls on "not urgent," or when a manager wants to know if a call's vision narrative landed before the product did, not just whether a vision was mentioned at all.

  Reaches the webInstructions only838 words
• sql-to-qualify

  Audits the first call after a sales-qualified lead (SQL) hand-off to check whether there's a real opportunity worth a rep's time — right contact, pain in the prospect's own words, rough budget/urgency fit, competitive awareness, and a concrete next meeting — or sweeps a CRM export for SQLs sitting untouched past this gate. Use right after an SQL is assigned and worked for the first time, before investing in a full qualification call.

  Self-containedInstructions only722 words
• technical-discovery

  Audits a technical/solution-fit call transcript against a rubric covering current stack, future-state vision, POC scope, and technical stakeholders, or sweeps a CRM export for deals missing technical-fit data. Use when reviewing a technical discovery or solution-engineering call, or checking pipeline for deals heading into a POC without technical groundwork.

  Self-containedInstructions only652 words
• upsell-expansion

  Audits an expansion/upsell call transcript against a rubric covering opportunity clarity, champion strength, renewal health, and strategic alignment, or sweeps a CRM export for expansion opportunities missing a health check. Use when reviewing an upsell or expansion conversation, or checking an account list for expansion pushes that skipped a renewal-health check first.

  Self-containedInstructions only531 words
• win-loss-brief

  Writes a structured brief on why one specific deal was won or lost — outcome, 3-5 cited drivers (competitive displacement, champion strength or loss, pricing/procurement friction, timing, technical fit), and forward-looking notes for a similar deal. Use for a manager/leader ritual like a QBR or win-loss review on a single closed deal, not a whole-book pipeline sweep.

  Self-containedInstructions only836 words
• won-pipeline-check

  Sweeps a closed-won deal export for missing handoff and record data the post-sale team needs — CS owner, kickoff date, signed value/term, contract reference, and date/stage consistency. Use when a deal desk or RevOps person wants to check closed-won deals before they hand off to onboarding/CS, or audit a pipeline export for won deals with incomplete records.

  Self-containedInstructions only641 words