Client Discovery
Skill by staybased
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/staybased/client-discoveryClient Discovery — Qualify, Diagnose, Close
Run discovery conversations that qualify prospects, diagnose real problems, and position your solution as the obvious next step.
Sources: Consulting Success (2026), Melisa Liberman (36 questions framework), Freelance Cake, HubSpot, Highspot.
All outputs go to workspace/artifacts/.
Use when
- Preparing for a discovery call with a prospect
- Qualifying whether a lead is worth pursuing
- Drafting discovery questions for a specific industry/niche
- Reviewing notes from a call to identify next steps
- Writing a proposal based on discovery findings
- Evaluating client fit before committing to a project
Don't use when
- Cold outreach (use cold-outreach skill — discovery comes AFTER they respond)
- Existing client check-ins (different dynamic — you already have context)
- Pricing decisions (use pricing-psychology skill)
- Building the actual deliverable (discovery is pre-build)
Negative examples
- "Write me a proposal" → Borderline. Discovery must happen BEFORE the proposal. If you haven't done discovery, do that first.
- "Help me negotiate a rate" → No. That's pricing/negotiation, not discovery.
- "How do I find leads?" → No. That's lead generation, not qualification.
Edge cases
- Upwork job evaluation → YES. Reading a job post IS discovery. Assess fit before bidding.
- Text/DM-based discovery → YES. Same principles apply, just compressed format.
- Qualifying yourself OUT of a bad fit → YES. The best outcome of discovery is sometimes "no."
The Core Truth
Peter Drucker: "My greatest strength as a consultant is to be ignorant and ask a few questions."
Discovery is not a pitch meeting. You're not there to impress — you're there to diagnose. The moment you start talking about your solution before understanding their problem, you've lost.
The 80/20 Rule (Melisa Liberman)
- Listen 80% of the time. Talk 20%. (Aspirational target — the point is to listen far more than you talk, even if exact ratios vary.)
- When you do talk, ask questions — don't monologue.
- Be comfortable with silence. Ask, then wait. Even if it's uncomfortable.
- The prospect should feel heard, not sold to.
Why This Matters for Revenue
Freelance Cake's Austin Church: "Insightful questions testify to your competence more than your clever monologues." Asking the right questions often increases project scope — a prospect willing to pay $2,500 for a plan may happily pay $2,500/month for a retainer when you uncover the real problem.
The Discovery Framework: 5 Phases
Phase 1: Context (Warm-Up)
Goal: Understand who they are and what's happening now.
Questions:
- "Tell me about your business — what do you do and who do you serve?"
- "How did you hear about us?" (reveals channel effectiveness)
- "What prompted you to reach out now?" (reveals urgency trigger)
- "What does a typical day/week look like for you?" (reveals workflow)
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-staybased-client-discovery": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Proposal Writing
Skill by staybased
ops-hygiene
Standard operating procedures for agent maintenance, security hygiene, and system health. Use when performing periodic checks, security audits, memory maintenance, secret rotation, dependency updates, or any recurring "housekeeping" tasks. Also use when setting up automated maintenance schedules or when asked about agent security posture.
Lead Magnets
Skill by staybased
Pricing Psychology
Skill by staybased
trade-validation
10-dimension weighted scoring framework for prediction market trade evaluation. Enforces disciplined position sizing, circuit breakers, and mandatory counter-arguments. Use when: evaluating prediction market trades, scoring opportunities, deciding position sizes, comparing Polymarket/Kalshi opportunities, running pre-trade checklists. Don't use when: general crypto analysis, DeFi yield farming, non-prediction-market investments, stock/equity analysis, sports betting (different framework needed). Negative examples: - "Should I buy ETH?" → No. This is for prediction markets with binary/discrete outcomes. - "What's the best DeFi yield?" → No. Wrong domain entirely. - "Score this sports bet" → No. Sports betting has different dimensions (injuries, matchups). Edge cases: - Crypto prediction markets (e.g., "Will BTC hit $X?") → YES, use this if on Polymarket/Kalshi. - Multi-outcome markets → Score each outcome separately. - Markets with <$25 liquidity → Auto-fail on Liquidity dimension.