Stripe reports, one for each reader

Stop building the Monday report.

Monday, 9am. The board wants one page. Support wants the failed payments. Your CFO wants retention. Today someone builds all three by hand. SaasReport builds each one from your Stripe data, in the order that reader cares about, and sends it on a schedule.

  • Every figure computed by code
  • AI writes sentences, never numbers
  • Signed links that expire
See a report built

Pre-launch. Be one of the first companies we build this for.

Board pack, sample month
ReportSaasReport
Sample data
  1. 1Stripe data comes inPlanned
  2. 2The engine computes the figuresPlanned
  3. 3Rules write the findingsPlanned
  4. 4Sentences are checkedPlanned
  5. 5A signed link is sentPlanned
10readers
9report types
30defined metrics

Written for

CEO / FounderCFO / Finance leadBoardInvestorsSalesMarketingCustomer successRefunds and returnsTech supportMarketplace / platform operator

The problem

The same month. Ten different questions.

1

Monday, 9am

The board wants one page. Support wants the failed payments. The CFO wants retention. Someone opens Stripe and starts three exports.

2

The sheet nobody trusts

Numbers get pasted, filtered and renamed on the way. Two people pull the same month and get two answers.

3

One view for everyone

The Stripe Dashboard is built for the person who runs Stripe. Everyone else asks that person for a screenshot.

How it will work

One set of numbers. One report per reader.

Install the app in Stripe.

SaasReport asks for read access only. It never moves money and never changes your account.

For exampleIt reads subscriptions, charges, refunds, disputes and application fees.

You getRead-only access

Pick who gets what.

Choose a reader, a report and a schedule. Each report says which schedules it supports.

For exampleCEO / Founder: Recurring revenue health, weekly, monthly, quarterly, annual. CFO / Finance lead: Recurring revenue health, weekly, monthly, quarterly, annual

You getA readerA reportA schedule

Code computes every number.

Each figure follows a published definition. Rules turn the figures into findings, with the evidence beside them. AI words the summary and never writes a figure.

For exampleNet revenue retention was 81.08%: existing customers brought in less revenue than they did at the start of the period.

You getFiguresFindingsChecked sentences

Each reader gets a link.

The email names the report and carries no figures. The link is signed, it expires, and you can revoke it.

For exampleThe report is a PDF stored under your own tenant.

You getSigned linkExpiresRevocable

Start with the person

Pick who is asking.

Who asks

Engine on sample data
CEO / Founder

Is recurring revenue growing, and is the growth healthy? Where is revenue leaking?

Sees

  • Monthly recurring revenue: USD 3,783.92
  • Net new MRR: USD 100.00
  • Net revenue retention: 81.08%
  • Churned MRR: USD 897.00
  • Annual recurring revenue: USD 45,407.04
  • Refund rate: 6.83%

Does

  • Report: Recurring revenue health, weekly, monthly, quarterly, annual
  • Report: Retention and churn, monthly, quarterly, annual
  • Report: Board pack, monthly, quarterly
  • Finding (act): Churned MRR of USD 897.00 was larger than new MRR in the same period.
  • Finding (watch): Net revenue retention was 81.08%: existing customers brought in less revenue than they did at the start of the period.
  • Finding (watch): The refund rate rose to 6.83% from 3.90%.
  • Finding (info): Net new MRR was USD 100.00: more recurring revenue arrived than left.
  • Stripe cannot tell them: profit, cash in the bank, burn and runway
CFO / Finance lead

What is the recurring revenue base and how did it move this period? How much of it is retained? How much leaks through refunds and disputes?

Sees

  • Monthly recurring revenue: USD 3,783.92
  • Annual recurring revenue: USD 45,407.04
  • Net new MRR: USD 100.00
  • Gross revenue retention: 72.94%
  • Net payment volume: USD 8,452.00
  • Refunded amount: USD 620.00
  • Disputed amount: USD 422.00
  • Churned MRR: USD 897.00
  • Contraction MRR: USD 100.00

