Build Your First AI Partner Team for a One-Person Business

A larger AI partner team also creates more work to inspect and coordinate. Build the first team around one job that repeats every week. Three roles are enough. You keep the goal and the final decision while AI partners gather material, track follow-ups, and prepare a draft.

The finish line is concrete. Each partner knows what it receives and what it must deliver, and you verify one real result in the original file, task, or channel.

Before you start

Choose a small job that takes only a few minutes to review and can be returned for revision. You might group a set of customer feedback, extract follow-ups from meeting notes, or prepare a help-doc draft from approved material. Keep payments, deletion, bulk messaging, and final publishing under human control for the first run.

1. Define one result for this week

Write one sentence that names the input, the deliverable, and the review location. For example, turn this week's customer feedback into a grouped list in a fixed document, then review the categories and next actions yourself.

A clear scope makes the owner easier to choose. Do not combine collection, analysis, writing, publishing, and review into the first handoff.

2. Choose three partners by role

Open AI Partners from the sidebar and narrow the list by role. Choose one partner to gather scattered material into usable input, another to identify follow-ups, and a third to prepare a draft from approved material. Their names can differ as long as each role fits in one sentence.

Check runtime state, recent activity, channels, tasks, and skills at the same time. Review existing work before using a Working partner, resolve runtime issues for an Offline or Error partner, and prefer an Idle partner whose setup is ready for new work.

3. Connect only the entry point this job needs

When a partner needs to receive material from Feishu, WeChat, or another channel, connect only the channel required for this job and complete any setup or confirmation shown on the page. When the material already lives in local files or a knowledge base, keep the first run local.

After connecting a channel, send one low-risk test message and confirm that it can be sent and received. A Connected label does not replace a message test.

4. Run one handoff in order

Give the original material to the gathering partner first. Review that result before passing approved material to the follow-up or drafting partner. Each step should request one explicit result and name the delivery location and prohibited actions.

Stop at the current step when the scope is unclear, material is missing, or the partner is still handling earlier work. Complete the input or choose another suitable partner before continuing.

5. Verify the result where the work belongs

Return to the agreed file, task, or channel and inspect the actual deliverable. Confirm that it is complete, stays within the limits, and gives the next partner input that you have already reviewed. Runtime state helps with progress decisions, but it does not replace acceptance.

Keep these three roles after the first successful run. Pause a role that repeatedly lacks a clear input or deliverable. Add another partner only after a new repeatable job has become stable.

Done when

You chose three roles around one repeatable job, completed one ordered handoff, and verified the final result in its original location. The next weekly run should require new material, not a redesign of the whole team.

Troubleshooting

• All three partners are busy Hand over only the step closest to the current goal. Keep the other steps manual or wait until earlier work finishes.
• Every result needs a major rewrite Reduce the handoff scope and include an acceptable example, the required format, and actions that must not be taken.
• You do not know which partner to keep Record inputs, deliverables, and revision reasons for two or three runs. Keep the partners whose roles remain clear and whose results are easy to review.
• You want to add more roles Confirm that the current three roles run reliably first. Every new role should own a recurring result that can be reviewed on its own.

Related pages

See Quickstart for installation and the first summon, Choose the Right AI Partner for a Task for task ownership, and Run a Daily Check from AI Partners for a team-wide status review.

Data boundary

Work data stays on your device by default; only channels you connect and model calls go online as the task requires.