About Anumat
Every request deserves a clear next step.
Why Anumat exists
In many offices, a request still travels by chat message, printed form and memory. A purchase waits on a desk. A leave request is approved in one group and lost in another. Someone walks from office to office asking who still needs to sign.
Anumat exists so that work no longer depends on who remembers to follow up. Every request gets a clear path, a visible next person and a record that stays.
Our name is a Khmer word
anumat · to approve
Anumat is written អនុម័ត in Khmer and means to approve: the moment every request is waiting for. We built the product in Phnom Penh for teams who work in Khmer and English, so the name stays in the language our users speak.
Our mission
Help every team in Cambodia get a request decided the same day, without anyone having to chase it.
Our vision
Every request finds its approver, in the language people work in, and every decision stays on the record.
How a request moves
Anumat brings requests, forms and approvals into one workspace. Instead of searching through messages to find who should decide, your team can see the request, its approvers and its history together.
Forms capture the details. Workflows route the request. Comments, attachments and activity history help people understand what happened and why. Workspace roles determine who can take part.
What we believe
The path is always visible
Who has the request, what happens next and what was decided are never a mystery.
Familiar beats novel
Approvers are busy managers, so every control behaves like the tools they already know.
Khmer is first-class
Khmer is designed in from the start, not translated at the end.
The record is the product
History, attachments and decisions stay trustworthy, so anyone can see what happened and why.
See how your first request moves
Explore the product or follow the guide to set up a workspace and submit a request.