This article was written by Atlas following an interview with Emeric Ernoult, CEO, conducted on September 28, 2026.
Emeric Ernoult, CEO of Agorapulse, used 
Lovable to build an internal application that centralizes one-on-ones, meetings, OKRs, decisions and performance tracking. Over the years, Agorapulse has nonetheless used several pieces of software to structure its HR and internal knowledge: HiBob, Lucca, Lattice and Slite.
But when you ask Emeric what his main HR tool is today, he does not name any of these products.
“The main HR tool we have today is the one we built in-house.”
This tool is called Radical.
Emeric developed it with Lovable, without being a developer himself. Radical centralizes one-on-ones, team meetings, OKRs, planning, decisions, tasks, follow-ups and performance plans.
And it is not an isolated case. For another workflow, Agorapulse stopped using a SaaS specialized in sales commissions and replaced it with an artifact built with Claude.
Why did Agorapulse build its own management tool?
The starting point is not a desire to replace every HR tool. 
HiBob remains Agorapulse's HRIS. The problem Emeric faced has more to do with the day-to-day practice of management.
Agorapulse had notably tried to centralize meeting notes in Slite, asking everyone to add their recaps there.
It does not work as hoped.
“Putting your one-on-one notes in a system that wasn't built for that doesn't work.”
Above all, Emeric lacks visibility into what is really happening. For example, he wants to be able to check that his managers are actually holding their one-on-ones with their direct reports.
“If I wanted to know whether my managers were doing their one-on-ones with their own team members, I had absolutely no visibility. I had no idea. (…) By the time I realized a manager hadn't been doing their job, they had already not been doing it for 18 months.”
Radical was born largely from this need: turning these management practices into a system structured enough to be tracked.
How did Emeric Ernoult build Radical with Lovable?
Emeric uses Lovable to develop Radical. The application now brings together one-on-ones, team meetings, OKRs, annual and quarterly planning, performance plans, decisions, tasks and follow-ups.
Meetings are captured and transcribed. AI then centralizes the tasks, decisions and follow-ups that come out of them. Emeric keeps evolving the application himself.
“Someone who isn't a developer to begin with can do incredible things.”
He also uses Claude Code, notably to run cross-audits with Lovable and look for problems in the software's structure, logic or security.
“Not everything is perfect, but the thing works.”
In his view, the capabilities of these tools have improved dramatically. Whereas about a year and a half ago they were mostly used to produce proofs of concept, he now considers it possible to build applications with them that people actually use.
How does Radical structure one-on-ones at Agorapulse?
Radical does not create Agorapulse's management method. It equips it.
For several years, Emeric has used a system called What Success Looks Like. For each role, a one- to two-page document describes the core responsibilities and expected accomplishments.
Every week, during the one-on-one, the manager must select one of these items. They can recognize strong performance, ask the team member to show how a responsibility is being fulfilled, or address a problem that has already been identified.
This weekly cadence is meant in particular to avoid discovering six months later that an important topic was never really addressed. Radical brings this follow-up into the same system as meetings, OKRs and performance plans.
Why does Agorapulse keep Slite?
Radical has not replaced 
Slite. For Emeric, the two tools serve two different types of information.
Radical holds the “living data.”
“All the meetings, all the decisions, all the tasks, all the next steps, all the follow-ups, everything that's alive and happens in meetings, team meetings or one-on-ones, that's in Radical.”
Slite, by contrast, holds the knowledge that has been formalized.
“The fixed data, the stuff we took the time to document, the processes, product discovery and so on, that's in Slite.”
Agorapulse chose Slite after also looking at 
Notion. The company was first and foremost looking for a knowledge base, whereas Notion's flexibility was seen as added complexity.
Since then, Emeric believes Slite has made a lot of progress on AI. Salespeople can notably query it from 
Slack to find product information, such as whether a feature or API access exists.
How did Agorapulse replace a commissions SaaS with Claude?
The second case goes further than Radical, since Agorapulse actually stopped using a purchased piece of software and replaced it with a tool built in-house.
The company was using an American SaaS specialized in sales commission management. The problem was how well it adapted to Agorapulse's own rules.
“We stopped because it couldn't adapt to our level of complexity. For us, the rules change all the time.”
Agorapulse therefore built its own system with Claude. The work was not done by a team of developers, but by someone on the team.
Getting it right still took time.
“It took a month and a half, so it took a lot of fine-tuning time to get it working. But today, it's the Claude artifact that does all of that.”
The case is interesting because the motivation is not purely financial. The existing software could no longer keep up with how variable the internal rules were. The in-house tool was therefore built specifically around this complexity.
Is building with AI really cheaper than buying a SaaS?
Agorapulse's experience adds nuance to the idea that building a tool with AI costs next to nothing.
The commissions artifact took about a month and a half of work before it worked properly. Radical also still takes up Emeric's time, as he keeps evolving it.
So the cost does not disappear. Part of the license and of the dependence on a vendor is replaced by internal time spent on design, iteration, review and maintenance.
What changes above all is how accessible development has become. People who previously could not have built business software on their own can now try to do so.
This is precisely what Agorapulse's two experiences illustrate: on one side, a non-developer CEO building his own management tool with Lovable; on the other, a specialized SaaS replaced by a system developed in-house with Claude.
Summary of the software this article mentions in Agorapulse's stack
| Status | Workflow | Tool | Usage |
|---|---|---|---|
| In use | Management / HR | Radical | Internal app for meetings, one-on-ones, OKRs and performance |
| In use | AI-assisted development | Lovable | Building and evolving Radical |
| In use | AIAI-assisted development |  Anthropic | Commissions artifact, presentations and CRM migrationCross-audits of Radical |
| In use | Knowledge management | Slite | Knowledge base and former home for meeting notes |
| Replaced | Knowledge management | NotionReplaced | Alternative considered against Slite |
| In use | Communication | Slack | Access to Slite knowledge, among other uses |
| Replaced | CRM |  SalesforceReplaced | CRM whose migration is being handled in-house with Claude's help |
| In use | CRM / marketing |  HubSpot | Destination of the migration |
| In use | AI agents | Grok Bot | Agents running tasks on a cloud computer |
