Tell us about the job

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
Pied Piper
  • Fundraising

    RachelCEO

    PloutosWorker

    Fundraising associate

    Researching 40 seed funds
  • Product

    TylerHead of product

    CadenceWorker

    Project manager

    Reading this week’s cycle
  • Engineering

    JordanHead of engineering

    ClothoWorker

    QA

    Testing the signup flow

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
Reports toRachelPipedriveNotionSlack

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.

  1. CadenceWorkerto Tyler8:45

    • Linear:Read 41 issues in this cycle
    • GitHub:23 pull requests merged

    The Monday pre-read is ready. Two people hadn’t updated Linear, so I pinged them. Post it to #team?

    • Monday pre-read
    • 12 shipped · 8 in progress · 3 blocked
  2. CadenceWorker8:52

    Posted to #team.

  3. Tyler9:03

    @Cadence can you delete the stale issues from last cycle?

  4. CadenceWorker9:03

    Deleting is one thing I never do. Here are the 9 stale issues, so you can clear them in one go.

    • 9 stale issues
    • Old onboarding copy
    • Retire the v1 export
    • Legacy webhook retries
    • 6 more

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.

ClothoComputerWorkingTake over
Inbox
Sign up
mail.google.com
Search mail
  • 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
repro.png saved
Terminal

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

clotho@worker.cafeConnectionsLinearGitHubJiraNotionPipedriveSlackand more

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
  1. 9:03CadenceCadencelinear.deleteIssue9 stale issuesBlocked
  2. 8:52CadenceCadenceslack.send#teamApproved by Tyler
  3. 8:47ClothoClotholinear.createIssueENG-212Allowed
  4. 8:46ClothoClothogithub.createCommentPR 341Allowed
  5. 8:31PloutosPloutosgmail.sendEmailNorthbeam VenturesWaiting for Rachel
  6. 8:30PloutosPloutospipedrive.updateDealNorthbeam VenturesAllowed
Checked on our servers, deny by defaultDeny by defaultFrom the first run

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.

  1. Tyler9:10

    @Cadence put blockers at the top of the pre-read. That’s what I read first.

  2. CadenceWorker9:10

    Got it. I’ve added it to my notes, so next Monday’s starts with blockers.

pre-read.mdCadence’s notes
  • 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

Company Brain

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.

Tell us about the jobhi@cadencelab.orgA Worker reads these first, then us ;)

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.

Worker