OPUS DENTAL  ·  PLANMECA GROUP  ·  KICK OFF 2026

The Next Chapter.

Peter Samuel — Chief Technology Officer  ·  May 2026

SINCE WE WERE LAST TOGETHER

The team shipped.

Compliance
SFM live — October 2025
Sentral forskrivningsmodul deployed and running through winter. Stable across Norway and Sweden.
Compliance
HelseID + Persontjenesten API 3.0 — March 2026
Address protection in place for 3,500+ protected patients across Norway.
Compliance
KPR — pilot underway
Quality reporting for public dentistry. First pilot clinic deploying now. Work in progress.
Platform
V8 on Azure — platform stable
Azure infrastructure operational. Performance improved Jan–May 2026. The cloud foundation is in place.
Markets
Payment terminals — NO and SWE
Worldline, Nets, PayEx, Resurs, Swedbank. Single terminal across firms. Reconciliation automated.
Markets
Kjeveortopedi HELFO — complete
Mandatory referral date. HELFO form updated. Duplicate FNR prevention in place. Orthodontic workflow done.

Opus Dental

PRODUCT RELEASE TIMELINE · NOV 2023 – MAY 2026 · V7 + V8 + ITB
V7 Legacy
V8 Cloud
ITB
Milestone
WHERE WE STAND TODAY

Two products. Clear-eyed.

V7 — The clinical workhorse

Thousands of clinics. Actively maintained.

Every regulatory deadline met. SFM live. HelseID current. Payments extended. Norwegian and Swedish compliance intact. This product is the foundation everything else runs on.

V8 — Stabilising

~50 customers. Azure live. Redirected.

V8 is on Azure. The migration has exposed real weaknesses in the architecture — but the platform investment is preserved. The infrastructure, integrations, and cloud foundation are not throwaway assets. The product is redirected, not abandoned.

V8 has shown us where the limits are. We have to change path to remain relevant. The question is what we build next — and where we build it.

WHERE WE STAND

Thousands of dental clinics run on Opus every day.
Across Norway, Sweden, and Iceland.

Opus must capitalise on the headstart we have inherited.

THE DIRECT PICTURE

Two reasons clinics stay with us.

They choose us.

Strong relationships. Deep product knowledge. Clinicians who know every shortcut. A decade of earned confidence.

Changing is painful.

On-premise servers. Complex migrations. IT projects that stay on the to-do list. High switching cost — both ways.

We want to be the first reason. Not the second.

THE TENSION

The gap between what clinics expect from modern software and what we have delivered has been widening.

Cloud-native competitors have entered the market. Sweden has shown us what happens when a competitor makes switching easy enough.

The window to close that gap is open. It will not stay open indefinitely.

THREE LESSONS — ONE CONCLUSION

The transition is not a choice. The question is pace and method.

The warning

Kodak, 1975

Invented the digital camera. Buried it to protect film revenue. Filed for bankruptcy in 2012. The loyal base became the reason they stopped moving.

The precedent

Adobe, 2013

Moved Creative Suite to cloud. 50,000-person petition against it. Stock dropped. Two years later, subscription revenue exceeded the old peak. Short disruption. Permanent improvement.

Our path

The gradual move

Nobody asked to throw away their documents. The desktop app kept working. Things got better, gradually. Sync. Anywhere. No IT call needed. That is how our customers want to move.

The difference between Kodak and Adobe is not capability. It is the decision to move.

WHAT THE MARKET IS ASKING FOR

Half the working day lost to administration.

Not to patients — to paperwork, systems, and overhead software should eliminate.  Swedish dental union survey

Chains want one screen for the whole business.

Single sign-on across every clinic. A BI view that rolls up the whole chain. M&A integration that is configuration, not a database project.

Patients book themselves, or they find a clinic that lets them.

Every credible competitor ships online booking by default. This is no longer a differentiator — it is a prerequisite.

WHAT WE TAKE FORWARD — AND WHAT WE DO DIFFERENTLY

Clarity is valuable. Even when it is expensive.

KEEP
Infrastructure

The Azure platform works.

Pipelines, monitoring, migration tooling — battle-tested. The SFM and HelseID integration work is close to production-ready. These are not throwaway assets.

The data

Thousands of clinics across three countries. No competitor has this breadth.

Within strict data protection boundaries, this dataset is the foundation for AI capabilities — benchmarking, diagnostics, ambient scribing — that single-clinic competitors cannot build. We have not used it yet.

DO DIFFERENTLY
UX

Start from clinical tasks. Not old toolbars.

V8 moved V7's interface to the browser. That is not product development — it is porting. We now have the chance to listen to what practitioners actually need and build from there.

Features

Earn every feature. Cut what nobody uses.

