Solution · Mid-size and large companies
AI across the whole company. With rules.
Kentor maps how each area really works, connects the systems you already have and puts agents on the routine with the permissions, approvals and logging the company requires. AI scales without anyone losing control of what it sees and does.
Kentor Brain
Company assistant
via Kentor Brain
Pedro · Sales
What's the margin on customer 4812's contract?
That information belongs to Finance and you don't have access. I can ask Juliana to answer.
Company assistant
via Kentor Brain
Juliana · Finance
What's the margin on customer 4812's contract?
The contract's gross margin is 31%, below the 35% target for the portfolio.
P&L by contractOmie · owner: Finance
Customer 4812 · monthly contract · gross margin 31%
Mid-size and large companies today
Where AI stalls at a large company.
The pain
AI is already in, and nobody controls what it does.
Instead of everyone using whatever AI they like with whatever data they like, agents work with written rules. What matters waits for approval, the forbidden is blocked beforehand and every action goes in the log.
How Kentor does it
Kentor Bot gives the company approval, limits, automatic review against the rules and an audit of every agent action.
Kentor BotToday's audit, all areas
- 07:52Email to supplier blockedDid not happenFinance does not send email on its own
- 09:12Contract deadlines checkedAllowed
- 09:58Access to the bank website deniedDid not happenBlocked by the bank rule
- 10:31Mirante proposal savedAllowed
- 10:42Message sent to MiranteAllowed
The pain
Nobody knows what the AI can see.
The Sales agent doesn't read HR's payroll. The same question gets different answers depending on who asks, and whoever can't see it is pointed to whoever can answer.
How Kentor does it
Kentor Brain connects the systems with the permissions they already have and applies those permissions to people and agents, by team.
Kentor BrainCompany assistant
via Kentor Brain
Pedro · Sales
What's the margin on customer 4812's contract?
That information belongs to Finance and you don't have access. I can ask Juliana to answer.
Company assistant
via Kentor Brain
Juliana · Finance
What's the margin on customer 4812's contract?
The contract's gross margin is 31%, below the 35% target for the portfolio.
P&L by contractOmie · owner: Finance
Customer 4812 · monthly contract · gross margin 31%
The pain
Each area tells a different version of the same process.
All areas' processes on one map, as they happen, with the shortcut nobody wrote down. The opportunities in order of return, so leadership can decide where AI goes first.
How Kentor does it
Kentor OS interviews many people at once, without stopping the operation, and ties every finding to the excerpt from who reported it.
Kentor OSCompany opportunities
All areas, ordered by time to return.
Daily reconciliation
FinanceR$ 33.280 per year
8 h per week · 2 interviews
Ticket triage
Customer serviceR$ 24.960 per year
6 h per week · 4 interviews
Sales follow-up
SalesR$ 20.800 per year
5 h per week · 4 interviews
The pain
The pilot worked. It never got past the first area.
Each area comes in with an owner, with training built on real work and with the yardstick of what needs to improve. You track usage by area, week by week.
How Kentor does it
Implementation rolls the platform out area by area, in 4-to-6-week cycles and in shadow mode before release. Training gets each team using it day to day, with adoption measured.
Implementation and TrainingImplementation · Rollout by area
Plan with your team
- SalesDone
- FinanceDone
- Customer service, in shadow modeIn progress
- OperationsNext
Governance
Governance you can see.
We don't ask you to trust us. We show you: who sees what, what needs approval and the log of every action.
Everyone sees what they can see. Including the AI.
Permissions apply by team. Whoever couldn't see a piece of data in the source system can't see it in Kentor either, person or agent.
What matters waits for your OK.
Customer message, discount, posting: the agent prepares and asks first. You define what needs approval and from whom.
Every action, logged.
What the agent did, in which tool, who approved and what the rules blocked: it's all in the log, to check whenever you want.
Data handled according to LGPD.
Each connection is enabled by the company, team by team, and can be turned off at any time. Data handling follows LGPD.
- Sensitive fields only for the team with access
- A written rule blocks the action beforehand, and the refusal is logged
- A reviewer checks every action against the rules you wrote
- What the agent learned is noted, and you can delete it
- Switch models whenever you want: the context stays
Area by area
The same rule, area by area.
Areas where routine volume is highest, and where governance weighs most.
The pain
The close depends on manual checking in each area.
Reconciled every day, with approval.
The finance agent reconciles, sets aside what didn't match and prepares collections. Nothing is posted or sent without the OK of whoever is accountable.
What goes out
- Manual check
- Collections with no standard
- Reconciliation checked every day
- Collections with approval
- Discrepancy flagged early
How Kentor does it
- Cross-checks statements, sales and the system
- Sets aside the discrepancies with the receipt
- Asks before posting or charging
Closing without spreadsheets · running in Case Pé de Sopa
Before and after
What changes in the team's day.
- AI in the company
Without Kentor: Each area with its own tool, and people pasting company data into personal AI
With Kentor: One AI layer for all areas, with the rules the company defines
- Permissions
Without Kentor: Nobody knows what the AI can read
With Kentor: Whoever couldn't see it in the source system can't see it, person or agent
- Systems
Without Kentor: ERP, CRM and spreadsheets that don't talk to each other, the same customer under three names
With Kentor: Systems linked, and the same customer becomes a single record
- Pilots
Without Kentor: Proof of concept that excites and doesn't get past the first area
With Kentor: AI enters through the process the map pointed to and scales area by area
- Control
Without Kentor: Finding out about the problem after it happened
With Kentor: Approval before what matters, rules that block the forbidden and a log of every action
- Adoption
Without Kentor: License bought, usage nobody measures
With Kentor: Training by area and usage tracked by person and by area
How we implement
One area, then the next.
The map points to where to start. Each area enters shadow mode, with the same rules, and the next follows once the yardstick is met.
Assessment
A conversation and an X-ray of the operation.
Implementation
Map
Kentor OS running with your areas, in parallel.
Kentor OS
Construction
Brain and agents on your processes, in 4-to-6-week cycles, each ending with something running and with an owner.
Kentor Brain and Kentor Bot
Shadow mode
The team operates, Kentor follows along and adjusts until the target is met.
Implementation
Ongoing operation
If you prefer, Kentor runs and evolves the agents day to day, with follow-up meetings.
Implementation
Implementation · Area by area
Plan with your team
- SalesDone
- FinanceDone
- Customer service, in shadow modeIn progress
- OperationsNext
How Kentor comes in
First understand. Then automate.
The same path in any area: AI knows the business before acting, and people approve what matters.
- 01
Understand
We map how the area really works, with AI interviews, and point out where AI pays back most.
Kentor OS - 02
Organize
We connect the systems and bring together what the company knows, with rules on who sees what.
Kentor Brain - 03
Automate
We put agents on the routines that weigh most. They act in the team's tools and ask for approval when it matters.
Kentor Bot - 04
Track
We stay on until the routine sticks: adjustments, training by area and tracking of what changed.
Implementation and Training
Connections
Inside the tools the team already uses.
Kentor works with what you already have, with the permissions you grant.
- Salesforce
- HubSpot
- Microsoft Teams
- Outlook
- SharePoint
- OneDrive
- Excel
- Slack
- Jira
- Zendesk
- Google Drive
- Claude
- Gmail
- Google Calendar
- Google Sheets
- Pipedrive
- Omie
- Notion
- Google Docs
- Google Meet
- Zoom
- ClickUp
- Trello
- Asana
- Monday
- Dropbox
- Canva
- Figma
- Google Ads
- Google Analytics
- Mailchimp
- Calendly
- Typeform
- Airtable
- Intercom
- Stripe
- QuickBooks
- Fathom
- Fireflies
- Granola
- tl;dv
Frequently asked questions.
Will AI see data the person couldn't see?
No. Brain inherits the permissions from the source systems and applies them to people and agents, by team. Whoever couldn't see it there can't see it here.
Does it replace our ERP or CRM?
No. Kentor works on top of the systems you already have: it reads with the permission you give and returns the work in the same place.
What about LGPD and the log of what the AI did?
Every agent action is logged, with the time, the tool and who approved. What matters goes through approval, and data handling follows LGPD.
Can we start with one area and expand?
This is how we do it. The map points to where AI pays back most, the first area goes into shadow mode, and the next ones follow with the same rules.
Who operates the agents afterward?
Your team, trained by area. If you prefer, Kentor operates and evolves the agents day to day, with a follow-up meeting.
See where AI comes in first, and with what rule.
We map the areas with your team and show the priorities, with the math and the governance for each.