Six jobs nobody wants on Monday.
The role pages answer who you would hire. These answer what gets done — six jobs a buyer already has a name for, each one described as the work rather than the feature, starting with an honest account of how it is done today.
Matching invoices to purchase orders and payments, every night, with the exceptions raised rather than resolved.
Read the use case →SUPPORT INBOXTriage, drafts and escalation running continuously, so the queue you open is already sorted and the urgent ticket is at the top.
Read the use case →MONTH-END CLOSEYour close checklist worked in order, the supporting documents gathered per item, and a daily account of what is still open.
Read the use case →CANDIDATE SCREENINGEvery application read against the criteria you wrote, with the reasoning shown — and nobody left in silence.
Read the use case →WEEKLY REPORTINGThe recurring report assembled from the systems it draws on, every figure carrying the source it came from.
Read the use case →OVERNIGHT MONITORINGProcesses followed across systems through the night, stalls fixed inside the mandate you set, and the rest raised with context.
Read the use case →How these pages are written
The work today is described honestly. Every page opens with the manual version of the job, written the way the person doing it would describe it — not as a strawman. If the manual version is fine, that is worth knowing before a call, not after one.
No new numbers. There are no hours saved, no error rates, no percentages and no customer names on these pages. The only figures anywhere on this site are the ones the rest of it already stands behind.
Systems are named generically. Your ledger, your helpdesk, your ATS, your CRM. Dutta connects to the systems the work lives in, but this site does not publish an integration list it has not confirmed.
What is true in all six
An AI employee is a named role on shift, not a script. It owns an outcome, asks when it is unsure, and reports what it did. Whichever job you hand it, the same four things come with it:
- Credentials scoped per system — read, write or send, granted by you, revocable immediately.
- A working memory of your business, from your documents and connected systems, with no onboarding period.
- Approval checkpoints you name, so a person decides anything with a consequence before it happens.
- A log of every action with its inputs, sources, reasoning trail and output — replayable, and exportable to your SIEM.
The same work, by role
Every job on this page belongs to a role you can read in full: finance, customer support, recruiting, operations and growth, or a role you describe yourself. See what each AI employee handles on shift.
Start with the one that hurts
Pricing is per AI employee on shift and humans are unlimited on every plan — see pricing or tell us the process that eats your team’s week.