Start with work you already understand. That makes it easier to tell whether the team helped. This job uses notes you paste into Murage, and you’ll know the right answer before you run it.
It needs an AI engine connected to Murage. It doesn’t need email, a calendar or any connected app.
Here are a week of made-up notes. Before Murage sees them, mark every promise: who made it, who it’s for, and when it’s due. Then mark which are overdue on Monday, October 5.
Test fixture. The people and companies are invented.
MADE-UP TEST NOTES for murage.ai/try-one-job. The people and companies are invented. Treat today as Monday, October 5, 2026. Mon Sep 28 - Call with Ana at Coastline Print. I promised her the revised quote by Thursday (Oct 1). - Invoice #212 to Northfield is still unpaid. Third reminder needed. Tue Sep 29 - Standup. Tomás said he'll send me the bug list by Friday (Oct 2). - Told Marco I'd review his onboarding draft next week. Wed Sep 30 - Van needs booking for the 14th. - Sam asked about holiday cover. I said I'd reply by Friday. Thu Oct 1 - New supplier price list came in. Someone should compare it with the current one. Fri Oct 2 - Ana chased the quote. I told her she'll have it Monday. - Lena at Ridgeway wants the contract. I said I'd send it by Friday the 9th.
Open a chat with your Chief of Staff, paste the notes, and send this. It tells the team to use only what you supplied.
“Here are my notes from last week. Treat today as Monday, October 5, 2026. List every promise in them: who made it, who it’s for and when it’s due. Tell me which are overdue as of today, and suggest the next three things I should do. Use only what’s in these notes. If a note has no owner or no date, say so instead of guessing.”
In the welcome, the starter job Make sense of these notes does something similar. Walk through it in the docs
Compare each item with the original notes, not with how confident the answer sounds.
Overdue on October 5: the reply to Sam and Tomás’s bug list, unless either already happened. Ana’s quote was late once and is due today.
Not promises, and no owner: the invoice #212 reminder, booking the van for the 14th, and comparing the supplier price list. A good answer lists them as open items, says nobody was named, and doesn’t add a date or month the notes don’t give.
Sensible next three: send Ana the quote today, reply to Sam, and ask Tomás for the bug list. Another order is fine if it follows from what’s overdue.
Say which item is wrong and why, in the same chat. Count the fix as part of the attempt: a result that needed one correction is still useful, and you should know it needed one.
“Tomás owes me the bug list, not the other way round. Fix that item and check the others for the same mistake.”
Copy the list out of the chat, or ask your Chief of Staff to save it as a file. The conversation stays in Murage, on your computer.
“Draft my reply to Sam about holiday cover. Keep it short, and don’t send anything.”
The draft stays in the chat for you to copy, change or throw away. Nothing is sent.
Then do the same with your own notes, where you already know what matters. For the standard we hold our own runs to, read how we test Murage. For what it can’t do yet, read the limits.
One job, and you judge it.
If it isn’t for you, the team’s memory and files are stored on your computer in files you can open, and the code is AGPL-3.0.
No account needed · Runs on the AI plan you already pay for