Building the first dashboard · ZopDev University

Outcome

By the end of this lesson, you will be able to set up the first unit economics dashboard, layout the key elements (big number, trend, comparison, annotations), and adopt a review cadence.


Prerequisites	M5.3.L1 (denominator) · M5.3.L2 (numerator)
Time	9 minutes

1. Concept

A metric nobody looks at is not a metric.

The dashboard is what turns “we calculate cost per user” into “the team saw it on Monday and noticed it moved”. Five things make one worth putting on a wall:

1. CURRENT cost-per-unit  (big number)
2. TREND over time         (line chart, 12 months typical)
3. HISTORICAL comparison    (this quarter vs last)
4. YEAR-OVER-YEAR           (if data available)
5. ANNOTATIONS              (notes on key events affecting the metric)

The five elements together tell a story: current state, direction, context, comparison, explanation.

Dashboard layout

[BIG NUMBER]                              [TREND SPARKLINE]
$11.83 / paying user                       ↘ down from $13.20 (3 mo ago)

[LINE CHART: 12 months]
   $14 -│      ████████
   $13 -│              ██████
   $12 -│                    ████████
   $11 -│                            █████
   $10 -│
   $9  -│
       └────────────────────────────────────
       Jun  Jul  Aug  Sep  Oct  Nov  Dec  Jan  Feb  Mar  Apr  May

[COMPARISON]
  This quarter vs same quarter last year:  improving 8%
  Quarter-over-quarter:                     improving ~10%

[ANNOTATIONS]
  Mar 15: launched new feature (cost up briefly)
  Apr 30: optimized data pipeline (cost down 6%)
  May 12: scaled to support EU expansion (small increase expected)

Update cadence

DATA REFRESH:
  Daily: dashboard reflects yesterday's data (24-hour billing lag)

REVIEW CADENCE:
  Weekly: review at team meeting (quick scan; flag anomalies)
  Monthly: detailed analysis with finance + leadership
  Quarterly: deep variance analysis; re-baseline forecast

The data refreshes daily; the review cadence is weekly/monthly. Don’t conflate the two: daily updates with monthly review is the typical pattern.

Annotations matter most

The fifth element, annotations, is the most-skipped and most-valuable:

KEY EVENTS to annotate:
  Major feature launches            (cost spike during ramp-up)
  Cost optimization sprints          (cost drop)
  Scaling events                     (Black Friday, EU expansion)
  Acquired company integrations      (one-time noise)
  Pricing model changes              (rate-card or commitment renewals)
  Methodology changes                 (numerator scope revisions)

WITHOUT annotations:
  Six months later, no one remembers why cost spiked in March
  Future-self misreads the trend
  Conversations stuck on "what happened in week 12?"

WITH annotations:
  Trend is interpretable years later
  Lessons captured in context

The discipline: annotate when the event happens, not later from memory.

Team adoption pattern

WEEK 1:     Set up dashboard; first data populates
WEEK 2-3:   Team starts reviewing in weekly meetings
WEEK 4-8:   Discussion patterns emerge:
              "Cost-per-MAU is up: investigate"
              "Why did cost drop in week 6?"
              "Annotation explains the drop"

WEEK 12+:   Mature usage; routine review
              Team trusts the number; uses it for decisions
              Annotations accumulate; trends become richer

The adoption curve is similar to other operating-cadence rituals. The first month is awareness; months 2-3 are habit-formation; month 4+ is routine.

INTERNAL AUDIENCES:
  Engineering: cost trend awareness in team metrics
  Finance: unit economics for financial reporting
  Leadership: business efficiency narrative
  Product: feature ROI per user

EXTERNAL AUDIENCES (some companies report externally):
  Investors: unit economics as efficiency proof
  Board: quarterly business efficiency
  Analysts: comparable to peer benchmarks (if disclosed)

CAUTION:
  External metrics need careful definition + consistency
  Once published externally, the definition is hard to change
  without explanation

Common dashboard mistakes

MISTAKE                                       FIX
──────────────────────────────────────────────────────────────────
Too many metrics on one dashboard              Pick one primary;
(visual overload)                              demote others to drill

No annotations (trends unexplained)            Annotate events as
                                              they happen

Bad axis scale (small variations look           Use absolute axis
huge or vice versa)                            range matched to value

No context (just current number)               Add comparison +
                                              trend

Updated weekly but reviewed never              Adoption ritual missing;
                                              build the review cadence

Where to build it

Most teams build the first version in a spreadsheet or BI tool: cost from the billing export, the denominator from the product database, one row per month. In ZopNight, the Unit Economics page defines the metric and its data feed, and the Cost Reports trend chart then shows cost per unit as a second axis. That covers the trend line and the current number. The annotations and the quarter-over-quarter and year-over-year comparison go in your own slide or doc.

For team-specific unit economics, scope the metric to one team or one tag value on the Unit Economics page.

