Model your business beyond rows and columns.

Define regions, products, departments and entities once, then use the same business structure to plan, compare and drill into every financial number.

A number means more with layers: region, product, team and every way the business is run.

An Oculon headcount planning model: beginning headcount, hires and terminations by department across months, with formulas in business terms.

Headcount Planning Q3 in Oculon. Dimensions like department keep the plan structured as the business grows.

HOW IT WORKS

Organising the business
by dimension.

When finance needs revenue by region or payroll by department, the model should already know those relationships.

01 / Define

Members with attributes
Category, owner, launch date

A product can have a category, owner and launch date. Those properties make the revenue breakdown useful instead of leaving you with a list of labels.

  • Stable members with typed properties
  • Links between dimensions
  • Variables that live on the dimension
02 / Layers

Roll up naturally
City to region to global

Move from Berlin to Germany to EMEA, or from a product SKU to a category total, without maintaining separate aggregation formulas.

  • Any number of levels
  • Automatic roll-ups and drill-downs
  • Group and filter by any property
03 / Reuse

Define once
Reuse in every model

When a new region is added, revenue planning, headcount and reporting can reference the same member instead of copying structures across files.

04 / Share safely

Share a slice
Never the whole dimension

Let a department head work with their own costs while finance retains the wider dimension and the detail behind other teams.

  • A view exposes only its rows and columns
  • Access to a view never opens the rest
  • Models use views as their source
IN PRACTICE

Organise the business once. Use it everywhere.

SStrategic Finance/Revenue by RegionEdited just nowShare
SearchCompareView
VariableTrendFormulaQ2Q3Q4
Revenue by Region
$Revenueby ◆ 4$ ARR÷# 4$5.6M$5.8M$6.1M
$North AmericaRegion$3.1M$3.2M$3.3M
$EuropeRegion$1.6M$1.7M$1.8M
$· United KingdomCountry$0.7M$0.7M$0.8M
$· GermanyCountry$0.5M$0.6M$0.6M
$APACRegion$0.6M$0.6M$0.7M
$NordicsRegion · new$0.3M$0.3M$0.3M
For Regional finance teams · Report by region · Roll every model up by region and drill into any country.Illustrative example · sample data

FAQs

Can I create my own dimensions and hierarchies?

Yes. Create dimensions such as product, region, department, channel or entity and define how they relate and roll up.

How is a dimension different from a database?

A dimension is a list of members with stable IDs and properties, such as Customer or Region. A database holds data pulled from a source, such as invoices, mapped onto those dimensions.

Can I limit what people see?

Yes. Share a view of a dimension with selected columns and rows. Access to a view never grants access to the rest of the dimension.

Page preview · This destination is not built in the local prototype yet.