Rebode — The Platform Years

Rebode is MasterBrand Cabinets' digital kitchen-remodel venture — a startup living inside North America's largest cabinet manufacturer. I joined in July 2024 as one of three frontend developers. Two years later I was in the strategic meetings, consulted on design and CMS direction, and owned three properties outright. My leader's words: one of the most reliable members of the team.

This page is the platform story. Vision, Universal Components, the Blog and the Parametric Cabinet System each get their own page.

Jumpstarter turns “I want to remodel my kitchen” into an actual plan — style, layout, budget, and who builds it. I owned the Style Quiz, the Design Questionnaire, and the first version of the Budget step: ZIP validation against a regional API, then the logic that turns home value, remodel type, and region into a realistic budget range.

The part I'm proudest of came last in the flow: the dealer locator. Custom markers, territory-zone logic, availability by region. Our dealers API shipped without coordinates, so geolocation ran through Google's Maps API on every visit — and the bill spiked. My fix: cache each visitor's nearest locations locally, geocode only on first visit. About $10k a month, gone.

Jumpstarter is also where I started mentoring our design team — flexbox, spacing, typography hierarchy, and eventually responsive Figma screens as a standard deliverable. They came from print and advertising; we met in the middle and both sides got faster.

API SPEND REMOVED

~$10k/moAPI SPEND REMOVED

TOYS is Rebode's generative-AI feature: upload a photo of your kitchen, and a multi-agent Gemini pipeline re-renders it in the style you picked during Jumpstarter. Three generation slots per user, responsible-AI screening on uploads.

The pipeline existed when I took the feature over — my job was making it great in front of users. I refactored the React component, worked a redesign with the design team, fixed the mobile experience, and owned the A/B rollout through Amplitude feature flags: some users got full generation, others restricted tiers, and the data told us what to ship. I also got access to our Google AI Studio account and contributed my own testing and ideas to the ML team's pipeline along the way. I designed most of the Overview page it lives on, and built its designer showcase slideshow.

Rebode's homepage came from a third-party agency, with minimal documentation. Someone had to make it ours — so I mapped the codebase, taught the other devs their way around it, added feature flags and A/B testing with Amplitude, and helped wire in Kontent.ai image optimization. Inheriting someone else's production code and making it safely operable is less glamorous than greenfield. It's also half the job, everywhere.

The thread through everything: making other people faster. GitFlow across our repos. The Amplitude experimentation workflow every launch used. Kontent.ai environments that promote content cleanly from DEV to PROD. Dev/design collaboration as a formal part of PR review — my push. I mentored three developers at Rebode, including training an engineer with zero 3D experience into the maintainer of our hardest product. Final review: “Breakthrough” — the company's top rating — with zero P0/P1 defects shipped that year.