Blog
Five tasks to hand an AI teammate first
The first five jobs to give an AI teammate, and why these five. Each one repeats, costs little when wrong and takes a minute to check. With the ask to type.
Benjamin Ben HattarThe first week with an AI teammate decides whether anyone is still using it in the fourth. Teams that start with something big and vague, like "run our marketing", get something big and vague back, and quietly stop asking. Teams that start with something small and checkable build trust one correct answer at a time.
So the first tasks matter more than the tool. Here are the five I would hand over first, the reason for each, and the exact sentence to type. The examples use Cedric, because that is the one I build, but the selection logic holds for any AI employee.
- Good first tasks repeat, cost little when wrong, and take a minute to check.
- The five: the weekly numbers, notes for one recurring meeting, the unanswered-inbox sweep, meeting prep, and collecting updates from people.
- Ask for each one by hand first. Correct it in the thread until it needs no edits, then put it on a schedule.
- None of the five sends anything outside the team without a yes, so a bad first week costs a few re-reads.
- Leave customer replies, money and judgment calls for month two.
The three tests
It repeats. A one-off task teaches you nothing about next week. A weekly task pays you back for every correction you make, because Cedric keeps the correction in the team's shared memory.
A wrong answer is cheap. If the output is off, the cost should be a re-read and a reply in the thread. It should never be an email to a customer or a changed record.
You can check it fast. You already know roughly what the right answer looks like, or you can confirm it in a minute. That is how you learn where the teammate is reliable, and it is the only way to learn it.
The five tasks
- 01
1. The weekly numbers
Type: "@Cedric last week's signups, revenue and open invoices, from billing, as one short post for the Monday meeting." He reads the connected tools and posts the figures with where each came from. Correct it twice, then say "post that here every Monday at 8".
Check it against the report you sent last week. Disagreement now is cheap. Disagreement in three months is not.
- 02
2. Notes for one recurring meeting
Add Cedric's address to the calendar series of your weekly team meeting. He joins every occurrence, takes notes, and posts the summary to the channel when the call ends, with decisions kept apart from open questions.
Easy to check: you were in the meeting. Read his notes against what you remember.
- 03
3. The unanswered-inbox sweep
Type: "@Cedric what's still unanswered in my inbox from this week?" He reads the threads, lists the ones waiting on you, and drafts the replies worth sending. Each draft waits as a preview until you approve it.
Open two of the threads he flagged and one he skipped. That tells you in a minute whether his sense of urgent matches yours.
- 04
4. Meeting prep
Type: "@Cedric prep me for my 2pm." He reads the invite, the notes from last time, the mail thread and the CRM record, and posts who you are meeting, what changed since, what to ask and what to keep out of the room.
You will walk into the meeting anyway, so you find out within the hour whether the brief was right. The same ask works in a direct message, which is how people use Cedric as an AI personal assistant.
- 05
5. Collecting updates from people
Type: "@Cedric get a status line from Tomas, Lena and Devin by Thursday and post the roll-up here." He asks each of them in a direct message, nudges whoever is quiet, and posts the roll-up when the last reply lands.
Low risk because the messages stay inside the team. You see who answered and who did not.
Task 5 in practice
Three people, one roll-up, no chasing by you.
Lucia Moreau9:14 AM
@Cedric get a status line from Tomas, Lena and Devin by Thursday and post the roll-up here.
CedricAPP9:15 AM
Running. I've asked all three in DM. Lena has answered. I'll nudge Tomas and Devin Wednesday morning and post the roll-up here when the last reply lands.
This one runs for days. The request does not live in a chat message that scrolls away. It is a job that waits for replies, survives the weekend, and finishes on its own. Workflows that wait explains how it keeps its place.
The five against the three tests
| Task | If it is wrong | How often | How you check | What you type |
|---|---|---|---|---|
| Weekly numbers | A re-read before the meeting | Weekly | Last week's report | last week's signups, revenue and open invoices, from billing |
| Meeting notes | A line to fix in the channel | Every meeting | You were there | Cedric's address on the calendar series |
| Inbox sweep | A draft you do not send | Daily or weekly | Open two threads | what's still unanswered in my inbox from this week? |
| Meeting prep | A brief you correct | Before key calls | The meeting itself | prep me for my 2pm |
| Collecting updates | A roll-up with a gap | Weekly | Who answered | get a status line from Tomas, Lena and Devin by Thursday |
How to ask so the first answer lands
A vague ask does not fail. It comes back generic, which is worse, because you have to read it to find out. Four things turn a generic answer into the right one. Say what the output should be, which source wins, how far to go, and who reads it. "Summarize the numbers" becomes "one page of last quarter's revenue by plan, from billing, for the board deck". How to write tasks Cedric nails has more before-and-after pairs.
When the answer is off, reply in the same thread with the fix. Do not start over. "Exclude internal test accounts" said once stays said, for you and for everyone else in the workspace.
Once a task needs no edits for two or three runs, schedule it in a sentence. Put the Monday report on a schedule walks through that step, including the check people skip.
What to leave for month two
Replies to customers. Cedric will draft them and they will wait for your yes, so the risk is contained. Still, give yourself a month of reading his internal drafts before you judge his tone with the people who pay you.
Anything that touches money, like refunds, invoices or ad budgets. Those are gated too. Start them once you know how he reads your billing data.
Decisions. Ask for the analysis on a schedule, and keep the choice.
What still needs a person
Reading the output. The approval gate only works if someone looks at what they approve, and a first-week report only teaches you something if you check it against what you know.
Deciding what the report is for. Cedric can post the numbers every Monday. Whether those are the right numbers to watch is your call, and it is worth revisiting every quarter.
FAQ
Work that repeats and follows a pattern: weekly reports, meeting notes and follow-ups, inbox sweeps, meeting briefs, collecting updates from people. Start with those before anything customer-facing.
Anything where one mistake reaches a customer or moves money, and anything that is a judgment call. Cedric asks before those anyway. They are still better as month-two tasks.
For a recurring report, usually two or three rounds of correction in the thread. Each correction goes into the shared memory, so it sticks for every later run.
Cedric will not. Anything that leaves the workspace, changes a record or costs money waits for approval. See how approvals work.
Cedric starts with 100,000 free credits, worth $50, and no card. Plans start at $19 a month for the whole team. See pricing.
100,000 free credits, no card.