Research date: 2026-09-25. Scope: a small B2B SaaS or subscription business, with room to grow into a larger finance team. This is a proposed product taxonomy, not a claim that every company has a separate employee for each role or that AgentWorks already connects to every named tool.

Job family / catalog category	Questions and recurring work	Candidate Crew identity and first useful result	Typical systems
Subscription billing & receivables	Are plans, usage, renewals, invoices, credits, and unpaid accounts correct? Which invoices need a human follow-up?	Billing Operations Coordinator: source-linked billing exception queue and reviewed customer drafts.	Billing system, CRM, email, accounting ledger.
Payments & recovery	Which payments failed, which payouts are delayed, which customers requested refunds, and which disputes need evidence?	Billing Operations Coordinator for failed payments, refund requests, and disputes; Finance Analyst for payout and fee reconciliation.	Payment processor, billing system, bank, support queue.
Revenue accounting & close	Do contracts, invoices, cash, deferred revenue, credits, and recognized revenue reconcile for the period?	Revenue & Close Analyst when a distinct accountant or reviewer exists; otherwise a Finance Analyst capability pack. First result: close checklist and exceptions with source records.	Accounting ledger, billing system, revenue recognition tool, bank.
Payables, procurement & spend	Which vendor bills, subscriptions, card charges, and employee expenses need coding or approval? Are duplicates or budget exceptions present?	Spend & Payables Coordinator when vendor/payment rights differ from finance analysis. First result: review queue with policy and duplicate checks.	AP system, cards/expense system, accounting ledger, vendor documents.
Planning & SaaS performance	What changed in MRR/ARR, churn, retention, margin, budget, burn, runway, and forecast? Which assumptions drove the change?	Finance Analyst: sourced weekly or monthly brief with metric definitions, variance, scenarios, and decisions.	Billing, product/CRM data, accounting, bank or authorized exports.
Cash & treasury	What cash is available, what is pending, what bills or payroll are due, and how do timing scenarios affect runway?	Finance Analyst at small scale; separate Cash & Treasury Analyst only for multiple banks/entities or a distinct cash owner.	Bank, payment processor, AP, payroll, accounting.
Indirect tax & tax preparation	What sales tax/VAT/GST data, invoices, exemptions, and filing-period exports need review?	Tax Export Preparer supporting pack (available v1); later Tax Compliance Coordinator only with distinct ownership and jurisdiction-specific review.	Billing, tax engine, accounting, source documents.
Payroll & people finance	Are payroll inputs, contractor invoices, deductions, and the payroll-to-ledger handoff complete?	Payroll Review Coordinator only when the user explicitly enables this sensitive data scope. First result: pre-run exception list; execution stays in payroll software with owner approval.	Payroll/HRIS, contractor platform, accounting.

Cross-functional boundary: Deal desk and quote-to-cash (discounts, contract terms, approvals, and handoff from a signed deal to billing) intersects Sales and Finance. Put its primary discoverability under Sales / Revenue Operations and link it to the Billing Operations Coordinator. Do not duplicate a full finance identity solely for quoting.

These families are grounded in current product coverage: Stripe documents subscription billing, receivables, recovery, reconciliation, and revenue reporting, including subscription-specific revenue recognition; QuickBooks and Xero both cover bank reconciliation and invoices, bills, expenses, and cash reporting; BILL covers bill intake, approvals, and payments; Ramp covers cards, expenses, and AP; Gusto covers payroll, taxes, and filings. Stripe's SaaS metrics guide covers MRR/ARR, churn, NRR, CAC, and unit economics. Tax treatment varies by region and product; a Crew prepares evidence and questions for a qualified reviewer rather than inferring a filing obligation from raw transactions. See Stripe's indirect tax overview.

Show tools as choose the system you already use, with an authorized CSV/file path for analysis-first jobs. Avoid a long checklist requiring every provider.

