Regulatory affairs · New hire

Hire the colleague who’s read every regulation.

Knut is an AI teammate for medical software companies. He joins your Slack or Teams, keeps your design history file current, chases the overdue CAPAs, and answers “do we need a 510(k) for this?” — with the clause to prove it.

Works where your team already works —SlackTeams
# regulatory-affairsSlack
Sarah Malik10:24
Do we need a new 510(k) for the updated detection algorithm?
KnutAPP
Likely yes — the modified intended use changes the risk profile. I drafted a Letter to File vs. 510(k) decision memo citing FDA’s own decision flowchart. Want me to walk you through it?
Open memoCite sources
Knut is drafting…

Already on the team at

NeuraDxCardia HealthMedivancePulseAIVitalinkOrtho Systems
The problem

The answers are scattered.

In a medical software company, the answers you need live in your QMS, GitHub, Jira and a hundred documents. Finding them is slow. Compliance work is manual. Audit prep eats weeks. And when someone leaves, their knowledge walks out with them.

You don’t need another dashboard. You need someone who already knows.

Meet Knut

The colleague who actually likes the paperwork.

Knut was built for one job: regulatory affairs for software as a medical device. He’s calm, methodical, and mildly obsessive about citations — the expert you’d otherwise rent by the hour. No retainer, no scope-of-work, no waiting three days for an email back.

“I’ve read every revision of ISO 13485 since 2003, and I remember all of them. Ask me anything — the worst I’ll ever say is ‘it depends,’ followed by the exact clause it depends on.”

Knut, in his own words
Knut
Regulatory Affairs · Full-time
Active now
startsFour minutes after you invite him
responds_inAbout 30 seconds
has_readISO 13485 · IEC 62304 · EU MDR · 21 CFR 820
connects_toYour QMS · Jira · Confluence · Drive
favorite_phrase“Here’s the clause.”
sick_daysNone on record
sourcesCited, always
Onboarding Knut

A regulatory hire takes nine months to find. Knut takes four minutes.

No dashboard, no training course. He works in the channels your team already argues in.

01

Day one: he joins the channel

Invite him like any new hire. He shows up with a profile, a status, and good channel etiquette — no new tool for anyone to learn.

02

Week one: he plugs into your QMS

Connect your QMS and your docs. He learns your intended use, quality system, and target markets, maps the clauses that apply to you — and finds the gaps before an auditor does.

03

Every week after: he keeps you ready

He doesn’t wait to be asked. He drafts the records, chases the overdue CAPAs, flags new guidance that touches your product, and answers the hard questions in-thread — every claim cited.

Integrations

The point where all your systems meet.

Your QMS
HubSpot
GitHub
Jira
Documents
Email
Knut

Read-only, scoped, and reversible. Every answer cites the record it came from.

Knut, at work

Ask in plain language. Or let him speak up first.

# regulatory-affairsSlack
KnutAPP09:12
Morning. Before standup: FDA posted a draft revision to its premarket cybersecurity guidance yesterday — two sections touch your DHF, so I drafted the impact assessment for review. Also, the Vektor Labs supplier audit comes due in 18 days.
Daniel Lund09:41
@Knut we have an ISO 13485 surveillance audit in three weeks. Where do we stand?
KnutAPP09:41
Better shape than you’d guess — 4 of 6 areas are ready. Two need attention before the auditor asks. Here’s the live checklist:
ISO 13485 — surveillance readiness4 / 6 ready
Management review records — current
CAPA log — no overdue items
Design history file — complete for v2.3
Supplier audits — 2 due this quarter
Internal audit — not yet scheduled
Training records — up to date
Schedule internal auditDraft supplier requests
Daniel Lund09:43
Schedule the internal audit for next Tuesday and assign the supplier requests to me. This used to take a week of digging.

Connected to your QMS and grounded in the applicable standard — with citations your auditor can follow.

Standards covered

The frameworks medical software lives and dies by.

Knut doesn’t look these up — he knows them. The clauses, the deliverables, and how one requirement quietly triggers three more.

21 CFR 820 · 510(k)

FDA QSR & premarket

Design controls, submission strategy, and Letter-to-File vs. 510(k) decisions.

ISO 13485:2016

Quality management

CAPA, management review, supplier controls, and audit readiness end to end.

IEC 62304

Software lifecycle

Safety classification, SOUP management, and lifecycle records that hold up.

HIPAA

Privacy & security

Safeguards, BAAs, and breach-response readiness for PHI-handling systems.

EU MDR 2017/745

European market

Technical documentation, clinical evaluation, and post-market surveillance.

SOC 2 Type II

Trust & controls

Control mapping and evidence collection to satisfy enterprise buyers.

References

We checked his references.

“We cut our 510(k) prep from months to weeks. Knut drafts, my team reviews. Nobody stares at a blank page anymore.”

Anna Reyes
CEO, NeuraDx

“Our consultancy invoices dropped to almost nothing. Knut answers in thirty seconds what used to be a $600 email — and our engineers actually ask him questions now.”

Tomas Krause
Founder, Cardia Health

“We walked into our ISO 13485 surveillance audit with zero surprises. Knut had flagged every gap weeks in advance.”

Maya Brandt
COO, Vitalink
Security & data handling

Held to the standard he helps you meet.

Your regulatory data is among the most sensitive you hold. Knut treats it that way.

Never trained on your data. Your documents are used to answer your questions — nothing else.
Encrypted in transit and at rest with SOC 2-aligned controls and least-privilege access.
SSO / SAML and role-based access, plus a full audit log of every action Knut takes.
EU data residency and GDPR data-processing agreements with every subprocessor.
knut · data-handling
retention= your policy
training_on_datafalse
encryptionAES-256 / TLS 1.3
accessSSO · SAML · RBAC
audit_logenabled
residencyEU
dpaGDPR · all subprocessors
attestationSOC 2 Type II
Pricing

One agent. One price.

Roughly half the cost of a compliance hire — working 24/7, fully documented, every answer sourced.

35 000NOK / month
per Knut
Includes 20 000 NOK of usage
Heavy usage billed on top, transparently
All integrations included
A direct line to the team building Knut
Book a call
Questions

The things founders ask first.

Can Knut replace our regulatory consultants?

For the day-to-day work, yes — the drafting, the tracking, and the “quick questions” that used to run up hourly invoices. Knut answers in seconds and the knowledge stays in your workspace. For high-stakes strategy, he makes your experts dramatically faster — and your team stays in control of every decision.

Where does our data go — is it used for training?

Your data is never used to train models. It’s encrypted in transit and at rest, accessed under least privilege, and handled under SOC 2-aligned controls with data-residency options for EU and regional needs.

How long does setup take?

Adding Knut takes minutes, and he’s useful the same afternoon. Connect your QMS and over his first week he absorbs your product context and quality system — his answers get sharper, and he starts flagging things you didn’t ask about.

Which standards does Knut support?

FDA QSR (21 CFR 820) and 510(k), ISO 13485, IEC 62304, HIPAA, EU MDR, and SOC 2 today — with new frameworks added regularly. If a standard applies to medical software, it’s on our roadmap.

Does Knut work in both Slack and Teams?

Yes — full parity across both. Knut joins as a member, responds in channels and threads, and posts interactive record cards in whichever tool your team already uses.

Does Knut make regulatory decisions on his own?

No. Knut drafts and recommends; your quality team approves. Every action is logged and every claim is traceable to a source, so you keep a complete audit trail.

Get started

Hire Knut.

Book a 30-minute call and watch Knut work, connected to a sandbox of your systems — in your own Slack or Teams.

Book a call

Request early access

Three fields. No sales sequence.

Request access