Layo

Run the launch before you build it.

Shipping a feature is still mostly guesswork. The Product Manager writes the brief, the team builds it, and the company only finds out how customers react after launch, when the damage is already done.

We thought guessing was a problem worth solving.

The Method · in four rooms

How a launch is rehearsed.

The simulation runs in minutes, not weeks. The PM stays in the chair: scrolling threads, pulling on the loudest argument, finding the objection nobody on the team thought to ask.

I.The Forum

Where personas convene

Layo opens a live forum the moment a brief lands. Two hundred personas, soon thousands, file in by segment.

Ticket#1042 · third-gate friction
NPS“… would not recommend.”
Call2026-04-18 · 12m · power user

II.The Witnesses

Built from your evidence

Each persona is distilled from your tickets, calls, NPS, app reviews. Not invented from a generic survey panel.

“Power users will hide this behind a toggle.”
“Segment C will churn before they understand it.”
“The previous version solved a job this drops.”

III.The Trial

Argument, not approval

They debate in public. Replies, upvotes, churn warnings, segment splits. The loudest critic is the one you click first.

IV.The Verdict

A change you can ship

What leaves the room is a transcript and a single decision: copy change, rollout condition, kill signal, by Tuesday.

§ The team

The founding team.

We met at hackathons in Zürich and Munich.

Mohanad as a pixel-art duck

CTO · Zürich

Mohanad

Undergrad at TUM.

Sara as a pixel-art duck

CEO · Zürich

Sara

Master Fine Arts ZHdK.

Arka as a pixel-art duck

CAIO · Zürich

Arka

ETH graduate bringing experience from both research and industry.

Bring us a feature you need fast feedback on.

We are pairing with product teams who have real customer data and a decision that cannot wait three weeks for another research cycle.