For managing directors and marketing directors of e-commerce brands

Your data is not the problem.
The decision is.

Every e-commerce brand past £5M has more data than it knows what to do with, and a leadership team that still cannot say what to change on Monday morning. That gap is where the cash goes.

The situation

It lives in six systems that do not talk to each other

Shopify knows what sold. Meta and Google know what you paid to sell it. Klaviyo knows who opened the email. The ERP knows what is left in the warehouse. The warehouse system knows what is actually on the shelf, which is not always the same thing. Xero knows who has not paid you yet.

Shopify
What sold
Meta & Google
What you paid
Klaviyo
Who opened it
ERP
What was ordered
WMS
What is on the shelf
Xero
Who has not paid

Six sources of truth. No truth.

So the MD asks a simple question. How much cash is tied up in stock that is not moving? Someone disappears into spreadsheets for two days. The answer lands on Thursday, and by Thursday it has already moved.

Why the dashboard did not fix it

Centralising the data changes nothing on its own

So you buy a BI tool. Now all the numbers live in one place, and the decisions still do not get made. You look at it in the morning. You look at it again after lunch. Brendan calls this data voyeurism, and it is exactly the right phrase for it. Watching your numbers is not the same as running your business.

Forty charts. Every one of them accurate. Not one of them tells you whether to cut the TikTok spend this week or leave it alone.

More reporting produces more looking. It does not produce a decision.

What it actually costs

So the four decisions that move cash never get made

The decisions that change a commerce P&L are always the same four. Kill the spend that stopped working. Move it to the spend that is working. Order more of what is selling. Discount what is not.

Every one of those answers is already sitting in your data. They do not get made, because making one properly means holding marketing, stock and cash in your head at the same time, and nobody does that at 7am on a Tuesday with a board pack due.

Cash frozen in stock
Lines sitting on 180 days of cover whilst the money that bought them could be funding the lines that sell.
Spend on dead campaigns
Budget still running on a cohort that stopped returning three weeks ago, because nobody joined the ad account to the margin.
Stockouts on the winners
The SKU with the best return in the account, out of stock, because the reorder point was never joined to the sell rate.

All three are free cash flow leaving the business. For a commerce company, free cash flow is the whole game.

Worth saying plainly

This is not a competence problem

The MDs and CMOs we work with are sharp operators who know their category better than any consultant will. Hand the best of them six platforms, 6,200 SKUs and no joined-up view, and they will still miss the £27,000 sitting in a wool throw that is selling out whilst the budget goes somewhere else.

Nobody is short of intelligence here. They are short of a surface that does the joining, so the judgement they already have gets pointed at the right thing.

Not a talent problem. A surface problem.

What actually fixes it

A decision layer, not another dashboard

One surface with the marketing, the sales, the stock and the cash joined into a single view. That part is table stakes and Supermetrics does most of it out of the box.

The part that is not table stakes is what sits on top. Something that knows the margin on every category, the lead time on every supplier, which one of them runs late, and where the business is actually trying to get to. It reads the joined data every morning and comes back with what to do next, in order, with the number attached and the reason stated.

You stay the gatekeeper. Nothing moves without you approving it.

Stop reading your data. Start deciding on it.

The agentic layer

That layer is Claude

A good chief of staff knows the business inside out, walks into the room having already done the reading, and puts the decision in front of you clean. They never take the decision. That is the job Claude does. Your marketing agents sit inside it, and it sits between your data and your Monday morning.

A dashboard knows your numbers. It does not know that Tableware carries your Christmas, that TerraStudio always runs a week late, or that the board agreed in January to hold margin above 50% even if it costs volume. Claude holds all of it.

01
Business context
What you sell, who buys it, which categories carry the year, what the board actually signed off. The things a new marketing director takes six months to learn.
02
Your data
Every connected source in one place and current. Marketing and sales through Supermetrics, stock and cash through the Build On bridge into the ERP and warehouse.
03
How you operate
Your lead times, your supplier behaviour, your approval chain. Who can release £4,000 of extra spend without asking, and who has to.
04
Your SOPs
What expediting a PO actually means here. Which template, which contact at the supplier, and what happens when OTIF drops under 85%.
05
The strategic vision
Where you are trying to get to over three years. Without it an agent optimises this month and quietly damages next year. Discounting to free cash is right on Tuesday and wrong if you are building a premium position.
Claude The agentic layer
Your marketing agents, and the chief of staff that briefs you
Business context Operating model SOPs Strategic vision
The joined dataset One pane of glass
Marketing, sales, stock and cash in a single view, joined on SKU and channel
Supermetrics
Marketing and sales, 170+ connectors, through the MCP server
IgniteAI Build On
ERP, warehouse and cash, through a custom MCP bridge

It does not make the call. It makes the call clear.

