51 of the 340 people who got this far clicked Save on the deck editor more than twice in ten seconds. The click registered. Nothing saved, and nothing told them it had failed. Most of them left the page without finishing setup.
Finding it is free.
Closing it is the job.
Growthmind watches real people use your product and tells you where they get stuck, with the recording and the numbers attached. That part costs nothing and always will. What you pay for is everything after: the experiment gets specced, tried first against a simulated version of your customer, dispatched to the coding agent you already use, verified live, measured, and closed with a straight answer.
You are buying experiments
that get finished.
The numbers that change between plans are how many experiments Growthmind can have running at the same time, and how much of your product it is responsible for. It caps experiments anyway, because two of them fighting over the same screen give you an answer you cannot trust.
on one product
- Products
- One
- Where it lives
- Slack, pull requests, and your own MCP
- Every finding arrives with the session recording and the numbers behind it
- Says what it would do about it, and what that should be worth
- Opens a pull request describing the problem, so it lands where you work
- Five simulated runs, to watch it use a flow the way your customer would
- Runs one experiment at a time, closed with a real verdict
on one product
- Products
- One
- Where it lives
- Slack, pull requests, and your own MCP
- $20 of usage included every month, drawn down by sessions read and simulated runs at the per-unit rates
- Every experiment gets a kill criterion and a readout date before it runs
- Simulated first, so an obvious problem is caught before a real user meets it
- Retention too: cohort experiments over long horizons, churn signals caught as they happen
- Guardrails watched overnight, with a kill switch that is one action
- Closes as persist, kill, or inconclusive
- Past the included $20, overage is off by default — it asks first, and only a human can switch it on
across your products
- Products
- As many as you run
- Where it lives
- Everywhere above
- What one product learns, the others inherit
- One ledger of everything tried and everything killed, across the portfolio
- Dead ideas are never proposed again, on any product
- Guest and team access controls, SSO/SCIM, audit exports, named support
- Metered usage exists here too, but only a human can switch it on, and off the same way
- First call on new connectors
Sessions
Two kinds, one word. Read is a real person: Growthmind skims every session cheaply and only reads one properly when the skim says something went wrong. Simulated is one run of a simulation you wrote, executed on our servers instead of your machine, on demand or on a schedule. Those are the only two things counted, because they are the only two that cost us anything. Your replay tool charges you for every session it records. We only charge for the ones we read. Everything else is unlimited: seats, questions, findings, pull requests, verdicts.
| Plan | Sessions read a month | Sessions simulated a month | Experiments at a time |
|---|---|---|---|
| Free | 500 | 5 | 1 |
| $20 | Drawn from the included $20 | Drawn from the included $20 | 3 |
| Custom | As agreed | As agreed | As agreed |
Run it yourself.
It is free.
Point Growthmind at your own model keys and your own infrastructure and none of the cloud numbers apply, because none of the cost is ours. No limit on sessions read, sessions simulated, or experiments. No meter to read. The same product, not a hobbled community edition.
- No limits of any kind. Sessions, experiments and products are yours to set
- Your session data never leaves your infrastructure
- Connectors, guardrails and the statistics library are open source
- You bring: model keys, Postgres, and somewhere to run a container
- Move to cloud later and your history comes with you
- Everything in free self-hosting, under a written licence
- Single sign-on and audit logging
- A named person to call, and an agreed response time
- Help with the first install and the first upgrade
- Air-gapped deployments are fine. Ask.
Your agent writes the simulations.
We run them.
Growthmind publishes a set of skills for whatever coding agent you already use. It reads them and writes your simulations as code, in your repo, reviewed like anything else you ship. None of that touches our servers, so none of it is charged.
Running them is the other half. A simulated customer working through your product for ten minutes would take over the machine you are trying to work on, so we run them on ours, on demand or on a schedule you set. That is the part we count.
You can install the skills, never pay us, and still end up with better simulations than you have today. That is fine. It is how you find out whether the rest is worth $20.
- growth-context: know whether the file you are about to change sits on the path to first value
- growth-events: instrument what you build, in English, tied to the line that emitted it
- growth-experiments: flag key, kill criterion, readout date, and which files never to touch
- growth-simulations: write a customer trying to get something done, as code
- Run any of them locally when you want to, on your own machine and your own bill
Findings are free forever
Not free for fourteen days. If you never pay a penny you still get to see where your product loses people, with the recording attached.
One cost is not ours
Growthmind hands the work to the coding agent you already pay for, so that runs on your token budget rather than a markup of ours. It shows you the estimated cost before it dispatches anything.
Everyone gets a seat
The whole company can read the findings and ask questions. Charging for the second person to care about growth would be a strange way to sell this.
A simulation run is capped
Each run stops at 40 steps or ten minutes, whichever comes first, so one run always costs about the same. If a simulation needs longer than that, it is really an integration test, and you should run it in your own pipeline.
Your simulations are yours
They live in your repo as code you can read. If you leave, you keep them, and they still run on your own machine or on a self-hosted install.
Monthly, and reversible
Cancel in one action, any month. Annual exists if you want it and is never required. The price you sign at is the price you renew at.
Some weeks Growthmind has nothing worth telling you. On those weeks it says so, and it still costs the same. Volume was never the product.
Build a product people use,
then use again