Example workflow: the weekday metrics post, step by step
The Loop wakes it
At 8:00 on weekdays its Loop starts a run on Reason's cloud computer, so it works while your laptop is closed.
It reads Stripe and PostHog
Through their connectors it reads yesterday's charges, subscriptions and invoices, then signups and active users. It changes nothing.
It applies your rules
It drops test and internal accounts and the exclusions in memory, then computes each number and the change since the last report.
It posts and explains
It posts a short table in #metrics, explains the biggest move and lists anything it could not read instead of guessing.
You correct it once
Reply in the thread when a number is wrong; it saves the correction to memory for every later run.
What it does
- Posts a daily or hourly table of revenue, paying customers, signups and active users in a Slack channel.
- Explains a change: which customers, plans or sources moved the number.
- Applies your exclusions every time, such as test accounts, refunds or internal users, because they live in its instructions and memory.
- Answers ad hoc questions in Slack, like "how many trials converted this week?"
A sample week of output
An example of what it posts in a normal week with the Loops from How to set it up. It shows the shape of the output, not real figures.
- Monday 8:00: the table for the weekend, then at 9:00 the weekly summary: last week against the week before, the three biggest moves and the plans or customers behind them.
- Tuesday 8:00: yesterday's table. A teammate asks in the thread how many trials converted last week; it answers from Stripe and says how it counted.
- Wednesday 8:00: yesterday's table, plus a note that it couldn't read one source, listed instead of guessed.
- Thursday 8:00: yesterday's table. You reply that refunds should come out of new revenue, and it saves the rule to memory.
- Friday 8:00: yesterday's table with refunds netted out, as you asked on Thursday, and a line saying the definition changed.
How to set it up
- Instructions sketch: "You report revenue and product metrics. Read Stripe and PostHog only; never create, refund or change anything. Exclude internal and test accounts listed in memory. Show each number with the change since the last report, and say how you computed anything that isn't a raw count."
- Connectors: Stripe for subscriptions, invoices and charges; PostHog for signups and product events; Slack to post. Give each the narrowest read access the connector lets you choose.
- Example Loop: weekdays at 8:00 (cron 0 8 * * 1-5), post yesterday's numbers in #metrics; Mondays at 9:00, a weekly summary.
- Memory: correct a number once ("exclude refunds from new revenue") and it applies the rule on every later run.
What it won't do
- Change billing, refund customers or edit analytics: the job is read-only, and its instructions say so.
- Replace your accountant or audited financials. It reports operating numbers from the tools you connect.
- Guess when data is missing: tell it to say what it couldn't read instead of filling gaps.
Inputs and outputs
- Inputs: Stripe subscriptions, invoices and charges and PostHog events, read through their connectors; your metric definitions and exclusions in its instructions; earlier corrections in memory.
- Outputs: a daily table with the change since last time and a Monday summary in a Slack channel such as #metrics, answers to follow-up questions in the thread, and a note of anything it couldn't read.
Approval points
- Access: connect Stripe and PostHog with the narrowest read access each connector offers.
- Definitions: when a number has no definition yet, such as whether refunds count against new revenue, it asks in the thread instead of choosing; your answer goes into memory.
- Email: if it ever emails the report, each Gmail send shows a preview and waits for your approval. Billing needs no approval, because the job is read-only.
Time saved: a worked estimate
Assumptions, not results: the counts and minutes below illustrate a small team's month; put in your own. The wage is the BLS median hourly wage for financial analysts, May 2025, read on November 2, 2026 ($49.79 an hour, $103,570 a year): wages only, before benefits and payroll taxes. Reason Pro is its list price as of November 2, 2026.
Saved: 20 × 20 minutes + 4 × 50 minutes = 600 minutes = 10 hours a month. Review: 20 × 4 minutes + 4 × 10 minutes = 120 minutes = 2 hours. (10 − 2) hours × $49.79 = $398.32 of time a month, against $50.00 for Reason Pro. Break-even: $50.00 ÷ $49.79 = 1.00 hours a month.
A person still owns the job: the review time above doesn't go away, and the estimate leaves out setup and the first week of corrections.
| Line | Count × minutes | Minutes a month |
|---|---|---|
| Saved: Weekday metrics posts done by hand (assumption) | 20 × 20 | 400 |
| Saved: Monday weekly summaries (assumption) | 4 × 50 | 200 |
| Review: Checking each weekday post (assumption) | 20 × 4 | 80 |
| Review: Reading each Monday summary (assumption) | 4 × 10 | 40 |
| Net time back | 600 − 120 | 480 |
Security and access
- What it can see: only what its connectors return: Stripe charges, subscriptions and invoices, PostHog events, and the Slack channels you add it to. Connect each with the narrowest read access the connector offers.
- What it can change: nothing in Stripe or PostHog. Its instructions keep it read-only; it posts in Slack, and an email report goes out only after you approve the Gmail preview.
- Where credentials live: its connectors sign in once in Customize and act with that account's access. Reason's privacy policy says connection tokens are stored encrypted and secret values are encrypted at rest, and an agent acts only when both the permission you approved and your instruction allow it.
- Who can talk to it: its Slack settings decide the channels it listens in and who can talk to it. Keep revenue in a private channel such as #metrics.
- Revoking: disconnect a service in settings or revoke access with the provider. Disconnecting stops future access but doesn't undo actions already taken.
- Never alone: refunds, discounts, plan changes, and sending numbers outside the company.
- Audit: every run is a Session you can read, and Settings › Audit log lists configuration and access changes.
Build it in 10 minutes in the web app
Everything here happens in the Reason web app at reasonmachines.com; the Mac app works the same way. The minutes are rough, and connecting accounts usually takes longest.
- Minutes 0 to 2, create it: choose New Reason in the sidebar, then open the Reason's Instructions and paste the instructions sketch from How to set it up above, edited for your business.
- Minutes 2 to 4, connect what it needs: in Customize › Connectors, connect Stripe and PostHog with the narrowest read access each offers, and in the Reason's Slack settings add #metrics under Listening in.
- Minutes 4 to 7, do the job once together: ask it in the chat for yesterday's numbers. Check each against Stripe and PostHog, and correct it in the same chat; it saves corrections to memory.
- Minutes 7 to 9, give it a Loop: ask it in the chat: "Every weekday at 8:00, post yesterday's numbers in #metrics, and on Mondays at 9:00 post the weekly summary." It creates the Loop, which then shows under the Reason's Loops, where you can pause or change it.
- Minutes 9 to 10, set approvals: set Who can talk to it to your team, and add a rule in Settings › Policies to ask before any email.
Your first week
- Day 1: build it as above and run the job once together. Write down how long the same post takes you by hand.
- Day 2: turn on the weekday Loop, and check every number against Stripe before anyone else sees it.
- Day 3: answer each definition question it raises, such as refunds, trials and internal accounts; every answer goes into memory.
- Day 4: open #metrics to the team and let them ask follow-up questions in the thread.
- Day 5: compare its week with your own numbers, count the corrections, and add the Monday summary Loop.
How to measure it
Measure it against the time you recorded on day 1. The AI workforce guide works the same method through for a support agent.
- Hours saved after review, per month, against the estimate above.
- Correction rate: posts you had to fix before anyone used them.
- Late or missed posts: weekdays when the 8:00 post didn't arrive.
- Questions answered in the thread without a person looking up the number.
AI revenue analyst alternatives compared
Facts and prices come only from each vendor's own site: as of November 1, 2026 for vendors on our other comparison pages, as of November 2, 2026 for the rest. Units differ, so prices are not directly comparable. We make Reason.
| Tool | Built for | Price | Fits best when |
|---|---|---|---|
| Reason | A Reason that reads Stripe and PostHog on a Loop and explains the numbers in Slack | Pro $50 a month per person; Max $200 a month | You want your own definitions, explanations in Slack and other jobs on one plan |
| ChartMogul | Subscription metrics (MRR, ARR, churn, LTV) from billing systems; Slack updates, API and MCP server | As of November 2, 2026: Free up to $10K MRR; Starter from $69 a month ($57 billed annually), rising with ARR; Pro from $119 ($99); Enterprise from $19,900 a year | You want standard SaaS metrics, benchmarks and forecasts out of the box |
| Baremetrics | Subscription analytics with segmentation, forecasting and email reports | As of November 2, 2026: plan cards show Launch from $75 a month, Growth $255, Scale $1,152; the page's FAQ lists $49, $189 and $749 and up to 35% off yearly | You want a ready-made dashboard plus failed-payment and cancellation add-ons |
| Stripe Sigma | Stripe's own product for analyzing Stripe data with SQL and AI | Not published on its product page | All your revenue data is in Stripe and you want to query it there |
What it costs
In Reason this job shares your plan's usage, with no per-employee fee: Pro is $50 a month per person, Max $200 a month. A more frequent Loop uses more. ChartMogul and Baremetrics price by the revenue they track.
Limits to know
- It reports only what the connectors return; a second billing system means partial totals until you connect or describe it.
- It has no ready-made SaaS benchmarks or forecast models. Write down how you define MRR, churn and active users.
Related AI employee roles
Each role is one Reason with one job. They share your plan's usage, and one can hand work to another in Slack.
Sources
ChartMogul, Baremetrics, Stripe and Stripe Sigma are trademarks of their owners. Reason Machines is not affiliated with or endorsed by them.
Questions
What does an AI revenue analyst do?
It reads billing and product data on a schedule, computes the metrics you care about, such as MRR, new revenue, signups and active users, and reports them with the change since last time and the reason for big moves.
Which tools does it connect to in Reason?
Stripe and PostHog through their connectors, and Slack to post. Reason can also use other data tools that have a connector or an API it can call.
Can it change anything in Stripe?
Set up as described here, no. Its instructions keep it read-only, and you should connect it with the narrowest read access the connector offers.
How often can it report?
As often as its Loop says: every hour, every weekday morning, or on a cron schedule you choose. Each run uses your plan's usage.
How is this different from ChartMogul or Baremetrics?
They are dashboards for subscription metrics with standard definitions and benchmarks. A Reason analyst applies your own definitions, explains changes in Slack and answers follow-up questions.
Can it read from ChartMogul?
ChartMogul's site lists an API and an MCP server, and Reason can use MCP servers you add.
What access does it need?
Read access to Stripe and PostHog, and Slack to post.
Can it email the report?
Yes, through Google Workspace; each Gmail send waits for your approval.
How long does it take to set up an AI revenue analyst?
About 10 minutes in the web app for a first version: create the Reason, paste its instructions, connect Stripe, PostHog and Slack, run the job once and give it a Loop. Plan on a week of corrections before you rely on it alone.
How much time does an AI revenue analyst save?
In our worked estimate, which uses assumptions rather than results, about 8 hours a month after review, worth $398.32 at the BLS median hourly wage for financial analysts (May 2025), against $50.00 for Reason Pro. Your number depends on how long the job takes you today; time it by hand once before you start.
What does it cost?
Reason Pro is $50 a month per person and includes cloud computers, Loops and 1,250 credits of usage a week; Max is $200 a month with four times the weekly usage. Eligible new customers can start Pro with a 3-day free trial. Every AI employee you set up shares your plan's usage; there is no per-employee fee.