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.
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.
Pull these ECC-native skills into the workflow when relevant:
customer-billing-ops for customer-specific remediation and follow-upresearch-ops when competitor pricing or current market evidence mattersmarket-research when the answer should end in a pricing recommendationgithub-ops when the billing truth depends on code, backlog, or release state in sibling reposverification-loop when the answer depends on proving checkout, seat handling, or entitlement behaviorPrefer live billing data. If the data is not live, state the snapshot timestamp explicitly.
Normalize the picture:
If the question is customer-specific, classify first:
Then separate that from the broader product question:
If the answer depends on implementation truth, inspect the code path:
Report:
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