Launch day: three departments run on AI. Month six: your whole org chart.

You want your Shopify brand run by the AI company in your document. This is the plan to get all of it. The three departments that touch every order go live at launch. The rest of your chart follows in three phases, about one integration or agent a week, until every box is live around six months after launch. Every role and every tool on your list has a phase and a price below.

What you asked for, what you get

What runs without you from day one

The point is fewer things on your desk. Anything reversible or read-only runs on its own from the first day. Approvals stay only where money moves or a customer is upset. Each approval is one tap in Slack, and every tap trains the rule that removes the next one.

Jarvis sits above all three in Slack. It posts one morning brief grouped by department, routes your requests, and escalates anything an agent is unsure about. A watchdog checks every agent ran and every integration answered, and tells you if not.

How you will know it works

The command center tracks these from day one, per brand: share of tickets closed without a human, first-reply time, approvals per day and how often you edit a draft, Klaviyo flow revenue, ROAS by channel, and model cost per order. If an agent is not earning its place, the numbers show it within weeks.

Your org chart, phase by phase

This is your chart from your document, every role in it. In the build, each specialist is a skill inside its department agent, not a separate server. You still see every role: each action in the log is tagged with the role that did it. Same reporting lines, far fewer moving parts, lower running cost.

All 41 tools, by phase

What actually runs on your server

Not a chat window and not my laptop. One VPS in your name, Ubuntu and Docker. Each agent is its own container running Hermes Agent, an open-source (MIT) agent runtime from Nous Research, under a process supervisor. It runs 24 hours a day and restarts itself in seconds if it crashes. Each container has its Slack connection, a scheduler for its timed jobs, and its own tool servers (MCP) for the platforms it works with.

This is the setup I run for my own ecommerce brand today: five always-on Hermes agent containers on one VPS, an operations agent with an approval-gated executor on Shopify and the 3PL, an email agent, and a shared Postgres + pgvector brain. Nine scheduled production agents, 62 automation scripts, four sales channels.

A-Z architecture

Top to bottom. You talk to Jarvis. Jarvis routes to a department. Department agents propose actions. The gate decides whether an action runs now or waits for you. Approved actions go to your tools. Everything is written to the brain, which every agent reads before its next task.

Your learning loop, at launch

The example from your document, step by step, with what runs at launch.

Phase 1: six weeks to launch

If kickoff is Monday 5 October, launch is the week of 9 November. Assumes your accounts (Shopify, Gorgias, Klaviyo, ad accounts, Slack) exist by the end of week 1 and someone on your side answers questions the same day. The launch date is yours. If it moves, the plan moves with it.

Milestones and payments

Four fixed-price milestones on Upwork, total $18,000. Each is funded when it starts and released when it is live and you have seen it work. If a milestone slips because of me, it is not released until it is live. If it slips because an account or an answer is late on your side, the date moves and the price does not.

Phases 2 to 4: the rest of your chart

Months assume kickoff on 5 October 2026 and shift with your launch date. Pace on the Operator plan is about one integration or one new agent a week. You can reorder anything between phases. If you want the chart done sooner, phase 3 or 4 can run as its own fixed-price build next to the plan, quoted when we get there.

What runs on its own, the rules

Every action an agent can take is classified once. The classification lives in the brain, so you change it without a code change.

After launch

Your other brands

The platform is multi-brand from week 1: one VPS, one brain with a brand tag on every record, one command center with a brand switcher. Rolling out a brand means connecting its accounts, loading its brand book and product facts, running the agents supervised for a week, then letting the proven ones run. Budget $6,000 per additional brand, two to three weeks each, as its own Upwork milestone. Best start is January, after Black Friday. A brand that already runs Klaviyo and Gorgias takes the longer end, because we map what exists first.

Running costs, paid by you to the providers

Honest notes

One person, start to finish. You get me on the weekly call and in Slack, not an account manager. You own the code, the server, and the data. Cancel the plan and everything keeps running. Anyone who can restart a container and read a log can take it over.

Next step