Best for
- Complex technical discovery calls
- Industrial and manufacturing sales teams
- Enterprise SaaS with security and integration requirements
Create role-specific technical and commercial question branches that state why each question matters, what evidence counts, and how the seller should follow up or stop.
A reusable discovery plan with stakeholder branches, evidence requirements, qualification mapping, follow-up logic, and post-call capture fields.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
4 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Discovery improves when each question has a purpose, evidence standard, follow-up branch, and capture field rather than existing as a generic checklist. The workflow packages reusable role-specific logic while preserving room for the seller to follow the buyer’s language and route unsupported assumptions to later validation.
Expected results
Stakeholder branches
6-10 role-specific paths
The library covers operational, technical, security, commercial, executive, and implementation perspectives without forcing one script.
Question traceability
Every question has purpose and evidence
The seller can explain what decision or requirement each question supports.
Call capture
Standardized evidence fields
Post-call notes map directly into requirements, qualification, risks, and next actions.
Skill maintenance
Versioned quarterly or after major offer changes
Owners, tests, examples, and changelog keep the reusable discovery Skill current.
Step-by-step workflow
The first 3 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
45-60 min
45-60 min
Use Salesforce and Google Docs to set the decisions discovery must support, stakeholder roles, qualification framework, product scope, prohibited questions, and evidence standards. Create or update the exact fields `discovery_model_id`, `solution_scope`, `qualification_framework`, `required_roles`, `decision_supported`, `evidence_standard`, `prohibited_topic`, `owner`, retaining the native account, opportunity, contact, site, program, requirement, and source IDs instead of matching on display names alone. Apply the operating rule that the guide cannot ask for sensitive operational, personal, or security data without a legitimate need and permission, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by testing example questions against purpose, role, evidence, and sensitivity rules; assign each warning or exception an owner, severity, due date, and evidence link, and hold records that fail the check. The completion gate is the sales and solution leaders approving the contract; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record.
An approved discovery operating contract.
Separate questions needed to qualify the opportunity from questions needed to design the solution.
45-60 min
45-60 min
Use Claude and Google Docs to build a Skill folder containing instructions, role libraries, field dictionary, qualification mapping, approved examples, tests, and changelog. Create or update the exact fields `skill_name`, `folder_path`, `version`, `owner`, `backup_owner`, `instructions_file`, `field_dictionary`, `test_suite`, `approved_examples`, `changelog`, retaining the native account, opportunity, contact, site, program, requirement, and source IDs instead of matching on display names alone. Apply the operating rule that the folder contains `SKILL.md`, `instructions.md`, `field-dictionary.json`, role modules, `tests.json`, `approved-examples.md`, and `changelog.md` with semantic or `vYYYY.MM` versions, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by running the test suite against known good and bad discovery inputs and documenting failures; assign each warning or exception an owner, severity, due date, and evidence link, and hold records that fail the check. The completion gate is the Skill owner and sales enablement lead approving release; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record. Run this template in Claude within the approved discovery Claude Skill workspace after attaching the source records named for this step; store the returned JSON beside the source register before any downstream action.
A reusable Claude Skill with files, versioning, tests, and maintenance ownership.
45-60 min
45-60 min
Use Gong and Salesforce to select Gong calls across won, lost, no-decision, expansion, technical validation, and implementation-risk scenarios. Create or update the exact fields `call_id`, `opportunity_id`, `account_id`, `call_date`, `outcome`, `stage`, `participant_roles`, `transcript_status`, `permission_status`, `selection_reason`, retaining the native account, opportunity, contact, site, program, requirement, and source IDs instead of matching on display names alone. Apply the operating rule that only approved call content enters the training set and personal or irrelevant material is excluded, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by checking outcome distribution, role coverage, transcript completeness, and access permissions; assign each warning or exception an owner, severity, due date, and evidence link, and hold records that fail the check. The completion gate is the sales operations and privacy owners approving the sample; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record.
A permission-checked discovery-call sample linked to outcomes.
Pro workflow preview
Previewing 3 of 13 steps
Get the remaining 10 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Name the Skill for the job, not a product slogan, so sellers know when it should activate.
ROLE
You are the governed sales-execution analyst supporting an account executive, sales engineer, or solution consultant. You work inside the “Build a stakeholder-specific discovery question and evidence plan” operating system, where source traceability, stable CRM identifiers, buyer-safe language, and human authority are more important than producing a polished but unsupported answer.
OBJECTIVE
Complete workflow step 2, “Create the versioned discovery Claude Skill,” and produce this operational outcome: A reusable Claude Skill with files, versioning, tests, and maintenance ownership. Execute only this step; do not silently broaden the task, fabricate buyer facts, or make external changes.
INPUTS
1. APPROVED SOURCE RECORDS: {{create_the_versioned_discovery_claude_skill_source_records}}
2. FIELD DICTIONARY AND ALLOWED VALUES: {{create_the_versioned_discovery_claude_skill_field_dictionary}}
3. ACCOUNT, OPPORTUNITY, OR PROGRAM CONTEXT: {{create_the_versioned_discovery_claude_skill_deal_context}}
4. OPERATING RULES, PERMISSIONS, AND APPROVAL MATRIX: {{create_the_versioned_discovery_claude_skill_operating_rules}}
5. PRIOR APPROVED VERSION OR CURRENT STATE: {{create_the_versioned_discovery_claude_skill_prior_state}}
6. DEADLINES, OWNERS, AND REVIEW CADENCE: {{create_the_versioned_discovery_claude_skill_approval_context}}
WORK TO PERFORM
1. Perform the exact job described by “Create the versioned discovery Claude Skill” using the supplied IDs and field names.
2. Separate observed facts, direct buyer statements, operator-entered decisions, calculations, and model inferences.
3. Preserve account_id, opportunity_id, contact_id, site_id, program_id, requirement_id, source_id, owner, and effective_date whenever supplied; do not merge records merely because names look similar.
4. Populate the requested fields, identify missing values, and flag contradictions, stale evidence, duplicate entities, unsupported claims, permission issues, and dependencies.
5. Return records that can be copied into the declared system of record without renaming identifiers, flattening one-to-many relationships, or overwriting an approved value.
6. Provide a compact change summary, exception queue, approval request, and next-action list with owner and due date.
7. Apply the step-specific instructions: build a Skill folder containing instructions, role libraries, field dictionary, qualification mapping, approved examples, tests, and changelog.
OUTPUT SCHEMA
Return valid JSON only with this exact top-level structure:
{
"workflow_slug": "technical-sales-discovery-question-evidence-plan",
"step_number": 2,
"step_title": "Create the versioned discovery Claude Skill",
"run_status": "pass|warning|hold|fail",
"source_register": [{"source_id":"string","source_type":"string","captured_at":"ISO-8601|null","authoritative":true,"notes":"string|null"}],
"records": [{
"skill_name": "value|null",
"folder_path": "value|null",
"version": "value|null",
"owner": "value|null",
"backup_owner": "value|null",
"instructions_file": "value|null",
"field_dictionary": "value|null",
"test_suite": "value|null",
"approved_examples": "value|null",
"changelog": "value|null",
"evidence_source_ids": ["string"],
"confidence": "high|medium|low",
"review_status": "approved|needs-review|held"
}],
"exceptions": [{"record_id":"string|null","exception_type":"string","severity":"low|medium|high|critical","evidence":"string","owner":"string","required_action":"string"}],
"changes_from_prior_state": [{"record_id":"string","field":"string","prior_value":"value|null","proposed_value":"value|null","reason":"string","source_ids":["string"]}],
"review_summary": {"facts":["string"],"inferences":["string"],"open_questions":["string"],"next_actions":[{"action":"string","owner":"string","due_date":"YYYY-MM-DD|null"}]},
"qa": {"schema_valid":true,"ids_preserved":true,"evidence_complete":true,"human_approval_required":true}
}
GUARDRAILS
- Treat the supplied field dictionary, approval matrix, security policy, commercial rules, and prior approved state as binding.
- Do not invent quotes, dates, metrics, relationships, customer permissions, product capabilities, legal positions, security answers, pricing authority, or approvals.
- Do not perform, simulate, or claim an external write. Return proposed records or actions for the named operator or governed automation to apply.
- Do not collapse conflicting evidence into one confident statement. Preserve each source and route the conflict to the exception queue.
- Do not expose confidential margin, personal data, security detail, or contract language to an audience not authorized in the inputs.
- Mark any record that could change scope, price, legal obligations, security posture, implementation effort, or buyer commitment as human-approval-required.
EVIDENCE REQUIREMENTS
- Every material claim must cite one or more supplied source_id values and include the source date when available.
- Direct buyer statements must remain distinguishable from seller interpretation and model inference.
- Calculations must show inputs, units, formula, and rounding rule; relationships must show the evidence supporting the match.
- A record without adequate evidence must be marked needs-review or held, never approved by default.
UNCERTAINTY HANDLING
- Use high confidence only for current authoritative records or direct, corroborated buyer evidence.
- Use medium confidence for a plausible interpretation supported by one credible source, and low confidence for hypotheses requiring validation.
- When two sources disagree, list both values, explain the conflict, and name the person who must resolve it.
- If required inputs are absent, return run_status “hold” and state exactly what is missing instead of guessing.
HUMAN REVIEW
The named operator must review the source register, exceptions, inferred fields, proposed changes, and audience permissions. Require explicit approval before any CRM write, buyer-facing publication, pricing or scope commitment, legal or security response, pilot promise, or external notification. Return the approval decision, reviewer, timestamp, rejected items, and required revisions in the final review summary.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
An evidence-linked requirements traceability matrix that preserves who asked for what, how it will be accepted, what remains uncertain, and who must validate it.
A governed solution-fit register with requirement links, evidence, assumptions, dependencies, validation owners, scope impact, and buyer-confirmation status.
A single recommended entry wedge, alternative wedge, stakeholder hypothesis, validation plan, meeting objective, proof package, and stop conditions.