AI Product · Recommendation Systems · Consumer App · Revi
My CEO wanted a fully personalized AI agent across Revi's 2M+ user ecosystem. I scoped the increment that got us to market: a marketing tool partners could activate today, built on the same intelligence, generating revenue while the bigger vision takes shape.
Shipped
Marketing agent — partners activate AI-powered recommendations from their dashboard.
In Build
Commerce tool — calendar + email integration, intent-based virtual assistant.
The Opportunity
Revi's ecosystem spans consumer app, kiosks, and point-of-sale terminals. Behavioral data across the full customer journey from discovery to ordering to repeat visits. Most companies have one slice of that picture. We had all of it.
The question I brought to the executive table wasn't "should we build a recommendation feature." It was: why are we sitting on this and only using it reactively? What if we could proactively surface food, events, and new places before a user even opened the app with clear intention?
How It Started
I was in the executive sessions, alongside the CEO, his CEO coach, the VP of Engineering, and the VP of Product, when the vision took shape: a fully personalized AI agent that could prompt recommendations across Revi's entire network. An idea that could define the company. Also one that could stall indefinitely if you tried to build it all at once.
So I found the increment. Instead of waiting on the full agent, I scoped a marketing tool that used the same recommendation intelligence but lived inside the partner dashboard. Something partners could activate themselves. Something the sales team could sell today. Same data, same AI backbone, but packaged as a product that could ship now and generate revenue while we built toward the bigger vision.
The Deep Work
Working directly with the ML engineer, I helped define an atomic taxonomy of intent types, each mapped to a confidence percentage that it would lead to an order. This wasn't a UX document. It was a design + data architecture problem: what are the smallest-unit signals we can trust, and at what threshold do we surface a recommendation versus stay quiet?
Getting this wrong in either direction has a real cost. False positives create noise and erode trust. False negatives leave revenue and engagement on the table. The intent taxonomy was the core logic that everything else was built on.
The Onboarding Challenge
For intent modeling to work well, the system needs to know the user from the start. Cold-start is the classic hard problem for recommendation engines, and the standard fix (a setup survey) kills activation rates before you even get to a first session.
I prototyped the onboarding in Loveable, designing for haptic feedback and puzzle-like interactions. The goal was to make preference-gathering feel like a playful experience, not a data intake form. Something users would actually complete. Every interaction became a training signal.
Impact
What's Next
The intent taxonomy was an educated starting point. What I want now is the data the marketing tool has been quietly collecting: real signal about which confidence-level recommendations convert, which intent types create friction, where the model's assumptions were wrong. That data shapes an MVP tight enough to ship fast.
AI is moving quickly. There's a version of this product that could be built leaner right now. Calendar and email integration that would have required months of infrastructure a year ago is accessible with modern LLM tooling. I want to close that gap before the moment passes.
The Design
Scroll to explore →