Shaping the Product roadmap by building AI-driven MVP in 3 days with Claude Code
Macabacus is a productivity tool for finance and banking.
Brand Kit is a self-serve tool that lets Investment Bankers define their organization's brand assets letting them generate on-brand presentations in seconds.
I built a working MVP in 3 days with Claude, which got the feature added to the product roadmap, then I moved it through design and development using Claude Code and Figma.
April — June 2026
/ my role
I turned an open suggestion from our Head of Product into a working Brand Kit MVP in 3 days, building it directly in Claude, which led to the feature being added to the product team's roadmap.
I owned the V1 scope moving the work through prototyping, Figma design, and development, using Claude Code with a Figma MCP connector while collaborating closely with the PM and Chief Product Officer on design direction and with engineering on implementation.
/ team
Sr. Product Designers (me!)
Product Manager
Backend Engineer
/ my Responsibilities
UI Design
Build with AI-assisted workflow
Design systems
/ Stack
Claude Code
Figma MCP
Figma Design
/ timeline
3 days in April 2026
/ the problem
Investment bankers lose hours reformatting slide decks to match a company's brand
Our Head of Product had a hunch there was a tool here: what if an admin could define a brand once, and every deck came out on-brand automatically? He handed it to me as an open question: see how far you can take this in one to three days.
/ chapter 1
Building MVP in 3 days using Claude
/ what I built in 3 days
Instead of mocking screens, I built a working tool the team could actually click
MVP made in 3 days: Managing colors and fonts in the brand kit
/ how I worked
I worked in a fast loop between Claude & Figma
This project changed how I work. I used to design in Figma and hand it off to engineering.
But now for the first time, I could push working code to staging myself.
Feeding my Figma frames to Claude Code through MCP, I turned designs into reviewable, staged code myself, which collapsed the design-to-dev gap from days into hours.
Me + PM
Figma
Used design components as references for the Claude Code.
Me + Engineering
Claude Code + Figma MCP
Built a clickable MVP straight from the idea, connected via MCP, and pushed to staging.
/ The turning point
A working tool made in days turned an a quickly made MVP into a roadmap project
/ chapter 2
Turning MVP into MLP — Minimal Lovable Product
After putting this project on a roadmap I took the reins on V1, turning the rough MVP into something people would actually enjoy using.
Now I work closely with the PM and Engineering team on visual direction and implementation.
In the MVP I laided colors out in a table that was tidy and dense, but the colors themselves, were hard to see. So I explored a card-based layout that put each color front and center.
/ initial UI
Compact, but colors were buried in the page structure
/ What I argued for
Engaging and easier to read at a glance
/ design systems update
Brand Book needed patterns our system didn't cover. I designed them in Figma and integrated them into the existing components library.
New elements I added to the main design system as a part of this project
Small interactions that make setup feel effortless
The MVP proved the idea; this made it usable. I shaped the flow to take the friction out of setup
Creating new palette
Organizing colors in the pallete
Setting color palletes
Defining brand settings according to the color palette
/ outcome and reflection
The impact
A three-day MVP turned an open question into a resourced roadmap project and reshaped how our team moves from design to shipped code.
What I took from it
Building the real thing early beats presenting mockups. A working prototype ends debates a deck would only start — and now I can build and stage it myself.