How Poplin Scaled Design Without Scaling Their Design Team

Poplin has been in growth mode all year. New service categories, new partnership integrations, new flows shipping into a consumer app and a Laundry Pro app that already serve 500+ cities. Every one of those launches needs design. Poplin has one product designer.

Talia, Lead Product Designer at Poplin, supports three pods and two apps. Hiring a second designer was on the table. The problem with hiring is that the demand is now, not in six months. By the time a new designer is onboarded and productive, the next wave of launches is already in motion.

So Poplin took a different route. They brought their design system into Moonchild and opened the design process up to the people already writing the specs and shipping the code.

The bottleneck wasn't the designer. It was the workflow.

Poplin is fully remote, and every product idea used to move through the same async handoff chain. A PM wrote a PRD, handed it to Talia, waited for mockups, reviewed, iterated, waited again. Engineering picked up the work a cycle later. A single feature could take a month to hit production, and most of that month was spent waiting for the next person in the chain.

Talia's craft wasn't the bottleneck. The translation between product intent and design exploration was, and translation doesn't need a designer's hands as long as whatever comes out the other end respects the system.

The design system did the heavy lifting

Moonchild turns your design system into a working environment that product, design, and engineering can all contribute to without breaking consistency. Every screen is generated on top of your actual system and can move straight into code.

The Moonchild team worked directly with Talia to port Poplin's system over from Figma and GitHub. Components, tokens, typography, the patterns Talia had spent months codifying. The setup took roughly 1 week of collaborative work.

That fidelity is what makes the rest of the story possible. A PM generating screens on a generic AI tool ships off-system noise that a designer has to rebuild. A PM generating screens on Poplin's actual system produces something Talia can review and refine.

"Moonchild has improved collaboration with product partners by helping them create designs that align more closely with the design system from the start." — Talia, Lead Product Designer, Poplin.

Talia's role shifted accordingly. She owns the system that lets every screen get drawn, instead of drawing every screen herself. Higher leverage, and a job a single designer can actually do.

What changed for the PMs

Karina Orton, a Product Manager at Poplin, ran her first deep Moonchild session on a PRD for a new service vertical. She wasn't blocked once. More interestingly, she found gaps in her own spec. Seeing the flow on a canvas in Poplin's actual components surfaced product decisions that a text document would have carried all the way to design review.

"Product jamming, getting to clarity with myself, and then streamlining alignment discussions with design, eng, and stakeholders." — Karina Orton, Product Manager, Poplin.

Across roughly 243 screens generated by PMs alone in the first month, the conversation in design review changed. As Talia notes, "instead of spending time explaining that certain components don't exist, we can focus on the feasibility and quality of the solution itself."

Why this didn't break engineering

Engineering wasn't the bottleneck. Between Claude Code, Codex, and Figma's MCP, engineers had ways to get from design to code. The question was whether moving design faster would create a downstream tax.

It didn't, because Moonchild generates UI in HTML and CSS natively rather than in Figma-style abstractions. Engineers export in the format they ship in. The font that renders in the design is the font that renders in the build. Pixel-perfect Figma-to-code handoff is famously impossible. With Moonchild, it's the default.

"Velocity improved because engineers are spending more time building and less time decoding intent." — Azra Mirza, VP of Product Engineering, Poplin.

What's next

Poplin is going deeper. Expanding the system to cover more states and patterns, bringing engineers further into iteration loops, and moving closer to a true PRD to system to code workflow. Moonchild is investing alongside them, with proactive in-canvas guidance that helps every contributor produce sharper work, and continuous quality improvements as new models ship.

This is the workflow Moonchild is built to power. AI-generated UI grounded in a real design system, usable by the whole product team, exportable to code. Poplin is one of a growing set of teams using it to scale their design function without scaling their design team.