A European cloud telephony provider's installation partners configured call routing through long forms, so answering "why isn't my phone ringing?" meant reverse-engineering setups page by page. The opportunity: one visual call flow that stays readable at 17,700 nodes per customer.

Shipped: in the client's premium tier, embedded in the partner portal

Adopted: by early-test partners without friction

Reused: as a template in ngDiagram, Synergy Codes' open-source Angular library

A B2B marketplace digitizing sales, order and supply management for building contractors and manufacturers in the Swiss market. An industry that runs on phone calls and paper will not adopt a webshop.

We designed the platform around how deals actually happen: per project, per vendor, position by position, with negotiation as a first-class state.

An early-stage founder had a vision, an investor ready to back it, and no shared answer to what to build first.

I designed and facilitated a five-day discovery workshop that turned that ambiguity into an agreed vision, a prioritized MVP scope and a 16-month roadmap.

The in-house product team asked for a six-month action plan. Every ranking question bounced off one they had not answered: which product leads, for whom, and under what name.

The morning named who they are. The afternoon wrote the roadmap. They left with a shared positioning statement, a value-exchange model, two focus areas with milestones for the next six months, and a next action for each person.

"Finally, we know who we are and where we're headed. That was the missing puzzle piece."

The company needed quarterly OKRs the people accountable for them would write themselves, still traceable to the mission, the values, the annual goals and the half-year product plans. The previous quarter had no dedicated facilitator.

I designed and solo-facilitated a one-day workshop. Three groups wrote the Q3 OKRs off Opportunity Solution Trees, then stress-tested them with silent De Bono-hats critique. Closing feedback landed between 4.5 and 5, and the company worked on those OKRs through the quarter.

A workflow builder team wanted to ride the EU AI Act wave with a compliance feature for AI in recruitment. The concept came out of a hackathon and looked convincing in a demo. The question, before any design hours: is this worth building, and if so, in what shape?

The committee chose to prove it as a feature in the product, on one real client, instead of selling a compliance layer nobody had deployed. The team went to an existing client who will need to meet the requirements. No design hours were spent before a real need was on the table.