Skip to main content

Command Centre & dashboards

Why this matters for your business​

Dashboards fail when they try to be one thing for everyone. The founder needs "is the business healthy?" in 30 seconds. The marketing team needs "are campaigns performing?" with drill-down. Ops needs "are systems running cleanly?". Security needs "any audit-grade events to investigate?". Cramming all of that into one dashboard creates noise; building separate ones without a shared spine creates contradictions.

The four dashboards on this platform are designed for distinct audiences with shared underlying data. The founder's Command Centre answers strategic questions in 30 seconds. My Dashboard is per-user, focused on what each person owns. Admin Dashboard is for ops + support team daily work. Engine Audit shows technical system health for the person responsible.

The shift: every role in the org has the right surface; nobody is reading wrong-fit dashboards.

What this typically unlocks​

OutcomeResult
Time on dashboard reading per role−50%
Right-data-to-right-personmeasurable
Cross-role dashboard contradictions0 (shared data spine)
New-employee onboarding to datahours vs. days

What you actually get​

DashboardAudienceTime-budgetFocus
Command CentreFounder / CEO30 secondsHealth: is the business growing?
My DashboardPer-user (marketing, ops, etc.)5 minutesWhat I own + what I should do
Admin DashboardOps / support team15 minutesDaily ops + support queue
Engine AuditTechnical lead / DevOps10 minutesSystem health + worker status

Command Centre — 30-second health check​

┌─────────────────────────────────────────────────┐
│ Command Centre                                   │
├─────────────────────────────────────────────────┤
│ Revenue (today / 7d / 30d)        ↑+12% YoY     │
│ Active customers (30d)            14,200 (+8%)  │
│ Conversion (7d)                   2.4% (stable) │
│ Top campaign                      "Spring sale" │
│ Top journey                       Cart recovery │
│ Top alert                         (none)        │
│                                                  │
│ This week's top action:                          │
│ → Apple Mail KPI shift detected; review         │
│   cart-recovery email metrics                    │
└─────────────────────────────────────────────────┘

Core metrics + DIE's top action of the week. No more.

My Dashboard — per-user​

Each user sees:

  • What I own (campaigns I created, journeys I manage, segments I built)
  • Performance of what I own (each in 1 line)
  • Notifications for me (approval requests, comments, flagged items)
  • DIE recommendations relevant to me

Removes the "reading dashboards I don't own" problem.

Admin Dashboard — ops surface​

| Section | Items |
|---|---|
| Today's queue | Approvals, refunds, support escalations |
| Customer profiles | New + flagged + at-risk signals |
| Webhook health | Failures, retry counts |
| Inventory alerts | Low-stock, restock-imminent |
| Compliance items | GDPR requests, opt-in audits |

The day-to-day operational surface for the team that runs the store.

Engine Audit — system health​

For whoever is responsible for the platform's technical operation:

  • Worker status (running, queued, failed)
  • Queue depths (per-engine)
  • Webhook delivery rates
  • API rate-limit headroom (Shopify, ad platforms)
  • Recent errors + resolutions
  • Deploy history
  • Security audit log

If the platform is "running well," this dashboard is boring — exactly what you want.

Real merchant scenarios​

Scenario A — Founder reviews Command Centre daily​

Setup. Solo founder. Pre-platform: opened Shopify, Klaviyo, Meta, sometimes Google Analytics, every morning. ~30 minutes.

Post-platform: Opens Command Centre once daily. 30 seconds. Acts on DIE's top recommendation if applicable.

Time saved: 25 min/day = 12.5 hours/month.

Scenario B — Marketing team uses My Dashboards​

Setup. Marketing team of 4. Each owns specific journeys, campaigns, segments.

Setup: Each gets My Dashboard scoped to their work. Manager sees roll-up.

Outcome: No more "who's looking at which dashboard?". Each person owns 5-10 metrics; sees them and acts.

Scenario C — Ops team works Admin Dashboard​

Setup. Ops team starts every day with Admin Dashboard. Sees:

  • 3 approvals waiting
  • 1 GDPR request to process
  • 2 high-AOV refunds to investigate
  • All webhook health green

~30 minutes to clear the queue. Days where queue is heavy visible immediately.

Scenario D — Engineering catches issue early via Engine Audit​

Setup. Engineer noticed in Engine Audit: "Email worker queue depth growing — currently 12K (typical 100)."

Investigation: Resend API hiccupping; queue building.

Action: Triggered failover to SMTP. Queue cleared in 30 min. Without monitoring, customers would have noticed delayed emails the next morning.

Best practices​

✅ Train each role on their dashboard, not all four. Founder doesn't need Engine Audit weekly.

✅ Set defaults to your role's home page. Saves a click every time.

✅ Use My Dashboard for individual accountability. Owner visible; performance visible.

✅ Pair Command Centre with the weekly digest. Daily for quick check; weekly for deep think.

❌ Don't try to make Command Centre a comprehensive dashboard. Keep it 30-second. Force complexity into the specialized dashboards.

❌ Don't disable Engine Audit because "it's boring." Boring is the goal; the day it stops being boring is the day you need it.

Plan tiers​

CapabilityFreeStarterProAgencyEnterprise
Command Centre✓✓✓✓✓
My Dashboard (per-user)—✓✓✓✓
Admin Dashboard✓✓✓✓✓
Engine Audit—✓✓✓✓
Custom dashboard widgets——✓✓✓
Scheduled dashboard exports——✓✓✓
Multi-shop roll-up———✓✓
Embedded dashboard SDK————✓

See also​