Autonomous product growth engineer
Gradient connects to your site, finds the components costing you conversions — buy buttons, checkout CTAs, pricing cards, forms, paywalls — builds variants, A/B tests them against your original, and keeps only what measurably increased revenue.
No platform fee. You pay from verified incremental revenue.
Watch the loop run
Gradient maps the page, finds where visitors hesitate, builds a variant, tests it against the original, and promotes it only if the revenue holds up.
Who this is for
What you don't have is someone whose whole job is finding where, testing a fix, and proving it worked. That is the role Gradient fills.
Ecommerce, DTC, marketplaces, or self-serve SaaS. Enough visitors that a 2% swing is real money.
A dedicated growth pod runs $300–500K a year. You know the funnel leaks; nobody has the hours to find out where.
You bought an A/B platform and discovered it needed a team to feed it. It has been idle for months.
How it works
The loop does not stop at a report. It ends by picking the next component worth testing and starting again.
Gradient reads your site the way a growth engineer would on their first week — every page, every step, every component that touches money.
Behavioural data shows where people stall. Gradient traces each drop-off back to the exact component causing it, and sizes what fixing it is worth.
Gradient builds real variants of that component, keeps your original running as the control, and splits traffic on a limit you set.
A variant that wins clicks and loses checkouts is a loss. Gradient reads the whole chain, down to refunds and retention.
Winners are promoted. Losers are reverted automatically. Either way the result is stored, so the next test starts from what you already know.
What it actually changes
Gradient rebuilds the component: what appears first, what proof sits next to the decision, how the purchase path is ordered. Your product, your price, and your fulfilment policy never move.
Shipping calculated later.
4.8 sample rating
Before Gradient changes anything, every component on your site is sorted into one of three classes. You set the lines, and it never crosses them.
See how components get classified
The operating mode changes who selects the next experiment. What Gradient is allowed to touch never changes.
Your team chooses the outcome.
Where this goes
Testing one winner for everyone is the starting point, not the end of it. A first-time visitor, a returning customer, and someone comparing prices are not the same person, and should not be pushed through the same static journey. As the evidence base grows, Gradient moves from picking the best single experience to picking the right one per visitor.
Delivery and returns
Fast delivery and a 30-day road trial sit beside the commitment point.
Pricing
No platform fee. No seat licence. No annual commitment. If Gradient doesn't lift revenue, there is nothing to pay.
A slice of your traffic never receives a Gradient change, for the life of the contract. The lift is the gap between the two — a number you can verify in your own analytics.
Not attributed revenue, not influenced revenue. The measured difference against traffic that saw nothing.
Remove the script and every variant reverts to your original. Nothing is baked into your codebase.
The holdback is what makes this checkable.
Performance pricing usually turns into an argument about attribution. A permanent holdback removes the argument: some of your visitors never see a Gradient change, ever. The difference between those two groups is the only number anyone is billed on, and you can measure it yourself.
Exact rate on the call.
Book a callFor agencies and freelancers
You already redesign your clients' checkouts and product pages. Gradient is the part that proves the redesign worked — and keeps improving it after you hand off.
Talk about partneringShip your redesign as a measured variant against the client's original instead of arguing taste in a review call.
The loop keeps running after launch, so there is a reason to stay on the account past delivery.
Performance-based pricing means you are not asking them to approve a new line item before it works.
Before you book
The SDK is a small async script. Variants are decided before first paint so there is no flash of the original, and if the script fails to load the visitor simply sees your existing page.
It is stopped and reverted automatically, without a deploy. Losing variants are the point — they are how the system learns what your customers don't respond to. You are never billed for one.
One script tag to install. After that, approvals are the only thing asked of your team, and only for the component classes you decide need them.
Behavioural events from the pages you connect, plus conversion and order values so revenue can be measured. No personal data is required for the system to work.
Only what you allow. Payment logic, authentication, consent, and legal copy are permanently protected and cannot be experimented on. Pricing and offer changes always require your approval.
Mapping and diagnosis take days. A first result depends on your traffic — enough visitors have to pass through the test for the number to mean anything.
Send us your site and we'll come to the call with the components we think are costing you the most, and what we'd test first. If there's nothing worth testing, we'll tell you that instead.
Book a call