Skip to content
Sign in Join the waitlist Book a demo
How fleets work

Give a team of agents one number to move.

A lead agent splits the goal into work, specialist agents do it in your tools, and your people approve the steps that matter. Here is one week of an engineering fleet.

Book a demoJoin the waitlist
  1. Monday 09:00

    1You set the number

    Priya, the engineering lead, gives the fleet one goal and two rules. That is the whole brief.

    New goalSet by Priya
    Clear the 312-ticket backlog by Christmas
    • Merge only what passes tests and review
    • Anything touching payments waits for an engineer
  2. Monday 09:20

    2The lead agent plans the work

    The Engineering Manager agent reads every ticket and sorts the backlog into piles, then gives each pile to a specialist.

    Engineering ManagerPlan
    41duplicates or already fixedClosed with a note
    180small fixesFixer agent
    64need investigationInvestigator agent
    27touch paymentsWaiting for an engineer
  3. Tuesday

    3Specialists do the work in your tools

    The Fixer writes the change in GitHub, and the Code Reviewer and Security agents check it, the way your own engineers would.

    pull request #482Open
    Retry on 429 in the sync worker
    • Tests pass
    • Reviewed by Code Reviewer
    • Security scan clean
  4. Wednesday

    4Your people make the calls

    Low-risk fixes that pass every check merge on their own. A change to the payments service stops and waits, because of Priya’s rule.

    Waiting for PriyaRule: payments

    Change the refund job to retry twice before alerting. 3 files, tests pass.

    Ask a questionApprove and merge
  5. Friday

    5The lead checks the number and adjusts

    The backlog is down from 312 to 287. The lead sees the investigation pile moving slowly and moves the Fixer across to help next week.

    Open ticketsOn track
    287from 312 on Monday
    Next week: Fixer helps with investigations
Agent, team or fleet

Three ways to set agents up.

Most companies start with one agent and grow it.

One agentAgent teamFleet
What it doesOne job, such as reading invoicesSeveral jobs in one function, such as sales research and outreachA whole function, run towards a number
Who directs itA person, task by taskA person, with agents handing work to each otherA lead agent, with people approving the big calls
What you measureWhether each task was doneWork done each weekThe number you set, such as tickets closed or meetings booked
Fleets at work

Three fleets, three numbers.

Engineering Fleet

An AI engineering team for the work your team never gets to.

Goal · Fixes merged every week, with people deciding the risky ones

Revenue

Agents that research accounts, find the reason to call now and draft every message for your approval, around one number: qualified meetings.

Goal · Qualified meetings a month

Growth

A growth team of agents that researches, writes, runs ads and reports, around one number your marketing lead owns.

Goal · Demos booked a month

Common questions

What is the difference between an agent team and a fleet?

An agent team is a group of specialists around one function. A fleet adds a supervisor that assigns the work, checks it against a number and asks a person when a decision matters.

Can a fleet act without approval?

Anything a customer sees waits for a person by default, and you choose what the fleet may do alone as trust grows.

Who coordinates the fleet?

The supervisor agent coordinates the specialists. People decide at the points that need a person.

Give a fleet its first goal.

Book a demoJoin the waitlist