Implementation in 7 days

Day 0 – Preparation (before flipping the switch)

Before officially starting “Day 1”, align on:

• Project owner: who will own the rollout?
• Main goal for the first 30 days: E.g.: “Have a working command center to track MRR, CX tickets and key SLAs”.
• Teams involved: Growth / CX / Operations / Product / Finance (according to scope).

Day 1 – Set up the account basics

Access Centriu with the administrator user.

Check and adjust:

• Company name and logo (to standardize the identity).
• Time zone and default currency.
• Language, if applicable.

Create the first key users:

• 1 project owner (admin);
• 1 CX user;
• 1 operations / growth user.

Define the main channels/systems to be connected during the 7-day cycle:

E.g.: support tool, sales CRM, billing spreadsheets, paid media platforms.

Day 2 – Connect the first data sources

Focus on what's essential to see the business:

Connect the revenue and pipeline sources:

• Sales CRM or contracts/renewals spreadsheet;
• MRR/ARR or billing data.

Connect the main customer experience source:

• ticketing system, chat, help desk or NPS.

Validate that the data is arriving correctly:

• required fields filled in;
• correct dates;
• funnel statuses and stages mapped.

Day 3 – Build the main leadership dashboard

Goal: have a simple dashboard that leadership can read in 5 minutes.

Recommended blocks:

1. Revenue / growth
   • MRR/ARR or billing per month;
   • New customers vs churn.
2. Operations / volume
   • number of tickets, calls, requests or orders;
   • open queues;
   • main reasons for contact.
3. CX / quality
   • NPS / CSAT / average response time;
   • first-contact resolution rate, if available.

Day 4 – Define short-term indicators and goals

With the dashboard built, the next step is to set realistic goals for 30 days:

• Choose 3 to 5 indicators that will be the “star” of the rollout: E.g.: MRR, resolved tickets, NPS, ticket backlog.
• Set short-term goals: E.g.: “Increase resolution rate by 5 pp in 30 days”; “Reduce backlog by 20%”.
• Record the goals inside Centriu (not in parallel spreadsheets).

Day 5 – Create reading and decision rituals

The platform only makes sense if it becomes a management routine, not just a pretty dashboard.

• Schedule a weekly data meeting:
  • – Duration: 30–45 min;
  • – Participants: leadership + area owners;
  • – Fixed agenda (reading the numbers, analyzing deviations, decisions).
• Define owners per indicator: who is accountable for NPS, for tickets, for revenue, etc.
• Set up basic alerts (if Centriu has this module): E.g.: alerts for a sharp NPS drop, backlog increase or revenue decline.

Day 6 – Engage the team and test the full flow

• Present the platform to the team in a quick demo meeting:
  • – show the main dashboard;
  • – explain what each person gains by using Centriu;
  • – reinforce that the goal is not to “monitor”, but to provide visibility.
• Choose a real case and follow the flow inside Centriu: a ticket, a campaign, a new account, an incident.
• Ask the team for direct feedback: what's clear, what's confusing, what's missing.

Day 7 – First official review and next steps

• Hold the first official meeting using the dashboard:
  • – compare the current week vs the previous one (or vs a baseline month);
  • – list 3 learnings;
  • – define 3 actions for the next week.
• Review whether the dashboard needs:
  • – additional filters;
  • – new breakdowns (by segment, channel, owner);
  • – metrics to remove (what is not being used).
• Record a rollout evolution plan for the next 3–4 weeks: new integrations, new dashboards, automations.