Needs you · 1 of 3 · oldest
Approve the plan: customers can pay by invoice
What changes: an invoice option at checkout. Touches: checkout and two billing e-mails. Could go wrong: a wrong total on the PDF. Undo: revert one change.
Task management, with digital workers
The task manager that does the tasks.
Write what you need in plain words. A digital worker plans it, builds it, checks it, and asks you for one yes. Then it ships while you get on with the next thing.
Needs you · 3 tasks across 3 businesses
Kestrel: the launch post is drafted, waiting for your readBuilder · 2 h
Northline: building the CSV export, check nextResearcher · now
Tidewater: support inbox sorted, 3 replies need a humanOps worker · 5 h
One press per plan · A second company's model checks every change · Your code stays in your GitHub · No per-person seats
What got done while you were away.
A Morning Log is written before you wake, in your time zone, and only on days something happened. One list shows what needs you, and nothing else.
Tidewater
While you were away
Approve the plan: customers can pay by invoicePlanner · 6 h
Refund window widened to 30 days, doneBuilder · 9 h
Support inbox sorted, 3 replies need a humanSupport worker · 8 h
Kestrel
While you were away
The booking page loads twice as fast, doneBuilder · 2 h
Three competitors' pricing, in a DocResearcher · now
Launch post drafted, waiting for your readWriter · 4 h
Northline
While you were away
CSV export done after the staging walkBuilder · 3 h
Last month's invoices reconciled, 2 flaggedOps worker · 5 h
Log written for 16 SeptemberLog writer · 1 h
How a task moves.
Five steps, one press. Everything between your words and the finished work is written on the task.
Write
Say what you want in plain words, from the list or your phone.
Plan
The Planner writes what changes, what it touches, what could go wrong, how to undo.
Approve
One press. Your yes covers the pieces inside the lines the plan drew.
Do and check
A Builder does the work. A Verifier from a different company checks it.
Done
A clean walk on staging sends it live. One change, one undo.
What the workers do
Digital workers for the list that never gets shorter.
Software is where they started. The same list takes research, writing, marketing, ops and support: the work that piles up between the big things.
Software
“Let customers pay by invoice at checkout.”
A plan in four parts, built on its own branch, checked by a second company's model, live after a clean walk.
Research
“How do three competitors price seats?”
A Researcher reads, compares, and leaves a Doc on the task with what it found and where.
Writing
“Draft the launch post and the release notes.”
A draft Post and a Doc on the task, in your voice, waiting for your read before anything is published.
Marketing
“Turn last week's changes into the newsletter.”
Reads what got done, drafts the issue, schedules it once you say yes.
Ops
“Reconcile last month's invoices and flag the odd ones.”
Works through the folder, writes the list of exceptions, asks about the ones it cannot tell.
Support
“Read the inbox and draft replies. Flag what needs a human.”
Sorts the queue, drafts answers from the Guide, and leaves the hard three for you.
Plain words
Every task comes back as a plan in four plain parts.
What changes, what it touches, what could go wrong, how to undo. Every question arrives with a catch-up, so you never open a task cold. The workers answer what they can infer and show you what they answered for you.
- The list shows what needs you and nothing else
- The chat files tasks and takes a dropped link or note
- A Guide of your product is kept true after every change
Plan · Tidewater · waiting on you
Customers can pay by invoice
- What changes
- An “Invoice” option at checkout. The order waits until the invoice is paid, then ships as usual.
- What it touches
- Checkout, the order record, and two billing e-mails. Nothing in payments.
- What could go wrong
- A wrong total on the invoice PDF. The check compares it to the order before it ships.
- How to undo
- One undo of the change. Orders already paid by invoice stay paid.
Machine · idlecycle 03:30 · 9 queued · 3 building · 2 checking · 1 in the merge trainOpen ›
Builder started on “customers can pay by invoice” · branch agent/TASK-118Builder · GPT · now
Verifier is checking the build · a different company's modelVerifier · Grok · 2 m
Second look passed · merge train, seat 2 of 3Reviewer · Claude · 14 m
Staging walked clean · live at 03:12Scouts · 1 h
The workers
Task management, with the team included.
Planner, Builder, Verifier, Librarian, Scouts, Guide and Log writer: digital workers named by what they do. Every task is done on its own branch and arrives as one change you can undo. Nothing goes live until a worker from a different company than the one that did it has checked it. That rule lives in code, not in a promise.
- Three model families: Claude, GPT through Codex, and Grok
- Approved work lands one task at a time
- Staging first; only a clean walk sends it to production
You stay in charge
Four kinds of work always come back for their own yes.
Your yes covers a plan's pieces only while a piece stays inside the lines the plan drew. “I could not tell” counts as outside. You can take a yes back at any time: every unfinished piece parks, and the task says which pieces had already gone.
- Who may approve is a setting per business
- Every plan says how to undo it before you say yes
- Undo today is one revert of the change, on GitHub
Always comes back to you
- Anything that cannot be undone
- a data migration, a deleted record
- Anything touching security or another business
- sign-in, keys, the wall between businesses
- Anything a reviewer flagged
- the second company's model said hold
- Anything that changes what you will be asked
- the questions themselves.
Unshipped pieces park. Shipped ones are named.
One business, or several.
Start with one. Add another when you need to. Each with its own settings, its own model accounts, and its own list. The same workers run them all.
Folders and Spaces
A business is a folder. Its work lives in Spaces, and every level has its own list.
Per-business settings
Who may approve, which repository, which model accounts, whether Scouts walk it.
Your own model accounts
Claude and ChatGPT subscriptions sign in on the machine. Grok by key. We never sell per-person seats.
A Space holds the pieces
A List, a Board, a Doc, a Post, Threads and a Map. The machine writes on them too.
The record in your GitHub
Every task, plan and decision is written in plain words, in your own GitHub account.
Scouts on or off
Scouts walk the live site after every ship and every day, and file what breaks as cards under their own names.
Pricing in one line.
Free to try, when our window has room. Then a flat monthly plan that buys the workers more time, better models and a faster queue. Unlimited Spaces and people on every plan.
Free
Free
Try the workers on your own list.
Start freeMost people start here
Basic
$25 /mo
Everyday work, done overnight.
Choose BasicPremium
$95 /mo
The best models where it counts.
Choose PremiumPro
$495 /mo
The best models everywhere. Front of the line.
Choose ProUltra
From $1,495 /mo
A machine of your own.
Contact us