Best for
- Enterprise deals where the seller cannot attend every internal meeting
- Complex buying committees with technical and commercial concerns
- Champions who need help persuading finance, IT, operations, or executives
Create buyer-safe internal materials, stakeholder FAQs, proof, value, implementation answers, and coaching so a champion can build consensus without the seller in the room.
A champion-ready internal deck, decision memo, forwarding email, stakeholder FAQ, proof library, implementation summary, objection guide, and coaching plan.
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
A champion needs more than enthusiasm; they need accurate language, credible evidence, stakeholder-specific answers, and a safe way to explain implementation and risk. This workflow converts the deal record into internal-forwardable assets while keeping confidential seller strategy, unsupported claims, and premature commitments out of the champion’s materials.
Expected results
Champion readiness
One complete internal kit
The champion can explain problem, value, proof, implementation, and next decision without relying on seller-only notes.
Stakeholder coverage
Role-specific FAQ and proof
Finance, technical, operational, security, procurement, and executive concerns receive appropriate evidence.
Buyer safety
All assets permission-reviewed
Internal competitive strategy, customer-confidential material, and unsupported commitments remain excluded.
Consensus feedback
Engagement and objections captured
The kit creates a structured way for the champion to report what moved and what remains blocked.
Step-by-step workflow
The first 2 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
Work in Gong to confirm the champion’s role, influence, credibility, access, motivation, internal objective, decision meeting, risk, and willingness to use materials. Create or update the exact fields `champion_id`, `contact_id`, `role`, `influence`, `credibility`, `access`, `motivation`, `internal_decision`, `decision_date`, `champion_risk`, `validation_source`, retaining the native account, opportunity, contact, site, program, requirement, and source IDs instead of matching on display names alone. Apply the operating rule that champion status requires direct evidence and remains separate from seller optimism, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by reviewing call evidence, actions completed, internal access, and whether the contact has corrected or challenged the seller; 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 account executive and manager approving champion status; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record.
A validated champion profile and internal decision objective.
A friendly contact is not a champion unless they can and will take action inside the buying process.
45-60 min
45-60 min
Work in Claude and Google Slides to package buyer-safe instructions, field dictionary, audience matrix, approved proof, value evidence, prohibited content, examples, tests, and changelog. Create or update the exact fields `project_version`, `instructions_file`, `field_dictionary`, `audience_matrix`, `proof_register`, `value_register`, `prohibited_content`, `test_cases`, `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 project contains required files, owners, `vYYYY.MM` releases, tests, refresh rules, and maintenance procedures, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by running buyer-safety regression tests and checking redaction across sample assets; 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 account owner and legal, product, or customer-proof owners approving the package; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record.
A maintained champion-enablement workspace with safe content rules.
Pro workflow preview
Previewing 2 of 13 steps
Get the remaining 11 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Include a test that removes seller-only competitive and relationship notes from every external asset.
ROLE
You are the governed sales-execution analyst supporting an account executive supporting a validated buyer champion. You work inside the “Equip a champion with an internal selling and consensus kit” 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 champion Claude Project,” and produce this operational outcome: A maintained champion-enablement workspace with safe content rules. 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_champion_claude_project_source_records}}
2. FIELD DICTIONARY AND ALLOWED VALUES: {{create_the_versioned_champion_claude_project_field_dictionary}}
3. ACCOUNT, OPPORTUNITY, OR PROGRAM CONTEXT: {{create_the_versioned_champion_claude_project_deal_context}}
4. OPERATING RULES, PERMISSIONS, AND APPROVAL MATRIX: {{create_the_versioned_champion_claude_project_operating_rules}}
5. PRIOR APPROVED VERSION OR CURRENT STATE: {{create_the_versioned_champion_claude_project_prior_state}}
6. DEADLINES, OWNERS, AND REVIEW CADENCE: {{create_the_versioned_champion_claude_project_approval_context}}
WORK TO PERFORM
1. Perform the exact job described by “Create the versioned champion Claude Project” 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: package buyer-safe instructions, field dictionary, audience matrix, approved proof, value evidence, prohibited content, examples, tests, and changelog.
OUTPUT SCHEMA
Return valid JSON only with this exact top-level structure:
{
"workflow_slug": "champion-internal-selling-consensus-kit",
"step_number": 2,
"step_title": "Create the versioned champion Claude Project",
"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": [{
"project_version": "value|null",
"instructions_file": "value|null",
"field_dictionary": "value|null",
"audience_matrix": "value|null",
"proof_register": "value|null",
"value_register": "value|null",
"prohibited_content": "value|null",
"test_cases": "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.
A governed decision-system map with criteria, authority, vetoes, sequence, committees, evidence requirements, conflicts, consensus risk, and next actions.
An executive sponsor brief, meeting objective, role instructions, questions, give and ask, proof, prohibited commitments, follow-up, and debrief template.
An auditable spreadsheet model, evidence register, scenario analysis, buyer-validation log, and CFO-ready decision brief with assumptions and uncertainty visible.