Commercial Policy logo

Commercial Policy

Community
borghei
commercial-policy

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval. Use when authoring a policy charter, defining discount/payment/liability rules, auditing deals, or generating a regional policy.

Overview

Publisherborghei
RepositoryClaude-Skills
Skill namecommercial-policy
Stars
856
Forks
154
Bundled files
6
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by borghei on GitHub. Read the source before you install it.

Installation

Install the Commercial Policy AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/borghei/Claude-Skills/tree/main/business-growth/commercial-policy
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p .claude/skills
cp -r /tmp/Claude-Skills/business-growth/commercial-policy .claude/skills/commercial-policy
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Commercial Policy in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Commercial Policy on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Commercial Policy is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Commercial Policy

End-to-end commercial-policy authoring and governance: defining the rules that govern what sales can offer, what triggers approval, and what's prohibited. Pairs with our deal-desk (operational enforcement) and pricing-strategy (price-setting) skills — this is the policy that those execute against.

A good commercial policy:

  • Makes deal-desk faster (fewer ambiguous cases)
  • Makes sales reps more autonomous (clearer authority)
  • Makes legal reviews lighter (most cases already covered)
  • Reduces concession drift over time
  • Provides audit-ready governance documentation

When to use this skill

SituationSkill applies
Authoring commercial policy from scratchYes — start with policy charter template + scripts/commercial_policy_generator.py
Refreshing an existing policy (annual)Yes — see annual policy review workflow
Auditing recent deals for policy complianceYes — scripts/policy_compliance_checker.py
Analyzing terms-deviation patternsYes — scripts/terms_deviation_analyzer.py
Tailoring policy for new region / verticalYes — scripts/commercial_policy_generator.py --region <X>
Drafting sales training on policyYes — see training section
Setting prices (not policy on deviations)Use business-growth/pricing-strategy
Per-deal approvalUse business-growth/deal-desk
Writing the specific contractUse business-growth/contract-and-proposal-writer

What commercial policy covers

Standard scope:

DomainPolicy area
PricingStandard pricing, discount thresholds, MFN, rebates, custom-bundle pricing
ContractStandard term length, payment terms, renewal terms, termination, customer audit rights
LegalAcceptable MSA modifications, liability cap, indemnification, jurisdiction, IP
OperationalSLA tiers, custom SLAs, security commitments, dedicated infrastructure
Customer commitmentsReference / case study / press release obligations
ChannelPartner discount tiers, channel-conflict rules, deal-registration
Special termsPerformance-based payment, acceptance criteria, ramp deals

