Case 07 / Swiss SaaS
QLYR
Every match clears compliance and books itself.
Qlyr pairs people facing a big decision with Swiss-regulated experts, and each match runs the same path on its own: matched, cleared for compliance, booked. We built the engine underneath, and everything around it.
DLVX / Case No. 07
In production
01
Matching engine
Weighs specialism, availability, and compliance status to pair a person with the right regulated expert.
02
Compliance layer
Swiss regulatory rules enforced in code, not in a policy document. A match that fails compliance never reaches a calendar.
03
Scheduling
Calendar sync and booking the moment a match clears compliance, no separate step for either side.
04
Marketing surface + waitlist
The public site and waitlist that turn a cold visit into a qualified account before anyone sees a dashboard.
05
Full-stack build
A clean codebase behind all of it is part of the package, web app, backend, and admin, one team, one repo, from the first commit.
The problem
- A big decision shouldn't get matched on convenience alone
- Regulated experts can only take work compliance clears
- The waitlist has to filter before anyone reaches a dashboard
Why it holds
Compliance runs inside the matching engine itself. A match that fails it is never shown to either side.
Compliance was the part I actually worried about. Everything else we could fix later. It passed review first time, no rework, and it has held since.
Luc
Founder, Qlyr
1
Matching engine, end to end
Code
Where swiss compliance rules live
Waitlist
To qualified account, not just signup
1 team
Full stack, start to finish
Want this inside your business?