Skip to main content
Finance teams already work in unit economics, cost per acquisition, cost to serve, cost per unit produced. OPTIMAZE applies the same idea to technology spend, it takes the cost attributed to a node and divides it by an outcome you measure, so a cost line becomes a figure you can compare across products and over time. A unit economic is always cost from a node ÷ a metric. The cost comes from your attribution model, the metric comes from business metrics or values you upload.

​
Before you start

​
The Unit Economics page

Under Measure, select Unit Economics.
Prebuilt tab listing unit economics derived from AWS billing, with category, trend, latest value and status
Each unit economic shows its latest value, the change against the previous period, a trend, its Status (Live once data is flowing) and the date of its last data. Filter by Status, search by name, switch between card and table views, and use Export to download the list.

​
Create a unit economic

  1. Select New unit economic.
  2. Enter a Name, for example Cost per customer.
  3. Under Cost from, choose the Attribution Graph and the Attribution Node whose cost forms the numerator.
  4. Under Divide by, choose one:
    • Published metric: pick a metric from Metric.
    • Upload values: select Upload values and upload a file of denominator values.
  5. Open More details and set the Owner, Currency, Unit Display Name (for example per customer) and an optional Description. Currency and Unit Display Name are required.
  6. Check the Preview, it shows the historical value of the unit economic once both sides are set.
  7. Select Create.
New unit economic builder with Name, Cost from (Attribution Graph and Attribution Node), Divide by and Preview

​
Use unit economics elsewhere

  • Goals: set a target on a unit economic linked to a node. See Goals.
  • Overview: unit economics you own appear on the Overview page.

​
Troubleshooting

  • The Preview says “No value yet”. Both the cost and the denominator need to be set, and their date ranges need to overlap.
  • One unit economic shows an error. Each unit economic is calculated separately, so an error on one does not stop the others loading. Check its node and metric still exist.