ISA Saúde
Payroll team
Home care, Tako customer since 2024
ISA Saúde's payroll team opened up, live, the dashboard, alerts and automations it built on top of Tako, and the Tako team showed others already running across the customer base. The full recording, with the chat questions answered.
< 2 days
to check a 300+ people payroll
It used to take three or four days, checking by hand.
~15 days
of work saved per month
The team's own estimate, adding up the dashboard, alerts and information requests.
1 click
to generate the contracts for 20 hires
Downloading documents and placing signatures used to take up to two hours.
Numbers reported by ISA Saúde's payroll team during the webinar.
One hour with ISA Saúde's payroll team showing its own routine and the Tako team building automations live, on a demo account. The data on screen is fictitious or anonymized.
Two quick steps and the player opens right here. Come back to this page whenever you want to watch it again.
Recorded on
October 6, 2026
Format
One hour, with chat questions answered live
Featuring
ISA Saúde and Tako's AI Deployment team
Who it's for
Payroll, People Ops and HR, Tako customers or not
In 2024, ISA Saúde's payroll team swapped an outsourced accounting firm and spreadsheets for Tako, and since January it has used Claude connected to payroll through the MCP. In the webinar, they open up what they built along the way, with the screen shared and the chat questions answered on the spot, without a single slide.
The payroll team at ISA Saúde, a home care company, opened up the dashboard and automations it uses every day, with the company's data hidden, and talked through what it had to adjust before each one worked.
On Tako's side, the AI Deployment team, which builds skills together with customers, showed other automations on a demo account and answered the questions that came up in the chat.
Payroll team
Home care, Tako customer since 2024
AI Deployment team
Builds skills together with customers
Half come from ISA Saúde's routine, and the Tako team built the other half live or brought them from other customers, always on demo data.
Headcount, terminations, cost per company, leave by type and the month-over-month comparison, pulled from Tako three times a day into a dashboard in Claude. Managers and Finance check it there without asking the payroll team.
Claude reads scheduled vacations in Tako and sends a single email to the manager and the employee, with dates, payment day and the company's internal rules, such as using the hour bank alongside it.
The invoice arrives by email, Claude reads it, updates the dashboard and separates the additions that need to go into the next review. The insurer's form comes out filled in with data from Tako.
Claude sees in Tako who hasn't sent this month's invoice yet, reminds each person on Slack or by email every week and, when the invoice arrives, uploads the file back into Tako.
Data coming from the recruiting system, a manager's email or a spreadsheet becomes an onboarding in Tako, ready for the payroll team to review and approve.
The first integration with an occupational health platform took two hours of conversation to build. It became a skill, and the next customer set up the same integration in fifteen minutes.
The MCP connects Tako to your company's Claude or ChatGPT. The AI reads and writes the same things you would on screen, with your login and your permissions: if someone manages one team, their AI only sees that team.
And connectors add up. In the webinar, Tako with Gmail sends the vacation notice and reads the health plan invoice, and Tako with Slack chases the contractor invoice. When the AI says it can't do something yet, the Tako team takes the request and builds it, and reading invoices that arrive by email was ready within a week.
Payroll isn't left exposed. Every write follows the same six steps, and that holds for a skill you wrote yourself:
You access the AI with the same Tako login. No permission to edit means the AI can't edit either.
It reads Tako's records before proposing anything.
If something looks off-pattern, it stops and hands the decision back to you.
It runs one case before applying the whole batch.
Contract changes go through the same approval steps as a change made directly in Tako.
Every edit is recorded under your name, with date and time.
Tako's structured records are what make this trustworthy. The spreadsheet that comes from the team always has an error in it. Tako is the source of truth that catches it.
Claude or ChatGPT. Whoever manages the company account in the AI tool enables Tako's MCP once, and then each person connects with their own Tako login and inherits the same permissions they have on screen. Token usage comes out of the tool's own plan and tends to be small.
“It was excellent, and you brought even more automation ideas.”
“Here I built a skill in Claude and it files every document in each employee's record.”
Billions in payroll already processed by Tako.
Whoever manages the company account in the AI tool adds Tako's MCP once. Then each person follows the connection guide and signs in with their own Tako login. The guides are just below, in the section for customers.
Usage comes out of the plan your company already has in Claude or ChatGPT, because it's your AI calling Tako. In practice it's small: so far no customer has run out of plan because of the MCP.
The AI inherits the permissions of the Tako login used to connect. On a shared account, everyone using it sees what that login sees, so connect with the lowest-permission user the team needs.
If the data is in Tako, yes. You describe the cut, for example one employee compared with another branch along with the payroll taxes, and the AI builds the file. Receipts and payslips also come out in bulk, in a single file.
It works with the tools your AI can connect to. The webinar shows Gmail and Slack. If your company uses another one, it's worth testing the connection in the AI tool itself.
Payroll and the whole employee lifecycle: onboarding with the candidate filling in their own data, vacations with request and approval, terminations, payslips, receipts and statements available to the employee, and contracts generated for signature through ClickSign. The MCP brings all of that into the AI your team already uses.
Yes. The AI Deployment team books a conversation of about forty minutes, builds the automation with you and, if it fits other companies, turns it into a ready skill for the next customer to use.
Connect the MCP with the guide and, if you want help, reach out to your Tako contact. In about forty minutes of conversation you leave with the automation running in your company's Claude.
Payroll, onboarding, vacations and terminations connected, and your team's AI running all of it with the right permissions. A conversation with the Tako team shows how it looks with your company's numbers.
The recording opens right here after two steps. If your question is about your company's payroll, a conversation with the Tako team gets you there faster.