Strategic design decisions
that generated $28.5M.
Buy Now, Pay Later had become a critical driver of e-commerce conversion globally. Competitors were already offering BNPL at checkout. Wayfair was late. The mandate: launch in four international markets, US, Canada, UK, and Germany, in 2.5 months, with a single senior designer.
This wasn't a project where I had a large team and extensive resources. It was a project where I had a hard deadline, four different markets with different legal requirements, three payment providers with different brand standards, and zero room to build 12 separate one-off checkout experiences.
The $28.5M in Year 1 revenue wasn't the product of flashy UI. It came from a series of specific strategic and architectural design decisions, made under constraint, delivered on time.
Four markets.
Three providers. One system.
Competitive analysis first.
Then find the gaps.
Before a single wireframe, I conducted a heuristic evaluation of Wayfair's existing checkout to identify every BNPL integration gap, places where the current component library couldn't support what we needed to build. I also ran a competitive analysis against IKEA, Amazon, and Bed Bath & Beyond to understand the conventions users already expected from BNPL at checkout.
Two findings shaped the entire project:
The component library was not ready. Wayfair's payment card components assumed text-only content. BNPL providers required logo integration, multi-line supplemental text, and supplemental disclosure copy, none of which the existing library supported. I would need to rebuild 14 card components before designing a single checkout flow.
Localization was a design problem, not just a translation problem. English BNPL copy that fits on one line wraps to three in French and German. That's not a copywriter's problem, it's a layout architecture problem that has to be solved at the component level.
Three problems that
shaped every decision.
Modular design was the
only path to on-time.
The single most important decision on this project wasn't a visual one, it was architectural. With 4 markets, 3 providers, 3 platforms, and a 2.5-month deadline, the only way to ship everything on time was to build a modular system where each provider's checkout pattern shared the same underlying component architecture, with locale-specific variations handled at the prop/token level.
This meant spending significantly more time upfront designing the component system than I would have if I'd built market-by-market. It also meant having harder conversations with engineering about implementation, the modularity only saves time if it's built correctly.
The 45% reduction in development effort wasn't an accident, it was the direct return on the time invested in modular component architecture. That's the value of design thinking applied to engineering constraints, not just user experience.
4 markets.
One modular system.
Each market below shares the same underlying component architecture, locale variations handled at the prop level, not rebuilt from scratch.
The lesson I carry from this project: when the deadline is impossible, the solution is almost always architectural. Build a system that makes the hard things easy, rather than building each hard thing individually. That applies to design systems, component libraries, and product strategy equally.