Getting started
From checklists and inboxes to one onboarding plan
Journey is a solution accelerator. The foundation is already built, so iomer builds your organization’s version, installs it in your tenant and pilots it with you. Most of your effort goes into deciding your streams, owners and approval routes.
Go live in five steps
Five steps, in order
-
Step 1
Plan
We map your onboarding from offer accepted to day 90: the teams involved, the streams and tasks, the policies to acknowledge, the forms to collect and the approvals.
From you: your current checklists, the policies new hires acknowledge, and who owns each part today.
-
Step 2
Build
We build Journey for your organization as a single deployment package: your streams, task collections, policies, approval routes, rules, roles, permissions and theme.
From you: decisions on stream owners, due days, approval levels and who each stream applies to.
-
Step 3
Install
We install your package in your tenant, including the flows, and test it there with your Microsoft 365 admin. There’s nothing for your IT team to assemble.
From you: an admin to approve the installation, a licensed service account for the flows, and up-to-date manager fields in Entra ID.
-
Step 4
Pilot
We run Journey with a group of real new hires and their managers, then adjust streams, tasks and wording before launch.
From you: a group of upcoming hires and their managers, and a few minutes of their feedback.
-
Step 5
Launch
Training for administrators, stream owners and managers, and rules switched on so journeys are assigned automatically. As your needs change, we build and install a new version of your package.
From you: an onboarding owner in HR or People Ops who will run Journey day to day.
Everyone on board
Bring HR, a manager, an IT or safety lead and your Microsoft 365 owner into the conversation early. Onboarding touches all four.
Who’s involved
Bringing your onboarding across
Start from what you already have
Your current checklists become task collections, your welcome pages and guides stay where they are and are linked from tasks, and the policies new hires acknowledge go into Journey’s versioned policy library. People already part-way through onboarding can be given a journey too.
We scope this with you, so you can see the effort before you commit.
What sets the size of the job
- How many streams and tasks you need
- How many approval levels and approver lists
- How many policies and forms new hires deal with
- Whether your HR system starts journeys, and whether you want a Power BI dashboard
Before we talk
Questions to think about
You don’t need answers to all of these for a first conversation. They’re what tells us how Journey fits, who else should be involved, and how big the job is.
Walk us through what happens from offer accepted to day 90. Who does what?
Gives us the streams we’ll build. Three or more teams involved is a strong fit.
Where does onboarding live today?
Spreadsheets and email mean an easy win. An HR system checklist means Journey takes the work side, fed by the HR system.
How many people do you hire a year, and do they start in waves?
Volume shapes the list design, archiving and the business case.
Which policies must new staff acknowledge, and does anyone ask for proof?
Audit, safety certification or regulator pressure makes acknowledgements by version important.
Do any onboarding steps need approval? How many levels?
Probation sign-off, access requests and competency sign-offs are common.
How reliable is the manager field in your directory?
If it’s patchy, we plan approver lists as a fallback.
Does every new hire have a Microsoft 365 account on day one?
Journey works from the day the account exists. Staff without accounts need licensing or a manager to record for them.
What HR system do you use, and does it trigger anything today?
A new-hire event or group membership can start journeys automatically. Integration is scoped separately.
What do managers ask for that they can’t see today?
Usually “who on my team is behind”. That’s the My team view.
What would HR or leadership want in a monthly report?
Confirms the report filters, and whether a Power BI dashboard is worth adding.
Which intranet platform are you on?
Native SharePoint is the cleanest fit. On Powell or Omnia, we look at the platform’s own onboarding features first.
Who owns onboarding across HR, IT and the business?
No owner, no success. If ownership is unclear, it’s the first workshop topic.
Why a solution accelerator
The benefits of off-the-shelf and custom, without the trade-offs
No two organizations are the same, but every onboarding program needs the same foundation. Journey gives you that foundation already built, and builds the rest around you.
| Onboarding software | Custom build | Journey solution accelerator | |
|---|---|---|---|
| Fits how you work | You adapt to it | Built around you | Your streams, approval routes, rules and policies are built in |
| Designed before you start | Yes | No, designed as it’s built | Yes, the foundation is already built |
| Time to go live | Fast to start, slow to fit | Slow, everything is built from scratch | Faster, because only your parts are built |
| Who sets it up | Your team | Your developers or a partner | iomer, as one deployment package |
| Where records live | Usually the vendor’s cloud, with its own sign-in | Wherever it’s built | Your own Microsoft 365 tenant |
| Cost | Per-user subscription | An open-ended project | Scoped with you first, then a work estimate and proposal |
| Changes later | Wait for the vendor’s roadmap | Another project | A new version of your package, built and installed by iomer |
Pricing
Scoped with you first, then a work estimate and proposal
Every Journey engagement starts by working through your onboarding with you: the streams, approvals, policies and integrations you need. Then we give you a work estimate and a written proposal for building, installing and piloting, so you can see the effort before you commit.
What the estimate depends on
- How many streams and tasks you need
- How many approval levels and approver lists
- Integration with your HR system, and a Power BI dashboard
- The number of regions, languages and hiring volume
Journey runs on the Microsoft 365 licences you already have. Already running Beacon or Hazel? Journey can share the same SharePoint site design, Entra ID set-up and governance model.
What happens next
From first call to proposal
Watch the 40-second tour first Download the datasheet (PDF, 2 pages)
- Discovery call
We learn how onboarding works today and what matters most.
- Tailored walkthrough
Thirty minutes with Journey, in your own brand colours.
- Discovery workshop
One or two sessions to map your streams, approvals, policies and forms. It produces your stream design and a work estimate.
- Proposal
A written proposal with the work estimate and timeline.
See Journey with onboarding like yours
Book a 30-minute walkthrough in your own brand colours, or take the evaluation kit away and come back when you’re ready.