discovery-and-qualification
Skill4 starsChanged 29 days agoMITView on GitHub
Use when qualifying a lead or preparing for a discovery call - deciding whether a prospect is a real opportunity and what to ask. Covers qualification frameworks (BANT, MEDDIC / MEDDPICC), designing open discovery questions, the listening ratio, cost-of-inaction, multi-threading a buying committee, and disqualifying fast to protect your time.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- account-researchSkill
- cold-email-writingSkill
- content-marketing-engineSkill
- email-deliverabilitySkill
- generative-engine-optimizationSkill
- gtm-automation-with-chronosSkill
- gtm-strategySkill
- ideal-customer-profileSkill
- lead-sourcing-and-enrichmentSkill
- linkedin-outreachSkill
- multichannel-sequencesSkill
- outbound-metrics-and-benchmarksSkill
- outreach-personalizationSkill
- positioning-and-messagingSkill
- reply-handling-and-objectionsSkill
- seo-fundamentalsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Not every reply is an opportunity.
- Distinctive: line 69
No real pain, or pain too small to fund a change.
- Distinctive: line 70
No path to the economic buyer and no willing champion.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Discovery & qualification
Overview
Not every reply is an opportunity. Qualification is how you decide where to spend selling time, and discovery is how you learn enough to help (or walk away). The best discovery feels like a useful conversation, not an interrogation - you're diagnosing a problem, not reciting a checklist.
Qualify early, disqualify fast. A clean "no" now is worth more than a vague "maybe" that eats three months.
Frameworks (use as a lens, not a script)
BANT - quick first-pass qualifier:
- Budget - can they fund a solution (or create budget if the pain is big)?
- Authority - are they the decision-maker, or who is?
- Need - is there a real, felt problem you solve?
- Timeline - is there a reason to act in a defined window?
MEDDIC / MEDDPICC - for larger, multi-stakeholder deals:
- Metrics - the quantified impact they want.
- Economic buyer - who controls the money.
- Decision criteria - how they'll choose.
- Decision process - the actual steps/approvals to purchase.
- Identify pain - the real, costed problem.
- Champion - an internal advocate with influence.
- (+ MEDDPICC adds Paper process - legal/procurement - and Competition.)
Pick BANT for velocity/SMB, MEDDIC for complex/enterprise.
Designing discovery questions
- Open, not leading. "Walk me through how you handle X today?" beats "You struggle with X, right?"
- Pain-first, then impact. Find the problem, then quantify its cost: "What does that cost you per month / in hours / in churn?" The cost of inaction is what justifies change.
- Future-state. "If this were solved, what changes for you?" - surfaces the metric that matters and the real motivation.
- Process & people. "Who else is affected / involved in a decision like this?"
- uncovers the buying committee early.
The listening ratio
In discovery, the prospect should talk far more than you - aim to listen most of the call. Every minute you spend pitching is a minute you're not learning what would make them buy. Ask, then shut up.
Multi-thread
A single contact is a single point of failure. Map the committee (economic buyer, users, blockers, champion) and build more than one relationship. Deals with one thread stall when that person goes quiet or leaves.
When to disqualify
- No real pain, or pain too small to fund a change.
- No path to the economic buyer and no willing champion.
- Timeline is "someday" with no trigger. → Exit gracefully to long-term nurture; don't force a dead deal forward.
Do / Don't
- Do qualify early and disqualify fast to protect selling time.
- Do quantify the cost of the problem (and of inaction).
- Don't pitch during discovery - diagnose.
- Don't single-thread a committee deal.
Common mistakes
- Treating the framework as a checklist to recite instead of a lens.
- Talking more than the prospect.
- Confirming a "need" you led them into (happy ears).
- Chasing an unqualified deal because the logo is exciting.
Go live with Chronos (optional)
Chronos runs the outreach that creates these conversations; the discovery call itself is yours. Where it helps:
geo_list_message_history/geo_get_message_thread- read the full reply context and intent signals before the call, so you prep with real information.geo_send_manual_message- send the meeting confirmation / pre-call note.
Connect in ~30s → CONNECT-CHRONOS.md. Free, no card.
See also: reply-handling-and-objections, ideal-customer-profile, positioning-and-messaging.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

