home / skills / gtmagents / gtm-agents / pricing-governance

This skill helps you run pricing councils, log decisions, and enforce approval workflows to maintain governance and price integrity.

npx playbooks add skill gtmagents/gtm-agents --skill pricing-governance

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: pricing-governance
description: Use to run pricing councils, track decisions, and enforce approval workflows.
---

# Pricing Governance Playbook Skill

## When to Use
- Facilitating pricing council meetings or steering committees.
- Logging approvals, assumptions, and launch timing for pricing changes.
- Auditing pricing experiments or discount policy adjustments.

## Framework
1. **Council Charter** – define members, meeting cadence, decision rights, and escalation paths.
2. **Decision Log** – capture proposals, outcomes, rationales, and follow-up actions.
3. **Approval Matrix** – map thresholds (discount %, price change scope) to required approvers.
4. **Communication Hooks** – standardize templates for stakeholder updates and launch checklists.
5. **Audit Trail** – store artifacts (models, decks, FAQs) and post-launch performance reviews.

## Templates
- Council agenda + minutes doc.
- Decision log spreadsheet with filters.
- Launch readiness checklist with owners/dates.

## Tips
- Keep logs centralized to reduce drift across regions.
- Pair with `enablement-kit` to ensure decisions convert to frontline training.
- Schedule retro sessions at 30/60/90 days post-launch to validate assumptions.

---

Overview

This skill runs pricing councils, tracks decisions, and enforces approval workflows for pricing changes. It packages a governance framework, decision logging, approval matrices, and templates to make pricing programs auditable and operational. Use it to standardize how pricing decisions are made, communicated, and reviewed across go-to-market teams.

How this skill works

The skill guides you through creating a council charter, capturing proposals in a decision log, and mapping approval thresholds to required approvers. It provides templates for agendas, minutes, and launch checklists while maintaining an audit trail of artifacts and post-launch reviews. Approval workflows are enforced via an approval matrix so only authorized changes proceed to implementation.

When to use it

  • Running pricing council meetings or steering committee sessions
  • Logging approvals, assumptions, and launch timing for price or discount changes
  • Auditing pricing experiments, promotions, or discount policy adjustments
  • Coordinating cross-functional launch readiness and stakeholder communications
  • Enforcing authorization before implementing sensitive or high-impact price moves

Best practices

  • Define a clear council charter with members, cadence, decision rights, and escalation paths
  • Centralize the decision log to avoid region- or team-level drift
  • Map approval thresholds (discount %, scope) in an explicit approval matrix
  • Attach artifacts (models, decks, FAQs) to each decision for traceability
  • Schedule 30/60/90 day retros to validate assumptions and capture learnings

Example use cases

  • A revenue ops team runs a weekly pricing council to approve territory-level discount changes
  • Product and pricing teams log a new packaging change with linked launch checklists and owners
  • A company audits past promotions by reviewing decision logs and post-launch performance
  • Sales leadership enforces an approval matrix before large account discounting
  • Marketing coordinates stakeholder comms and enablement tasks tied to approved price changes

FAQ

How do I set approval thresholds?

Determine thresholds by impact (discount %, revenue at risk, or deal size) and map each band to required approvers in the approval matrix.

What artifacts should be stored with each decision?

Store models, slide decks, FAQ drafts, rollout plans, and the launch readiness checklist to ensure full auditability.

How often should the council meet?

Set cadence based on volume of pricing activity—weekly for high-volume teams, biweekly or monthly for lower-frequency organizations.