The super agent for DTC commerce

Eight tools.
One agent.
Zero growth hires.

Shapelab plugs every tool you run your store on into one agent through a single MCP: store, ads, email, analytics, marketplaces, even Canva and Figma for creative. It watches everything, decides what to change, and ships the change. You approve from your phone.

One MCP · every ecommerce tool · approvals from your phone

Overview Agent live Last 7 days
Revenue£48.2k▲ 18.4%
Blended ROAS3.9×▲ 0.6
Stock cover23 daysReorder in 4
Revenue vs ad spendRevenue Spend
Agent queue4 actions
f

Meta Ads 3 ad sets fatigued. New variants built in Figma from your brand kit.

Approve
C

Canva 6 creatives resized for Stories and Reels.

Preview
▣

Inventory Reorder 1,200 units by Friday to cover a 4-week lead time.

Review
✉

Email Win-back subject lines rewritten. Claim check passed.

Shipped
Shapelab MCP Store Ads Email Analytics Canva Figma +6

Product preview · sample data

Reads and writes Shopify Admin GraphQLKlaviyoAmplitudeGoogle Merchant CenterAmazon Seller CentralMeta AdsMicrosoft AdsPeec AI

Super agent

Your whole ecommerce stack, behind one interface.

A DTC brand runs on eight dashboards, eight logins and eight sets of exports nobody reconciles. Shapelab puts one agent in front of all of them. It holds the context across every system, so a drop in Amplitude, a segment in Klaviyo and a listing in Merchant Center are one conversation, not three tickets.

Before

  • admin.shopify.com
  • klaviyo.com/flows
  • app.amplitude.com
  • merchants.google.com
  • sellercentral.amazon.com
  • adsmanager.facebook.com
  • ads.microsoft.com
  • app.peec.ai

8 logins · 8 exports · context lost between every one

After

# one agent, every system as a tool
agent: shapelab
planner: claude-opus
workers: claude-sonnet
mcp_servers:
  - shopify-admin   # graphql, read/write
  - klaviyo         # flows, segments, templates
  - amplitude       # events, cohorts
  - merchant-center # feeds, diagnostics
  - seller-central  # listings, inventory
  - meta-ads
  - microsoft-ads
  - peec-ai         # AI engine visibility
guardrails: [tone-spec, claim-check]

The system

Read, reason, write. On a schedule.

Each agent runs on a schedule, keeps its skill definition in version control, and writes back to the same systems it reads from. No exports to a spreadsheet, no report waiting for someone to act on it.

read

MCP servers on the live stack

Every commercial system is wrapped as an MCP server, so agents query real orders, segments, events, listings and ad spend.

  • Shopify, Klaviyo, Amplitude
  • Merchant Center, Seller Central
  • Meta, Microsoft, Peec AI
reason

Two models, two jobs

Claude Opus does the planning and the judgement calls. Claude Sonnet handles the high-volume passes: diffs, audits, drafts at site scale.

  • Built on the Claude Agent SDK
  • Shared tone specification
  • Pre-send claim check
write

Changes land where they belong

Theme edits ship through the Shopify CLI, flows through the Klaviyo API, listing files to the marketplaces. Each write is versioned and reviewable.

  • Scheduled, not prompted
  • Skills in version control
  • Write-back, not reports
RuntimeClaude Agent SDK, cloud-hosted sessions
PlanningClaude Opus: decomposition, judgement, approvals
ExecutionClaude Sonnet: diffs, audits, bulk drafts at site scale
Integrations8 MCP servers wrapping production APIs (GraphQL and REST)
Triggerscron schedules and platform events (orders, inventory, visibility exports)
Skillsversioned in git, changed by pull request, reviewed like code
Write pathShopify CLI theme pushes, Klaviyo API, marketplace listing files
Verificationpost-write checksum against the live store; refused files surface, not vanish
Guardrailsshared tone spec + pre-send claim check (MoCRA, FDA labelling, EU CPNP)

In production

Four pipelines running today.

These run against a real store with real inventory and real regulatory exposure. They are the proof, not the pitch.

Demand and visibility

Live

Pulls prompt-level AI engine visibility exports, diffs them against live product and content pages, generates page-level changes, and pushes theme edits through the Shopify CLI.

Peec AIShopify CLIpage-level edits

Lifecycle messaging

Live

