AI, employed.
It takes a job off your plate, reports to someone on your team, and does the work itself.
Run your company this way:
- Your team
- Xpeople
- Today
- 10Xthe work, with Workers
- Next year
- 100Xthe work, same team

Fundraising
RachelCEOResearching 40 seed fundsPloutosWorker
Fundraising associate
Product
TylerHead of productReading this week’s cycleCadenceWorker
Project manager
Engineering
JordanHead of engineeringTesting the signup flowClothoWorker
QA
Trust it like someone you trained.
Rachel briefed Ploutos in three sentences, the way she’d brief a new hire. It has done the job her way since.

PloutosWorker
Fundraising associate · ploutos@worker.cafe
Rachel
“Find seed funds that back developer tools and get us warm intros. Keep the pipeline current. Nothing goes to an investor without me.”
- Startsevery weekday at 8:00
- Works inPipedriveNotionSlack
- Asks firstanything sent to an investor
Your rules, kept.
A good hire doesn’t check with you on every small thing, only on the ones that could cost you. A Worker is the same. You decide what those are, and it can’t talk its way past them.
When a rule says ask, it asks you in Slack and waits for your answer.

It has its own computer.
Every Worker has its own email address and its own computer, with a browser, a terminal, and files that stay put between jobs. From there it reaches the tools your team already uses, and every call still answers to your rules. Watch its screen anytime, or take over.

- JordanFwd: Signup button does nothing – Can you reproduce this?9:12
- LinearENG-207 Flaky export test – Tyler assigned it to you8:40
- GitHubPR 341 is ready for review – 2 files changed8:31
worker linear.createIssue “Signup button does nothing”
allowed · ENG-212 created
worker github.createComment 341 “Repro in ENG-212”
allowed · comment posted
worker notion.appendBlock “QA log” ENG-212
allowed · QA log updated
worker slack.send #releases “Hold 2.4, signup is broken”
asks first · waiting for Jordan
Every action, on the record.
Workers act in your tools through Worker’s servers, so the keys to those tools stay with us and never reach the Worker. Every read and every change is checked against your rules and written down: what it saw, what it did, and who approved it. The log starts with the first Worker you hire.

Audit log
All6Asked2Blocked1- 9:03CadenceCadencelinear.deleteIssue9 stale issuesBlocked
- 8:52CadenceCadenceslack.send#teamApproved by Tyler
- 8:47ClothoClotholinear.createIssueENG-212Allowed
- 8:46ClothoClothogithub.createCommentPR 341Allowed
- 8:31PloutosPloutosgmail.sendEmailNorthbeam VenturesWaiting for Rachel
- 8:30PloutosPloutospipedrive.updateDealNorthbeam VenturesAllowed
It learns how you work.
Correct it once and it writes the lesson down. Its notes are plain documents you can read and fix, and earlier versions are kept. The lessons you approve go into your Company Brain, so every Worker you hire starts out knowing how your team works.

Tyler9:10
@Cadence put blockers at the top of the pre-read. That’s what I read first.
CadenceWorker9:10
Got it. I’ve added it to my notes, so next Monday’s starts with blockers.
- Post it by 9:00 on Monday.
- Blocked means no update in 3 days.
- Put blockers first. Tyler reads them before anything else.
Learned from Tyler, Sep 28
Worker is early.
We’re looking for a few teams to build it with. If there’s a job on your team that everybody avoids, we’d like to hear about it.
Founders’ note
At our last company we built an AI project manager for ourselves. Soon sales, hiring and QA each wanted one. None of them could set it up without us, so we spent our weeks wiring up everyone else’s.
Everyone can name the job they want AI to do. Almost nobody can set it up. We’re building Worker so they can.





