Metrics Platform

One metric dictionary for the whole company — define once, reference everywhere

Metrics-as-a-Service: define business metrics like revenue and collection rate once, then reference them from BI dashboards, OKR, commissions, approvals, and alerts — one consistent definition everywhere.

Metrics Platform: main interface screenshot

Product Screenshots

Metrics Platform: create a metric
Place here: Metrics Platform metric details and lineage
Place here: Metrics Platform downstream references

It solves these problems

Pain pointThree departments, three revenue numbers — meetings start by arguing about definitions.
Zhilai CRMDefine metrics once in the platform; the whole company references the same definition — conflicting numbers end here.
Pain pointThe same metric is calculated differently across reports, performance reviews, and commissions.
Zhilai CRMDefine once, reference everywhere: BI, OKR, commissions, approvals, and alerts reuse the same definition.
Pain pointEvery definition change means redoing downstream reports.
Zhilai CRMChange the definition in one place and every referencing view updates automatically, with the change fully audited.

Features

Frequently Asked Questions

What problem does the Metrics Platform actually solve?

It solves inconsistent definitions. Metrics like revenue, collection rate, and win rate are defined once in the platform; reports, BI, performance, and commissions all reference that single definition, so every view shows the same number.

Who can define metrics?

Metric definitions are permission-controlled, usually maintained by management or data administrators. Consumers such as BI and OKR can only reference them — no private rewrites of the definition.

How do downstream systems reference metrics?

BI, OKR, commissions, approvals, and alerts within the Zhilai ecosystem reference them natively; external systems can query metric results through the open API.

Start your 30-day free trial

Full features. No credit card required.