Twelve years of running experiments, mostly on other people's funnels.
Awasero Digital Solutions Inc. is a Florida corporation, operating since 2016 and based in Miami. It has been a holding company for several ventures over that time. In 2026 the services side relaunched around one thing: conversion rate optimization and web personalization.
The experimentation experience behind it spans agency, in-house, and founder roles: running testing programs for national fitness franchises, a course-and-membership platform, and funnel-software SaaS, plus consulting and execution work for venture, cloud, and workspace companies. Across client experimentation programs at a national performance marketing agency, that work aggregated to roughly a 35% conversion lift.
We describe that history by category rather than by client name, and we publish no client logos. Those programs belong to the companies that ran them. On a call we will go into detail, with the same discretion we would extend to your work.
Why the pivot
The previous version of this company sold AI development and consulting alongside four other service lines. It was a wide offer, and wide offers are hard to be excellent at. The narrower bet is that most conversion agencies are slow for a structural reason, not a talent one: every test is hand-built, so the build queue sets the pace of the entire program.
AI assistance changes that constraint specifically. Research synthesis, variant implementation, and QA compress; strategy and statistical judgment do not, and we do not pretend otherwise. The method page is explicit about which steps are which.
Bilingual, and not as a footnote
Spanish and English, with real LATAM market connections. This matters for one concrete reason: Spanish-language copy tests written in Spanish behave differently from translated English copy tests. LATAM-facing SaaS and FinTech companies are close to unserved by CRO agencies with that fluency, which is a large part of why this practice exists in this shape.
Things we hold to, including when it costs us the engagement.
We will tell you when you are not a fit
Test velocity depends on your conversion volume, not on our effort. Selling a retainer to a funnel that cannot reach significance produces an unhappy client and a story we do not want told about us.
Stopping rules are set before launch
Deciding when to call a test after seeing the data is the fastest way to lose a finance team's trust permanently. We register the criteria up front and hold them.
Losses get reported
A program that only surfaces wins is marketing, not measurement. Losses are how the roadmap gets re-ranked, and hiding them makes every subsequent hypothesis worse.
No number we cannot defend
We do not publish cycle-time averages before we have logged enough cycles to defend one, and we do not publish case study percentages we cannot source. There is a lot of that in this category.
Carlos Ruiz del Vizo
Founder. Bilingual, Caracas by origin and Miami by base, with CRO and performance marketing experience across agency, in-house, and founder roles.
Delivery is founder-led today. As retainer volume grows, contractors come in for implementation, but the strategy, the analysis, and the call on every result stay with the same person through the life of an engagement. That is a real cap on how many clients this practice can hold at once, and it is a deliberate one.
The delivery stack is Claude Code and Cursor for implementation, paired with VWO, Optimizely, or Intellimize depending on what you already run, and GA4 or equivalent for analysis. Awasero also builds its own products on Next.js, Supabase, and Vercel, which is why tests get implemented against real stacks rather than handed over as a specification.
There is a small venture studio attached.
Awasero builds and holds a few of its own products. It is deliberately secondary to the services business, and it is not what we sell you.
Ask the hard questions on the call.
Bring the numbers above and push on them. A practice that cannot defend its own claims has no business auditing yours.