An AI buddy for your people — and for the work behind them
Remy at Work puts a screen-aware buddy inside the tools your staff already use. It helps everyone get the job done, shows you which processes are quietly costing you most, takes the repetitive parts over, and brings your directie along with it. Licensed and implemented per organisation — we start with a conversation, not a demo request.
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 hard part was never the model
Nobody in your building is short of AI. What is missing is anyone actually using it on the work in front of them — and any way to prove it happened.
The licenses are bought. The habit isn't.
Most organisations have already paid for AI. It sits unopened, because a chat box asks people to know what to ask before it can help them.
Nobody can see where the work actually goes
You can feel that some processes are expensive. Proving which ones, and by how much, normally takes a consultancy and a quarter.
The directie is expected to lead on something they've never used
A board asks about AI. A course explains the theory. Neither gets someone confident in the tools they open every morning.
A colleague who knows where everything is
Helps everyone, in the tools they already have
Remy lives inside your ERP, CRM, portal or admin console. Someone asks in plain words, Remy answers and flies a cursor to exactly where to click — then walks them through the steps.
Shows you where the work is stuck
Every question asked, every abandoned flow, every place people slow down. Not a survey — the real friction, in aggregate, as a by-product of helping.
Takes the repetitive parts over
The steps we find worth automating, Remy does in the same interface your people use. It does the work, a person confirms it. No integration project.
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 small and pays for the next step
Every engagement begins with the Scan. What follows is scoped from what the Scan actually found — so nothing is bought on a hunch.
- 1
Scan
Weeks 1–6
We put Remy in one department and instrument it. You get an adoption baseline, a map of where work gets stuck, and a ranked list of what to automate first — with hours and euros attached.
- 2
Onsite
Ongoing
Remy stays, across the tools that matter. Licensed per year. This is the part everyone feels day to day, and the spine of everything else.
- 3
Flows
Per process
We build the automations the Scan found and run them. Human-in-the-loop first: Remy does the steps, your person confirms.
- 4
Directie
Per cohort
The leadership programme. Remy on their own screens, cohort sessions, and a measured AI-vaardigheid score per person and team.
- 5
Partner
Quarterly
A re-scan, an updated roadmap, new flows, and a review with your MT. The processes keep moving, so the map has to as well.
What every engagement has in common is a license at its centre. What changes per organisation is the size — how many people, how many tools, how many processes — 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.
- Process insight is aggregate and anonymous by construction — never per-employee reporting.
- Remy only looks at a screen while someone is asking it something.
- What it sees and hears is never stored, and never sold.
- 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
- You have staff working in tools they find hard
- Software is something you buy, not something you sell
- You want to know which processes to fix before you fix them
- 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 where your people get stuck
One conversation about how your organisation actually works, and we will tell you honestly whether a Scan is worth it. No slide-ware, no procurement dance to get to a first answer.