Lynus

The people behind Lynus

Built by people who've lived the problem

Two of us spent years inside Innovasjon Norge, on the funding side of the desk. One has shipped software since the IBM and AT&T days. We didn't research this problem. We lived it.

Samuel Dirksz – CEO & Product, LynusCEO & Product

Samuel Dirksz

Co-founder & CEO · Product and strategy

Sam was a senior advisor at Innovasjon Norge from 2020 until the office closed in 2026, the last stretch on the digital product team building MinSide and En vei inn, the public funding portal Norwegian founders actually use. Before that he led product at Digital Revisor, automating the routine work of auditors and accountants with early AI. That is where he and Erik first worked together. Twenty-five years of building came first: custom PCs, bike shops in Amsterdam, digital ventures. Lynus is the tool he kept wishing existed while doing the job by hand.

Grant funding from the insideProduct strategyPublic-sector digital product25 years building
LinkedInSunnfjord, Norway
Rune Blom – CCO & Finance, LynusCCO & Finance

Rune Blom

Co-founder & CCO · Commercial and finance

Rune has done the exact job Lynus is built for. At Innovasjon Norge he was a financing advisor handling grant applications, the saksbehandling itself, alongside sparring with founders and growth companies. The commercial and finance spine runs deep: audit at EY, five years of management consulting at BDO, a strategy master from NHH, and CFO at Vestnes Ocean today after running a branch at SAR. At Lynus he owns the commercial side, the pricing, the pipeline, and the long public-sector sales cycle, with a finance brain that keeps every number honest. He has closed B2B deals in regulated, slow-moving industries long enough to know trust comes before the contract.

Commercial & B2B salesSaksbehandling, from the insideAudit (EY) & consulting (BDO)NHH strategy master
LinkedInSunnfjord, Norway
Erik Einebærholm – CTO & Engineering, LynusCTO & Engineering

Erik Einebærholm

Co-founder & CTO · Engineering and architecture

Erik has been building and running systems since the late 1990s, from IBM and AT&T global networks to five years leading IT at Telenor, then software development at Digital Revisor, where he and Sam first worked together. Today he is a system developer at ProResult. He is the critical eye on every decision, pushing on security, data flow and the way it actually feels to use. He lives close to AI, following it day to day, and keeps the build honest. Nothing reaches a user until it has cleared his questions: deployable without an IT project, and able to survive a DPIA. He ships things that stay shipped.

Full-stack25+ years in systemsGDPR & security scrutinyAI, every day
LinkedInSunnfjord, Norway

Why this team

Three disciplines. One unfair advantage.

Most AI startups hire domain consultants after the fact. We started from the inside and worked out.

Built from the inside

Two of the three of us came out of Innovasjon Norge. Sam advising founders and building the funding portal, Rune doing the saksbehandling on grant applications. The product wasn't designed from interviews. It was designed from memory.

Commercial patience

Public sector sales take longer than anyone admits. Rune did the grant saksbehandling at Innovasjon Norge, audited companies at EY, consulted at BDO, and now runs the books as a CFO, with a strategy master from NHH behind it. He keeps the finances clean and the timeline honest.

No overengineering

Erik has built and run systems since the late 1990s, from IBM and AT&T to Telenor and Digital Revisor. He is the one who challenges every choice on security, data flow and how it feels to use. European servers, audit trails on by default, nothing clever for its own sake. If it can't survive a DPIA, it doesn't ship.

DomainPublic sector & innovation funding know-how
CommercialSales, pricing and revenue discipline
EngineeringSecure, compliant, production systems

Where these overlap is where Lynus gets built.

What we stand for

Principles we build by

01

Compliance first

GDPR and Schrems II aren't features we added later. The stack was chosen specifically because it passes a Norwegian public sector DPIA.

02

Human judgment stays central

AI does the groundwork. The caseworker reads the brief, applies their judgment, and makes the call. That order doesn't change.

03

No tool to learn

If a caseworker needs training to use Lynus, we've built it wrong. You describe how you evaluate. The platform figures out the rest.

04

Ship with intention

Three people means nothing ships by accident. We're building for organisations that can't afford a failed AI rollout, so we don't rush.

Work with us

Want to pilot Lynus with your team?

We're running early access pilots with a handful of Nordic public sector and grant organisations. We configure it to your policies, sit with your team during onboarding, and don't invoice until it's actually working.

Get in touch
Back to home