Boardroom Answers · Strategic Command · Business Value & ROI
We are 4 business units heading to 7. Does this scale with organisational complexity, or do I end up buying five subscriptions and a headache?
The question a President / Chief Operating Officer (COO) asks.
The short answer
One subscription that ladders: $149 → $649 → $1,799 → Enterprise, with business-unit chargeback and directory-synced seats built in. You scale a plan, not a portfolio of licences.
The full executive answer
The commercial ladder is built for exactly that growth path: Basic at $149 a month covers 17 modules and 5 seats for a single leadership team; Pro at $649 covers 44 modules and 10 seats; Max at $1,799 covers 66 modules and 50 seats — which is where a multi-business-unit executive population usually lands — and Enterprise, from $9,000 a month, opens all 68 modules with unlimited seats plus the white-label, SDK and integration surface. You move up one subscription, not five parallel ones, and annual billing takes roughly 17% off list.
On the operational mechanics of multi-unit scale: the cost-governance layer supports business-unit tagging and chargeback, so AI usage can be attributed and internally billed per division — a real feature in the FinOps module, not a spreadsheet we hand you. Custom fields let each unit adapt taxonomies without forking the platform, SCIM keeps seat sprawl synchronised with your directory as units are added, and the report builder assembles unit-level and group-level views from the same underlying data. Every organisation’s data is isolated at the database layer with row-level security, which matters when units have information barriers between them.
Honest boundary: what today’s architecture gives you is one organisation with unit-level attribution and access control inside it. Fully federated multi-entity structures — separate subsidiaries wanting hard tenant separation under one group contract with consolidated group reporting across them — is an Enterprise-tier conversation and partly roadmap, and I would want your group structure on a whiteboard before promising the topology.
Grounded in: TCO (total cost of ownership) laddering · SOC 2 TSC logical-access principles (RLS isolation)
The natural next questions
Related governed answers
- Concretely, what changes in my operating cadence in the first 90 days, and how much of my team’s time does deployment eat?
- Every analytics tool I have bought became shelfware in six months. Executives do not change habits. Why is this different?
- In one minute, without jargon: what problem does this solve for me and my board that a good chief of staff plus ChatGPT does not?
Want this answered live, on your data?