What it doesn't cover:

  • Day-to-day pricing decisions (that's pricing strategy)
  • Per-deal approval mechanics (that's deal-desk operations)
  • Sales targets / quota (that's compensation policy)
  • Customer success / churn-prevention tactics

Commercial policy charter (template)

The foundational document. Every company that does $5M+ ARR needs one. Use this template:

markdown
# Commercial Policy Charter

## Purpose
This Commercial Policy defines the rules that govern commercial terms
offered to customers. It is binding on all customer-facing functions
(Sales, Customer Success, Partner / Channel) and is enforced by Deal Desk.

## Scope
Applies to:
- All new customer agreements
- All renewals (with material change)
- All partner-mediated deals
- All custom / non-standard agreements

Does not apply to:
- Self-serve / PLG transactions per standard published terms
- Auto-renewals at standard terms

## Owners and Approvers
- Policy owner: CRO + CFO + General Counsel (jointly)
- Operational enforcement: Deal Desk
- Updates: quarterly review by policy owners
- Material changes: board awareness

## Pricing Policy

### Standard pricing
- All new customers offered at published list pricing
- Published price is canonical; deviations require approval per matrix

### Discount approval matrix
[Per the deal-desk approval matrix — see business-growth/deal-desk]

### Maximum allowed discount
- Standard maximum: 50%
- Beyond 50%: CEO + Board awareness required
- Discount > 60%: only with explicit strategic-rationale documented and CEO sign-off

### Most Favored Nation (MFN)
- Not granted by default
- Granted only with: strategic-tier customer + CRO + CFO + GC approval
- Always scoped narrowly: same product, same volume, same term length, same geography
- Disclosure-only (never automatic price-match)

### Rebates
- Performance-based rebates allowed per partner-program tier
- Customer-tier rebates: discouraged; if granted, time-bounded and explicit

## Contract Policy

### Standard term
- 12-month contract with annual prepay
- Auto-renew unless 90-day notice

### Term flexibility
- < 12 months: requires Director approval
- 24-36 months: Director approval
- > 36 months: VP Sales approval
- Multi-year discounts: per discount matrix

### Payment terms
- Standard: Net 30, annual prepay
- Net 45-60: Director approval
- Net 90+: CFO approval
- Custom milestone-based: CFO approval; revenue recognition impact reviewed

### Renewal
- Standard: auto-renew, same terms, same price (or per published renewal pricing)
- Renewal expansion > 20%: deal-desk review
- Renewal contraction > 10%: deal-desk review + customer success consultation

### Termination
- Standard: termination for convenience requires 90-day notice
- Termination for cause: 30-day cure period
- Customer-requested termination flexibility: Director approval
- Mid-term termination rights: VP Sales approval

## Legal Policy

### MSA modifications
- Pre-approved modifications: tracked list in approved-modifications appendix
- Custom modifications: General Counsel approval required
- Customer-supplied MSA: full GC review; default to push back to our MSA

### Liability cap
- Standard: 1x annual fees
- 2x annual fees: GC + CFO approval
- > 2x annual fees: CEO sign-off
- Carve-outs: IP infringement, gross negligence, willful misconduct — always uncapped

### Indemnification
- Standard mutual indemnification per template
- Customer-favorable indemnification: GC approval
- Defense / settlement control: vendor by default; customer-controlled needs CEO

### Jurisdiction and governing law
- Standard: vendor's jurisdiction
- Customer jurisdiction: GC approval
- Arbitration vs litigation: per template; deviations need GC

### IP
- Standard: each party retains pre-existing; joint inventions per default
- Customer-favorable IP terms: GC approval
- Source code escrow: only for OEM / strategic; never standard customer

## Operational Policy

### SLA tiers
- Standard published SLA (99.5%)
- Enhanced SLA (99.9%): per published pricing
- Custom SLA: Customer Success + Engineering approval; pricing premium per agreement
- Custom SLA with penalties: CRO + CCO + Engineering approval

### Security commitments
- Standard SOC 2 / ISO 27001 commitments per template
- Custom security: CISO + GC approval
- Customer audit rights: GC approval (limited to annual, with notice, third-party auditor)

### Dedicated infrastructure
- Not standard; available only with CTO + GC approval
- Premium pricing required

## Customer Commitments

### Reference / case study requests
- Standard: requested but not required
- Discounted deals (> 15%): case study or reference required as condition
- Strategic logos: explicit case study + press release commitment

## Channel Policy

### Partner-mediated deals
- Per Partner Agreement; discount per tier
- Deal registration governs conflict
- Direct rep authority same as direct deals on partner-led opportunities

## Special Terms

### Performance-based payment
- Payment-on-acceptance / acceptance criteria: CFO + GC approval
- Milestone payments: CFO approval

### Ramp deals
- ≤ 3 months: Sales Manager
- 3-12 months: Director
- > 12 months: VP Sales

### Source code escrow (for customer)
- Not standard; available only with CTO + GC approval

## Documentation Requirements

Every non-standard deal documented per Deal Desk packet template:
- Deviation explicitly listed
- Justification documented
- Approver identified
- Customer commitments (if any) explicit
- Expiration / conditions clear

## Annual Review

This policy is reviewed annually by CRO + CFO + GC.
Material changes communicated to sales with training.

## Effective Date
<date>
## Last Updated
<date>
## Approved By
- CRO: <signature>
- CFO: <signature>
- GC: <signature>
- Board (acknowledgement): <date>

See references/commercial-policy-charter.md for the full annotated charter with notes on each section's typical contentious issues.


Discount and terms policy details

See references/discount-and-terms-policy.md for deeper guidance on:

  • Discount-percentage policy by ACV bracket
  • MFN clause design (when to allow, how to scope)
  • Performance-based rebate structures
  • Multi-year discount mechanics
  • Payment-term flexibility and revenue-recognition implications
  • Renewal pricing policy (escalators, holds, contraction)

Contract and commercial guardrails

See references/contract-and-commercial-guardrails.md for deeper guidance on:

  • Acceptable MSA modifications (a list-based, not case-by-case approach)
  • Liability cap negotiation
  • Termination rights design
  • IP and joint-development clauses
  • Customer audit rights
  • Cross-jurisdictional terms (EU vs US vs APAC)

Clarify First

Before generating the policy, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Company stage + ARR scale — drives whether a full charter is warranted and how tight thresholds should be
  • Approver structure — who owns the policy and sits in the chain (CRO/CFO/GC, VP Sales, Director) (populates Owners/Approvers and every approval line)
  • Region / jurisdiction — US / EU / APAC (changes payment norms, governing law, and triggers a regional overlay)
  • Max discount + liability risk appetite — the discount ceiling and liability-cap tolerance (drives the Pricing and Legal policy sections)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the policy.

End-to-end workflows

Workflow: Author commercial policy from scratch

  1. Assemble policy committee — CRO + CFO + GC sponsors + Deal Desk Lead + Sales Operations
  2. Inventory current deals — what terms have been offered? What's been ad-hoc?
  3. Identify policy gaps — areas where ad-hoc behavior is hurting (concession drift, customer surprises)
  4. Draft charter using template; one section per domain
  5. Internal review — Sales VP, Eng VP, CISO, Customer Success VP, Finance for revenue recognition
  6. Pilot with sales managers for 30 days — collect feedback
  7. Final approval — CRO + CFO + GC sign-off; board awareness
  8. Sales training — workshop + recorded session + quick-reference cards
  9. Publish to sales wiki / partner portal / customer-facing communications team
  10. Quarterly review thereafter

Workflow: Refresh existing policy (annual)

  1. Pull deal data for past 12 months: discount distribution, terms deviations, approvals
  2. Identify drift — what's the deviation rate by policy category?
  3. Survey sales managers — what's working / what's blocking
  4. Survey customers — what terms have been requested but declined?
  5. Identify market shifts — competitive landscape, customer expectations
  6. Draft amendments — specific policy changes with rationale
  7. Approve with CRO + CFO + GC
  8. Communicate changes to sales with training
  9. Update charter + effective date

Workflow: Audit deal compliance

  1. Export deals from CRM for the period
  2. Run compliance checker — scripts/policy_compliance_checker.py --deals deals.csv --policy policy.yaml
  3. Review non-compliant deals — investigate each: was the deviation approved? was it documented?
  4. Categorize:
    • Compliant with approved deviation: OK
    • Non-compliant unapproved: investigate; corrective action
    • Compliant but suggests policy gap: amend policy
  5. Report to policy committee; track corrective actions

Workflow: Generate region-specific policy

  1. Identify region-specific requirements — currency, jurisdiction, payment norms, regulatory
  2. Run scripts/commercial_policy_generator.py --base policy.yaml --region <region> to get base + regional overlay
  3. Tailor further with local team (regional VP Sales, regional GC, regional CFO)
  4. Approve through standard governance
  5. Communicate to regional sales

Anti-patterns

  • Policy without enforcement. Written policy + ad-hoc execution = policy is theater.
  • Policy that's never updated. Markets shift; competitive landscape changes; policy goes stale.
  • Policy with no compliance audit. Without measurement, you can't tell if policy is followed.
  • Policy too restrictive. When sales bypasses constantly, the policy is wrong; tighten or loosen.
  • Policy too lax. When everyone "complies" but margin still erodes, policy doesn't constrain enough.
  • Policy authored without sales input. Reps see it as imposed; comply minimally.
  • Policy with no training. Reps don't know what they can offer; default to over-asking deal desk.
  • Policy that's a contract appendix. Buried in legal docs; never read.
  • Same policy across regions when market conditions differ substantially.
  • Policy reviewed only after a customer complaint. Reactive only.

Tooling outputs

ScriptInputOutput
scripts/policy_compliance_checker.pyDeal CSV + policy YAMLPer-deal: compliant / non-compliant with policy violation listing; aggregate compliance metrics
scripts/terms_deviation_analyzer.pyDeal CSVDeviation patterns: which terms most often deviate? from which standard? by what magnitude?
scripts/commercial_policy_generator.pyBase policy YAML + optional region overlayGenerated policy document (markdown), tailored to company stage, ICP, region

All scripts: stdlib only, argparse CLI, JSON or markdown output.


References


Related skills

  • business-growth/deal-desk — operational enforcement of policy
  • business-growth/pricing-strategy — sets prices that policy governs deviations from
  • business-growth/contract-and-proposal-writer — drafts contracts respecting policy
  • business-growth/channel-economics — channel deals subject to policy (with overlay for partners)
  • business-growth/partnerships-architect — partnership terms subject to commercial-policy oversight
  • c-level-advisor/cs-cro-advisor — CRO is co-owner of policy
  • c-level-advisor/cs-cfo-advisor — CFO is co-owner of policy
  • ra-qm-team/soc2-compliance-expert — policy compliance is audit-relevant evidence

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Commercial Policy AI skill do?

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval. Use when authoring a policy charter, defining discount/payment/liability rules, auditing deals, or generating a regional policy.

Why use Commercial Policy on TypingMind?

Because you install it once and use it with any model. Commercial Policy is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Commercial Policy in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/borghei/Claude-Skills/tree/main/business-growth/commercial-policy. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Commercial Policy?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Commercial Policy?

As many as you like. As long as a model supports skills, you can use Commercial Policy with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Commercial Policy AI skill free?

It is published on GitHub by borghei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