Does

  • Report: Recurring revenue health, weekly, monthly, quarterly, annual
  • Report: Sales performance, weekly, monthly, quarterly
  • Report: Refunds and returns, daily, weekly, monthly
  • Report: Payment health, daily, weekly, monthly
  • Finding (act): Churned MRR of USD 897.00 was larger than new MRR in the same period.
  • Finding (act): Refunds issued as fraudulent this period: 1.
  • Finding (act): Disputes opened rose 50.00% to 3, from 2.
  • Finding (watch): Net revenue retention was 81.08%: existing customers brought in less revenue than they did at the start of the period.
  • Finding (watch): The payment failure rate rose to 11.67% from 6.00%.
  • Finding (watch): The refund rate rose to 6.83% from 3.90%.
  • Finding (info): Net new MRR was USD 100.00: more recurring revenue arrived than left.
  • Stripe cannot tell them: costs and expenses, profit and loss, cash balance outside Stripe
Board

Is the business on track? What changed since the last meeting?

Sees

  • Annual recurring revenue: USD 45,407.04
  • Net new MRR: USD 100.00
  • Net revenue retention: 81.08%
  • Gross revenue retention: 72.94%
  • Logo churn rate: 25.00%
  • Dispute rate: 5.66%

Does

  • Report: Recurring revenue health, weekly, monthly, quarterly, annual
  • Report: Retention and churn, monthly, quarterly, annual
  • Report: Board pack, monthly, quarterly
  • Report: Investor quarterly, quarterly, annual
  • Finding (act): Churned MRR of USD 897.00 was larger than new MRR in the same period.
  • Finding (act): Disputes opened rose 50.00% to 3, from 2.
  • Finding (watch): Net revenue retention was 81.08%: existing customers brought in less revenue than they did at the start of the period.
  • Finding (info): Net new MRR was USD 100.00: more recurring revenue arrived than left.
  • Stripe cannot tell them: burn and runway, headcount, pipeline
Investors

How efficient and durable is the revenue growth?

Sees

  • Annual recurring revenue: USD 45,407.04
  • Net revenue retention: 81.08%
  • Gross revenue retention: 72.94%
  • Net new MRR: USD 100.00
  • New MRR: USD 698.00
  • Expansion MRR: USD 300.00

Does

  • Report: Recurring revenue health, weekly, monthly, quarterly, annual
  • Report: Sales performance, weekly, monthly, quarterly
  • Report: Board pack, monthly, quarterly
  • Report: Investor quarterly, quarterly, annual
  • Finding (act): Churned MRR of USD 897.00 was larger than new MRR in the same period.
  • Finding (watch): Net revenue retention was 81.08%: existing customers brought in less revenue than they did at the start of the period.
  • Finding (info): Net new MRR was USD 100.00: more recurring revenue arrived than left.
  • Stripe cannot tell them: customer acquisition cost, burn multiple, benchmarks against other companies
Sales

How much new and expansion revenue did we add? How big is a typical deal?

Sees

  • New MRR: USD 698.00
  • Expansion MRR: USD 300.00
  • New customers: 2
  • Net new MRR: USD 100.00
  • Average order value: USD 171.17
  • Average revenue per account: USD 315.33

Does

  • Report: Sales performance, weekly, monthly, quarterly
  • Report: New customers, weekly, monthly, quarterly
  • Finding (act): Churned MRR of USD 897.00 was larger than new MRR in the same period.
  • Finding (info): Net new MRR was USD 100.00: more recurring revenue arrived than left.
  • Stripe cannot tell them: pipeline, quota attainment, win rate, sales cycle length
Marketing

How many new paying customers arrived, and how much revenue do they bring?

Sees

  • New customers: 2
  • New MRR: USD 698.00
  • Average revenue per account: USD 315.33
  • Average order value: USD 171.17
  • Gross payment volume: USD 9,072.00

Does

  • Report: New customers, weekly, monthly, quarterly
  • No finding fires for them on this sample month.
  • Stripe cannot tell them: marketing spend, channel attribution, customer acquisition cost, leads and funnel stages
Customer success

Which parts of the base are shrinking or leaving? Are payment failures putting customers at risk?

Sees

  • Logo churn rate: 25.00%
  • Churned MRR: USD 897.00
  • Contraction MRR: USD 100.00
  • Gross revenue retention: 72.94%
  • Net revenue retention: 81.08%
  • Payment failure rate: 11.67%