System of record / job	Examples to show	Template setup implication
Billing and payment source	Stripe or Paddle; Chargebee when the business already uses it	Ask which provider is authoritative for invoices, subscriptions, refunds, and payment status. Stripe and Paddle have different merchant-of-record and tax responsibilities; do not merge their meanings. Stripe SaaS, Paddle SaaS docs
Accounting ledger	QuickBooks Online or Xero; NetSuite for a larger finance stack	Ask for chart of accounts, fiscal period, reporting currency, and source of truth for the books. Require an authorized export until a connector is verified. QuickBooks reconciliation, Xero bookkeeping
Payables and company spend	BILL, Ramp, or Brex	Only ask for these when the payables/spend pack is selected. Separate bill reading from payment execution and approval. BILL AP, Ramp products, Brex technology
Payroll and contractors	Gusto for US payroll, Deel for international contractors, or the user's existing provider	Payroll details belong to a narrower access scope. A review pack should not run payroll or change payees. Gusto payroll, Deel contractors
Tax and revenue accounting	Stripe Tax, Stripe Revenue Recognition, Chargebee RevRec, or the user's accountant/ledger process	These are optional specialist sources, not prerequisites for the Finance Analyst brief. Check jurisdiction, accounting method, and reviewer. Stripe Tax, Stripe Revenue Recognition, Chargebee RevRec
Bank and cash	The user's bank or authorized statement export; Mercury is one startup-oriented example	Ask for actual bank statement/deposit evidence before saying a processor payout arrived. Mercury cash management

This list is a relevance map, not a measured popularity ranking. Provider choice depends on country, company size, billing model, and the customer's existing stack. For a SaaS-first launch, prioritize Stripe/Paddle + an accounting export or ledger + bank statement for the first Finance Analyst and Billing Operations Coordinator outcomes. Add AP/spend, payroll, tax, and advanced RevRec only when their selected job needs them.

The bundled MCP configuration currently lists Stripe, Paddle, and PayPal; the connector browser groups Stripe and PayPal under payments and explicitly says the accounting shelf is empty until QuickBooks or Xero arrives. A bundled MCP entry is a discovery option, not proof that a customer account is connected or that a particular write action is available. QuickBooks, Xero, BILL, Ramp, Gusto, Deel, and Chargebee are research examples / integration candidates, not implemented connectors in this repository. Use exports, files, or a user-supplied server where the product supports them, and disclose the reduced behavior in the setup proposal. Source: agent_go/configs/mcp_servers_clean.json and frontend/src/components/connectors/catalog.ts.

1. Keep Finance Analyst as the default entry point for analysis, SaaS metrics, Stripe/Paddle account checks, cash planning, and exports. Add selected capability packs with independent setup checks.
2. Billing Operations Coordinator now has a v1 Crew template for customer-facing invoices, failed payments, refunds, and disputes. Its first run prepares a queue and drafts; sending, retrying, and refunding require separate reviewed actions.
3. Revenue & Close Analyst and Spend & Payables Coordinator have v1 Crew templates with local skills, export-first setup checks, and reviewable first artifacts. Suggest them when accounting or payment access belongs to another person or team. They are optional slots in Finance Operations Review; automated handoff contracts for those slots remain future work.
4. Keep Tax Export Preparer as a supporting pack. Offer Tax Compliance Coordinator, Payroll Review Coordinator, and Cash & Treasury Analyst later as optional specialist roles with distinct access and owner requirements.
5. Finance Operations Review is available as an Automation Playbook proposal when two distinct ready Crews need a handoff. Billing Operations Coordinator produces a source-linked exception queue; Finance Analyst reports its finance impact. The first route has a deterministic queue/readout validator and a manual-run setup check. It does not grant account access or execute a refund. A weekly brief from one Crew stays a Crew schedule.

The catalog should filter on these job families and show the first output, required data, supported provider choices, access level, and setup status. It must distinguish an installable Agent Playbook from a planned role and from a supporting pack.