Thirteen agents run the whole Amazon business.

A Sydney pet brand was running its Amazon business out of data scattered across systems, with the analysis done by hand and the routine work eating the day. We built a team of thirteen specialist agents that watch the business, run the routine work, and answer any question about ads, inventory or margins on demand. A briefing lands in Slack at 9am.

01

The problem

Running an Amazon business well means pulling data from a few places, ad performance, inventory, settlements, and doing the analysis yourself to work out what it means. Is this campaign earning its keep or quietly bleeding money? Is that product about to run out?

None of those are hard questions on their own, but answering each from scratch takes time, and the context-switching adds up. The expensive problems rarely announce themselves. A suppressed listing or a stockout in peak season shows up in the data well before it shows up in the revenue.

02

What we built

A team of thirteen specialist agents, each looking after one corner of the business. A CEO orchestrator routes every input to one agent and pulls the answers back into a single report. Under the hood it is deliberately unexciting: Claude for the reading and reasoning, n8n for scheduling, and connectors into Amazon, Xero and Slack.

TriggerCEO routes to agentsAgent reads a serviceMemory
⏰ Cron 9am
daily briefing
⏰ Cron hourly
health scan
Slack events
messages, asks
⌨ System cmds
$INIT $STATUS
⚠ Big calls
over a threshold
CEO
Routes each input to one agent, then pulls the answers back.
Slack Listener
always on, routes events
Dedicated agents
ScoutMetaPPCMarketing
Claude sub-processes, in parallel
Mask agents
FinancialInventoryMarket IntelReview IntelAccountant
CEO takes the persona, then returns
Tools & protocol
Review RequestCouncil, big calls
Python tool. Bull, Bear, Balanced, then a chair
Amazon SP-API
sales, orders
Amazon Ads
campaigns, spend
Supabase
agent memory
Notion
catalogue, POs
Slack #reports
reports, alerts
Xero
the books
Memory, cache-first, shared by every agent
L1In-process cache · fastest, about four hours
L2 Supabase · the source of truth, shared
L3Disk backup · a fallback if Supabase is down
Every agent checks memory before any API call. Fresh? use it and skip the call. That cut external calls by about 78 percent.

Secrets are injected fresh on every run; scheduling runs on n8n.

Triggers
Cron 9amdaily briefing Cron hourlyhealth scan Slack eventsmessages, asks System cmds$INIT $STATUS Big callsover a threshold
CEO orchestrator
CEOroutes each input to one agent, pulls answers backSlack Listeneralways on
13 specialist agents
Dedicated, run in parallel
ScoutMetaPPCMarketing
Mask agents, CEO takes the persona
FinancialInventoryMarket IntelReview IntelAccountant
Tools & protocol
Review RequestCouncil, big calls

Bull, Bear, Balanced, then a chair.

Reads & writes services
Amazon SP-APIsales, ordersAmazon Adscampaigns, spendSupabaseagent memoryNotioncatalogue, POsSlack #reportsreports, alertsXerothe books
Shared memory, cache first
L1 in-process~4 hoursL2 Supabasesource of truthL3 diskfallback

Every agent checks memory before any API call. About 78% fewer external calls.

  1. 01

    Thirteen specialist agents each own one part of the business: ads and bids, stock and reorder timing, margins, competitor pricing, reviews and the books.

  2. 02

    A CEO orchestrator routes every input to exactly one agent and pulls the results back into a single report.

  3. 03

    It runs on triggers: a 9am briefing, hourly health scans, and Slack messages or questions whenever the owner asks.

  4. 04

    A shared memory layer lets agents reuse fresh data instead of refetching it, which cut external calls by about 78 percent.

  5. 05

    It connects to Amazon SP-API and Ads, Xero and Notion, and Slack, with secrets injected fresh on every run.

  6. 06

    Decisions run in tiers: small actions run and get logged, medium ones land in Slack to approve, the big calls go through a structured review first.

03

What we had to figure out

Amazon data lives in many places and updates on its own schedule

Ad data, inventory, settlements and reviews all refresh at their own pace. The agents had to know when their data was fresh enough to act on, so we built a memory layer that tracks how old each source is and decides whether to reuse it or fetch again. That cut external calls right down and made the whole thing quicker.

The first briefings read like a raw dashboard dump

Early versions listed the numbers accurately and stopped there. They told the owner what had happened and left him to work out whether it mattered. So each agent now says what the numbers mean and what to do about it.

The hard part was making it run unsupervised

The individual agents were never the hard bit. It was making the whole thing dependable enough to run every day with nobody watching. Error handling, freshness tracking, and falling back gracefully when a source goes down. That is what decides whether an agent system can be trusted in production.

04

The result

~15 hrs/wkOwner time back

The 13 agents now run the work the owner used to do by hand every week: the analytics, inventory checks, ad tweaks, bookkeeping, review-request emails and competitor monitoring. For a seller doing all that themselves it adds up to about 15 hours a week, ongoing.

9amDaily briefing

A full briefing lands in Slack every morning before the owner starts, pulled from every connected system. Sales, inventory, ad spend and margins are all in one place by 9am.

SecondsAnswers on demand

Any question about ads, margins, inventory or competitors comes back in seconds, with current data. No spreadsheet to open and no report to wait for.

$150/moRunning cost

All 13 agents monitor the business around the clock for $150 a month, on Claude plus n8n and the connectors. That is the full ongoing cost to keep them running.

Figures from the running system.

Published with the client's permission. Identifying details withheld at their request.

Talk through a problem like this one.

A free intro call. we'll show you where your hours are and what they're worth.