Build · Meridian · Operational

Meridian

One brand, across a hundred forecourts.

Meridian is a marketing-operations platform for organisations that sell through networks — dealers, retailers, franchises, multi-brand groups. Every location submits plans its own way; the organisation receives one standard, one calendar, one live picture — flowing both ways, to every level of the network. Nobody changes how they work. That is the point.

Request a demonstration → See the difference ↓

The whole platform, in three figures.

0formats

the number of new templates or tools your retailers must learn. They keep their own files — Meridian does the translation.

Adoption friction, engineered away.

2ways

HQ plans, offers and events stream down. Submissions and requests stream up. Live, in both directions.

A circulation, not a corridor.

4levels

Retailer · Area · Region · Global — every desk sees, changes, approves and requests exactly what its role allows.

One picture, alive at every level.

The difference · Two ways to run a network

Same network. Different physics.

Below, the same five retailers submit the same five plans, twice — once through the corridor every network office knows by heart, and once through Meridian. One produces a photograph. The other stays alive.

Choose how the plans arrive ↑
The schematic runs wide — turn your phone
Same plans. Same network. Different physics.
The problem

A hundred versions of the truth.

Everyone saying the same things — in very different ways.

The picture was already out of date the day it was assembled.

Where it was designed
Meridian was designed from the inside of the problem: years running marketing across international networks where every player belonged to a different group — each with its own procedures, templates and terminology, standards built for their portfolio and holding priority over the brand’s. Every submission arrived in a different shape.
The manual answer
Standardising by hand became a job in itself — necessary, endless, and out of date the moment it was finished. A dedicated tool was never the answer: one more standard on top of the existing ones would simply have doubled the workload on both sides. A shared folder, a scrap of automation — the friction survives them all, because there is still no universal format, and still no live picture reaching every level of the organisation.
The cost
Latency measured in weeks. Errors found late, and corrected later. Data too scattered to cross-read — and the few insights that survived, trusted too little to act on.
The platform · Five capabilities

Any format in. One standard out.

01Ingest Any plan, in any form, read into one standard. 02Orchestrate Calendar, activity pages, approvals — generated. 03Circulate The channel runs both ways — HQ to edge, edge to HQ. 04Observe The live picture, scoped to every level. 05Cross-read Intelligence the manual way never reaches.
01 · Ingest

Any format in.

The platform learns their language.

Adoption friction is why network tools fail.

What it does
Retailers drop their plan in whatever form it exists. Meridian detects and interprets the content, and fills your standard plan format with it.
  • Any submission format — deck, sheet, document, mail
  • Content detected, interpreted and mapped to your standard
  • Gaps and conflicts flagged at source, back to the desk that owns them
  • No retraining, no new templates for the network
Why it matters
The translation burden moves from people to the platform — retailers change nothing, so the network actually uses it. Your standard becomes the one that holds, without asking anyone to learn it.
How it runs
Each submission is parsed against your plan standard the moment it lands. What is complete flows on; what is missing goes back to the retailer at entry — before it becomes an error downstream.
02 · Orchestrate

The calendar builds itself.

Machinery, not maintenance.

Coordination is where the hours went.

What it does
From the standardised plans, Meridian assembles the operating machinery of the network year.
  • The network activity calendar, generated live
  • A page for every activity, created automatically
  • Approval chains routed to the right desks
  • Reminders that follow the calendar — not the other way round
  • One global plan, dissectable to a single retailer’s open day — invitee lists included
Why it matters
When the machinery assembles itself, HQ time goes back to judgement — and the network’s events stop depending on whether somebody remembered. Generated, not maintained.
How it runs
Every change propagates to every view at once. Calendar, activity pages, approvals and reminders stay one object — never four copies.
03 · Circulate

The channel runs both ways.

A circulation, not a corridor.

The centre sees the edge. The edge sees the centre.

What it does
The stream flows down as well as up. What HQ publishes is live to the network the moment it exists.
  • HQ plans, offers and available events — visible to every retailer
  • Requests and submissions — visible to the desks that answer them
  • Every change, in both directions, without an email in between
Why it matters
A shared folder is a place; a channel is a flow. When the edge can see the centre — the offers, the events, the plan — the network stops asking and starts acting. The corridor becomes a circulation.
How it runs
One system of record, streamed live to every desk that has the right to see it — no export step, no distribution list, no version to chase.
04 · Observe

The picture is live.

No reporting cycle. No compilation step.

A report is a photograph of a moment that has already passed.

