What we read
MRR, new customers and churn, refreshed every twenty-eight days.
What changes in your plan
Shipped plays are measured against money, not activity, so wins are hard to fake and retention work gets ranked against real churn.
- Plays sized by what they should add to MRR each month
- Retention and churn plays ranked when churn is the real constraint
- Pricing and packaging plays grounded in your actual average revenue
- A before-and-after read on every play you ship
How to connect
Paste a restricted Stripe key in Integrations. Read-only.
What we never do
A restricted key means no charges, no refunds, no writes of any kind. We do not need or store customer names, emails or card data.
Connecting it, step by step
Create a restricted key with read access only
A restricted key gives the plan the numbers without giving anything the ability to move money.
- In Stripe, create a restricted API key
- Grant read access to charges, customers and subscriptions; leave everything else off
- Paste the key into Integrations in your workspace
- Refresh your plan — plays are now scored against revenue
- Effort
- Three minutes
- Payoff
- Every play sized in money before you start it
Before you start
Can it move money or issue refunds?
No. A restricted read-only key cannot create charges, refunds or any other write.
Do you store customer details?
No. We keep aggregate figures — revenue, counts and churn — not customer records.
How often does it refresh?
Every twenty-eight days, and whenever you refresh your plan.
Do I have to connect anything?
No. Every play still spells out the steps by hand. Connecting just makes the ranking sharper.
Can I disconnect later?
Yes, from Integrations, and we stop reading immediately.
See your own ranked plan