2. Demo

A team’s unit economics dashboard, 6 months in:

DASHBOARD: "Acme: Unit Economics Q2"

BIG NUMBER:
  Cost-per-paying-user: $11.83
  Q-o-Q change: -9% (improving)
  Y-o-Y change: -14% (improving)

LINE CHART (12 months):
  Trend visible: descending from $13.50 (Jun) to $11.83 (May)
  Two visible bumps:
    Feb (data pipeline migration)
    Apr (brief spike during EU launch)

COMPARISON BLOCK:
  vs Q1 2026:    -9% (improving)
  vs Q2 2025:    -14% (improving)
  vs forecast:   -3% (better than forecast: wins)

PER-TEAM BREAKDOWN (chart):
  Platform team:    $4.20 / paying user
  Product team:      $5.10
  Data team:         $1.80 (heavy ETL but small surface)
  ML team:           $0.73 (small inference cost; large user base)

ANNOTATIONS (5 visible):
  Feb 8:   Data pipeline migration (one-time +$0.30)
  Mar 15:  Smart Tags campaign (+5% coverage, no cost change)
  Apr 1:   Q1 optimization completed (-$0.80)
  Apr 18:  EU expansion launch (+$0.40, expected)
  May 5:   Auto-rem rule activated (-$0.20)

DISCUSSION at monthly review:
  "Trend is positive; Q1 optimization sustained."
  "Investigate why ml-team's cost-per-user is so low:
    can we apply the pattern elsewhere?"
  "Q2 target: cost-per-paying-user < $11."

OUTCOME: dashboard is used weekly; annotations are kept current;
team is making decisions from the data.

3. Hands-on (5 min)

Sketch your unit economics dashboard:

PRIMARY METRIC (from L1-L2):    $___ per __________

LAYOUT elements you want:
  □ Big number with delta
  □ 12-month trend line
  □ Quarter-over-quarter comparison
  □ Year-over-year comparison
  □ Per-team breakdown (if relevant)
  □ Annotations

REVIEW CADENCE:
  Daily / weekly / monthly: __________
  Owner of the review: __________
  Distribution (who sees it): __________

ANNOTATIONS to seed (events you remember from past 3 months):
  __________________________________________________________
  __________________________________________________________
  __________________________________________________________

FIRST REVIEW MEETING (calendar date):    __________

The first review is where the dashboard either becomes a routine or atrophies. Schedule it explicitly.

Do it through MCP. The same task you just did in the console, asked in one sentence.

BEFORE  A ZopNight account with one cloud connected. A business number you can pull daily: orders, active users, tenants.
ASK     "Track orders shipped as a unit metric, pull yesterday's value, and show me cost per order."
CHECK   the pull works before you wire a schedule to it. A denominator that stops arriving takes the whole metric down.

Tools behind it: create_unit_metric (write, tier 2, reversible), test_pull_unit_metric (write, tier 2, reversible), ingest_unit_metric_values (write, tier 2, reversible), get_unit_economics (read, Cost). Connection details are in the MCP integration docs.

4. Knowledge check

Q1

A dashboard with no annotations:

A. Cleaner: less noise
B. Fine, since the trend speaks for itself
C. Trends become mysterious
D. Better: viewers focus on numbers

Show answer

Correct: C. Six months later, no one remembers why cost spiked in March. Annotations capture the why in real time and preserve context for future readers. Annotations are essential for interpretable trends.

Q2

Year-over-year comparison on cost-per-unit:

A. Useless because too much changes year-over-year
B. Misleading, since the denominator changed
C. Required only for finance
D. Useful because it removes seasonality

Show answer

Correct: D. Same month last year vs same month this year accounts for natural seasonal variation (Black Friday, holiday traffic, ML training cycles). Y-o-Y is often a cleaner signal than Q-o-Q for some workloads.

Q3

Per-team comparison of cost-per-unit:

A. Same as the aggregate
B. Identical once normalised per user
C. Different per team
D. Per-team is meaningless

Show answer

Correct: C. Each team’s workload differs (compute-heavy vs IO-heavy vs ML-heavy), so cost-per-unit varies. Use the comparison for understanding patterns and identifying optimization opportunities, not for cross-team competition or fairness arguments.

5. Apply

Build the dashboard at Costs → Unit Economics. Configure the primary metric per M5.3.L1; the scope per M5.3.L2; annotations as events occur.

Schedule the first review meeting on your calendar. The dashboard exists; the review cadence is what makes it useful.

Glossary terms touched

Unit economics · Operate cadence

Outcome

1. Concept

Dashboard layout

Update cadence

Annotations matter most

Team adoption pattern

Sharing the dashboard

Common dashboard mistakes

Where to build it

2. Demo

3. Hands-on (5 min)

4. Knowledge check

Q1

Q2

Q3

5. Apply

Related lessons

Glossary terms touched

Start with the bill.