A fleet per client

A separate reporting fleet for every client you run

Reporting is where agencies quietly lose their Fridays — and where client data quietly leaks between accounts. Sprawl runs it differently. Each client is its own project, its own fleet, on that client's own connected accounts: their inbox, their Slack, their project tools. You describe the reports you want once; Sprawl provisions an agent, gathers from the right client's stack, drafts in plain language, and delivers them — every report that goes out by email waits for your approval. One client's fleet never touches another's data.

Set up a client fleet Explore workflows

Client-facing weekly update

Per-client wins, blockers, decisions, and next steps — drafted from that client project on its own connected accounts, not from memory.

Internal pipeline roll-up

A cross-fleet view of what shipped, what slipped, and where capacity is going, pulled from every client project at once so you can replan.

Owner-level monthly summary

Retainers active, churn risks, hours by client, and one-line health notes — rolled up across all your client fleets.

Start with one client, then add the next

Stand up one client as its own project on its own accounts. Get the gathering and drafting reliable there. Once that fleet runs cleanly, describe the same workflow in a new project for the next client — different connected accounts, no data crossing between them.

Plain-English workflow

Every Friday, inside each client's project, gather this week's updates from that client's own tools, draft their weekly report and my internal roll-up, and send each report once I approve it.

Give each client its own project, connected to its own accounts — inbox, chat, project tools, and CRM.
Inside each project, gather the past week of updates from its connected tools only.
Draft the client update, internal roll-up, and owner summary in plain language, without inventing facts.
Deliver each report once you approve it, and check with you first on anything sensitive.
Keep every client isolated inside its own fleet, so one project never reads another.

Sources to gather from

Project management tools (Linear, Asana, Jira, Trello, ClickUp)
Time tracking and timesheets
CRM and pipeline records
Shared docs, briefs, and SOWs
Team chat channels and threaded decisions
Inbox threads tagged to the client

What always checks with you first

Money always checks with you first — anything that spends, refunds, or bills.
Deletions always check with you first — nothing is removed on a hunch.
Every report sent by email asks before it sends: the first to a new client contact and every routine one after it.
Never invent metrics, hours, or outcomes that are not in the source tools, and never hide bad news — surface it factually.
Never blur one client fleet into another — each project stays on its own accounts.

What each client fleet delivers

A good first setup has each client's fleet prepare the client-facing weekly update, the internal roll-up, and the owner summary from that client's own accounts. Every report it emails waits for your approval, so tone and sensitive details get your eye before anything goes out.

How Sprawl fits

Sprawl is for operators and agencies running more than one thing at once. You describe an outcome; Sprawl provisions an agent and runs it for you — there is no canvas to wire and no chat to babysit.

The unlock for agencies is isolation. Every client is a separate project with its own fleet on its own connected accounts — a different Gmail, Slack, and set of project tools per client. One client's agent only ever sees that client's data.

It runs on the best fit from 200+ models across ~25 providers — Anthropic, OpenAI, Google, and more — on a schedule or from triggers — and it checks with you on money, deletions, and every email before it sends.

Give your first client its own fleet

Pick one client, connect its accounts, and let Sprawl gather and draft the reports — every emailed report waits for your approval.

Start with one client