Your people work across a dozen systems. Remy makes it feel like one.
Remy at Work is the layer that sits over every tool your staff already use — ERP, CRM, portals, admin consoles, the system nobody wants to touch. Someone asks in plain words, Remy answers and flies the cursor to exactly where to click. And when something changes, Remy is what tells each person what changed for them, in the tool where it matters. Licensed and implemented per organisation — we start from whatever you are changing next.
Building software and want to guide your own users inside it? That is a different product — Remy Onsite, with pricing you can read and an embed key the same day.
The tools were never the hard part
Nobody in your building is short of software. What is missing is anyone who knows all of it at once — and any way to make a change land without everyone starting over.
One job, a dozen systems
To the person doing it, a return or a claim or a case is one piece of work. To your estate it is six logins, four conventions, and a spreadsheet nobody will admit to.
Every change starts the learning over
New release, new system, new procedure. You budget for the dip every time — hypercare, floorwalkers, a lunch session — and every time it arrives anyway.
The people who know are the bottleneck
Every system has its key-user. There are never enough of them, they have their own work to do, and when one leaves the knowledge walks out with them.
A colleague who knows every system in the building
One way of working, across every system
Remy sits over your ERP, your CRM, your portal and the console with no API. Same buddy, same way of asking, whatever is on the screen — so your people learn one thing instead of eleven.
Carries every change to the person it affects
A new release, a new flow, a new procedure. Remy notices what changed, works out who it changes things for, and shows them — in the tool, at the moment they do the thing that is now different. Not a company-wide email nobody opens.
Takes the repetitive parts over
The steps worth automating, Remy does in the same interface your people use. Remy does the work, a person confirms. No integration project — and it reaches screens an API cannot.
Makes leadership genuinely AI-vaardig
Remy sits on a director's own screen, in their own work, and offers. Paired with cohort sessions and a maturity score you can actually show a board.
It starts with whatever you are changing next
Every organisation has something coming — a migration, a release, a new procedure, a department that never quite left the old way of working. That is where we start, and everything after it is scoped from how the first one went.
- 1
Connect
Weeks 1–3
Remy live across the systems in scope. It reads the real interfaces your people work in, so there is no guide library to write and nothing to keep in sync afterwards.
- 2
Change
Per go-live
Remy carries the change. Each person gets what is different for them, in the tool, at the moment it matters — and you get to see how far it has actually landed.
- 3
Ongoing
Licensed per year
Remy stays, across the tools that matter. This is the part everyone feels day to day, and the spine of everything else. The next change costs a fraction of the first.
- 4
Flows
Per process
The repetitive steps a department can point at, built and running. Human-in-the-loop: Remy does the steps, your person confirms.
- 5
Directie
Per cohort
The leadership programme. Remy on their own screens, cohort sessions, and a measured AI-vaardigheid score per person and team.
- 6
Partner
Quarterly
A review with your MT, the next change on the calendar, and the flows worth building before it lands.
What every engagement has in common is a licence at its centre. What changes per organisation is the size — how many people, how many systems, how many changes a year — not the shape.
Learning AI by doing your own work, not a course about it
The reason AI training rarely sticks at the top is that a chat window asks you to already know what to ask. Remy works the other way round: it sits on your own screen, in your own inbox and spreadsheets, sees where you are, and offers.
Alongside it, cohort sessions with your MT and a measured AI-vaardigheid score per person and per team — re-measured each quarter, so progress is something you can put in front of a board instead of describing.
What a cohort covers
- Remy running on each participant's own machine, in their real work
- Where AI genuinely helps in your organisation — and where it does not
- Reading an AI proposal well enough to challenge it
- What to ask your own teams before approving an AI project
- A baseline and a quarterly re-measurement per person and team
A colleague, not a monitor
Remy exists to help the person in front of it. It is not a productivity tracker, and it is built so it could not become one.
- Remy reports on the change it was hired to carry — never on how your processes run, and never on a person.
- There is no per-employee view. Not hidden behind a role, not switchable on request: it is not built.
- Remy only looks at a screen while someone is asking it something.
- What it sees and hears is never stored, and never sold.
- Nothing leaves Remy except through an export you start yourself.
- EU hosting, a signed DPA, and support for your DPIA and works-council process.
- Bring your own model account — Azure, Bedrock or Anthropic — if your policy needs it.
- Audit logging and role-based access for every administrative action.
Two doors, and it is worth taking the right one
Remy at Work — you are here
- Your staff use several systems to get one job done
- Software is something you buy, not something you sell
- You have a migration, a release or a new procedure coming
- Procurement, a DPIA or a works council will be involved
- Your directie needs to get comfortable with this too
Remy Onsite — the other door
- You make a product and your users are the ones getting stuck
- You want fewer support tickets and faster activation
- You would rather read a price than book a call
- One script tag, live the same day
Tell us what you are changing next
One conversation about what is coming and how your people work today, and we will tell you honestly whether Remy would make it land faster. No slide-ware, no procurement dance to get to a first answer.