About
We built the thing that was missing.
Every company between about five and a hundred people hits the same wall: it outgrows the point where one person can hold the whole operation in their head, long before it can justify hiring somebody to look after it. The software available at that moment mostly stores employees. Almost none of it understands how the company runs.
The gap is not a feature. It is a modelling decision. An HR database holds a person, a contract and a folder of documents, and from those three things it genuinely cannot tell you who owns supplier reconciliation, which responsibilities have no backup, or what would have to move if a particular person resigned tomorrow.
Orglume models the relationships instead: person, role, responsibility, authority, skill, access, objective. That structure is unglamorous to build and it is the whole reason the product can answer a question nobody thought to record the answer to.
The AI sits above it rather than in place of it. It makes the structure understandable and actionable — and because the structure is real, every answer can name the record it came from. When the subject is a colleague, that matters more than it does anywhere else.
What we believe
Six decisions that shaped this.
Each of these rules something out, which is the only reason any of them is worth stating.
The structure is the product
Deterministic records underneath, AI reasoning above them. Reversing that order produces a system that makes confident, plausible, occasionally wrong statements about people — which is the worst possible failure in this category.
Responsibilities outlive people
The thing a business depends on is not a person's job title. It is that the monthly filing happens, that suppliers get onboarded, that escalations reach somebody. Modelling that separately from who currently does it is what makes a handover possible.
Software does not make employment decisions
It can tell you that six responsibilities are overdue. It cannot tell you what that means about the person who owns them, and any product that offers to has misunderstood what it is for.
Employees are users, not records
Most workforce software is designed entirely for the employer. That is a mistake commercially as well as ethically, because the people who have to use it every week are the ones it treats as rows.
Say where it stops
Every feature page on this site names what the feature does not do. We do not calculate payroll, run rotas, enforce authority or control your identity provider. Saying so is more useful than a page of capabilities you have to test to disbelieve.
A small company should not need a specialist
If this requires somebody whose job is to look after it, it has failed the companies it is for. Setup is an afternoon, the employee experience is under a minute, and nothing here needs training to use.
The measure
One sentence we want to hear from a customer.
“I can finally see who actually owns everything in my business.”
That is the outcome the product is built around, and it is worth considerably more to an owner than being told their employee database is complete. If the first fifteen minutes do not move somebody towards it, the rest of the feature list does not matter.
Questions, disagreements and requests all go to [email protected], and they reach a person.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]