Finance Billing Ops
Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Finance Billing Ops when an AI agent needs a reusable SKILL.md workflow for this job: Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.
When not to use it
Skip Finance Billing Ops when the task is outside the business category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/finance-billing-ops # Save SKILL.md to ~/.claude/skills/finance-billing-ops/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/finance-billing-ops/SKILL.md. For a shared project, commit the folder at .claude/skills/finance-billing-ops/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Finance Billing Ops skill for this task: user asks for Stripe sales, refunds, MRR, or recent customer activity. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Finance Billing Ops
Use this when the user wants to understand money, pricing, refunds, team-seat logic, or whether the product actually behaves the way the website and sales copy imply.
This is broader than `customer-billing-ops`. That skill is for customer remediation. This skill is for operator truth: revenue state, pricing decisions, team billing, and code-backed billing behavior.
## Skill Stack
Pull these ECC-native skills into the workflow when relevant:
- `customer-billing-ops` for customer-specific remediation and follow-up - `research-ops` when competitor pricing or current market evidence matters - `market-research` when the answer should end in a pricing recommendation - `github-ops` when the billing truth depends on code, backlog, or release state in sibling repos - `verification-loop` when the answer depends on proving checkout, seat handling, or entitlement behavior
## When to Use
- user asks for Stripe sales, refunds, MRR, or recent customer activity - user asks whether team billing, per-seat billing, or quota stacking is real in code - user wants competitor pricing comparisons or pricing-model benchmarks - the question mixes revenue facts with product implementation truth
## Guardrails
- distinguish live data from saved snapshots - separate: - revenue fact - customer impact - code-backed product truth - recommendation - do not say "per seat" unless the actual entitlement path enforces it - do not assume duplicate subscriptions imply duplicate value
## Workflow
### 1. Start from the freshest billing evidence
Prefer live billing data. If the data is not live, state the snapshot timestamp explicitly.
Normalize the picture:
- paid sales - active subscriptions - failed or incomplete checkouts - refunds - disputes - duplicate subscriptions
### 2. Separate customer incidents from product truth
If the question is customer-specific, classify first:
- duplicate checkout - real team intent - broken self-serve controls - unmet product value - failed payment or incomplete setup
Then separate that from the broader product question:
- does team billing really exist? - are seats actually counted? - does checkout quantity change entitlement? - does the site overstate current behavior?
### 3. Inspect code-backed billing behavior
If the answer depends on implementation truth, inspect the code path:
- checkout - pricing page - entitlement calculation - seat or quota handling - installation vs user usage logic - billing portal or self-serve management support
### 4. End with a decision and product gap
Report:
- sales snapshot - issue diagnosis - product truth - recommended operator action - product or backlog gap
## Output Format
```text SNAPSHOT - timestamp - revenue / subscriptions / anomalies
CUSTOMER IMPACT - who is affected - what happened
PRODUCT TRUTH - what the code actually does - what the website or sales copy claims
DECISION - refund / preserve / convert / no-op
PRODUCT GAP - exact follow-up item to build or fix ```
## Pitfalls
- do not conflate failed attempts with net revenue - do not infer team billing from marketing language alone - do not compare competitor pricing from memory when current evidence is available - do not jump from diagnosis straight to refund without classifying the issue
## Verification
- the answer includes a live-data statement or snapshot timestamp - product-truth claims are code-backed - customer-impact and broader pricing/product conclusions are separated cleanly
Intended uses
- user asks for Stripe sales, refunds, MRR, or recent customer activity
- user asks whether team billing, per-seat billing, or quota stacking is real in code
- user wants competitor pricing comparisons or pricing-model benchmarks
- the question mixes revenue facts with product implementation truth
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.