I've been building Velyr because I kept seeing the same problem with conversion rate optimization.
You get an audit.
You get a list of recommendations.
You get a dashboard with 20 things you could improve.
And then... nothing happens.
The developer is busy. The founder has other priorities. The CRO agency sends another report next month.
So I started building an AI CRO agent that actually implements the fixes.
Velyr connects to a Shopify store or a React/Next.js/Vite site through GitHub.
Every week it:
Reads the site's analytics and user behavior
Scans the site to find the biggest conversion problem
Writes the actual code change
Shows you a preview
Waits for your approval
Ships the change
Measures what happened afterwards
For Shopify, the fix goes into the theme. For GitHub projects, it arrives as a Pull Request.
The part I'm particularly interested in is what happens after the change.
Velyr doesn't just say "this should improve conversion."
It measures the result. If the numbers get significantly worse, it proposes a rollback.
The goal isn't to replace a CRO expert.
It's to make continuous conversion optimization practical for a small SaaS, indie hacker, or Shopify store that doesn't have a CRO team.
I'm calling it an AI Growth Agent because that's really what I'm trying to build: something that doesn't just find growth opportunities, but actually does the implementation.
The question I'm still testing:
Would you trust an AI agent to make one conversion-focused change to your website every week if you could preview and approve everything first?
That's what I'm building with Velyr.
I like the distinction between an AI that recommends changes and one that actually closes the loop by implementing and measuring them.
For me, the preview + approval step is important, but I think the bigger trust factor would be the rollback logic. A founder probably doesn't need to trust the AI blindly — they need to trust that the system can fail safely.
I'd be interested in seeing how you define “significantly worse” before triggering a rollback. Conversion rate alone can be noisy, especially with smaller traffic volumes.
The idea becomes much more compelling if the agent can explain not only what it changed, but why it believes the result is statistically meaningful.