The team interviewed the system, not the customers. The new version starts from the clinical task. If a feature cannot be justified by a patient outcome or a clinician workflow, it does not ship.

THE HYBRID STRATEGY

Cloud capabilities, built into Opus. In stages.

1
Identity & Access
One login. Everywhere. Single sign-on, licence management, cross-clinic access.
Now
2
Online Booking
Patients book from their phone. Automated scheduling. No voicemails.
Next
3
Patient Records
Journal accessible from anywhere. No server in the building required.
Next
4
Clinical Workflows
Treatment planning, charting, imaging — connected to Planmeca hardware.
Later
5
Economics
HELFO, reimbursement, reporting — the thing that fills our support queue when it breaks.
Later

Each stage works on its own. Each stage makes the next one possible. No forced migrations.

THE NORTH STAR — 2028

Monday morning at Oris.

They walk into the clinic. Open Opus — same screen, same login.

Not once per machine. Not once with a certificate that expired over the weekend.
Once. Their access follows them — Oslo on Monday, Bergen on Thursday.

First patient booked online, two weeks ago. No voicemail. No rescheduling call.

The appointment adjusted itself when the patient's plans changed. The clinic handled none of it.

During the appointment — the AI scribes the clinical note.

The practitioner speaks. The entry writes itself, structured, ready for HELFO.
Review. Approve. Done. No documentation backlog at the end of the day.

End of day: HELFO filed. KPR reported. Recalls sent.

The chain's dashboard updated across every clinic in the group.
The practice manager goes home on time.

WHO THIS IS BUILT FOR

Sharper focus. Clearer priorities.

The chains

Oris · Colosseum · Smile Tandvård

They want SSO across every clinic, chain-level BI, and a Control Plane Portal that makes running 70 clinics feel like running one. If we don't deliver this, they will build it themselves.

Public sector

Kommunal dental & Folktandvård

KPR compliance is a buying trigger for public tenders in 2026. Opus has a head start. That lead is worth protecting — and communicating.

Iceland

~95% market share

Strategically important to the Planmeca group. The same gradual cloud transition — protecting a position that took decades to build, without asking customers to take a leap.

Small clinics

Thousands of practices

Every improvement to the foundation reaches them. Online booking, identity, API integrations — they benefit from everything we build for the chains without separate effort.

We are working more closely with Plandent than we have in years. That energy is directly shaping what we build.

BLUE SQUAD — API-FIRST

Every integration. Through one front door.

We are not building point integrations one at a time. We are building the API foundation that makes every integration faster, more reliable, and available to every clinic — not just one. Sam is in place. The programme is open.

OPUS
API
Under evaluation
Telavox Dentdesk Pearl AI 3Shape Insurance Payments
Where the API programme is aimed
Ambient AI scribing AI radiograph reading Chain BI

If you are talking to a partner — send it to Blue squad. That is what they are for.

PART ONE — THREE COMMITMENTS
KPR: pilot underway — now.
First pilot clinic deploying now. The solution is in place. We are moving forward.
IAM starts now.
Agreements signed. Team assembled. Work begins this week. Identity foundation in place by Q3.
The API programme is open.
Blue squad. Sam in place. Send us your partner conversations. The answer is yes.
PART TWO

Future Opus technical organisation.

2
SQUAD MODEL — TEAM TOPOLOGIES

Feature teams. Clear ownership. One backlog each.

🟩 Green — Cloud Foundation
Victor Barrera, Head of Product
Identity & Access (IAM). Control Plane Portal. The foundation everything else is built on.
🟥 Red — National Health
Gajaen (joining June) — Technical PM
HelseID, KPR, SFM NHN. Compliance integrations that keep Opus in every tender.
🟦 Blue — API & Integrations
Sam — Technical PM
The API programme. Every partner integration. The front door for third-party connections.
🟨 Yellow — Economy
Hannah Nicol — PM
Payments, HELFO, reimbursement. The things that fill our support queue when they break.
🟪 Purple — UI & Workflow
Coming soon
User interface and workflow improvements. The NEXT track — not active yet.
⚙️ Ops — Platform
Simen (lead) · Robin · Dexter
Azure, environments, monitoring. The infrastructure that keeps everything running safely underneath.
THE TEAM

The ambition is bigger. The team is growing to match it.

🇳🇴
Norway
Core delivery hub · Growing
🇸🇪
Sweden
Delivery hub · Active
🌐
Expanding network
Delivery partners · In progress

Recent additions: Gajaen (Technical PM, Red squad, joining June)  ·  Gautam (SQL database expert, Norway)  ·  Roman (senior developer, Norway)

OPUS DENTAL  ·  PLANMECA GROUP  ·  MAY 2026

The Next Chapter.

Thank you.

1 / 20
SPEAKER NOTES