Solution · Small and mid-size companies
The company runs. Without everything going through you.
Kentor understands how your company really works, brings together what it knows in one place and puts AI on the routine that today depends on you or a spreadsheet. The team approves what matters, and you get back to what only you do.
Kentor Bot
- Mirante proposal with a 12% discountAbove policy: needs your OKWaiting for your OK08:50
- Day's list delivered to sales6 accounts, each with the reason07:00 · Done
- CRM updatedNext step on every deal06:45 · Done
- Collecting overdue invoices4 of 6, each in the customer's tonenow · In progress
- Yesterday's reconciliation closedNo discrepancy07:40 · Done
- The week's expenses classifiedWith the receipts07:50 · Done
Small and mid-size companies today
Where the company depends on you.
The pain
Everything goes through you.
You see which decisions and tasks only move when you're there, and what can come off your desk first, with the math in hours and money.
How Kentor does it
Kentor OS talks to the team with AI, draws how the company really works and points out where AI pays back most.
Kentor OSProcess map
How the company works · 4 processos
| Process | Steps |
|---|---|
| Discount approval | 3 |
| Commercial proposal | 5 |
| Month-end close | 6 |
| Reply to the customer | 4 |
Inferred from the conversations, with who mentioned it
Discount approval
LeadershipR$ 16.640 per year
4 h per week · 3 interviews
The pain
What the company knows is in the heads of two people.
Price, policy, customer history and the agreement with the supplier are written down and up to date. Newcomers learn faster, and whoever leaves doesn't take the company with them.
How Kentor does it
Kentor Brain links the systems and documents you already use and delivers that context to people and AI, with each one's permission.
Kentor BrainHow we work · Rule
Sales policy
A discount above 10% needs leadership approval.
3 sources · 6 calls
Historyprevious values are kept
- 10/11The discount limit without approval dropped to 10%.
- 14/10Payment in three installments was added.
- 01/09Record created from the sales policy.
The pain
The routine gets done by hand, when there's time.
Follow-up, reconciliation, reporting, repeated questions: the work comes out ready every day, and the team reviews instead of starting from scratch.
How Kentor does it
Kentor Bot's agents work in your tools, ask before sending and log every action.
Kentor Bot- Preparing today's outreach4 of 6 readynow · In progress
- Day's list delivered to the team6 accounts, each with the reason07:00 · Done
- Mirante proposal with a 12% discountAbove policy: needs your OKWaiting for your OK08:50
- CRM updatedNext step on every deal06:45 · Done
- Opportunity scores recalculatedThe whole base06:30 · Done
The pain
There's nobody here to implement AI.
You don't need to hire a technology team. AI comes into the routine ready, and each person learns to use it on their own work.
How Kentor does it
Implementation gets everything running with your team, in short cycles, and Training takes each area to everyday use.
Implementation and TrainingImplementation · Cycle 1
Plan with your team
- Area map with Kentor OSDone
- Brain with the documents and the CRMDone
- First agent in shadow modeIn progress
- Team trainingNext
Where AI comes in
Where AI comes in at a company like yours.
The areas where the routine weighs most on a lean team. Each with what comes off your plate.
The pain
The follow-up gets left for later, and the lead cools off.
No lead forgotten.
The sales agent looks at the base every day, writes each contact's message and updates the CRM. The salesperson reviews and sends.
What goes out
- List made by hand
- Follow-up that never goes out
- Outdated CRM
- The base reviewed every day
- The message ready to review
- The CRM up to date
How Kentor does it
- Reads the CRM and each account's history
- Writes the reason for contact and the message
- Asks before sending and updates the CRM
Outreach ready for the sales rep · running in Case Lobby Tech
How we implement
We implement together with your team.
One routine at a time, starting with the one that gives back the most. The team learns by doing, and Kentor stays until the routine sticks.
Assessment
A conversation and an X-ray of the operation: where the routine weighs most and where to start.
Implementation
Map
Kentor OS runs with your areas, in parallel, and prioritizes with you what to tackle first.
Kentor OS
Construction
Brain and agents built on your processes, in 4-to-6-week cycles, each ending with something running and with an owner.
Kentor Brain and Kentor Bot
Routine
Shadow mode before release, training for whoever operates, adoption measured and evolution every month.
Training
Implementation · Cycle 1
Plan with your team
- Area map with Kentor OSDone
- Brain with the documents and the CRMDone
- First agent in shadow modeIn progress
- Team trainingNext
Before and after
The company that doesn't depend on you to keep moving.
1Decisions
Everything goes up to the owner, because only they know
With Kentor: The team answers with the information at hand and escalates only what needs you
2Routine
Follow-up, reconciliation and reporting done by hand, when there's time
With Kentor: Agents run the routine in your tools and ask for the OK before what matters
3Knowledge
Price, agreements and policy in two people's heads
With Kentor: What the company knows, written down, up to date and with the source
4Tools
System, spreadsheet and WhatsApp that don't talk to each other
With Kentor: The systems you already use linked, without replacing any
5Where to start
Every vendor sells an AI tool
With Kentor: A map of what AI takes off your team first, with the math
6Grow
More customers call for more people in the same proportion
With Kentor: More customers with the same team, because the routine doesn't depend on hands
Governance
Small, but with rules.
A small company has customer, salary and pricing data too. AI comes in with the rules you set.
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.
Case
Kentor itself operates this way.
A lean team, several areas and agents connected to the process, each with an owner.
Ourselves
Kentor
Sales, marketing, finance and people running with connected agents.
View caseConnections
Inside the tools the team already uses.
Kentor works with what you already have, with the permissions you grant.
- Gmail
- Google Sheets
- Excel
- Google Drive
- Omie
- Pipedrive
- HubSpot
- Notion
- Slack
- Google Calendar
- Outlook
- Microsoft Teams
- Google Docs
- Google Meet
- Zoom
- Salesforce
- ClickUp
- Trello
- Asana
- Monday
- Jira
- OneDrive
- SharePoint
- Dropbox
- Canva
- Figma
- Google Ads
- Google Analytics
- Mailchimp
- Calendly
- Typeform
- Airtable
- Zendesk
- Intercom
- Stripe
- QuickBooks
- Fathom
- Fireflies
- Granola
- tl;dv
Frequently asked questions.
Do I need to switch my system, CRM or ERP?
No. Kentor works with the tools you already use: it reads what's there, with the permission you grant, and returns the work in the same place.
Do I need someone in IT?
No. Kentor implements together with your team, trains whoever will use it and follows the adjustments until the routine sticks.
What about company and customer data?
Every person and every agent sees only what they can see. The agent asks for approval on what matters, every action is logged and data handling follows LGPD.
Where do we start?
By the map. Kentor OS talks to the team and shows where AI pays back most, with the math. The first agent goes in there.
What stays with the company?
Everything that was built: the mapped processes, the knowledge in Brain and the agents' configuration.
Take off your desk what doesn't need you.
We map the company with your team and show what AI takes over first.