What should your first AI teammate do?
For founders and small teams: start with a useful piece of work you can review, such as a customer email, a project update or a bug fix. Ask in Channels and build from there.
Choose something you already need done. A draft customer email is a good first assignment when you have an update to share: you can check the facts, give feedback and decide when it is ready to send.
Find work your team needs now
These requests show where to begin. Use your own words. Your teammate works out the steps and asks for anything it needs.
Draft a customer email
You have something to announce and want a draft you can send after review.
Say in Channels
“Maya, draft the waitlist launch email. I’ll review it before we send.”
Ask it to bring back
An email draft based on the current launch plan, with any missing facts called out.
What to check
Check the offer, dates and product claims against what you have agreed. Read the email aloud: does it sound like your team? Give corrections in the same conversation and approve the final version before sending.
Find what is holding up a project
A launch or handoff is coming up and you need to know what still needs a decision.
Say in Channels
“Sam, can we tell the pilot teams they’ll get access on Monday? I need to know what’s still open.”
Ask it to bring back
A readiness summary that names what is ready, what is still open and who needs to act.
What to check
Ask for the messages or files behind the summary. Check that an unanswered question has not become a confirmed date. You decide which commitments to make to customers.
Turn customer feedback into a proposed change
You have customer feedback and want to decide what to improve next.
Say in Channels
“Nina, what’s the first onboarding change you’d make based on the pilot feedback?”
Ask it to bring back
A proposed change, the feedback that supports it and a way to check whether it helps.
What to check
Read the original feedback alongside the recommendation. Separate what customers said from what the teammate inferred. Decide whether the proposed test would answer the question you care about.
Prepare a bug fix for review
You know what is going wrong and have someone who can review and test the change.
Say in Channels
“Leo, the report export fails when a filter matches zero rows. Can you take a look before the pilot?”
Ask it to bring back
A proposed patch, a test for the reported failure and the results of the relevant existing checks.
What to check
Review the code and reproduce the original failure. Check that the fix works and that existing behavior still passes. Repository access and permission to release are separate from asking for a patch.
Judge the result before handing over more
Open the work it returns. Check the facts against the source and try anything that needs to work. If something is wrong, say what needs changing in Channels. Review the revision before using it.
After a few assignments, compare the time you spend asking, reviewing and correcting with doing the work yourself. Look at whether the result meets your standard. That tells you which responsibility is worth giving it next.
Keep talking as its role grows
Your first assignment does not lock in its role. Tell your teammate what to take on, stop doing or prioritize. It can keep useful guidance for later work as your needs change.
“Look after our customer updates from now on. Bring each draft to me before it goes out.”
For work that should repeat, say when: “Every Monday at 9 AM Chicago time, check the launch plan and tell me what still needs a decision.” Your teammate can arrange the schedule and confirm it with you. Changing its role alone does not create a schedule or grant new access.