Does

  • Report: Retention and churn, monthly, quarterly, annual
  • Report: Payment health, daily, weekly, monthly
  • Finding (act): Churned MRR of USD 897.00 was larger than new MRR in the same period.
  • Finding (watch): Net revenue retention was 81.08%: existing customers brought in less revenue than they did at the start of the period.
  • Finding (watch): The payment failure rate rose to 11.67% from 6.00%.
  • Stripe cannot tell them: product usage, health scores, support satisfaction
Refunds and returns

How much are we refunding, and why? Is the refund rate rising?

Sees

  • Refunded amount: USD 620.00
  • Refund rate: 6.83%
  • Refunds: 5
  • Refunds requested by the customer: 3
  • Refunds for duplicate charges: 1
  • Refunds for fraud: 1
  • Disputes: 3

Does

  • Report: Refunds and returns, daily, weekly, monthly
  • Finding (act): Refunds issued as fraudulent this period: 1.
  • Finding (act): Disputes opened rose 50.00% to 3, from 2.
  • Finding (watch): The refund rate rose to 6.83% from 3.90%.
  • Finding (watch): Refunds for duplicate charges this period: 1.
  • Stripe cannot tell them: returned goods and inventory, product-level return reasons, shipping
Tech support

How many payments are failing, and is it getting worse? How many disputes need a response?

Sees

  • Payment failure rate: 11.67%
  • Failed payments: 7
  • Disputes: 3
  • Dispute rate: 5.66%
  • Refunds for duplicate charges: 1

Does

  • Report: Payment health, daily, weekly, monthly
  • Finding (act): Refunds issued as fraudulent this period: 1.
  • Finding (act): Disputes opened rose 50.00% to 3, from 2.
  • Finding (watch): The payment failure rate rose to 11.67% from 6.00%.
  • Finding (watch): Refunds for duplicate charges this period: 1.
  • Stripe cannot tell them: tickets and response times, error logs, product incidents
Marketplace / platform operator

What does the platform earn on the volume that flows through it? Is the take rate holding? Are disputes and refunds on the platform's payments under control?

Sees

  • Platform fees (net): USD 263.97
  • Take rate: 9.00%
  • Gross payment volume: USD 9,072.00
  • Dispute rate: 5.66%
  • Refund rate: 6.83%
  • Payment failure rate: 11.67%