What it does
Dashboards populate as submissions land and plans change — current at any moment.
  • Network, market and retailer views, live
  • Scoped by credential — retailer, area, region, global: each desk sees, changes, approves and requests exactly what its role allows
  • One source: the same data the calendar and approvals run on
  • Nothing compiled, nothing reconciled, nothing waited for
Why it matters
The latency that made every decision a decision about the past is gone. What the centre sees is what the network is doing — now. The live picture, not the last photograph.
How it runs
There is no reporting cycle to fall behind, because there is no reporting cycle. The dashboard is a reading of the system — not a document about it.
05 · Cross-read

Intelligence the manual way never reaches.

The questions the data could finally carry.

The insights were always there. The format was in the way.

What it does
With every plan in one standard, the network becomes comparable — for the first time.
  • Spend against activity against outcome, across the whole network
  • Retailers, markets and seasons, read side by side
  • Patterns surfaced, not hunted
Why it matters
The questions that could never be asked before become routine — not because nobody thought of them, but because the data could not carry them.
How it runs
Cross-referenced views across the network — a layer of intelligence that exists only because the standard holds all the way down.
The engine

ARGOS-P — the hundred-eyed watchman

The myth at the core of the machine.

A network drifts, locally, constantly.

Why the myth
Argos Panoptes, the watchman of myth, never closed every eye at once. A network has the same problem a brand has — it drifts, locally, constantly. The engine inside Meridian is the eye that sees the whole of it.
What it aligns
Every plan, every asset, every event — read, extracted and reconciled into one consistent brand, so the standard set at the centre is the standard met at the edge.
Who it’s for

Brands that live or die by a distributed network

Anywhere the brand at the centre and the brand at the edge are quietly drifting apart.

Sectors
Automotive dealer groups, luxury and premium retail, multi-site and franchise operations, multi-brand store networks.
The problem it solves
Local execution that fragments the brand — inconsistent assets, unsupported events, plans that never reconcile. Meridian brings the whole network into one view, and one standard.
Engagement

Operational, by application.

Meridian is operational and deployed by application — configured to your plan standard, your approval chain, your calendar. Adoption is the platform’s job, not your retailers’.

  • Demonstration. Shown on a model network as standard. On request, run against your own material — allow set-up time, as some parameters are inherently bespoke.
  • Deployment. Configured to your standard, your approvals, your calendar.
  • Counsel. The same senior practice that runs Measure and Advise stays close while it beds in.
Questions

Asked before engaging.

Q.01 What is Meridian?
Meridian is Pitot Group’s marketing-operations platform for organisations that sell through networks — dealers, retailers, franchises and multi-brand groups. Retailers submit plans in their own formats; Meridian reads and interprets the content, fills the organisation’s standard plan, flags what is missing, and generates the activity calendar, activity pages, approval chains, reminders and live dashboards. It is powered by the ARGOS-P engine.
Q.02 Do our retailers have to change how they work?
No. Eliminating adoption friction is Meridian’s founding design decision. Retailers keep their own formats, templates and tools; the platform does the translation. That is why the network actually uses it.
Q.03 What does Meridian generate from the plans?
From each submission, Meridian fills the standard plan format and flags gaps back to the retailer. From the standardised plans it generates the network activity calendar, a page for every activity, approval chains and reminders — and populates the dashboards live, with cross-referenced intelligence across retailers, markets and seasons.
Q.04 Is Meridian a self-serve subscription?
No. Meridian is operational and deployed by application, configured to each organisation’s plan standard, approval chain and calendar — a deployed system with senior counsel around it, not a self-serve subscription. A demonstration runs on a model network; on request it can be configured against your own material, with set-up time for the parameters that are inherently bespoke.
Q.05 Who sees what inside Meridian?
Access is scoped by credential, at every level of the network — retailer, area, region, global. Each desk views, modifies, approves and requests exactly what its role allows, and each sees its slice of the picture live. The stream runs both ways: retailers see HQ plans, offers and available events the moment they exist.
Q.06 Which organisations is Meridian for?
Organisations that sell through distributed networks: automotive dealer groups, luxury and premium retail, multi-site and franchise operations, and multi-brand store networks — anywhere the brand at the centre and the brand at the edge are quietly drifting apart.
Operational

The eye that sees the whole of it.

Meridian is operational and deployed by application. Request a demonstration — and if you would rather see it against your own network’s material, we will configure it to do exactly that.

Request a demonstration → Back to Build →
Up