How to Build a Unit Economics Dashboard

A unit economics dashboard puts the numbers that decide whether growth is profitable in front of the people who control them, on one page, with definitions everyone agrees on. Most companies already have the underlying data, scattered across the order system, the ad platforms, the warehouse and the ledger. A good dashboard joins them, shows contribution per order and per customer, tracks acquisition cost and payback, and flags changes early. A poor one shows revenue and traffic with attractive charts and no answer to the question of whether each sale makes money. This guide walks through a build in seven steps: choosing the questions, defining the metrics, designing the data model, laying out the page, setting alerts, building in a tool and keeping the numbers trusted. It belongs to unit economics and budgeting and forecasting, builds on the unit economics template, and works alongside unit economics for fundraising and sensitivity analysis on unit economics.

Step 1: start with the decisions

List the decisions the dashboard should inform. Typical ones are how much to spend on each marketing channel, whether to change a price, whether a product line should be kept, which customers or accounts need attention and whether the business is on track for its plan. Each decision implies a question, and each question implies a metric. If a chart does not support a decision, leave it out. Interview the people who will use it: the head of marketing, the head of operations, finance and the founder or CEO. Ask what they look at today, what they wish they could see and what they argue about.

Step 2: define the metrics once

Disputes about numbers usually come from different definitions. Write a short definition for each metric, with the formula, the data source and the owner. A starting set:

Decide how to treat edge cases: free shipping, bundles, subscriptions, B2B orders and marketplace sales. Publish the definitions on the dashboard itself, behind an information icon or on a separate tab.

Step 3: design the data model

A dashboard is only as reliable as the data behind it. Build a simple model with a few tables and clear keys.

Join order data to cost data at the order level where possible, and allocate period costs (such as returns processing) by a stated rule. Use the same customer identifier across tables. Reconcile the sum of revenue and cost to the general ledger every month. A reconciliation line on the dashboard, showing the difference between the model and the ledger, builds trust.

Step 4: lay out one page

Design for a person who has two minutes. Place the most important numbers at the top and the explanations below.

1. Header row of five tiles: contribution per order, contribution margin, CAC, payback and return rate, each with change versus last period and a target.
2. Trend charts: contribution per order and CAC over twelve months on the same time scale.
3. Channel table: channel, spend, new customers, CAC, first-order contribution, payback and a color flag.
4. Cohort view: cumulative contribution per customer by month since first order, with the CAC line drawn across to show the payback month.
5. Product table: the ten products with the largest revenue and their contribution margin.
6. Notes: definitions, last refresh time and the reconciliation to the ledger.

Use plain labels, consistent colors and the same order of channels everywhere. Avoid more than two or three chart types. Put the dollar value of a change next to its percentage so users see what it is worth.

Step 5: add targets and alerts

A number without a target invites argument. For each tile set a target range with green, amber and red thresholds that were agreed in advance. Examples: payback within two orders is green, between two and three is amber, and above three is red; return rate within a stated band. Add alerts for sharp changes, such as CAC rising by more than 15 percent in a week or contribution margin falling by more than two points. Send alerts to the owner with a short link to the supporting table. Review thresholds each quarter, as unit economics change with scale.

Step 6: build it in a tool

The method is the same in any tool. A spreadsheet works for a small business with a few thousand orders, with formulas on a data tab and a summary tab. For larger data, a business intelligence tool such as Power BI or Tableau connects to databases and refreshes on a schedule. In either case:

• Keep the calculation logic in one place, either in a data model with measures or in a set of named formulas, and not copied across many charts.
• Build the contribution waterfall as a table first and check it against a manual calculation of 20 orders before visualizing it.
• Use filters sparingly: date, channel, product category and customer segment are usually enough.
• Set the refresh schedule to match how the data changes: daily for orders and marketing, monthly for cost allocations and ledger reconciliations.

A check you should always run

Take one week and one channel. Calculate the contribution per order by hand from the raw rows and compare it with the dashboard. For example, if the dashboard shows 480 orders, $28,800 of net revenue and $11,600 of contribution for the week, then net revenue per order should be 28,800 / 480 = $60.00 and contribution per order 11,600 / 480 = $24.17. Any difference between the dashboard and the hand calculation points to a join or definition error that must be fixed before the dashboard is shared.

Step 7: keep it trusted

1. Assign an owner who answers questions and approves changes to definitions.
2. Keep a change log of definitions, thresholds and data fixes.
3. Reconcile monthly to the ledger and note differences.
4. Hold a monthly review where the owners of each metric explain movements and agree on actions. A dashboard that nobody discusses will be ignored.
5. Remove what is not used. Check usage and retire unused charts.
6. Train new users in what each metric means and where it comes from.

Common mistakes

• Starting with the data and not the decisions.
• Several definitions of the same metric.
• Showing revenue and not contribution.
• Blended CAC only, with no channel view.
• No targets, so no way to tell good from bad.
• No reconciliation to the ledger.
• Too many charts.

If you would like help building a dashboard on your own data in Excel, Power BI or Tableau, contact us.

FAQs

What should a unit economics dashboard show?

Contribution per order and per customer, customer acquisition cost, payback, return rate and retention by cohort, with targets and trends, for each channel and product.

How often should it be updated?

Orders and marketing spend daily or weekly, and cost allocations and ledger reconciliations monthly.

Which tool should I use?

A spreadsheet is enough for small data sets. Power BI or Tableau suit larger data and scheduled refresh. The definitions and the data model matter more than the tool.

How do I make sure the numbers are right?

Reconcile to the general ledger each month and check a sample of orders by hand against the dashboard.

Who should own the dashboard?

A named person in finance or analytics, with each metric owned by the team that influences it.