Act one said this was a surface problem rather than a competence one. This is the surface. Claude does the part nobody can do at 7am, which is holding the marketing, the stock, the cash, the SOPs and the three year plan in mind at the same time.

What comes out is not an instruction. It is your decision, with the fog cleared, the number attached and the reason stated. You still say yes or no, and nothing moves until you do.

Your judgement. Now with something worth judging.

What that looks like

Here is the surface, running on a real trading month

Composite data from a 6,200 SKU homewares brand. Change the range, the channel or the category and every figure recomputes, because all of it derives from the same joined dataset. The queue at the bottom is Claude's brief on what that data means today.

You are looking at a working demo. Composite, anonymised data for a homewares retailer. Every control recomputes the whole surface, including the decision panel at the bottom.
Ignite AI Solutions
Built on the Supermetrics MCP server, extended with a custom ERP and WMS bridge.
Live 6,200 SKUs £5.9M run rate 20 employees Last 30 days

The MD's pane of glass

Where money comes in, where it goes out, where it gets stuck.
Shopify Plus Klaviyo Meta Ads Google Ads TikTok Ads Pinterest Ads Brightpearl ERP WMS

Forge

Product content pipeline

Range
Channel
Category
Revenue
£0
+0.0%
Blended ROAS
0.00x
+0.00
Gross margin
0.0%
+0.0pp
Freight up 4%, watch
Stock cover
0d
+0d
AR balance Ledger
£0
+£14K
Open POs
£0
0 inbound

What this demo proves. Supermetrics pulls the marketing and sales surface in sections one and two natively, through their MCP server and 170+ connectors, with no code. The IgniteAI Build On layer extends that view with supply chain data from the client's ERP and WMS, then runs an agentic decision layer on the joined dataset. The MD sees one pane of glass.

1. Marketing performance Supermetrics native

Daily spend, channel ROAS and top campaigns, pulled live from the connected ad platforms and GA4. Scope:

Daily spend vs revenue
Revenue Spend
ROAS by platform
Top campaigns by revenue
CampaignPlatformCategorySpendRevenueROAS
2. Sales and customer Supermetrics native

Revenue by channel, order economics and geography, pulled from Shopify and Stripe. Customer behaviour is joined to acquisition channel, so the attribution is real rather than last-click.

Revenue by channel
Sales engine
Order economics for the current scope
Average order value
£0
Repeat rate, 90d
0%
New vs returning
0 / 0
CAC, blended
£0
Top SKUs by revenue
SKUCategoryUnitsRevenue
Geographic split
Below this line, IgniteAI Build On extension
3. Supply chain IgniteAI Build On

Stock cover, stockout risk, open POs and supplier OTIF. None of this is native to Supermetrics. The Build On layer bridges the Brightpearl ERP and the warehouse management system into the same surface through a custom MCP server, joined to the marketing and sales data above.

Stock cover by category
Days of cover against an 81 day target
Under 35d Under target At or over
SKUs at stockout risk
Open POs and incoming stock
Supplier OTIF, last 90 days
On time, in full. Below 85% triggers escalation.
Accounts receivable ageing Not filtered
4. MD decision panel IgniteAI agentic

Claude reading the joined data against everything it knows about the business. One queue, ordered by what it costs you to wait. Every row states the cash going out, the cash coming back, and which systems had to be joined to see it. This is the panel that exists nowhere else, because no other system holds both halves of the picture.

Claude, this morning

Cash to deploy
Where this sits today. Human plus Claude plus MCP in chat, moving to an agentic workflow with you as gatekeeper. Approving a row queues it. In the live system the marketing agents inside Claude then pause the campaign, shift the budget or draft the PO amendment through the same MCP surface that pulled the data in. Nothing moves without you pressing the button.

What Supermetrics delivers

Live marketing and sales data from 170+ platforms, plugged into Claude through the MCP server. No code, no spreadsheet phase. Marketers ask in plain English and get charts, tables and forecasts back. AI Chats for self-serve, Build On for custom systems like this one.

What IgniteAI Build On adds

The supply chain bridge into ERP and WMS, the agentic decision layer that turns data into next actions, and the dashboard surface an MD actually opens every morning. Productised on top of Supermetrics, sold and delivered as a joint capability.

See this running on your own numbers

Twenty minutes with Chris. Bring your Shopify, your ad accounts and your ERP, and walk out with a real read on where your cash is stuck and what to do about it first.

What an AI build layer is, and what it does for an e-commerce business

What is an AI build layer?

An AI build layer is a thin system built on top of the tools a business already runs, which joins their data into one view and adds a decision layer over it. It does not replace the Shopify store, the ERP, the email platform or the ad accounts. It reads from all of them, reconciles them into a single set of numbers, and then uses a model to surface the handful of decisions that matter that morning. The word “build” is doing real work here: this is assembled around one company's actual stack and processes, not bought as a product and configured afterwards.

