Revenue anomaly watch

A daily agent compares charges, refunds, and subscription movement against trailing baselines and explains anything that moves beyond normal bounds — you approve the drafted next step from your inbox.

Join the waitlist

What it installs

Agents 1

  • Revenue Watch Agent

    Owns the daily revenue pulse: baseline comparison, anomaly explanation with a drafted next step, and the anomaly log.

Workflows 1

  • Revenue anomaly watch

    Pull yesterday's billing movement, compare to baselines, write the briefing or all-clear, and sign off the next step.

Documents 1

  • Anomaly log

    The dated record of every daily pulse: baselines, flagged movements, explanations, and how each resolved.

Goals 1

  • Revenue surprises surfaced within a day

    Catch unusual movement in charges, refunds, and subscriptions within one daily cycle, with a usable explanation.

Skills 2

  • revenue-baselines

    Track daily billing movement against trailing same-weekday baselines, split MRR into new, expansion, contraction, and churn instead of blended averages, and judge the split against SaaS health thresholds. Adapted from deanpeters/Product-Manager-Skills/saas-revenue-growth-metrics.

  • anomaly-explanation

    Explain a flagged revenue movement with materiality thresholds that gate the investigation, driver decomposition into volume, price, and mix effects with a narrative per driver, and one reversible drafted next step. Adapted from anthropics/knowledge-work-plugins/variance-analysis.

Schedules 1

  • Daily revenue pulse

    Runs the revenue anomaly watch every morning: pull, compare, brief, sign off.

Connected services pick at least 1 of 4

  • Stripe

    Connects to Stripe so the watch agent can read daily charges, refunds, and subscription creations and cancellations for the baseline comparison.

  • Paddle

    Connects to Paddle so the watch agent can read daily transactions, refunds, and subscription creations and cancellations for the baseline comparison.

  • Polar

    Connects to Polar so the watch agent can read daily orders, refunds, and subscription creations and cancellations for the baseline comparison.

  • PayPal

    Connects to PayPal so the watch agent can read daily transactions, refunds, and subscription creations and cancellations for the baseline comparison.

Folders 1

  • Revenue watch

Requirements

What this playbook expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.

  • Billing data in your payment provider — The agent reads daily charges, refunds, and new and churned subscriptions from the billing provider you pick during setup (Stripe, Paddle, Polar, or PayPal). Until that access is authorized, it works from the daily exports you attach to the run.

Setup guide

How to Monitor Revenue Anomalies

Run a daily revenue pulse that compares billing movement to baselines, explains anomalies, and routes next steps for approval.

Read the setup guide

Install Revenue anomaly watch and run it with approvals.

Join the waitlist and we will send early access when the first private beta spots open.

Private beta. We invite teams in batches and never share your email.