Built to answer
which variant
paid.
Optimiser.Pro is made by a product-ops team and runs on that team’s own payment funnels. The tools the team paid for reported conversion. The question was revenue.
The team runs a set of payment-led products. Each one takes card payments, and each one has a funnel where a small change moves real money.
The team ran experiments with a testing tool for the split, an analytics tool for the traffic, and a spreadsheet where someone tried to reconcile the two against what the payment processor settled. The testing tool would call a variant a winner on conversion. The settlement would disagree, because the variant that converted better also authorised worse.
Optimiser.Pro closes that gap. It assigns the variant, takes the events, and joins both back to the payment data — authorisation rate, rebill rate, revenue per acquired customer — then runs the significance test and returns a verdict per metric, each judged in its own direction.
One workspace runs on it today. New workspaces are opened by hand.
Three rules
A lift in conversion that authorisation rates, rebills and refunds cancel out is not a win. The verdict is computed on the payment data.
A test that has not cleared its control is shown as still running, not spun as promising. Where the product shows illustrative figures, the page says so. Nothing on this site is a customer result unless it says it is.
Not a suite. No session replay, heatmaps or cohort builder. Assign the split, join it to the payment data, return a verdict.
Workspaces
Tell us what you run and what you want to test. Workspaces are opened by hand. The first step is the request form: your name, work email, company and site. We reply by email.