Free
Start collecting why they pay and why they don't — free.
$0Free
Try the demoIncludes
- 1 seat
- Unlimited projects and signals
- 30-day history
- Public board
- Track one paying baseline
- BYOK on every plan
Pay for the closed loop, not more pageviews.
Start free. Upgrade when you need private evidence, deploy verification, and clear ownership across a team.
Installed on live checkout sites
The same one-question card is already on six paying walls. Seats stay a score, not a cut of their checkout.
Checking secure checkout…
Most popular
Pro
For teams that live in conversion work.
$20/mo
Try the demoNot a checkout. Open the homepage demo first.
Includes
- 3 seats included
- Unlimited projects and signals
- 1-year history
- Private boards
- Custom domain
- Paying scoreboard
- Extra seats · $5/mo or $60/yr
Team
Roles and access for the whole product team.
$50/mo
Try the demoNot a checkout. Open the homepage demo first.
Includes
- 10 seats included
- Everything in Pro
- Roles and permissions
- Per-project access
- Paying-amount comparison across projects
- Extra seats · $5/mo or $60/yr
Lifetime judgment export
One-time. Keep the weekly judgment and CSV export without a seat.
$29
Try the demoWhat the paid plan unlocks
Free proves the loop. Pro turns blockers into private, ranked revenue work and keeps the evidence through the 7/14/30-day measurement window. Team adds ownership across products. End users who answer are never seats, and MorePaying never takes a cut of lift.
FAQ
How is this different from analytics?
Analytics tells you where users came from and where they dropped. MorePaying joins the paywall objection to usage, channel, money, the shipped SHA, and the paid result after release.
Do I send MorePaying a Stripe secret?
No. Keep the secret on your server. Sync only the customer identifiers, statuses, and amounts needed for the paying baseline and lift check.
Are people who answer counted as seats?
No. Seats are teammates who use the workspace. End users who answer the in-product question are unlimited.
What counts as verified lift?
A new customer identifier that was not in the locked baseline counts as a new conversion. Renewals and upgrades stay separate. The release SHA keeps the result traceable.
Why keep a 7, 14, and 30-day window?
A deployment is not a result. The windows make fast signals visible while preventing one good day from being mistaken for a durable conversion improvement.