How do you actually go from “we found a problem” to “we fixed it”?

Hey Product Hunt 👋

I’ve been thinking a lot about this while building Spectry.

Most teams already have plenty of ways to find problems on their websites.

• You can see that users are dropping off in a funnel.

• You can watch session recordings.

• You can look at heatmaps.

• You can check rage clicks, errors, Core Web Vitals, surveys, and analytics.

But then what? Someone still has to decide what the problem actually is.

• Then someone has to figure out what to change.

• Then someone has to build it.

• Then someone has to set up an experiment.

• Then someone has to wait for enough data to figure out whether it worked.

That gap between finding an insight and actually doing something about it is what we're trying to solve with Spectry.

Spectry looks at your behavioral data every 12 hours, identifies potential conversion problems, and suggests specific fixes. You can turn those suggestions into A/B tests, approve them, run them on real traffic, and see whether they actually worked.

But we're still figuring out what the right version of this looks like.

So I'm curious:

How do you handle this today?

When your analytics or CRO tools tell you that something is wrong, what happens next?

• Do you have someone dedicated to CRO?

• Does it go into a product or engineering backlog?

• Do you run experiments regularly?

• Or do most insights just end up sitting in a dashboard?

And if you've stopped using a CRO or analytics tool before, what made you cancel it?

I'd genuinely love to hear how other teams handle this.

I'm also happy to run Spectry against your website. Drop your URL below and I'll take a look at what it finds.