finance-billing-ops

Topics in the source

• Finance Billing Ops
• Skill Stack
• When to Use
• Guardrails
• Workflow
• 1. Start from the freshest billing evidence
• 2. Separate customer incidents from product truth
• 3. Inspect code-backed billing behavior

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-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 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 distinguish live data from saved snapshots separate: revenue fact custome

This is an excerpt. Refer to the complete source and its current requirements.