An AI team of ten is useful when it improves one outcome

Build capacity around a real job

Organize assistants around decisions and handoffs, then measure progress through the whole workflow rather than counting generated artifacts. The aim is to make a testable improvement with an explicit decision rule. Ten assistants means ten clearly defined roles, not a requirement to buy ten accounts or run ten agents at once. Several roles can begin as separate conversations in one tool. Add automation only after you understand the job and can recognize an acceptable result.

Ten roles to adapt to your work

1. Outcome framer. Turn a vague goal into a person, task, and observable result.
2. Evidence organizer. Attach sources, dates, and confidence to what is known.
3. Journey mapper. Describe the steps, expectations, and dependencies in the current experience.
4. Friction analyst. Separate observed problems from possible explanations.
5. Hypothesis challenger. Propose alternative mechanisms and ways the idea could fail.
6. Experiment planner. Define an intervention, signal, guardrail, and decision date.
7. Prototype partner. Make the smallest artifact needed to test the hypothesis.
8. QA reviewer. Check whether the artifact matches the intended intervention.
9. Measurement partner. Summarize findings without treating correlation as proof.
10. Decision recorder. Document the choice, rationale, owner, and next observation.

Give each role a working agreement

Specify the inputs it may use, the output format, the quality bar, the tools it needs, and where it must stop for your decision. Keep an approved project brief and source folder shared across the workflow. Begin with draft-only or read-only tasks; review a few examples before allowing changes. An assistant needs enough context to help, but not access to every file or account you own.

Practice one handoff before building a team

Start with the first two roles on a real example. Review the output before passing it onward. Ask the second role to flag missing evidence and contradictions rather than quietly filling them in. Keep a short decision record alongside the artifact. If you are correcting the same error repeatedly, improve the brief, examples, or checklist before adding another assistant.

A starting prompt

Review this journey and supplied evidence. Identify one friction point, two plausible explanations, and the smallest test that could distinguish them. Specify the observable result, possible harms to the experience, and what evidence would change the recommendation. Label assumptions.

What would “20×” actually mean?

Define the unit first: for this workflow, it could be a decision-ready evidence summary. In a hypothetical comparison, 200 minutes of manual work divided by 10 minutes of total AI-assisted work would be 20× faster for that task. The assisted time must include briefing, review, corrections, and an appropriate share of setup. Both results must meet the same acceptance standard. This is an illustration of the calculation, not a result we have measured or a promise about your work.

Measure the whole system

Record at least a few comparable runs before making a performance claim. Track accepted output, total time, tool costs, failures, and rework. Large gains, including more than 20× on a narrow repeatable task, are mathematically possible, but the size and reliability must be demonstrated. Ten simultaneous drafts do not make the business ten times more effective if you spend the next day fixing them. Revenue, customer outcomes, and hours saved are different measures.

Choose tools by the job

• ChatGPT Work: multi-step work with connected context and tools.
• Claude’s Cowork capabilities: help with multi-step knowledge work and files.
• Claude Code: coding tasks with specialized subagents.
• Grok Bot: persistent assistants working across connected tools.
• OpenClaw: an advanced option for separately configured agents and routing.

Access and limits depend on the product and plan. OpenClaw also involves configuration, maintenance, and model costs. You do not need every option. Choose one that fits your current task and learn to review its work before expanding.

Your first-week experiment

Choose one recurring task and capture how you currently do it. Set up the two roles that remove the most repeated effort. Use them on a real piece of work, inspect the result, and record total time and changes needed. Keep the roles that help you produce acceptable work; revise or remove the ones that add overhead. The exciting part is gaining the confidence and capacity to attempt useful work you previously postponed.

Learn the process by building something small

In Two Mondays, Ashley will build a product and show the steps from validation and planning through design, coding, testing, and marketing. Bring a small project and practice the workflow. The workshop meets October 26 and November 2, 2026, from 7–9 p.m. Eastern, on Zoom with a West Palm Beach in-person option. The $99 ticket covers both Mondays and optional setup help and office hours. Paid software and hosting are separate; you can follow the demonstrations without buying every tool mentioned here.