The pane of glass above is a working example of that, running on composite data from a homewares brand of the size we usually build for: around £5.9M annual run rate, 20 employees, 6,200 SKUs, selling through Shopify Plus with Klaviyo, Meta, Google and TikTok on the marketing side and Brightpearl on the ERP side. The filters, the charts and the decision cards are all live. The numbers behind them are anonymised.

What is a single pane of glass for e-commerce?

A single pane of glass for e-commerce is one screen that shows revenue, ad spend, margin, stock cover and cash position together, sourced from the systems that own each number. The reason to build one is not tidiness. It is that the decisions an MD has to make are cross-functional, and the data is not. Whether to keep spending on a campaign depends on the margin of what it sells and whether that line is about to go out of stock. Whether a cash squeeze is a problem depends on whether the receivables behind it are collectable. Nobody can answer those questions from a marketing dashboard, because half of each answer lives in a different system.

Most businesses of this size solve it by having someone rebuild a spreadsheet every Monday. That works, and it costs a day a week, and it is always looking backwards. The point of joining the data properly once is that the answer is there before the question is asked.

Which data sources does the Build Layer connect to?

The marketing surface is pulled natively through Supermetrics, which covers more than 170 connectors across ad platforms, email, analytics and e-commerce, and which we read through MCP so the model can query it directly rather than waiting on a scheduled export. The commerce and supply-chain surface (ERP, warehouse management, purchase orders, receivables) is joined by IgniteAI, because that half is rarely standardised and almost never has a connector waiting for it.

That split is worth understanding before commissioning anything. The marketing half of an e-commerce data problem is largely solved by existing connectors and is comparatively cheap to stand up. The expensive, differentiating half is the join: reconciling an ERP's view of a SKU with the store's view of the same SKU, and both with what the ad platform thinks it sold. That is where a build earns its cost, and it is why buying another dashboard tool usually does not fix the problem.

What does the agentic decision layer actually do?

The decision layer is the part that reads the joined data and proposes actions before someone asks it to. Rather than answering questions on request, it watches the same set of conditions every day: stock cover falling below target on a line that is currently being advertised, margin eroding on a category while spend holds steady, receivables ageing past terms on accounts that are still being shipped to. It raises the ones that have crossed a threshold, with the numbers behind them attached. It anticipates instead of reacting.

It proposes. It does not act unilaterally. Every card carries the working that produced it, so the person reading it can disagree with it, and a human makes the call. That is a governance decision as much as a design one, and it is deliberate: an agent that quietly changes ad budgets or reorders stock is an agent nobody can audit six months later. We write that boundary down before anything is built. Our approach to that is set out on the AI governance page.

Is the Build Layer a SaaS product or a bespoke build?

It is a build, not a SaaS product. There is no sign-up page for the pane of glass above, because the value of it is that it matches one company's systems, categories, margin structure and reporting cadence. What is reusable is the method: how the data is joined, how the decision layer is specified, how the governance boundary is written. That is what we bring. The result belongs to the client and runs against their own accounts.

In practice most engagements start with a SPARK Discovery, which establishes what data actually exists, in what state, and which decisions are worth automating first. That answer is different for every business, and it is the difference between a build layer that pays for itself and an expensive second dashboard. If you want the wider picture of how we scope this kind of work, bespoke AI solutions covers it, and our build services covers the rest of the delivery model.

What is Forge, and how does it relate to the Build Layer?

Forge is a separate IgniteAI system, built on EVA (Enhanced Virtual Assistant), which turns inconsistent manufacturer product data (CSVs, PDFs and spec sheets that all describe the same thing differently) into brand-true, SEO-ready product listings automatically. It appears on this page because it feeds the same class of business, and because it demonstrates the same discipline applied one layer down: take a messy input that a person is currently normalising by hand, and make it consistent and fast without losing the brand's voice. It is proven on a real kitchenware retailer.

Is the data shown on this page real?

The system is real and the behaviour is real. The data is composite and anonymised. Every filter, chart and calculation above runs live in the browser against a modelled dataset built to look like a homewares brand of that size, so what you are testing is the actual logic rather than a set of screenshots. We publish it this way deliberately: showing a client's live commercial numbers to demonstrate a build would be a clear breach of their confidence, and a consultancy that would do that to them would do it to you.

Who this is built for

The shape above suits a business that has outgrown its reporting but has not outgrown its team: typically £2M to £30M of revenue, a headcount somewhere between 15 and 200, several channels, real inventory, and an MD who is still personally close enough to the numbers to act on them the same day. Below that scale, a well-built spreadsheet is really the right answer. Above it, there is usually a data team and the conversation is a different one.

If that is roughly your shape and you want to see what it would take against your own systems, get in touch or book time through the decision panel above. The first conversation is about what your data is actually like, which is usually the part that determines whether any of this is worth doing.

Last reviewed .