Billing & Dunning Engineer

What it does

Billing & Dunning Engineer is a Cursor agent playbook named billing-engineer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The billing-engineer agent handles money after the first checkout. integration-engineer connects Stripe; this role fixes dunning, proration, seat math, and portal UX. It never changes live prices without an explicit confirm.

Failed cards, proration, seats, portal, dunning mail. Owns Stripe edge cases after checkout exists: failed payments, upgrades, downgrades, seat changes, and the customer portal.

Why it exists

A pile of agent files is not a team. billing-engineer exists so one job, billing & dunning engineer, has a written brief, required skills, and a stop condition.

It ships in the Engineering Kit. Skills it must read: Billing Dunning, Seats & Portal; Stripe Subscriptions & Webhook Handling; SaaS Architecture Patterns & Multi-Tenancy. Commands that adopt this role: /billing-fix: Stripe Dunning, Seats, and Portal Fixes; /stripe-billing: Stripe Billing & Subscription Setup; /notify: Transactional Email and In-App Notifications.

When to use it

• Cards failing and users vanishing
• Team seat add/remove that bills wrong
• Customer portal that 500s on cancel

When not to use it

• Do not ask billing-engineer to do a different role's job. If you need a launch post, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Engineering Kit so .cursor/agents/billing-engineer is on disk.
2. Run /billing-fix: Stripe Dunning, Seats, and Portal Fixes, or start a chat and tell Cursor to adopt the billing-engineer role.
3. The agent should read: Billing Dunning, Seats & Portal; Stripe Subscriptions & Webhook Handling; SaaS Architecture Patterns & Multi-Tenancy.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are billing-engineer. Cards failing and users vanishing. Read billing-dunning before you edit."

Or let the pipeline invoke it: /billing-fix: Stripe Dunning, Seats, and Portal Fixes.

Capabilities you should actually see: invoice.payment_failed and dunning sequences

Example output

• billing-engineer should leave files or a written verdict, not a vibe check. invoice.payment_failed and dunning sequences Proration and seat-count upgrades
• Engineering agents should touch the slice they were given (schema, route, test, or review note) and nothing else.

Best practices

• invoice.payment_failed and dunning sequences
• Proration and seat-count upgrades
• Customer portal and self-serve cancel paths
• Idempotent webhook handling for subscription lifecycle
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using billing-engineer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Letting the writer approve its own PR.
• Invoking this agent and three unrelated ones in the same prompt.