Hypotize wordmark
Start free

For CRO teams

The archive of every test you ran, and the backlog of what to test next

Your A/B testing tool runs the test. Hypotize keeps the programme around it: a backlog of test ideas scored with PIE, ICE or RICE, the stage of every test, and an archive of results, winning variants and learnings that you and your AI agent read before planning the next test.

The problem

Where A/B test learnings end up

From public threads on r/UXResearch and r/GrowthHacking, January to March 2026. Quoted as written and linked to the comment.

“In the product, then in the garbage can.”
u/travoltekAnswering “Where do your A/B test learnings actually live?”
“hypothesis, expected lift, confounding factors at the time, what you decided and why -- that stuff evaporates when the sheet changes.”
u/BP041On what a spreadsheet loses
“If you can’t write baseline + stop rule, it’s not an experiment yet, it’s exploration.”
u/ppatryksOn pre-registering a test before it runs
“We have a system in Airtable. So each A/B test has a specific ID, with tags and extra details about the tests.”
u/xynaxiaOn where A/B test learnings live

The test result usually survives in the testing tool. The hypothesis, the decision and the learning do not. Hypotize keeps those next to the test ID, and refuses to move a test to Ready without a hypothesis and a metric.

How it works

How a CRO team runs it

Hypotize sits around your A/B testing tool, from the first idea to the archived learning.

A scored backlog the whole team votes on
Every idea has a hypothesis, a funnel stage and a score in PIE, ICE, RICE or your own framework. Invite designers, developers and stakeholders with a link: they vote and comment for free, and the priority is computed from the average of the votes.
Pre-registration the server enforces
A test cannot move to Ready without a hypothesis, a success metric, a segment and dates. That holds for your team and for any AI agent writing to the record.
Variants and the winner
Your agent records each variant with a unique key, at most one control, the winning variant and the end date, from your testing tool or when it imports your archive.
Evidence linked to your testing tool
Your agent attaches evidence as URLs, file paths or external IDs, such as the test ID in your A/B testing tool or a Meta study ID, so the next reader can open the source.
No test closes without a learning
Closing a test needs a result (win, lose or neutral) and a written learning that matches it. Inconclusive tests stay in the archive too, with what they taught.
An archive your agent reads first
Before proposing the next test, the agent reads past outcomes with their evidence and learnings, filtered by result or by date, so a losing idea does not come back as new.
Example conversation with a connected agent

  1. You

    Plan the next test on the product page.

  2. Your AI agent

    hypotize_learnings_list

    Three product-page tests closed this year. Moving reviews above the fold won on add-to-cart rate. Two price-anchoring tests were neutral, so I would not test anchoring again yet.

  3. Your AI agent

    hypotize_idea_create

    I added “Show the delivery date next to the price” to the backlog, with a hypothesis, add-to-cart rate as the metric and a PIE score. It can start once it has a segment and dates.

Pricing

What it costs

Free for 1 member and 1 project. Solo is $19.90/month with unlimited projects. Team is $39/month for up to 3 members and $10 for each extra member. Viewers, contributors and AI agents never count as members.

Scope

What Hypotize does not do

Hypotize does not run A/B tests, split traffic, serve variants or calculate significance. Keep your testing tool for that: Hypotize keeps the programme around it, and works with any tool whose test ID you can link.

Start with one project

The Free plan has no time limit. Connect your agent with the MCP server, or install the plugin with the skills.

Start freeConnect your agent