Skip to content

Begin with one work process.

The first process carries the pilot; the next opens when it runs.

How to choose the first process

Everything you run today stays.

Inora goes on top of what is there. One process, one team, the login people already have.

Nedap Ons, eCare Puur
Stays the record. From day 15 Inora reads along on the care worker’s login; after the pilot through the connection, and then the report goes in on the care worker’s approval.
Attendi
The team keeps dictating. Inora picks up what follows.
Medimo
Medication stays where it is.
Zenya
Your documents stay where they are. In the pilot we load the released version; after the pilot Inora picks up each new version itself.
Entra ID, Okta
The login people already have.

The next process opens only when the first one runs.

See the connections

Five steps. Each leaves you something.

Every step has a fixed length and a fixed result. After the evaluation, you choose.

  1. 01 · Readiness check
    Five minutes

    Where Inora helps you first, and which team starts.

    What it takes

    No account, no call, no commitment.

  2. 02 · See it
    One hour, with your own questions

    You have seen what Inora does with your questions before anyone signs.

    What it takes

    A sample organisation or a guided demo. No personal data, so nothing for IT.

  3. 03 · Pilot
    Live from day 15

    Your working agreements organised, with owners and versions, in a knowledge system that is yours.

    What it takes

    Eight weeks. Your manager signs. Your team works with Inora from day 15. Onboarding included.

  4. 04 · Evaluation
    Measured in FTE

    Your baseline and your measured result: the basis for the decision on your whole organisation.

    What it takes

    A baseline before the start and a measurement in week 8, with us or on your own.

  5. AZWA window
    €600m

    Money for the rollout across your organisation, 2027 to 2029.

    What it takes

    For district nursing, mental health and general practice. The baseline before the start, the after-measurement in week 8. Applications from 1 to 31 January 2027, through the portal of Zorgverzekeraars Nederland.

05 · Next teams
Faster and cheaper

Everything from the pilot; every next team starts on the same organised knowledge.

Stop
After the evaluation

Your knowledge, your files and the structure of your knowledge system.

They ask Inora before a colleague. And they stay.

Adoption is decided in the first three weeks, so nothing waits for people to start asking.

The message comes first. The day is on the phone before the first visit, without anyone asking.

94%

still work with it half a year on, of those active in five of their first eight weeks

45%

of questions come in the evening, at night or at the weekend, when no colleague is there to ask

96%

of staff with an account at Vitala+ work with it

80%

use it when a small first group starts; mass invitations reach 12%. So: one team first, never a training day.

“Technology that is well implemented and carried by the team adds directly to job satisfaction and quality of care.”
‘

Mooi om te ervaren hoe technologie, mits goed geïmplementeerd en gedragen door het team, direct bijdraagt aan werkplezier én kwaliteit van zorg.

’
Staff adviser, quality and safety, elderly care, South LimburgOur translation

Everyone who started, stayed.

Bergweide began with twelve people. Vitala+ with three test teams. All of them stayed.

  1. Vitala+One organisation

    12 days

    to the start menu of every workstation

    12 days

    to the start menu of every workstation

    Who decided for the whole organisation
    The director, with the management team, from its own budget.
    Started with
    Three test teams in September 2025, from the director to housekeeping.
    Now
    The organisation’s whole quality handbook is in Inora; 96% of its staff with an account worked with it.
    How it started, and now
    Started with
    Three test teams in September 2025, from the director to housekeeping.
    Now
    The organisation’s whole quality handbook is in Inora; 96% of its staff with an account worked with it.
    Vitala+
    Vitala+
  2. VVT Platform Zuidoost-BrabantPartnership

    3 → 13

    care organisations, since September 2025

    3 → 13

    care organisations, since September 2025

    Who decided for the whole organisation
    The boards of the first three organisations.
    Started with
    A pilot with 60 care workers at three locations, in the evening, at night and at the weekend.
    Now
    All twelve members of the platform and one organisation outside it, and a second year agreed by every board.
    How it started, and now
    Started with
    A pilot with 60 care workers at three locations, in the evening, at night and at the weekend.
    Now
    All twelve members of the platform and one organisation outside it, and a second year agreed by every board.
    South-East Brabant
    South-East Brabant
  3. ZorgConnect Zuid-LimburgRegional network

    100%

    of the ten in the project chose a second year

    100%

    of the ten in the project chose a second year

    Who decided for the whole organisation
    The network’s steering group of directors, for the ten organisations in its project.
    Started with
    The first teams on 15 September 2025, on CZ zorgkantoor’s Wlz transition funds. Bergweide began with nine nurses and three team leads.
    Now
    A second year from the same steering group, with 1,520 hours of the organisations’ own people. Across South Limburg 16 care organisations work with Inora, outside the project too.
    How it started, and now
    Started with
    The first teams on 15 September 2025, on CZ zorgkantoor’s Wlz transition funds. Bergweide began with nine nurses and three team leads.
    Now
    A second year from the same steering group, with 1,520 hours of the organisations’ own people. Across South Limburg 16 care organisations work with Inora, outside the project too.
    South Limburg
    South Limburg

