Recruitment automation that leaves the decisions to you.
Claude summarises applications, candidates live in one CRM and invitations go out on time. Your team makes every call.
When an application reaches the jobs inbox, have Claude summarise it, add the candidate to the CRM and post the summary to #hiring.
Shortlist a candidate and Tutti emails them the invitation from your template and puts the interview in Google Calendar.
When I shortlist a candidate, email them the interview invitation and add the interview to Google Calendar.
Every Monday, find backend engineers in Lisbon on Apollo and add the new ones to the CRM.
After an interview, transcribe the recording and have Claude add the notes to the candidate in the CRM.
Candidates live in Tutti’s CRM, with your own stages.
Add a Stage column with the options your team uses. Every workflow can read a candidate’s stage and set it.
Keep candidate data on your own servers.
Tutti is open source under Apache 2.0. Run it in your own cloud account, and candidates’ records stay in your database.
Open source under Apache 2.0. Read the setup guide or the code on GitHub
Questions recruiters ask about Tutti.
- Does Tutti replace an applicant tracking system?
- For a small team it can: candidates and their stages live in Tutti’s CRM. Larger teams often keep their ATS and use Tutti for the work around it, calling the ATS’s API with the HTTP step.
- Does the AI decide who gets hired?
- No. Workflows can have Claude summarise and sort applications, but people make the decisions. You choose what every step does, and you can read each run.
- Can Tutti send calendar invitations?
- Yes. A workflow can create events in Google Calendar or Outlook.
- Where is candidate data stored?
- In your workspace’s database. If you want it on your own servers, Tutti is open source under Apache 2.0 and runs there.
