sales-craft
Craft Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
- What do you need help with?
- A) Evaluating Craft for my team (pricing, fit, ROI)
- B) Setting up Craft — CRM connection, sales process upload, onboarding
- C) Real-time field sales coaching — how it works during appointments
- D) AI Call Center — 24/7 booking, call scoring, CSR coaching
- E) Revenue Recovery AI Agents — automated follow-up for missed opportunities
- F) Comparing Craft to Rilla, Siro, or SalesAsk
- G) CRM integration (ServiceTitan, Salesforce, HubSpot, Jobber, etc.)
- H) Troubleshooting — coaching alerts not firing, CRM sync issues, implementation delays
More from sales-skills/sales
sales-enrich
Enriches contacts and companies with verified emails, phones, and firmographic data — single-record, batch, and waterfall enrichment with credit optimization. Use when contact data is missing emails or phones, lead records are incomplete or outdated, enrichment credits are burning too fast, you need to enrich a batch of leads before a campaign, or a single enrichment provider isn't catching enough data. Do NOT use for building new prospect lists from scratch (use /sales-prospect-list), interpreting buying signals (use /sales-intent), CRM data hygiene and deduplication (use /sales-data-hygiene), ZoomInfo-specific enrichment config (use /sales-zoominfo), Clearbit/Breeze Intelligence platform help (use /sales-clearbit), RB2B platform help (use /sales-rb2b), 6sense platform help (use /sales-6sense), general Apollo platform help (use /sales-apollo), Clay platform help (use /sales-clay), or LeadMagic platform help (use /sales-leadmagic).
70sales-lead-score
Designs, weight, and tune a lead scoring model for your sales funnel. Use when scores don't predict conversion, MQL/SQL threshold feels arbitrary, reps ignoring lead scores because they're inaccurate, too many unqualified leads passing to sales, or not sure which signals actually matter. Do NOT use for reading existing buying signals (use /sales-intent), building prospect lists (use /sales-prospect-list), or marketing-to-sales handoff process design (use /revops).
70sales-cadence
Designs multi-channel outbound cadences with timing, A/B testing, and content. Use when outbound sequences getting low reply rates, unsure how many touchpoints or what spacing to use, cadence emails sound generic, prospects ignoring calls, A/B tests not moving the needle, sequence performance plateauing, or not sure which channels to include in outreach. Do NOT use for general outreach message writing (use /sales-outreach), marketing cold email (use /cold-email), automated email flows (use /email-sequence), or general Salesloft platform help (use /sales-salesloft).
70sales-deal-inspect
Inspects deal health, map stakeholders, identify risks, and recommend next actions. Use when a deal feels stuck or at risk, you're not sure who the real decision-maker is, champion seems weak or disengaged, MEDDPICC gaps are unclear, a deal review is coming up and you need to prep, or you can't tell if a deal will actually close. Do NOT use for portfolio-level pipeline management (use /sales-pipeline), revenue forecasting (use /sales-forecast), or reviewing a specific sales call (use /sales-call-review).
68sales-proposal-page
Writes and structure a Qwilr proposal page that closes deals. Use when your proposals look generic and aren't closing, you don't know what sections to include, the pricing table confuses buyers, your proposal doesn't stand out from competitors, or you're staring at a blank Qwilr page and need a structure that sells.
68sales-apollo
Apollo.io platform help — config, integrations, CRM sync, API, analytics, dialer, Chrome extension, credit management, admin. Use when Apollo settings aren't configured right, CRM sync is breaking or duplicating records, running out of credits too fast, API calls returning errors, or something in Apollo isn't working as expected. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), interpreting buying signals (use /sales-intent), or designing outbound sequences (use /sales-cadence).
68