The expertise wasnever the problem.

A compliance and governance firm serving multinational clients across more than 120 countries. Their team is lawyers, accountants, and governance specialists who've spent careers thinking in jurisdictions, not sprint cycles. They had board backing and a clear platform opportunity. What they needed was someone who could translate the expertise already in the room into a product.

The constraint was specific: one month to ship an MVP, two months to produce outcomes worth showing investors. That timeline doesn't leave room for guessing. The work had to start from a different place.

The real product requirements weren't in any brief. They were in the gap between how the service was designed and how the people running it actually experienced it.

Bringing the full leadership team into one room, from compliance lawyers to operations leads, made that gap visible for the first time. What one group called standard process, another experienced as friction. From that conversation came more than a product plan: scope, program structure, operational model, and the alignment that unlocked board funding.

• ·Three programs defined with owners, problem statements, and sequenced action plans
• ·Operations model, program structure, and staffing plan produced in the same session
• ·Platform scope grounded in operational reality, not product assumptions
• ·Shared language established between compliance, operations, and product for the first time

The first question wasn't what to build. It was why the portal already in place wasn't being used.

We audited it systematically: every customer path, every point of failure. Ticketing buried new messages beneath old ones. Key account information was missing or unfindable. Twelve interviews across active and lapsed users confirmed it: when the platform couldn't surface what people needed, they defaulted to email. Small friction, consistent cost.

Then we stress-tested the build decision itself. Four leading platforms, live demos, full schema review. None fit the compliance workflows closely enough. That analysis didn't just confirm the decision to build. It gave the team evidence they could defend at board level. All of that before a single screen was designed. Not because there was time to spare. Because there wasn't.