Catalogs and the library

Catalogs are your shared library of standard definitions. Pick a finance line, a KPI, or a role from the catalog and every engagement that uses it speaks the same language.

Without this, the same idea ends up named four different ways and totals can never be trusted.

Finance catalog

Standard P&L lines used across your engagements. Examples:

Monthly Recurring Revenue
Project Revenue
Labour Cost
Software Licensing
Subcontractor Cost
Travel and Expenses

Each line belongs to a category (Revenue, Cost of Goods Sold, Operating Expense). The category drives margin calculations: revenue minus cost of goods sold equals gross margin, minus operating expense equals net.

Performance catalog

Standard KPIs and SLAs. Examples:

Availability / Uptime (%)
First Call Resolution (%)
Average Response Time (hours)
Customer Satisfaction Score
Mean Time to Resolution (hours)

Each entry stores its direction (higher is better, lower is better, target is best) and an optional default target you can override per engagement.

Roles

The roles your delivery teams use. Examples:

Senior Consultant
Project Manager
Service Desk Analyst
Developer
Solutions Architect

Each role has a default hourly rate, used to value hours when no contract rate is set.

AI use cases

A catalog of AI initiatives across your engagements: what they are, where they run, and what economic impact they have.

Why this matters

With one shared library you can:

Aggregate and compare across engagements with confidence.
Benchmark a line or KPI across your portfolio.
Update a definition once and have it flow through every template that uses it.

Templates: how catalogs become per‑engagement structure.
Library: manage the catalogs.
Data domains: how Finance, Performance, Capacity, and AI Usage fit together.