Roadmap and architecture Prepared for Huseyin T. · 26 September 2026 Valid 30 days · Mike Navitsky
Proposal · AI operating system for a new Shopify brand
Three departments on AI agents, live on launch day.
You launch a Shopify brand in six weeks. Nothing is built yet. You want Customer Support, CRM & Retention, and Marketing running on AI agents from day one, then the same system on your other brands. This page says exactly what gets built, what runs where, what it costs, and what is not included.
6 weeks
Kickoff to launch. Three departments live, every action that touches money or a customer behind an approval step.
$18,000
Fixed build price. Four Upwork milestones, each released when you have seen that part working.
$3,500 / month
To run it after launch: monitoring, fixes, and new agents and integrations added month by month.
What gets built
Your architecture document has the right shape: founder, a Jarvis that routes work, departments, specialist agents, a second brain, and three governance levels. That is what gets built. One adjustment: in your chart, directors and managers are layers. In the build they are routing and rules inside each department agent, not separate agents. Fewer moving parts, same control, and cheaper to run.
Customer Support
Gorgias · one agent, two jobs
Reads every new Gorgias ticket, pulls the order from Shopify and the tracking from AfterShip, drafts the reply in your voice.
At launch every draft goes to Slack for a one-tap approve. When a ticket type has 50 approved drafts with no edits, that type flips to autonomous. First candidates: where is my order, address change before shipping, sizing.
Refunds, replacements, discounts, and upset customers always stay on approval.
Okendo reviews: positive ones get a drafted reply for approval, negative ones arrive in Slack with the order history attached.
Friday digest: top complaints, top questions, suggested fixes.
Gorgias · Shopify · AfterShip · Okendo · Slack
CRM & Retention
Klaviyo · flows plus one agent
Launch flows built in Klaviyo and tested end to end: welcome, abandoned checkout, post-purchase, winback. Subscription flows (failed payment, cancel save) if you pick Recharge or Skio.
Flow copy and structure by me on your brand email template. Images and layout assets come from your designer.
Retention agent runs every morning: reads Shopify orders and Klaviyo profiles, lists who is due to reorder, who went quiet, who bought twice, and proposes one campaign with the segment and the copy. You approve in Slack, it schedules in Klaviyo.
Segments (first-time, repeat, lapsed, VIP, subscriber) refreshed nightly from order data.
Klaviyo · Shopify · Recharge or Skio · Slack
Marketing
Paid media, content, research · three agents
Paid media agent reads Meta Ads, Google Ads, TikTok Ads, and GA4 every morning and posts one report: spend, revenue, ROAS by campaign, what to pause, what to scale. Budget and bid changes are proposals you approve. At launch it changes nothing on its own.
Content agent drafts text: ad copy variants, email copy, product page copy, from your brand book plus the customer language the support agent collects. Text only.
Research agent pulls competitor ads from Meta Ad Library and TikTok Creative Center weekly and files a one-page brief in ClickUp.
Meta Ads · Google Ads · TikTok for Business · GA4 · Ad Library · Creative Center · ClickUp
Shared by all three
Jarvis. The front door, in Slack. Routes your request to the right department agent, posts the morning brief at a time you pick, escalates anything an agent is unsure about.
Brain. Postgres with pgvector, as your document specifies. Brand book, product facts, decisions, customer language, governance rules, and a log of every action every agent took. Each record carries a brand tag, so brand two shares the platform without sharing the data.
Approval gate. Every write action goes through one executor. It classifies the action from the rules in the brain, posts to Slack if a human must decide, runs it, and logs it.
Command center v1. One web page behind a login: pending approvals, what each agent did today, failures, model spend. Plain and functional. Brand switcher arrives with brand two.
Learning loop. When you correct a draft in Slack, the correction is saved as a rule in the brain and the agent reads those rules before its next draft of that kind. This is a rule store, not model training.
Not included in the six weeks
Images, video, ad creatives, or design of any kind. The agents write text and briefs. A designer, or you in Canva, makes the visuals. Canva and CapCut are not connected.
The other 25 tools on your list. Triple Whale, Motion, Foreplay, Semrush, Similarweb, Reddit, KnoCommerce, Intelligems, Replo, Littledata, Modash, impact.com, Merchant Center, Clarity, Search Console, and the rest are added after launch, one at a time, in the order you choose.
Executive Assistant (Gmail, Calendar, Drive). First item after launch, not inside the six weeks.
SEO, influencers, affiliates, loyalty, a returns portal. After launch, as separate scopes.
The store, the products, the brand book. Shopify theme, product photos, and brand voice document come from you. The agents read them.
A second brand. Rolled out after the first one is live and stable.
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. If a container crashes it restarts in seconds. Each container has its Slack connection, a scheduler for its timed jobs, and its own tool servers (MCP) for the platforms it works with.
The pieces, plainly
Agents: Hermes Agent containers, one per agent, supervised, 24/7. Slack gateway, cron scheduler, and MCP tool servers are built into the runtime.
Models: a setting per agent, not a rewrite. Start with GPT-5.5 for routing and reports and Claude for customer-facing drafts. Switch when one is better or cheaper. Billed to your own API keys.
Executor: one small service in front of every write action. Rules live in the brain, so you change them without a deploy.
Brain: Postgres + pgvector container, nightly backup to S3-compatible storage.
Command center: small web app on the same box, behind Cloudflare Access login.
What is not part of the runtime
My laptop. Claude Code and Codex are my build tools. They write and test the tool servers, skills, and rules. Nothing that runs depends on them or on me being online.
No-code glue. No n8n, Make, or Zapier. The agents and tool servers are code in your GitHub, versioned and testable.
Any account I own. VPS, GitHub, API keys, Slack app: all yours. Revoke my access in a minute and it keeps running.
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.
Assumes kickoff within a week of your yes, 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 to set. If it moves, the plan moves with it.
Milestones and payments
Week 1
Foundation liveWritten blueprint for your stack. Decisions locked: Recharge or Skio, ad accounts, brand voice source. VPS, brain, approval executor, Slack app, and Jarvis running. Command center skeleton up.
$4,000
Week 3
Customer Support liveSupport agent answering seeded test tickets end to end in Gorgias with the approval queue in Slack. Reviews watch on. Friday digest running.
$5,000
Week 5
CRM & Retention liveAll launch flows built in Klaviyo and tested. Retention agent proposing from real order data. Segments refreshing nightly.
$4,000
Week 6
Marketing live, launch, handoverDaily paid media report from your live ad accounts. Content and research agents drafting. Command center v1. Runbooks written. Dry run passed. Brand launched.
$5,000
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. All payment runs through Upwork.
What runs on its own
Every action an agent can take is classified once. The classification lives in the brain, so you change it without a code change. Start conservative, loosen with evidence from the logs.
Level
Rule
Examples at launch
Autonomous
Runs, logs, reports. Read-only or reversible.
Reading tickets, orders, ad accounts. Writing reports and briefs. Tagging and segmenting. Standard support answers once a ticket type has earned it.
Supervised
Runs, shows up in the daily digest, can be undone.
Replying to a positive review. Sending a scheduled flow email. Updating a customer note. Pausing an ad that spent with zero results, inside a cap you set.
Approval
Proposed in Slack with reason and data. Nothing happens until a human taps yes.
Refunds, replacements, discounts. Any ad budget or bid change. Any campaign send. Publishing copy or a site change. Any upset customer. Anything the agent is unsure about.
After launch
Operator plan · recommended
$3,500 / month
I watch every agent daily and fix anything that breaks in what I built, at no extra charge.
New agents and new integrations from your list added on the plan. We set the order together. A read-only integration takes about a week. One with write actions and approval rules takes one to two weeks.
Approval gates loosened step by step as each agent earns it in the logs.
Weekly call, weekday Slack support, monthly cost and performance review.
Covers one brand. Each additional brand on the plan adds $1,000 a month. Month to month, cancel any month. Billed as a monthly Upwork contract.
Care plan · lighter option
$1,500 / month
Monitoring, fixes to what I built, and small tweaks included.
One call a month, weekday Slack support.
New agents and integrations quoted as separate fixed-price Upwork milestones, most between $1,500 and $6,000, agreed before work starts.
Right if the launch build is all you need for a while and someone in-house owns the day to day.
Your other brands
The platform is built for more than one brand from week 1: one VPS, one brain with a brand tag on every record, one command center. Rolling out a brand means connecting its accounts, loading its brand book and product facts, running the agents in supervised mode for a week, then flipping the proven ones. Budget $6,000 per additional brand, two to three weeks each, as its own Upwork milestone. It can start the week after the first launch. 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
Item
Estimate
Notes
VPS (Docker, Postgres)
$60 to $150 / mo
One box carries several brands. Upgrade the box, not the design.
Model usage (OpenAI, Anthropic, Gemini)
$200 to $800 / mo
Estimate. Depends on ticket and order volume. Every call is metered per agent in the command center. Starts low, grows with the brand.
Cloudflare, S3-compatible storage
$0 to $20 / mo
Access login for the command center, nightly backups.
Your tool subscriptions
as today
Shopify, Klaviyo, Gorgias, ad platforms and the rest stay on your accounts, in your name.
Code in your GitHub, data in your database, accounts in your name. Prices in USD. Every payment to me goes through Upwork.
One ticket, end to end
A customer writes "where is my order?". Gorgias receives it and the support agent picks it up within a few minutes.
The agent looks up the order in Shopify, the shipment in AfterShip, and the customer's history in the brain. The parcel is two days late.
It drafts a reply in your voice with the tracking link and a realistic date. At launch, the rule says approval: the draft lands in Slack.
You tap approve. The executor sends it through Gorgias and logs what was said, which data it used, and which rule applied.
After 50 approved drafts of this type with no edits, the rule flips to autonomous. Refund requests never flip. They always wait for a tap.
Friday, the digest shows five late-parcel tickets, all one carrier. The retention agent proposes a small apology offer to those five. You approve. Monday's marketing report shows whether it worked.
Why us
Already built against
Shopify, Gorgias, Klaviyo, Meta Ads, Google Ads, GA4.
Hermes Agent containers on a VPS with Slack and Telegram gateways, cron, and MCP tool servers.
An approval-gated executor on Shopify and a 3PL, running in production for my own brand.
Email triage agents with rule stores, and a shared Postgres + pgvector brain read by several agents at once.
Not yet built against
Okendo, AfterShip, Recharge, Skio, TikTok for Business, ClickUp.
All six have documented REST APIs. They are budgeted as new work, which is why they sit in weeks 2 to 5 and not week 1.
If any of them turns out not to expose what we need, you hear it in week 1 with the substitute, not in week 5.
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 retainer and everything keeps running. Anyone who can restart a container and read a log can take it over.
Next step
Reply in this Upwork thread
Two answers and a 45-minute call
Tell me your launch date and whether it is Recharge, Skio, or no subscriptions at launch. I send the Week 1 milestone on Upwork and we book the kickoff call through the Upwork room. On the call you bring the brand name and the status of your Shopify, Klaviyo, and ad accounts. I bring the first draft of the week 1 blueprint.
If after that call this is not the right build for you, we stop there and you keep the blueprint notes.
Mike Navitsky runs Monadops and an ecommerce brand of his own on this architecture. The systems described for his own brand are live. The ones for yours are proposed. Prices in USD, valid 30 days from the date above. All payments through Upwork.