discovery-coach
Use when an org role acts as discovery coach and must improve reps' sales discovery calls with SPIN, MEDDIC or BANT qualification and call scorecards. Sales discovery, not product discovery (see product-discovery).
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-14
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- discovery-coach
- tags
- [ "sales", "customer-research", "communication" ]
- tools
- []
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- description
- Use when an org role acts as discovery coach and must improve reps' sales discovery calls with SPIN, MEDDIC or BANT qualification and call scorecards. Sales discovery, not product discovery (see product-discovery).
03 SKILL.md 正文
Discovery Coach — Best Practices
Focus
Sharpens how reps run discovery calls — the questions they ask, the depth they go to, and the qualification rigor — since discovery quality predicts win rate more than almost any other sales skill.
Best practices
- Push reps toward the proven question arc: Situation → Problem → Implication → Vision/Need-payoff (SPIN), rather than jumping straight to pitching a solution.
- Target roughly an 80/20 open-to-closed question ratio, and coach toward 11-14 substantive questions per call rather than a rushed five-minute checklist.
- Emphasize implication questions specifically — top performers ask far more of these than average reps, and they correlate strongly with win rate and deal size.
- Require real pre-call preparation; asking questions whose answers are obvious from public info signals no homework and erodes buyer trust immediately.
- Coach toward listening, not talking — buyers consistently rank "listen to my needs" as their top ask, and talk-ratio is one of the most fixable, highest-leverage metrics.
- Anchor every discovery call to a qualification framework (MEDDIC or BANT) so reps leave with Metrics, Economic Buyer, Decision Criteria/Process — not just vague interest.
- Review calls with structured scorecards mapped to the chosen methodology, not gut-feel impressions.
- Reinforce that the goal of discovery is diagnosis, not qualification theater — the rep should be able to state the customer's problem back better than the customer can.
Common pitfalls
- Reps pitching too early, before the customer's actual pain, priority, and buying process are understood.
- Surface-level situation questions without ever pushing into implication/impact — leaves the business case fuzzy for the customer.
- Skipping economic-buyer and decision-process questions, leading to deals that stall in "no decision" because the real buyer was never engaged.
- Treating discovery as a one-time call instead of an ongoing thread refined throughout the deal cycle.
Tools & techniques
- SPIN and MEDDIC/BANT as the two core qualification lenses — pick one as primary and coach consistently against it.
- Discovery call scorecards scoring question mix (situation/problem/implication/vision), talk ratio, and qualification field completeness.
- Call recording + transcript review for implication-question frequency, a strong leading indicator of win rate.
- Standard discovery question bank, refreshed from what's actually working in recent won deals.
04 同仓库更多 Skills
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.