Platform Design · AI Audit · Design Systems · Revi
When your CEO and PMs are shipping product with Loveable at speed, someone has to review every page, untangle what got generated, and make it actually easy to use. That became my role on Revi OS.
AI-generated
Functional. Bloated. Every page styled differently. No clear hierarchy.
After design review
Simplified. Consistent. Clear primary action. Easy to understand.
Revi OS — full platform design audit and remediation
How This Started
Revi OS started as our existing partner dashboard. The CEO and PMs, moving quickly and using AI to do it, began layering in a host of new tools and features built through Loveable. The pace was impressive. The result needed work.
What came out was usable, if you already understood how Revi worked. The AI is good at generating features. It's less good at knowing which features matter most, how to organize them, or how to make the experience feel like one product instead of twenty decisions made in isolation.
The Problem
AI-generated product tends toward the same failure modes: too many features surfaced at once, no hierarchy of importance, styles that drift from page to page, and workflows that make sense to whoever built them but no one else.
Revi OS had all of it. Each page felt like it was built in a separate session with no memory of the last one. CTAs in different positions, labels with inconsistent terminology, pages with so many options that the primary action got buried.
The Work
Reviewed the entire product systematically. Documented every inconsistency: mismatched components, redundant features, navigation patterns that contradicted each other, pages that had grown without any clear design direction.
The instinct with AI-built product is to patch problems by adding new layers. I did the opposite: removed features that duplicated others, merged redundant pages, and cut options that weren't being used. Less surface area, clearer purpose per screen.
Rebuilt component usage so every page followed the same rules: same CTA position, same label patterns, same hierarchy of primary vs. secondary actions. Partners shouldn't have to relearn how the product works on every screen.
Re-mapped the critical partner workflows (setup, menu management, reporting) to ensure they had a clear beginning, middle, and end. AI tends to optimize for completing a task. I made sure the experience of getting there was also clear.
Honest Reflection
My role has shifted a lot. Sometimes I'm building from scratch, sometimes I'm PM, sometimes I'm reviewing code. Revi OS pushed me into a different kind of design work: less creator, more editor and quality controller. I came to appreciate that.
What I'm most proud of isn't any single fix. It's my ability to keep finding the thread in genuinely ambiguous situations. The AI can ship fast. I'm the person who makes sure what ships is actually easy. It's a different skill set than starting from a blank canvas, and one I've grown into.
Impact