OSUnderstand your company. From the inside out.
Kentor OS talks to the people who do the work and turns what it hears into process maps and priorities with a business case.
Aroeira Distribuidora
Kentor OS
- Campaigns
- Knowledge
- Process maps
- Ask OS
Campaigns
Purchase approval
Interviews in parallel · Operations, Finance and Purchasing
Participants
- JUJulianaOperationsDone
- CACarlosFinanceDone
- COPurchasing teamPurchasingIn progress
Key points
Atalho
Urgent purchases go straight to finance. The spreadsheet is only updated afterward.
Juliana's interview
Fora do sistema
Purchasing tracks urgent orders in a side spreadsheet.
Carlos's interview
Example with a fictional company
Some Kentor clients and partners
Every slow handoff and every manual task costs money every day.
AI turns that friction into capacity, margin and room to grow, as long as it goes in the right place.
Slow handoffs
The order waits in someone's inbox and nobody sees where it stopped.
Repetitive manual task
The same check, every day, by people who could be deciding.
An exception only one person knows how to handle
When that person is out, the process stops.
Start with the people. See the whole picture.
Three steps, and each one ends in a deliverable you can take to the board.
Interview · Juliana, Operations
How does a purchase request reach you?
Through the team's WhatsApp. I log it and send it to the manager for approval.
And when the purchase can't wait?
Then it goes straight to finance, and the spreadsheet can wait.
You can't improve what you don't understand.
OS lays out the steps, the decisions and the handoffs that keep the company running, with who does each one and in which tool. Including what nobody wrote down.
From the interviews
Order recorded
Juliana · Operations
Is it urgent?
Decision with no written rule
No · the official path
Manager approves
Area manager
Purchasing quotes and closes
Purchasing
ERP
Opportunity
The urgent-purchase shortcut leaves no trace. It can be recorded and approved in the same flow.
Less time assembling. More time creating value.
Until the first decision
Without Kentor OS: Months of workshops before knowing where to start.
With Kentor OS: Priorities from parallel conversations, without stopping the operation.
Where the knowledge lives
Without Kentor OS: In slides, spreadsheets and in the heads of whoever was in the room.
With Kentor OS: In a single layer that people and agents query through Kentor Brain.
Implementation
Without Kentor OS: Tool bought before understanding the process.
With Kentor OS: Focused on what the map showed, with the Kentor team.
Business impact
Without Kentor OS: A pilot that excites in the meeting and disappears in three weeks.
With Kentor OS: Return measured in time, cost and capacity.
The map becomes context and work.
Everything OS learns goes into Kentor Brain and becomes the context for Kentor Bot's agents, with each area's permissions.
Maps
Kentor OS
Talks to the team, designs the processes and shows where AI pays back the most.
You are here
Remembers
Kentor Brain
The mapped processes go into Brain and become context, with source and permission.
Explore Kentor BrainExecutes
Kentor Bot
Bot's agents execute with this context, at the point the map indicated.
Explore Kentor Bot
A clear picture of the operation starts with a conversation.
Pick an area or a process that holds back the operation and see it mapped, with what to tackle first.
Example with a fictional company
Questions about Kentor OS
Can we shape the conversations around our questions?
Yes. You define the goal, the topics, the questions and how OS should dig deeper, or start from a ready-made process discovery script.
How does OS use what it already knows?
Accumulated knowledge gives context to the next conversations. Known gaps become targeted questions, and the team decides the scope and who takes part.
Who can access the knowledge?
You choose the campaigns and who takes part. Each campaign's permissions control access to the answers, and what goes into Kentor Brain follows the permissions by area.
Is it a performance review?
No. OS asks about the work, not about the person. The goal is to find where the process gets stuck.
How is it different from process mining?
Process mining reads system logs and only shows what was typed in. OS talks with the people who do the work and captures what isn't in any system: the side spreadsheet, the exception, the judgment call.
Who implements the solutions?
You can implement on your own or with Kentor's Implementation, where our team builds it with you, starting from the approved business case.
How much of my team's time does this take?
The conversation happens at each person's own pace, without stopping the operation.