Avoid information overload at onboarding

Onboarding Studio helps new people get going on their own — instead of burying them in information.
Checklists and short guides show what to do now, who to ask, and what can wait.
It lives as an onboarding website and on the phone.
For new employees, new arrivals and patients.

Ask for a walkthroughWhat does it cost? →

What a journey looks like

The councilEN

Welcome aboard

What you need to do, step by step — at the pace it becomes relevant.

1Before you startContract, background check, equipment.
2First dayAccess, a tour, who to ask.
3First weekSafety, fire drill, health and safety.
4First monthPension, holiday, sick leave.

Video · 2 min

New employee · English

The councilUK

Ласкаво просимо

Покроково — з чого почати.

1Ваш приїздДе ви живете перші тижні.
2Ваше житлоВід тимчасового до постійного.
3Мовна школаРеєстрація та розклад.
4РоботаРезюме, центр зайнятості.

Відео · 2 хв

New arrival · Ukrainian

The journey is divided into steps, and you can see how far you have got. Each step has what has to be done, who to ask, and a short video where showing beats writing.

The mechanism is borrowed from the patient-journey apps hospitals use. There it is obvious that you cannot give someone everything on day one: each step arrives when it is relevant. The same holds for a new employee who gets access, pension, holiday and the fire drill in one morning.

Why most lists end up too general

People want a precise answer: that phone number, that deadline, that link. It is also the kind that goes wrong first — a number changes, a page moves, a form gets a new name.

So it gets written generally instead. “Contact HR.” “See the intranet.” That kind of line never goes wrong — and it never does the job either. The price of being precise is that somebody has to keep watch.

That is what we put monitoring on. The system keeps watch on the links in the journey and says so when one of them stops working. Nobody has to set a reminder in the calendar, and nobody has to review the list twice a year.

If something needs changing, you do it yourself in the editor, and it is on the phone within minutes. She does not have to update anything, download it again or react to a message — the next time she opens it, the text is the new one. That goes for people who started six months ago too.

The system noticesThe monitoring catches the links that stop working, and says so.
→
She sees it next time she opens itNo update, no reinstall, no message to react to.

You are not paying to have an app. You are paying for what is in it to be right.

That is why we do not charge per editor or per change. The moment a communications officer thinks “does it cost anything if I fix this phone number?”, she leaves it — and then a wrong number stays up to save a fee.

The price follows the number of journeys, not how much you use the tool.

Several languages, one set of content

One journey can run in several languages at once. You pick yours at the top, and everything follows: steps, checklists, contacts and the narration in the videos. Change something in the main text, and you can see which languages have yet to follow.

What it costs

WhatPrice
SubscriptionPer year, per onboarding site. DKK 5,000 / year
Site 2 and onwardsIf you run several journeys — integration, employment services, elderly care — the next ones cost less.DKK 2,500 / year

Included in the subscription

Available on top

Fair use: 2 GB of content and 250 GB of traffic a year per site. The limits are set so you do not have to think about them — 250 GB is about 5,000 video views a month.

If you get close, we tell you in good time.

Two things to know before you decide

You can host it yourselves. You get a folder of files to put on your own server. Be aware of one thing: if you do, a change only reaches the reader once your IT department has published the new files. If we host, it takes minutes from the moment your editor hits publish.

The app sends nothing from the reader’s phone. That is a deliberate choice. It also means we cannot give you figures for how many people have seen what.

Data processing

The people the journey is for. The app collects nothing. There is no account and no login. What you tick off or write — the name and number of the person to contact, for instance — stays on the phone and is sent nowhere. There are no fields for national ID numbers, and no usage statistics. The app fetches neither fonts nor scripts from third parties.

Your editors. To let them log in to the editor we store name, email and an encrypted version of the password. The password cannot be read — not by us either.

Where it sits. Everything is processed and stored in the EU: operations and database in Frankfurt, files in Cloudflare’s EU jurisdiction.

Show us the journey you are dealing with

Tell us briefly who has to go through it, and how many languages it has to run in. Then we come back with what it would take.