One quote, four lines.

Pilot, evaluation, implementation and licence: what you buy and what is fixed. The price is fixed per team; you get it on one sheet after the first call.

Quote · model

Inora for your organisation

Each line separate on your quote

StepWhat you buyWhat is fixedFunding
01PilotInora for one team or location, eight weeks, onboarding in the pilot price. The first team is live from day 15.Price, scope and term.
02EvaluationThe week-8 measurement against the baseline. Stop after the evaluation, no notice period.The baseline from the start.
03ImplementationImplementation per team or location, by the people who build Inora, until your teams work without us.A fixed price per team, on its own line alongside the licence; every next team faster and cheaper.Fundable
04LicenceInora per location or team, per year: your knowledge system, updates and support.From the evaluation, a structural cost for your organisation; the breakthrough funds don’t pay the licence.Not from the breakthrough funds

Request the pilot agreement

Funding

Implementation is the item the funding routes pay for. The breakthrough funds pay no licence, not even in the first year.

See the funding routes

Every next team faster and cheaper.

We organise your handbook once. Every next team starts on it.

  • The fund pays. AZWA breakthrough funds, the care office or the insurers pay for implementation; the licence is your own item.
  • The base is laid. We organise your knowledge once; every next team starts on it, and so starts faster and cheaper.
  • After the evaluation. The licence becomes a fixed cost for your organisation, paid from the hours that come back.
  • Your works council’s brief is ready. What goes to the organisation and what never does, with the model request for consent. What the works council asks and gets.
Organise your knowledge once, then implement every team faster and cheaper.

After go-live, your contact stays.

Updates are in the licence. We answer questions within two hours on working days and respond to an outage within an hour, day and night.

  • One named contact. Whoever led your implementation stays your point of contact after go-live: for questions, for the next team and for the next work process.
  • Updates are in the licence. Every new version of Inora is ready for your teams. You see in advance what changes.
  • Questions answered within two hours. On working days from 8:00 to 18:00, our team answers your functional administrators and key users within two hours.
  • An outage line, day and night. Report an outage to support@axiomatic.digital, 24 hours a day, seven days a week. We respond within an hour and resolve 95% of outages within four hours.

Measured in FTE, for your board.

Measured before the start and in week 8: 44.9% of every team’s working time back. Your figures convince your board.

Worked example of a pilot team

Your team · 20 FTE · the pilot

  1. 01

    Labour saved, the whole job

    Looking up, reporting, recording, handing over · hours per worker a year

    1,260 420 · 44.9% working time back

  2. 02

    Admin time

    Admin, share of working time

    34% 11% · 23 points down

  3. 03

    Your sector’s measure

    Questions to whoever is on call or decides, a week

    12 8 · 33% fewer

  4. 04

    Professional confidence

    Professional certainty, 1–10

    6.4 8.2 · +1.8

  5. 05

    Your own knowledge in use

    Finding a working agreement

    6 min 20 s · 18× faster

  6. 06

    Conversations prepared

    Share of conversations prepared with the current rule

    25% 50% · 2× as often

At 6 and 12 months
  • Quality and safety6 months 30% fewer
  • Competence and learning6 to 12 months 2× as fast
  • Work pressure and retention12 months 15% less
Labour saved in FTE · the whole job

9 FTE

back per team of 20 per year. Your own figures, measured before and after.

Inora, the whole job · Your teams’, for your board

(1,260 − 420) h × 20 / 1,872 working hours = 9.0 FTE, measured as hours per work process, before and after.

Then

The rollout across your organisation: on your funding route or your own budget, on these figures.

Evaluation kit

Download the evaluation kit PDF · 8 pp.

What you build, you take with you.

Every part works outside Inora too.

01

Your knowledge

Every working agreement current, with owner and version.

Pressure ulcer preventionv7

Owner
Wound nurse
Since
14 Oct 2026
Cited in
214 answers

Topics

  • Red patch on the heel
  • Repositioning
  • Heel protectors
Markdown · PDF
01

Your knowledge

Every working agreement current, with owner and version.

knowledge/pressure-ulcers.md

---
title: Pressure ulcer prevention
kind: protocol
owner: Wound nurse
version: 7
in_force_since: 2026-10-14
earlier_versions: [6, 5, 4]
cited_in: 214 answers
---

## 3.2 Repositioning
Reposition every two hours,
nights too. At category 1:
free the heel, heel protector.
Opens without Inora.
02

Your files

Everything you supplied, and what Inora built on it.

Supplied212

  • Pressure ulcers v7.pdf
  • Medication policy 2026.pdf
  • GP service agreement.docx

Built by Inora64

  • Repositioning card
  • Night-shift SBAR template
  • Evening and night call card
Originals · ZIP
02

Your files

Everything you supplied, and what Inora built on it.

files/

