Analyze Billing and Revenue
Your AI delivers accurate insights into revenue, pricing, refunds, and team billing logic backed by code and data. It distinguishes live sales facts from product behavior and compares competitor pricing for operator truth.
affaan-m on GitHub
Curated by PromptsEdge from a public repo · MIT license. All credit goes to the author.
What is this skill?
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.
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
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-opsfor customer-specific remediation and follow-upresearch-opswhen competitor pricing or current market evidence mattersmarket-researchwhen the answer should end in a pricing recommendationgithub-opswhen the billing truth depends on code, backlog, or release state in sibling reposverification-loopwhen the answer depends on proving checkout, seat handling, or entitlement behavior
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
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
Install this skill
- 1
Get the skill — it’s free
Use the Get this skill panel. Unlocked skills stay in My skills. - 2
Download or clone the files
Download the zip, or clone the repo and copy theskills/finance-billing-opsfolder. - 3
Put it where your agent looks for skills
For Claude Code, use your personal skills folder (every project) or a project’s own folder:~/.claude/skills/finance-billing-ops/SKILL.md # all projects .claude/skills/finance-billing-ops/SKILL.md # this project only
- 4
Just ask
No command needed. The agent reads the skill’s description and loads it on its own when your request matches.
SKILL.md frontmatter
What your agent reads to decide when to load this skill.
--- name: finance-billing-ops description: 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. ---
Files
Open any Markdown file to read it here.
Related skills
View all →- Business Name Fit CheckFreeYour AI suggests or vets business, startup, or product names that stay true to your cultural roots and work professionally in your target markets. Avoid embarrassing meanings, pronunciation issues, and weak branding before you commit.
- Returns & Reverse LogisticsFreeYour AI manages product returns from authorization to refund and fraud detection. It applies grading frameworks, disposition decisions, and warranty claims handling informed by 15+ years of returns operations experience.
- Manage Quality Non-ConformanceFreeYour AI guides investigating and resolving manufacturing quality issues through root cause analysis and CAPA planning. It supports NCR lifecycle, SPC data interpretation, and audit preparation in regulated environments.
- Schedule Production JobsFreeYour AI sequences and balances manufacturing jobs to maximize throughput and meet delivery targets. It handles job priorities, line balancing, changeover trade-offs, and disruption responses across ERP, MES, and scheduling tools.