Release check · pilot
Know what your release broke, for every kind of customer, before they do.
On every release, test shoppers work through the journeys that make you money: find a product, choose, add to bag, reach payment, sign up. Each one uses your store the way a real kind of customer does, with that customer's limits.
Sign-up opens shortly.
Three test customers
Who tries your journeys.
| Who | What it catches | Status |
|---|---|---|
| The shopper on a phone | Sees the screen and taps. Catches dead buttons, rejected inputs, pop-ups that swallow taps, prices that vanish. | Pilot |
| Keyboard and screen-reader path | Uses only the keyboard and what a screen reader would announce. Catches unnamed buttons, focus traps, unlabelled fields. | Pilot |
| AI shopping agent | Reads the page the way agents do, from text and labels. Catches prices drawn as images, delivery facts only in pictures, press-and-hold buttons. | Pilot |
On every release
What you get.
- A result per journey and per customer type: blocker found, friction found, or none found on this run Pilot
- The exact element, a screenshot and the change to make, per blocker Pilot
- A fix, a re-check, then real visitors confirm Pilot
- Your coding agent gets the fixes Building
- Runs start on each release automatically Pilot
- Results in your dashboard, release by release Pilot
What we promise, and what we don't
We report blockers found. Nothing more.
- Test shoppers stop before payment and never place real orders Pilot
- Test shoppers are kept out of your analytics and ad numbers Pilot
- We never change your store; your developer, agency or coding agent makes each change Pilot
- We never say your store “works” or is “accessible”. A run can miss things; an audit and real people with disabilities stay the final word.
Price and pilot
For stores that ship every week or two, and their agencies.
Price on request
Price on request
In the pilot, our team runs the checks with you while the automation is built. Shopify first.