files/
├─ supplied/                 212
│  ├─ quality-handbook/
│  ├─ medication-policy-2026.pdf
│  └─ gp-service-agreement.docx
└─ built-by-inora/            64
   ├─ cards/
   │  └─ repositioning.pdf
   ├─ night-shift-sbar.docx
   └─ evening-night-call-card.pdf
Every original, and all built on it.
03

Your structure

How your sources hang together, and who manages what.

Your organisation

  • QualityProtocolsPolicy
  • PharmacyMedication
  • RegionAgreements
  • TrainingFormatsInstructions
JSON
03

Your structure

How your sources hang together, and who manages what.

structure.json

{
  "owners": [
    { "role": "Quality",
      "manages": ["protocols",
                  "policy"] },
    { "role": "Pharmacy",
      "manages": ["medication"] },
    { "role": "Region",
      "manages": ["agreements"] },
    { "role": "Training",
      "manages": ["formats",
                  "instructions"] }
  ]
}
Readable by Copilot and SharePoint.
“What we built in the pilot is ours. That made the decision a small one.”
Board member, elderly-care organisation · translated from Dutch

The knowledge stays yours.

Your knowledge trains no model, ours or anyone else’s. When you stop, you get all of it back, at no charge.

Ask every vendor

What happens to our sources and our record on the day we leave?

The answer should be: you get everything back, in a form your next system reads.

Export, on the day you leave

  • Your sourcesProtocols, working agreements and formats, with version and ownerDOCXPDF
  • The knowledge baseEvery passage with its source, version and ownerJSONCSV
  • Your test questionsYour own questions with the answer you expectCSV
  • Reports per teamWhat was measured, per team and per monthCSVPDF

Yours to request at any time, not only on the last day.

You send links, not explanations.

One link per colleague, the question they will ask already answered. They read side by side while you plan the pilot.

OutboxReady to send

  • To CISO or IT managerRe: Does this cost my team work?

    Re: Does this cost my team work?

    Wabvpz · NEN 7510 · Cyberbeveiligingswet

    A yes in one meeting. The file is ready.

  • To Data protection officer or privacy officerRe: Can I finish my DPIA from this?

    Re: Can I finish my DPIA from this?

    GDPR · Wabvpz

    Everything in the EU. Your data never trains a model.

  • To Members and secretary of the works councilRe: Does anyone read what colleagues ask?

    Re: Does anyone read what colleagues ask?

    WOR art. 27(1)(k) and (l)

    Clear agreements on who sees what. The letter is ready.

  • To Quality adviser, nursing council, care director or elderly-care physicianRe: Does the professional still decide?

    Re: Does the professional still decide?

    IGJ · AI Act · intended use

    Answers from your own protocol; the professional decides.

  • To Controller or care directorRe: Which pot pays for this?

    Re: Which pot pays for this?

    AZWA · Wlz · SPUK

    Your route: insurer, care office, innovation budget, municipality.

Whoever builds it puts it to work.

We build Inora, and we sit at your table for the first two weeks: we read in your sources and test Inora on your own experts’ test questions. A founder leads the rollout every week. What each rollout teaches goes back into the product: the latest took 38% fewer hours than the first.

Ask any vendor

Who sits at our table in the first weeks, and do the same people build the product?

With a partner in between, what your rollout teaches never reaches the product.

Your knowledge baseTested on your test questions
  • ProtocolsRead in412 documents
  • Report formatsRead in36
Week 1 of the pilot: one team, its sources read in. From day 15 the team works with it.

You already have the answer.

This is what you answer when they ask.

  • Does this have to go through procurement?

    No.

    Your manager signs the pilot, from their own budget. Procurement gets a quote that prices every line.
  • What does IT have to do?

    Only the sign-in.

    You set up single sign-on yourself in one click, through the identity provider you already have (Entra ID, Okta, Google or any SAML/OIDC provider), with SCIM to create and close accounts. Inora is built to NEN 7510 and ISO 27001, and your CISO has the file before the first meeting.
    Read how it is secured
  • Who owns what we build?

    You do.

    The knowledge your team organises, the files and the structure of your knowledge system stay your organisation’s, whether you carry on or stop.
  • What if we stop after the pilot?

    Then it stops.

    No notice period, no follow-on contract.
  • Can the pilot be funded?

    The fund pays for the implementation.

    The fund pays for the implementation across your organisation. The pilot delivers the baseline and the measured result. Your own budget covers the pilot and the licence; the breakthrough funds pay for the implementation after it.
    See the funding routes
  • Can we take it in parts?

    Yes, part by part.

    Start with the record review, or what follows a fall or wound. Each next process joins once the first runs.
  • Aren’t we too big for you?

    Inora goes on top of what you have.

    One work process, one team, the login people already have. Ons or Puur, Attendi, Medimo and Zenya all stay. The next process opens when the first runs. Scale is settled: we build software tens of millions of people use every day.
  • What does the licence cover?

    Inora for one location or team, per year.

    The licence covers Inora, your knowledge system, updates and support. Implementation has its own price per team, alongside the licence, and that implementation is exactly what the funding routes pay for.

Put the pilot for your team on paper.