About Vyrdis
Vyrdis was built to make user feedback count.
Why Vyrdis exists
The idea behind Vyrdis comes from Jonas Lillevold, a UX designer with years of research practice behind him — interviews, surveys, support transcripts, feedback widgets. The kind of work that piles up.
Feedback lived in user reports and Miro boards, scattered across people and teams. Patterns lived mostly in memory. It worked, but it came with a cost: older findings slipped out of view, teams repeated each other's work, and tracing a decision back to its source took longer than it should.
So he started building. First for his own team. Then for everyone with the same problem.
The name
Vyrdis comes from the Old Norse virða — to heed, to honour, to take into account.
The name was chosen because user feedback deserves more than a folder in Notion or a report no one reads. It deserves to be weighed seriously, traced carefully, and revisited as your users change.
That's what Vyrdis is built to do — and the name is a daily reminder of why it was built that way.
How Vyrdis is built
Every claim traces back to a quote.
When Vyrdis suggests a hypothesis or a recommendation, you can follow it back through the chain: conclusion → hypothesis → facts → original feedback. Nothing floats. Nothing gets lost.
Newer feedback weighs more.
Vyrdis weighs newer feedback higher than older. As your users change, your hypotheses change with them — without anyone having to remember to revisit them.
The AI proposes. You decide.
Vyrdis extracts claims from feedback, links them to your hypotheses, and calculates how strong the evidence is. Every step is visible and reversible. You stay in the loop on the calls that matter.
Where we are now
Vyrdis is in early access. The first teams in shape how it works — direct input on what gets built next, free for the duration. When pricing arrives later this year, your early-access org rolls into your paid one. Same data, same setup.
No credit card. Export or delete your data anytime.