Teams
Five worked examples for building your first AI team. Each includes the inputs to collect, a usable task brief, expected artifacts, and the checks a person should make.
Example workflows. Connections and live agent execution are planned.
Pick a concrete first job
Software teams
Bring the issue, relevant code, reset policy, and test commands. A builder prepares the change; QA verifies recovery and existing flows.
Output: A focused diff and verification report. You approve merge and release.
Read the worked exampleCustomer care
Bring the customer’s thread and approved invitation guide. Prepare recovery instructions and escalate unsupported account details.
Output: An unsent reply draft and an internal note with sources.
Read the worked exampleGrowth teams
Bring the release brief, help article, audience, and voice examples. Prepare an email and an in-app announcement from the same verified facts.
Output: Two reviewed drafts. You choose the audience and approve publication.
Read the worked exampleBusiness operations
Bring a tracker snapshot and the onboarding checklist. Identify overdue incomplete milestones and missing owners using an agreed reporting cutoff.
Output: An exception table and proposed next steps for the operations lead.
Read the worked exampleFinance workflows
Bring read-only invoice and payment exports plus approved matching rules. Preserve source rows and separate ambiguous matches.
Output: A reconciliation worksheet and exceptions for finance review.
Read the worked exampleYour workflow
Choose a recurring task with accessible inputs and a result you can check. Name the person who should review it before expanding the scope.
Output: A task brief with a deliverable, acceptance checks, and an approval boundary.
Plan your own teamA reusable starting brief
Outcome: What should be different when this is done?
Inputs: Which files, links, records, and rules are authoritative?
Deliverable: What exact artifact should the owner hand over?
Acceptance: Which checks decide whether it is ready?
Boundary: What must the owner ask before doing?
Reviewer: Who accepts the output and decides the next action?“Research competitors” is hard to finish. “Compare the published pricing of three named products, cite each source and date, and list any unknowns in a one-page brief” gives the owner and reviewer the same target.
Keep the first team small
One agent can collect inputs and prepare a bounded result. Splitting every small step across agents adds handoffs before you know whether they help.
For code, calculations, customer replies, or public content, ask a separate reviewer to check the acceptance criteria and evidence. You remain the owner of consequential decisions.
A coordinator becomes useful when several deliverables depend on each other. Its job is to keep owners, prerequisites, and blockers clear—not to create a larger team by default.
Bring the brief into setup
Use your first deliverable as the mission. Select the roles that actually need to contribute, describe the workload, and compare the illustrative credit estimate. Add the review boundary to the brief.
Decide where it should run
The same task brief can inform a managed Cloud or self-managed plan. Compare who will operate the runtime, arrange provider access, and maintain the connected tools before choosing a path.