How it works
One Hand, one working day.
A Hand is an AI agent with a name, its own computer, your logins and a memory. The clearest way to say what that means is to follow one through a day, from the routine that runs before you're up to the record it leaves at night.
Chases invoices · Thursday
Approved by you, 9:14
Sent. Three chasers went out from your address. I'll watch for replies.
A Tuesday
What one Hand does with a day.
There's no catalogue of automations here. A Hand doing an agency's proposals and a Hand watching a rental portfolio are the same thing with a different brief and different accounts connected.
-
It has already started
A routine woke it at seven. By the time you look, it has read the overnight mail, checked what moved in the accounts you connected, and left a briefing at the top of the thread: what changed, what it did, and what it left for you.
You didn't ask for that this morning. You asked once.
-
You hand the job over in a sentence
Not a prompt and not a flowchart. “Work out who hasn't paid us, and go after them.” The way you'd put it to someone at the next desk.
Then it does it, on its own computer: a desktop in the cloud with a browser and a shell. Your accounts are its accounts — Gmail, Slack, Stripe, QuickBooks and hundreds more, connected once and per business, so a Hand in one can never reach another's. It can read its reply aloud if you'd rather listen.
-
It stops at the thing it can't take back
A send, a payment, a deletion, an ambiguous call: each one comes back as a card with the reasoning attached. Allow it, deny it, or answer in a sentence.
This is the line the whole product is drawn around. Everything before it is speed; this is the part that lets you turn the speed up.
-
It hands work on, and writes down what it did
Put a few Hands in one business and they pass work to each other. Maya chases the invoices and hands the numbers to Nia, who puts them in the weekly report. You see what happened rather than approving every step.
All of it lands as an entry with a time and a name on it. Ask what happened this week and the answer is the record, not a summary of a summary.
Dana Kessler Kessler & Co · client since 2024Owes $4,200- dana@kessler.co
- Pays
- Usually late, always pays
- Next
- Check for payment Monday
- Maya sent a chaserYou approved it · Thu 9:14 · gmail
- Maya found invoice #1182 is 41 days lateThu 9:06 · stripe
Theo noted Dana promised to pay "this week"Mon 8:40 · from her email- YouYou added Kessler as a clientMarch 2024
-
It takes the night shift
Routines run on a schedule. Something outside changes and a Hand wakes up to it. When it hits a login it can't get past, it stops and leaves it for you rather than guessing.
All of it is opt-in, and every run leaves a receipt with what it cost.
Every job
Three steps, every time.
- Brief itIn a thread, the way you'd say it to a new hire. No workflow builder, no graph to draw.
- It worksOn its own computer, with your accounts, while you do something else. Watch its screen or take the keyboard whenever you like.
- It asks, then writes it downAnything irreversible comes back as a card. Everything it did lands in the record with a time, a name and a source.
For the technically minded
Open parts, all the way down.
The day above runs on pieces you can take apart.
Built on open source
Hands is built on OpenMausBot by Milind Soni, an open-source agent harness, and extended for running a business.
MCP both ways
Hands use the MCP tools you add, and expose the record over MCP, so you can reach your businesses from Claude Desktop or Cursor.
Your record, exportable
Contacts, deals and tasks export as spreadsheets, and notes as Markdown.
Who it's for
The same Hand, briefed for your work.
Each page shows the jobs people in that line of work hand over first, and the questions they ask before they do.
Meet your first Hand.
Sign in with your email or Google and give it something you've been putting off. Plans start at $20 a month, with work included.
