Adding new modules
This guide shows how to plan and enable new Centriu modules (for example, CX, Pulse, financial modules, etc.) without creating chaos, ensuring consistent data and real adoption by the team.
When does it make sense to add a new module?
Consider expanding your use of Centriu when:
- The current command center is already part of the management routine.
- There is a concrete pain point that the module solves (e.g., combining NPS with tickets, unifying financial and CX data).
- There is at least one area owner willing to be the module's sponsor.
Important tip
If the team is not yet making good use of what already exists, prioritize adoption first.
Planning the expansion
1. Define the module's objective
Write the objective in one clear sentence:
- “Add the CX module to track NPS + tickets in one place.”
- “Enable the financial module to track MRR, churn, and LTV by segment.”
Avoid generic descriptions. Always tie it to a business outcome.
2. Map the data sources
For the module to be added:
- Which systems will feed the module?
- Is there more than one source for the same data?
- Is there already a ready-made integration, or will spreadsheets be needed temporarily?
Build a mini table (even outside Centriu): Data | Source | Update frequency | Owner
3. Start with a pilot
Instead of enabling the module for the entire company:
- Choose one area (for example, CX only).
- Or start with a customer segment (e.g., enterprise).
This reduces risk, makes corrections easier, and increases the chances of adoption.
Enabling the module in Centriu (conceptual overview)
Adapt this to the actual Centriu modules, but follow this logic:
- Go to Settings > Modules / Products.
- Select the module to be enabled.
- In the setup wizard:
- connect the necessary integrations (CRM, help desk, ERP, etc.);
- choose the required fields;
- define the historical period to import (e.g., the last 6–12 months).
- Create initial dashboards for the module:
- overview;
- view by team, segment, or product.
Ensuring adoption of the new module
Adding a module that goes unused only increases complexity.
Adoption checklist:
- There is a clear sponsoring leader.
- Specific dashboards have been created for the team that will use the module.
- The module has been incorporated into the rituals (weekly meetings, analyses, action plans).
- The team has been trained on what to look at, where to click, and what decisions to make based on the data.
Recommend at least one hands-on session of 30–45 min with real cases.
How do you know if the module has “caught on”?
Positive signs
- Frequent access to the module's dashboards.
- Business questions being answered with it.
- Less use of parallel spreadsheets for that topic.
- The team requesting new filters, breakdowns, or views.
If none of this happens within 30–60 days
- Investigate the configuration (wrong vs. incomplete data).
- Clarity of the module's objective.
- Lack of usage rituals.