Do styling A/B tests work in SaaS / Software?

Better than the SaaS / Software average, though not because the industry helps. Styling tests win 15% there against 9% for all change types in SaaS / Software. Across all industries styling tests run at 15%, so the category is carrying this, not the vertical.

It is the strongest change type we can currently measure in SaaS / Software.

The numbers

	SaaS / Software	all industries
Tests analysed	100+	1,000+
Beat control	15%	15%
No measurable difference	74%	—
Lost to control	11%	—
Median lift when it won	+38.2%	—

Median traffic per variant was 1505 visitors. Most ran on homepages (78), pricing pages (16), lead capture pages (13).

Every change type we can measure in SaaS / Software

change type	win rate in SaaS / Software	tests
Styling (this page)	15%	100+
Split URL	12%	100+
Body copy	9%	33 tests
Headline	6%	100+
CTA copy	2%	50+

The industry overview is at SaaS / Software benchmarks; rates across all industries are on the styling benchmark.

What counts as a styling test

Visual treatment shifts — spacing, weight, borders, colour, shadows — with the same content in the same order. Move the content and it is a layout test. Rewrite it and it is a copy test.

Control and variant wireframe for a styling A/B test — Control on the left, variant on the right. Only the changed element is highlighted.

Styling tests that won in SaaS / Software

Sets a fixed height of 760px on an element, changing its layout size without altering content
Repositions and resizes a fixed floating element on the page without changing any text
Hides paragraph text within list item description blocks and adjusts remaining paragraph font size to 16px
Hides the v1 header button and shows the v2 header button instead

Styling tests that did not

Changes the second link/button's background to yellow and text to black, no wording change
Shows the announcement banner, hides the corner pop-up, and adjusts nav/hero top padding/spacing
Changes font size, color, letter-spacing, and spacing of headline and surrounding text elements without altering wording

These are individual tests, not rules. Each ran on one site, with one audience, against one page we are not showing you. They are picked to be illustrative rather than sampled at random, and a change that won here can lose on your page for reasons none of this captures. Read them as prompts for what to test, not as findings to copy.

Who ran these tests

This is every Mida account that ran a readable test — in-house marketers, founders, product teams, and agencies working on client sites. Nothing here is filtered by who ran the experiment or how experienced they are.

Low win rates are normal in experimentation, including at the top end. Microsoft's experimentation team, reporting on its own platform, found that only about one third of ideas improve the metric they were designed to improve — and that roughly another third actively hurt it. That is a dedicated experimentation organisation with research, prioritisation and review behind every test.

A mixed population like this one runs below that. The gap is roughly what disciplined practice buys you: ideas grounded in research rather than opinion, one variable at a time, and tests built so the result can actually be read.

So treat these as a general base rate, not a target. If you would rather not close that gap the slow way, find a CRO agency in the United States, the United Kingdom, the Netherlands or Australia — or browse every region.

A win is a variant that beat its control on that test's primary goal with a statistically significant result. Tests that never got enough traffic to say anything either way are excluded. The methodology has the full detail, including what these numbers cannot tell you.