Proof and method
Evaluate Lontra with concrete reference points.
A production deployment, a review-time reference, and reactions to demonstrations. See the context behind each, then use a practical method to assess what Lontra contributes to your own team.
The client's name stays at their discretion.
Reference points
Understand what each reference describes.
100,000
people in the retail group where Lontra is in production, across more than 40 countries
Headcount and country count describe the client group. They do not measure active users or the scope actually deployed.
> 2 h → < 1 h
reported time per full review cycle, per employee
Preparation, conversation, write-up, and entry. This client reference is not a forecast for your team; the public summary does not specify sample size or observation dates.
5
respondents minimum before any aggregate
Minimum threshold for aggregate HR views. Suitable groups and access rules are also required; this threshold alone does not guarantee anonymity.
What we were told
Their reactions during demonstrations.
These prospect reactions concern a demonstration. Excerpts are condensed, translated where needed, and anonymised by role and sector. They describe interest in the product, not measured results after deployment.
“This back-and-forth between managers and their people, there isn’t enough of it today. That is what I liked.”
“We are trying to build out so many trainings for managers, and it’s just the two of us. You just created a training within minutes, and it could even capture our style.”
The method
A method for setting up and reviewing your trial.
Start with a specific issue, decide what will make the trial useful, and set a review date. This method guides your evaluation; it does not describe a completed customer study.
Step 01
Gap
A KPI shows a difference between two comparable populations during a defined period.
Step 02
Question
The accountable team states what it needs to understand without assuming the cause.
Step 03
Conversations
Lontra gathers specific examples from the relevant people by voice or in writing.
Step 04
Context
Recurring elements, differences, obstacles, and counterexamples are structured with their sources.
Step 05
Hypothesis
A practice is presented as something worth testing, with its limits, not as the proven cause of the gap.
Step 06
Human action
The manager or accountable leader chooses what to adapt, test, and follow in their scope.
Step 07
Measurement
At the agreed date, the team reviews the action and chosen indicator. A later campaign can gather fresh feedback; it is separate from the single trial campaign.
A useful recommendation always shows what it rests on, and what it cannot yet prove.
Rigor
Rules for reading the evidence
In a real setting, every result stays connected to its scope, population, period, sources, and interpretation limits.
Comparable scope
A useful comparison specifies populations, periods, and context differences. Otherwise, it remains a lead worth investigating.
Facts, synthesis, hypotheses
Raw examples, recurring elements, and inferences are not presented as one level of truth.
Counterexamples
A practice is not presented as universal when comparable teams succeed differently or context explains the difference.
Measurement after action
Progress is reviewed after a human decision and a defined period. Lontra does not promise in advance how much of the gap will be recovered.
The simplest thing is to check for yourself.
Try a conversation and review the resulting brief. Check whether it helps you prepare a real discussion, then choose a group to invite.
One campaign, up to 30 invitations over 60 days, no credit card.
Rolling out across countries, or want to look at your case together? Book a thirty-minute conversation.
30 minutes. Your problem, your teams, your measure.
Less theater. More humans.