Does

  • Report: Marketplace health, weekly, monthly, quarterly
  • Finding (act): Disputes opened rose 50.00% to 3, from 2.
  • Finding (watch): The payment failure rate rose to 11.67% from 6.00%.
  • Finding (watch): The refund rate rose to 6.83% from 3.90%.
  • Finding (watch): Net platform fees fell 0.76% to USD 263.97, from USD 266.00.
  • Finding (watch): The take rate fell to 9.00%, from 10.00%.
  • Stripe cannot tell them: seller-side revenue of connected accounts (not readable from the platform's install), listing quality and supply health, buyer and seller acquisition cost

Want this for the people who ask you?

One report, three readers

Same data. The order follows the reader.

Open the same report as three different readers.

Engine on sample data
Board pack: BoardBoard
Where we stand: Annual recurring revenue
USD 45,407.04
Where we stand: Monthly recurring revenue
USD 3,783.92
How revenue moved: Net new MRR
USD 100.00
How revenue moved: New MRR
USD 698.00
How revenue moved: Reactivation MRR
USD 99.00
How revenue moved: Expansion MRR
USD 300.00
How revenue moved: Contraction MRR
USD 100.00
How revenue moved: Churned MRR
USD 897.00
How much we kept: Net revenue retention
81.08%
How much we kept: Gross revenue retention
72.94%
How much we kept: Logo churn rate
25.00%
Payment risk: Dispute rate
5.66%
Payment risk: Refund rate
6.83%
Who pays: Average revenue per account
USD 315.33
Board pack: CEO / FounderCEO / Founder
Where we stand: Monthly recurring revenue
USD 3,783.92
Where we stand: Annual recurring revenue
USD 45,407.04
How revenue moved: Net new MRR
USD 100.00
How revenue moved: Churned MRR
USD 897.00
How revenue moved: New MRR
USD 698.00
How revenue moved: Reactivation MRR
USD 99.00
How revenue moved: Expansion MRR
USD 300.00
How revenue moved: Contraction MRR
USD 100.00
How much we kept: Net revenue retention
81.08%
How much we kept: Gross revenue retention
72.94%
How much we kept: Logo churn rate
25.00%
Payment risk: Refund rate
6.83%
Payment risk: Dispute rate
5.66%
Who pays: Average revenue per account
USD 315.33
Board pack: InvestorsInvestors
Where we stand: Annual recurring revenue
USD 45,407.04
Where we stand: Monthly recurring revenue
USD 3,783.92
How much we kept: Net revenue retention
81.08%
How much we kept: Gross revenue retention
72.94%
How much we kept: Logo churn rate
25.00%
How revenue moved: Net new MRR
USD 100.00
How revenue moved: New MRR
USD 698.00
How revenue moved: Expansion MRR
USD 300.00
How revenue moved: Reactivation MRR
USD 99.00
How revenue moved: Contraction MRR
USD 100.00
How revenue moved: Churned MRR
USD 897.00
Who pays: Average revenue per account
USD 315.33
Payment risk: Refund rate
6.83%
Payment risk: Dispute rate
5.66%

Findings, not opinions

Every finding names its evidence.

Every rule that fires on the sample month, most urgent first.

Engine on sample data
  1. SaasReport

    Churned MRR of USD 897.00 was larger than new MRR in the same period.

    Compare what was added with what was lost this period and decide whether acquisition or retention needs attention first.

    • Churned MRR: USD 897.00 (before: USD 299.00)
    • New MRR: USD 698.00 (before: USD 498.00)
  2. SaasReport

    Refunds issued as fraudulent this period: 1.

    Review the payments refunded as fraudulent and check whether your fraud rules, for example in Stripe Radar, need tightening.

    • Refunds for fraud: 1 (before: 0)
  3. SaasReport

    Disputes opened rose 50.00% to 3, from 2.

    Open the disputes that still need a response in the Stripe Dashboard and submit evidence before each deadline.

    • Disputes: 3 (before: 2)
    • Dispute rate: 5.66% (before: 4.26%)
    • Disputed amount: USD 422.00 (before: USD 223.00)
  4. SaasReport

    Net revenue retention was 81.08%: existing customers brought in less revenue than they did at the start of the period.

    Look at the customers behind churned and contraction revenue and note the likely cause of each (price, fit, a failed payment, or a change on their side).

    • Net revenue retention: 81.08% (before: 92.72%)
  5. SaasReport

    The payment failure rate rose to 11.67% from 6.00%.

    Check how failed subscription payments are retried and how customers are told about them, in your Stripe Billing settings.

    • Payment failure rate: 11.67% (before: 6.00%)
    • Failed payments: 7 (before: 3)
  6. SaasReport

    The refund rate rose to 6.83% from 3.90%.

    Read a sample of this period's refunds, group them by reason, and act on the largest group first.

    • Refund rate: 6.83% (before: 3.90%)
    • Refunded amount: USD 620.00 (before: USD 322.00)
    • Refunds: 5 (before: 3)
  7. SaasReport

    Refunds for duplicate charges this period: 1.

    Check how checkout or your integration could create the same charge twice, for example double submits or retries without an idempotency key.

    • Refunds for duplicate charges: 1 (before: 0)
  8. SaasReport

    Net platform fees fell 0.76% to USD 263.97, from USD 266.00.

    Check whether fee settings, pricing tiers or the mix of sellers and categories changed during the period, and compare the fee earned per payment against the prior period.

    • Platform fees (net): USD 263.97 (before: USD 266.00)
  9. SaasReport

    The take rate fell to 9.00%, from 10.00%.

    Check whether fee settings, pricing tiers or the mix of sellers and categories changed during the period, and compare the fee earned per payment against the prior period.

    • Take rate: 9.00% (before: 10.00%)
    • Platform fees (net): USD 263.97 (before: USD 266.00)
    • Gross payment volume: USD 9,072.00 (before: USD 8,253.00)
  10. SaasReport

    Net new MRR was USD 100.00: more recurring revenue arrived than left.

    Note what drove the gain (new, expansion or fewer losses) so it can be repeated.

    • Net new MRR: USD 100.00 (before: USD 248.00)
    • New MRR: USD 698.00 (before: USD 498.00)
    • Churned MRR: USD 897.00 (before: USD 299.00)

Dashboard or report?

The Dashboard shows everything. A report says what matters to you.

The questionA SaasReport reportStripe Dashboard
Who it is forEach reader: CEO, CFO, board, investors, sales, marketing, success, refunds, support, platform operators.The person who runs Stripe.
What you see firstThat reader's priority figures, in that reader's order.Every payment, customer and subscription.
When it arrivesOn a schedule: daily, weekly, monthly, quarterly or yearly, as the report allows.When you open it.
What it says about a changeThe figures, and a finding that names its evidence.The figures.
Who can read itReaders you choose, by a signed link that expires.People with a Stripe login.

What it costs you today

How long does the Monday report take?

Reporting by hand, on your inputs.

Sample
Inputs
Results

Hours spent each month 12.0 hours

Cost each month 600 your currency

Cost each year 7,200 your currency

Seen the number? Let us build the reports instead.

Who it is for

If you take payments through Stripe, one of these is you.

Subscription businesses

Recurring revenue, retention and churn for the CEO, CFO, board and investors, plus new customers for sales and marketing. Reports: Recurring revenue health, Retention and churn, Sales performance, New customers, Board pack and Investor quarterly. Needs Stripe Billing subscriptions.

Merchants without subscriptions

Payments, refunds and disputes for finance and support. Reports: Refunds and returns and Payment health. They read charges, refunds and disputes only, so no subscriptions are needed.

Marketplaces and platforms

What the platform earns, and how its refunds and disputes behave. Report: Marketplace health. Stripe lets an app on a platform read only the platform's own data. Your merchants install SaasReport on their own accounts, and you can recommend it. That is a referral, not a data feed.

How a report reaches a person

A signed link, not an attachment.

The path of one report. Every stage is planned.

Sample
  1. Stripe sends the data

    SaasReport

    Charges, refunds, disputes and subscriptions arrive through the Stripe app, and are stored under your tenant only.

  2. Code computes the figures

    SaasReport

    A deterministic engine turns the data into integers under published definitions.

  3. Rules write the findings

    SaasReport

    Published rules read the figures and state what changed, with the evidence.

  4. AI words the summary

    SaasReport

    The AI sees aggregates only. A number guard rejects any number the engine did not compute.

  5. The PDF is stored

    SaasReport

    The report is saved under your tenant's own prefix.

  6. A signed link is emailed

    SaasReport

    The reader gets a link that expires. The email carries no figures.

The five cadences and the period each one covers.

Engine on sample data

As of October 28, 2026

  1. Annual: covers 2025 (2025-01-01 to 2025-12-31)

    The schedule

  2. Monthly: covers 2026-09 (2026-09-01 to 2026-09-30)

    The schedule

  3. Quarterly: covers 2026-Q3 (2026-07-01 to 2026-09-30)

    The schedule

  4. Weekly: covers 2026-W43 (2026-10-19 to 2026-10-25)

    The schedule

  5. Daily: covers 2026-10-27 (2026-10-27 to 2026-10-27)

    The schedule

Security and trust

What we promise, and where each promise stands.

1

Planned

The Stripe App requests only read permissions and never creates, changes or deletes anything in the customer's Stripe account, and never moves money.

2

Planned

SaasReport does not receive, store or process card numbers or bank account numbers.

3

Planned

Each customer's data is stored and read only under that customer's own tenant identifier; one customer cannot read another's data.

4

Planned

Every figure in a report is computed by deterministic code from Stripe data under published definitions; AI-written text is checked so that it contains no figure the code did not compute.

5

Planned

The AI provider receives only computed aggregates and never customer names, email addresses or other personal data from the customer's Stripe account.

6

Planned

After the customer uninstalls the app, the data derived from their Stripe account is deleted within the period stated in the privacy policy.

7

Planned

Report emails are sent only through SaasReport's own mail service on Cloudflare, and each carries the legal footer.

8

Planned

The website sets no cookies other than those strictly necessary, and runs no third-party advertising or tracking scripts.

9

Planned

SaasReport does not sell personal data, and does not use a customer's Stripe data to train AI models or to build benchmarks for other customers.

10

Planned

All traffic between Stripe, SaasReport's services, and report recipients' links uses encryption in transit.

11

Planned

Findings and recommendations in a report come from published rules applied to computed figures, not from AI judgement; each cites the figures that triggered it, and the thresholds are not benchmarks against other companies.

12

Planned

Reports are delivered as signed, expiring links to files stored under the customer's own tenant, and a link can be revoked.

Pick a group of Stripe roles to see which reports they could read.

Engine on sample data
Super Administrator, Administrator and 5 more

Super Administrator, Administrator, Developer, Analyst, View Only, Accountant, Tax Analyst

Sees

  • Recurring revenue health
  • Retention and churn
  • Sales performance
  • New customers
  • Board pack
  • Investor quarterly
  • Refunds and returns
  • Payment health
  • Marketplace health

Does

  • A person opens SaasReport. We read their Stripe roles and offer only the reports those roles can see.
Refund Analyst, Support Associate, Support Specialist

Refund Analyst, Support Associate, Support Specialist

Sees

  • Refunds and returns
  • Payment health

Does

  • A person opens SaasReport. We read their Stripe roles and offer only the reports those roles can see.
Dispute Analyst, Transfer Analyst

Dispute Analyst, Transfer Analyst

Sees

  • Payment health

Does

  • A person opens SaasReport. We read their Stripe roles and offer only the reports those roles can see.
IAM Administrator, Support Communications and 11 more

IAM Administrator, Support Communications, Terminal Specialist, Data Migration Specialist, Connect Onboarding Analyst, Connect Risk Analyst, Sandbox Admin, Sandbox User, Identity Analyst, Identity View Only, Top-up Specialist, Financial Connections Specialist, Data Engineer

Sees

  • No report: this role cannot see financial data.

Does

  • A person opens SaasReport. We read their Stripe roles and offer only the reports those roles can see.

Run two drafted sentences through the guard.

Engine on sample data

Net revenue retention came in at 81.08%, a little under full retention.

Allowed Passed every stage every number was computed by the engine

Only a sentence that passed.

  1. Computes the figures

    Engine

    Integers from your Stripe data.

  2. Drafts a sentence

    AI

    It sees aggregates only.

  3. Checks every number

    Number guard

    Each number must be one the engine computed.

  4. Sentence enters the report

    Report

    Only a sentence that passed.

Questions

Straight answers.

Can I use it today?

Not yet. The engine that computes the numbers is built and tested. The Stripe app, the report pages and the email delivery are not. Ask for early access and we will tell you when we start building for you.

Is my data safe?

Nothing is stored yet, because nothing is built. The design is: read-only access, data kept under your own tenant identifier, encryption in transit, and no use of your data to train AI. Each promise is a commitment in the register above with its status.

Who sees what?

A person sees a report only if their Stripe role already lets them see the data behind it. A role we do not know sees nothing. Try it in the Trust section.

Will AI make numbers up?

It cannot. Code computes every figure. The AI is meant to write only the sentences around them, and a guard rejects any sentence that holds a number the engine did not compute. The guard exists in code. Try it in the Trust section.

What does it read?

Only what the reports need: subscriptions, charges, refunds, disputes and application fees. It reads nothing today.

What does it cost?

We have not set prices. Early-access companies help us decide what is fair.

When can I use it?

There is no date. We will not invent one. Early access is how we choose what to build first.

What can it not tell me?

Anything Stripe does not hold. Across the readers above that includes profit, cash in the bank, burn and runway, costs and expenses, profit and loss, cash balance outside Stripe, headcount and pipeline. SaasReport will not pretend to know them.

I run a marketplace. Can I see my merchants' numbers?

Not through SaasReport. Stripe lets an app installed by a platform read only the platform's own data. Merchants can install SaasReport on their own accounts, and you can recommend it.

Is it in the Stripe App Marketplace?

No. It is not listed there.

Who is behind it?

SaasReport. The legal entity is not set up on paper yet: legal name, registration number, country of incorporation, governing law and courts are not set.

Early access

Be one of the first companies we build this for.

Tell us who asks about your Stripe numbers and which report each would read. We will use your answer to decide what to build first.

No card, no commitment. It is a form: we write back.