Yrsa, in stealth until winter 2027
Yrsa
Yrsa is the product manager you talk to.
She accepts a prompt the way Lovable or Claude accept prompts. She responds the way a thoughtful senior product manager would: by asking what you are actually trying to build, surfacing considerations you may not have thought of, and quietly assembling a structured specification as the conversation unfolds.
The prompt becomes the artifact.
Yrsa is not a chatbot dressed as a product manager. She is the first layer of the specification of record. Every conversation with her produces something you can hand to an agent, an engineer, a designer, or a tester, and each of them will know what is meant and why it is meant.
Coming winter 2027.
We are in stealth until winter. A specification platform cannot be patched in public. The first teams that use it have to trust it with the shape of their work, and that trust is earned in private, with real product teams, before it is offered to the market. The launch will be small and deliberate.
Who is building it
Robert Kristiansen. Twenty years between Oslo and Bangalore, spent as a moderator between engineering teams in Europe and India. Founder of what is today Kongsberg Digital India, a development hub that now counts close to four hundred engineers.
Later, founder of Semine, an accounts payable automation company for European enterprises, grown into a category leader and sold. That decade was the deepest education in what enterprise software actually sells: buyers believe they are purchasing automation, but what they pay for is governance. The automation was the surface. The governance was the substance.
The founding story
I went to Bangalore as a young engineer. I sat in long meetings where specifications were translated, sometimes literally, sometimes culturally, from the head of one engineer in Oslo to the keyboard of another in Bangalore. I watched the gaps that opened in those translations, and I watched the engineers fill them with judgement. The specifications are the visible architecture. The interpretation is the load-bearing structure that nobody sees.
In April 2026 I gave an AI coding agent a small task. What came back was elegant. Too elegant. It had handled cases I had not asked about and ignored a rule I thought was obvious. The agent absorbed nothing. Where my specifications were incomplete, it invented.
That was a preview of how software is going to be made. The interpretation layer organisations have relied on for decades is about to stop scaling. Yrsa is the layer that takes its place: the decisions a team has actually made about how its software should behave, made structured, governable, and inheritable.
Robert Kristiansen, Kristiansand