Best for
- Enterprise pricing and contract negotiations
- Software plus services packages
- Deals involving discount, terms, scope, and implementation concessions
Model buyer asks, concession cost, package options, give-get exchanges, sequencing, walk-away limits, approval levels, scripts, and CRM controls before commercial negotiation.
A confidential negotiation plan with buyer motivations, package options, concession economics, give-gets, approval boundaries, scripts, escalation, and post-meeting updates.
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
Commercial outcomes improve when concessions are priced, sequenced, exchanged for buyer commitments, and kept within explicit approval boundaries. The workflow separates buyer-visible packages from internal walk-away logic and creates an auditable path for exceptions without exposing margin or negotiation strategy to unauthorized audiences.
Expected results
Concession visibility
Every give has quantified cost
Discount, terms, services, risk, support, and scope changes are evaluated rather than improvised.
Give-get discipline
Each concession has a buyer return
The plan links concessions to signature, term, scope, reference, payment, access, or timeline commitments.
Approval control
Clear authority by package
Reps know what they can offer, what needs approval, and what is prohibited.
Negotiation learning
Outcome and deviation logged
Final terms, unused options, exceptions, and lessons update future planning without exposing confidential data.
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 Salesforce and Slack to set plan owner, participants, confidential fields, approval roles, communication channels, versioning, retention, and prohibited sharing. Create or update the exact fields `plan_id`, `opportunity_id`, `plan_owner`, `participant`, `confidential_field`, `approval_role`, `approved_channel`, `version`, `retention_rule`, `sharing_prohibition`, 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 authorized participants can access confidential fields and buyer-facing packages are stored separately, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by testing access, channel membership, file permissions, forwarding controls, and retention; assign each warning or exception an owner, severity, due date, and evidence link, and hold records that fail the check. The completion gate is sales leadership and deal desk approving governance; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record.
A restricted negotiation governance and access contract.
Keep walk-away, margin, and approval boundaries out of buyer workspaces and broad deal channels.
45-60 min
45-60 min
Work in Claude and Google Sheets to package instructions, concession taxonomy, approval matrix, pricing rules, examples, red-team cases, tests, and changelog. Create or update the exact fields `project_version`, `instructions_file`, `field_dictionary`, `concession_taxonomy`, `approval_matrix`, `pricing_rules`, `test_cases`, `changelog`, `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 project has required files, restricted ownership, `vYYYY.MM` releases, tests, 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 access and output tests that confirm confidential values never appear in buyer-facing sections; assign each warning or exception an owner, severity, due date, and evidence link, and hold records that fail the check. The completion gate is deal desk and sales leadership approving the package; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record.
A restricted, versioned negotiation workspace.
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
ROLE
You are the governed sales-execution analyst supporting an account executive, sales manager, or deal-desk lead. You work inside the “Plan commercial negotiation give-gets and approval boundaries” 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 negotiation Claude Project,” and produce this operational outcome: A restricted, versioned negotiation workspace. 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_negotiation_claude_project_source_records}}
2. FIELD DICTIONARY AND ALLOWED VALUES: {{create_the_versioned_negotiation_claude_project_field_dictionary}}
3. ACCOUNT, OPPORTUNITY, OR PROGRAM CONTEXT: {{create_the_versioned_negotiation_claude_project_deal_context}}
4. OPERATING RULES, PERMISSIONS, AND APPROVAL MATRIX: {{create_the_versioned_negotiation_claude_project_operating_rules}}
5. PRIOR APPROVED VERSION OR CURRENT STATE: {{create_the_versioned_negotiation_claude_project_prior_state}}
6. DEADLINES, OWNERS, AND REVIEW CADENCE: {{create_the_versioned_negotiation_claude_project_approval_context}}
WORK TO PERFORM
1. Perform the exact job described by “Create the versioned negotiation 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 instructions, concession taxonomy, approval matrix, pricing rules, examples, red-team cases, tests, and changelog.
OUTPUT SCHEMA
Return valid JSON only with this exact top-level structure:
{
"workflow_slug": "commercial-negotiation-give-get-approval-planner",
"step_number": 2,
"step_title": "Create the versioned negotiation 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",
"concession_taxonomy": "value|null",
"approval_matrix": "value|null",
"pricing_rules": "value|null",
"test_cases": "value|null",
"changelog": "value|null",
"owner": "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 auditable spreadsheet model, evidence register, scenario analysis, buyer-validation log, and CFO-ready decision brief with assumptions and uncertainty visible.
A controlled deal-readiness record with workstream status, evidence, owners, buyer dates, internal SLAs, dependencies, blockers, approvals, escalation, and close decision.
A governed decision-system map with criteria, authority, vetoes, sequence, committees, evidence requirements, conflicts, consensus risk, and next actions.