Solo Unicorn Club logo

Skill Packs

Discovery Coach

Run discovery calls that uncover real pain and budget

// First 7 days

What can be running fast.

01

Get a ready-to-run system that replaces blank-page setup.

02

Ship a usable package with 6 included files and working structure.

03

Move from purchase to first setup in about 5 min.

// Included files

What is inside the package.

discovery-coach.md
templates/call-script.md
templates/post-call-summary.md
playbooks/objection-handling.md
examples/meddic-filled.md
README.md

Description

What is Discovery Coach?

A skill that guides your agent through structured discovery conversations. Covers MEDDIC qualification, open-ended questioning techniques, pain quantification, decision process mapping, and champion identification. Includes call scripts, objection handling playbooks, and post-call summary templates.

solo-unicornclaude-code

Upgrade path

  • 01Start with this package and validate the workflow.
  • 02Add specialized skills or bundles once the core system is stable.
  • 03Use the community to sharpen positioning, demos, and feedback loops.
Previewdiscovery-coach.md
# Discovery Coach Skill

## MEDDIC Framework
Qualify every opportunity against these criteria:

### Metrics
- "What would solving this problem be worth in dollars per quarter?"
- Quantify the cost of inaction

### Economic Buyer
- "Who signs the check? Have we met them?"
- Map the org chart: champion, influencer, blocker

### Decision Criteria
- "What are the must-haves vs nice-to-haves?"
- Rank criteria by weight

### Decision Process
- "Walk me through how you bought your last tool"
- Timeline, approvals, legal review, procurement

### Identify Pain
- "What happens if you do nothing for 6 months?"
- Pain must be personal, not just organizational

### Champion
- "Who internally is pushing for this solution?"
- Test: would they sell for you when you leave the room?

// Community acceleration

Use the room after the purchase.

Bring your workflow into the Solo Unicorn community for sharper feedback, operator critique, and more visibility once the system is live.

Discuss implementation