How it works

Live in weeks, not quarters.

Two build paths, one system. Here is exactly what happens after you say yes.

See the live demo

Build it with us

8 weeks

The bootcamp and the mentorship run the same eight weeks.

Cadence

1 meeting/week

The build path is one meeting per week for eight weeks.

Built for you

14 days

Your team’s calendar is not required. We need accounts, not meetings.

First system live

30 days

30 days in, your first system is already live.

The build path

Eight weeks, week by week.

8 weeks

The bootcamp and the mentorship run the same eight weeks. The bootcamp runs them in a group. The mentorship runs them one to one, on your accounts.

Mentorship: 30 days in, your first system is already live.

Start on the free webinar
usemai.com / workspace / accounts
Week 1Foundations and accounts01 / 08

Revenue, yesterday

$9,418

Ad spend

$3,127

Blended MER

3.0×

Three sources, one number06:12 · reconciled
Meta Adsattributed, 7-day click$9,982
GA4last non-direct$9,610
Shopifyorders banked$9,418
Shopify is the number we report on. Meta over-attributed by 6%.
We map your funnel, your margins, and your stack, then get every account connected.demo data
AS

Install progress

Day 9 of 14

On schedule

Accounts

6 of 6

Modules on

9

First report

Day 14

Install steps14 days
1. Access and auditAccount access · Funnel and margin audit · Stack inventoryDone
2. InstallPlatform install · Module configuration · Data reconciliationDone
3. Integrate and trainTool integrations · Business context load · Team walkthroughRunning
4. Live and managedGo-live · Morning reports on · Managed from hereQueued

demo data

The partnership path

Or we install it in 14 days.

14 days

The partnership path skips the build weeks. You grant access, we install and operate, and the reports start landing in two weeks.

  1. 1

    Days 1 to 2

    Access and audit

    You grant scoped access to your store, ads, and email. We read what is actually happening before we touch anything.

  2. 2

    Days 3 to 7

    Install

    Your OS platform goes up on your own server with the modules your business needs turned on.

  3. 3

    Days 8 to 12

    Integrate and train

    Every tool gets connected, Hermes gets your business context, and your team learns the approval flow.

  4. 4

    Days 13 to 14

    Live and managed

    The reports start landing, the calendar starts filling, and MAI keeps operating it from there.

Your team’s calendar is not required. We need accounts, not meetings.

The operating loop

Then it runs on a loop.

Once the build is done, the OS keeps going around this circle without being asked. Each stop is owned by a module, and every handoff is something a person can read and approve.

  1. Plan · Campaign ManagerLive01 / 05

    Planned ahead

    3 weeks

    Campaigns

    4

    Assets briefed

    22

    September calendarplanned 24 Aug
    MTWTFSS
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    Labor DayBundle launchWelcome flow rewriteFall drop teaser

Pick any stage to read what it does. Nothing in the loop sends or spends until a person approves it.

The bots layer

Manager bots keep it running.

Not another chatbot, and not a workflow you babysit. Every system belongs to a manager bot, the bots work in channels you can read, and nothing ships without a human approving it.

Every bot has a channel

Each manager bot owns its systems and runs them from one channel. Open it and read every move, like any other conversation.

They talk to each other

A campaign needs statics, a landing page, and three emails. The bots split that work across their channels and hand the results back.

You stay in the loop

Anything that ships or spends waits in the channel as queued on approval. One click clears it. Everything else just gets done and filed.

What that looks like in practice

#launch-labor-dayA promo goes out on time.

You

Labor Day sale, 20% off bundles, runs Friday to Monday.

Ops lead

Booked. Splitting it up: offer, eight statics, three emails.

Creative

Eight variants done, sized for Meta, brand check passed.

Email

Three sends drafted. Waiting on your approval to schedule.

You approve once. It ships Friday 09:00.

#emailA leak gets found and fixed.

Email

41% of new subscribers open a code that already expired.

Reporting

That gap is worth about $3,400 a month at last month’s rate.

Email

Fix drafted: second email at 20 hours, code valid seven days.

One click in the morning report. Live on the next send.

#adsAd spend stops bleeding.

Ads analyst

Two ad sets have run above target for nine days.

Reporting

Checked against Shopify. Meta is over-attributing by 6%.

Ads analyst

Move their budget to the three under target. Saves $780 a week.

Approve or not. Either way, the reason is written down.

Runs on your serverScheduled checksOwner assignedDocumentedHandover included

Before and after

Your growth work, before and after.

Same team, same budget, same stack. The difference is that the work now has an owner that never forgets it.

Before

Before the OS

  • Meta, Triple Whale and Shopify never agree
  • Campaigns planned the week they launch
  • Creative waiting on one designer
  • Landing pages waiting on a dev ticket
  • Klaviyo gaps found in a quarterly audit
  • Every report is somebody copying cells

After

Live

After the OS

  • One reconciled morning report
  • Next month on the calendar already
  • On-brand statics the same day
  • A landing page per angle, no tickets
  • Klaviyo audited daily, gaps ranked by dollars
  • Reports arrive before you ask

Ready when you are

Watch the build path on a live system.

On the discovery call we open a working Growth OS and walk the eight weeks in order, with the tools named. Then we show what a partnership install looks like.

See the live demo

No commitment · 30 minutes · Custom system map included