16 flows and 61 always-on emails, specified as structured definitions and built against the Klaviyo API. Customer state is modelled as dynamic segments computed from Shopify events, not stored properties.

16 flows61 emailsevent-driven segments

Organic growth

Live

Social reply triage, PR outreach and publishing across four platforms. Every message passes a shared tone specification and a pre-send claim check, because cosmetic claims are regulated.

4 platformsMoCRAFDA labellingEU CPNP

Catalogue operations

Live

Marketplace listing file generation, INCI and compliance data, and image filename and alt text audits across the whole site.

listing filesINCIalt text audits

Results

What it does once it is switched on.

+100%growth in 3 daysClient A
16 / 61flows and always-on emails built through the Klaviyo APIkoppa beauty
4social platforms triaged and published behind one claim checkkoppa beauty
6markets run by a team of twokoppa beauty

Runs from your phone

Run the store from the train.

The agents run in the cloud, not on a laptop that has to stay open. Scheduled jobs fire whether you are at a desk or not. When one needs a decision, it asks on your phone: approve a rewrite, preview a theme change, redirect a run, or ask it anything about the business in plain language.

  • Approvals and previews from any device
  • Ask questions across every connected system
  • Start, pause or redirect a run on the move
shapelabrunning
Claim check stopped 2 Instagram replies. "Heals scarring" is a drug claim under FDA rules. Rewrite ready.
"Copper peptides support the skin's own repair process."
ApproveEdit
Also, why did serum traffic dip yesterday?
Amplitude shows the dip is all Meta. The prospecting ad set hit its cap at 11:00. Organic and email sessions were flat.

Example conversation

Next

The part we will sell.

The next agents make the decisions that cost the most when they are wrong: spend, demand and stock.

Spend control

Building

The agent reasons about a budget ceiling across Meta and Microsoft Ads instead of obeying a static cap. It moves money toward what is working and explains why.

Demand prediction

Building

Behaviour and demand forecasts from first-party event data in Amplitude and Shopify, not third-party panels.

Reorder sizing

Building

Inventory reorder quantities sized against three to four week manufacturing lead times, so you reorder before the stockout, not after it.

One dashboard, read and write. It is the agent's interface, not a report. You see what it plans to do, approve or adjust it, and the change goes out from the same screen.

Join the waitlist

Tenant zero

Proven on our own brand first.

koppa beauty

A GHK-Cu copper peptide skincare brand, and a real business.

koppa has inventory, regulatory exposure and customers in six markets. It is exactly the problem we are solving: genuine operational complexity and no headcount. Every agent runs on koppa before it runs for anyone else.

Visit koppabeauty.com ↗
6markets
4SKUs
2people
3regulatory regimes
MoCRA · FDA labelling · EU CPNPchecked before anything is sent

Who builds it

Built by an operator who has shipped software at scale.

Our founder is also Head of Product at My Study Life, a cross-platform student planner with 24 million lifetime downloads across 197 countries.

Early access

Running a DTC brand with a small team?

We are opening Shapelab to a small number of operators with the same problem we had. Tell us about your store and we will be in touch.

Or email hello@shapelab.me

FAQ

Questions operators ask.

Is this a dashboard or an agent?

An agent. The dashboard on the roadmap is how you read and steer it, but the work happens on a schedule whether you open it or not.

Which platforms does it work with?

Shopify Admin GraphQL, Klaviyo, Amplitude, Google Merchant Center, Amazon Seller Central, Meta Ads, Microsoft Ads and Peec AI today. Each is wrapped as an MCP server, so new systems are added the same way.

Will it publish things I have not approved?

Outbound messages pass a shared tone specification and a pre-send claim check. You decide which pipelines write automatically and which wait for approval.

Why does the claim check matter?

Cosmetic claims are regulated: MoCRA and FDA labelling rules in the US, CPNP in the EU. One wrong word in a reply or an email is a compliance problem, so every claim is checked before anything goes out.

Do I need to be at a computer?

No. The agents run in the cloud on their own schedules. You approve, preview and redirect them from your phone.

Who is it for?

DTC operators with real operational complexity, such as inventory, several markets and regulated products, and not enough people to run a growth team.

When can I use it?

The production pipelines run on koppa beauty now. We are onboarding a small group of operators ahead of the spend, prediction and reorder agents. Request access above.

Run the whole commercial side with the team you have.

Request early access →