Opportunities overview
How Spectry turns an observation about your site into a proposed A/B test you can approve.
AI insights tell you what is happening on your site. Opportunities go one step further: each one is a concrete, specific change to a specific element, packaged as an A/B test that is ready to launch the moment you approve it.
The pipeline
- Observation — analytics, heatmaps, replays and funnels surface something: a CTA nobody clicks, a step everyone abandons, a headline that fails on mobile.
- Proposal — the change is written out: which page, which element, what the variation says, and why it should work.
- Your review — nothing is live yet. You approve, edit or decline.
- Test — approving creates a real A/B test, with the original as control.
- Outcome — the test runs to a result like any other, and the result is fed back against the original claim.
Nothing changes without your approval
This is the design guarantee worth internalising: a proposal is a suggestion sitting in a list. It does not modify your site, does not start a test, and does not affect a single visitor until you approve it.
Proposal states
- Open — waiting for review.
- In review — someone on your team has picked it up.
- Launched — approved; a live A/B test now exists.
- Declined — rejected. Declining teaches the system what you are not interested in.
- Expired — the evidence behind it went stale, or the element it targeted is gone.
- Completed — the resulting test has reached a conclusion.
Opportunities need real traffic behind them. On a site with a few hundred visits a month there is not enough signal to propose anything worth testing, and you will see few or no proposals.