Culturro is the HR AI Studio. Since 2017 we've worked with more than 30 organizations on the things HR is actually judged on, and we've built two products of our own inside that work. When we write your AI strategy, we're writing it from the same side of the table you sit on.
What the function is for, what it owns, and what it gets measured on over the next three years.
The operating layer. How work moves, who approves what, and which policies survive contact with a real week.
Measuring what people experience, then changing the things that produced it.
Turning a capability gap into something people can practice, at a scale a small L&D team can carry.
The managers in the middle, who decide most of what your engagement survey ends up saying.
Where AI belongs in your function, in what order, and what stays a human decision. Then the systems that roadmap calls for, built one use case at a time. It's the same five kinds of work, with a tool none of them had before.
All six land in the same place: how well your people perform, and how long they stay.
Culturro started in 2017 as a people consultancy, and that work is still the ground we come from. Since then, more than 30 organizations have brought us in on the five areas above, usually because something they measured had stopped moving.
Then we built Agnya, an employee engagement platform, because a diagnosis is only worth what happens after it. Managers needed something inside their week rather than a report at the end of a quarter.
Risely came next: leadership development, delivered by an AI coach called Merlin that works where managers already are, in Slack and Teams. Merlin has coached 5,000+ people in 40 languages, and it's still running. We still ship to it.
Today Culturro is the HR AI Studio, and both halves of that history do the work. The consulting tells us what a function can absorb and in what order. The products taught us what it takes to put AI in front of employees and have them still be using it a quarter later. Your strategy gets written from both, which is why we write it before we build anything.
2017
In the people domain since
30+
Organizations worked with
5,000+
People coached by Merlin
40
Languages in production
The parts nobody puts in the deck.
Where the data sits, who can see it, what's retained, whether anything trains on your people. We've answered those questions from the vendor side, on our own product, inside other people's companies. So we design for them from the start, and write the answers down before your CIO asks.
A system people don't trust gets routed around quietly, and the dashboard is the last thing to notice. What earns use is narrow scope, reasoning you can see, and a person who makes the call. We learned that on our own users. Some of them stopped until we changed how it worked.
Every renewal conversation ends with someone asking what it actually moved. If which number, whose it is, and when it gets looked at weren't settled beforehand, there's no answer worth having. We've been on the wrong end of that question. Now we write it down before anything gets connected.
We're a team of AI engineers, domain experts and organizational psychologists, and we bring in the mix each engagement actually needs. The person on your first call stays on it, so nothing gets handed on to someone you haven't met.
Engineer first, at Nagarro and Oracle. Then four years at Lafarge in Paris on strategy and M&A across their Asia portfolio, which is where the habit of starting from a P&L line comes from. Founded Culturro in 2017, built Agnya, then Risely, and has worked on the people side of more than 30 organizations since. HEC Paris MBA.
Works on HR-AI strategyUse-case sequencingThe business case
AI can inform, surface, rank, summarize, or draft. A person makes every call about a person, and the system gets built so it can't do otherwise. Past that line, where the controls sit and who signs off are yours to set: we recommend, and we put the recommendation in writing.
Some ideas aren't worth the trust they'd have to earn. Others need data that's sitting in five different systems. We'd rather tell you in month one, even when that ends the conversation. Finding it out in month nine costs you the year.
Built in your environment, on the model provider your security team approves, with that provider's no-training and retention terms in writing. Code, prompts, evaluation sets, documentation, and runbooks are yours, with no dependency on a Culturro platform. Every technical decision gets explained in plain English, because you're the one who'll have to defend it.
The strategy month is a fixed fee. Each use case after it is quoted as a fixed fee for the agreed scope once the proof has run, with the number it's meant to move written down first. No time and materials. A support period after handover is included and scoped with the build; hosting and model usage are billed to you by your own providers. If you want us on the roadmap after that, it's a month-to-month retainer that a delivered system doesn't need.
Bring the numbers you already report on, and we'll tell you where AI would move them and what we'd do first.
Thirty minutes, on your function.
