RUMAZA Studio
Dashboards & data

Commercial Dashboard: manage the team with data, not anecdotes

Objectives, pipeline, useful activity, and forecast — for the sales director who needs to act before month-end.

The problem: commercial management without operational visibility

The sales director needs to know who needs help, which deals are at risk, and if the forecast is credible. Without a dashboard, management relies on individual conversations and gut feelings.

Endless pipeline meetings where everyone shares their version. Without common data, the meeting does not prioritize: it only updates.

Forecasts made in Excel alongside the CRM. When the numbers don’t match, management distrusts the sales team, and the sales team distrusts the process.

Poorly chosen activity KPIs encourage toxic behavior: empty calls, false opportunities, discounts to close before month-end.

Without visibility by funnel stage, you don’t see bottlenecks: many opportunities in proposal but few in negotiation, for example.

Sales turnover worsens if the new hire inherits a chaotic CRM without a dashboard to order priorities.

In practice, the problem does not appear suddenly: it starts with small frictions that the team normalizes until it costs money. Longer meetings, slower decisions, and a silent erosion of trust in internal numbers.

When there is no shared system, each area optimizes its own indicator, and the overall result deteriorates without anyone noticing until the close. That is what a good dashboard should prevent: early visibility and a common language.

The good news is that a two-year project is not necessary. With limited sources, clear KPIs, and a usable MVP in weeks, the change is already noticeable in the day-to-day of the management and operational team.

The ROI is not just in saving hours on Excel: it’s in detecting a margin drop, a customer at risk, or a channel that has stopped converting earlier. That is worth more than any BI license.

In practice, the problem does not appear suddenly: it starts with small frictions that the team normalizes until it costs money. Longer meetings, slower decisions, and a silent erosion of trust in internal numbers.

When there is no shared system, each area optimizes its own indicator, and the overall result deteriorates without anyone noticing until the close. That is what a good dashboard should prevent: early visibility and a common language.

The good news is that a two-year project is not necessary. With limited sources, clear KPIs, and a usable MVP in weeks, the change is already noticeable in the day-to-day of the management and operational team.

The ROI is not just in saving hours on Excel: it’s in detecting a margin drop, a customer at risk, or a channel that has stopped converting earlier. That is worth more than any BI license.

In practice, the problem does not appear suddenly: it starts with small frictions that the team normalizes until it costs money. Longer meetings, slower decisions, and a silent erosion of trust in internal numbers.

When there is no shared system, each area optimizes its own indicator, and the overall result deteriorates without anyone noticing until the close. That is what a good dashboard should prevent: early visibility and a common language.

What is a commercial dashboard

It is the tool for the sales manager: it combines team management (objectives, progress, relevant activity) with funnel health (stages, stagnation, forecast).

It is not the same as the management sales dashboard: here there is more operational detail, lists of at-risk deals, coaching tasks, and weekly follow-ups.

Includes scorecards by salesperson, pipeline heatmaps, opportunity aging, and comparisons vs. the same period last year.

It must integrate with the CRM as a source of activity and with billing to validate results. CRM alone is not enough.

A well-made commercial dashboard reduces meeting time and increases time spent selling in the field or on valuable calls.

Alerts are central: large deal without movement, red target with two weeks remaining, key customer without activity.

The key is that each metric has an owner, a written definition, and an identified source. Without that, the dashboard is just an opinion with graphs. With that, it becomes a management tool.

Cadence also matters: an operational indicator that moves every hour is not the same as a financial indicator that consolidates at close. Mixing them without context generates false alarms.

A mature system documents exceptions: returns, credit notes, canceled orders, internal customers. If they are not modeled, the dashboard lies with a good appearance.

Visualization is the last mile. Before that, it is necessary to agree on what each number means and who is responsible when it deviates. Without light governance, the best chart in the world won’t save the project.

The key is that each metric has an owner, a written definition, and an identified source. Without that, the dashboard is just an opinion with graphs. With that, it becomes a management tool.

Cadence also matters: an operational indicator that moves every hour is not the same as a financial indicator that consolidates at close. Mixing them without context generates false alarms.

A mature system documents exceptions: returns, credit notes, canceled orders, internal customers. If they are not modeled, the dashboard lies with a good appearance.

Visualization is the last mile. Before that, it is necessary to agree on what each number means and who is responsible when it deviates. Without light governance, the best chart in the world won’t save the project.

The key is that each metric has an owner, a written definition, and an identified source. Without that, the dashboard is just an opinion with graphs. With that, it becomes a management tool.

Cadence also matters: an operational indicator that moves every hour is not the same as a financial indicator that consolidates at close. Mixing them without context generates false alarms.

A mature system documents exceptions: returns, credit notes, canceled orders, internal customers. If they are not modeled, the dashboard lies with a good appearance.

Visualization is the last mile. Before that, it is necessary to agree on what each number means and who is responsible when it deviates. Without light governance, the best chart in the world won’t save the project.

When it makes sense

Criterios
  • Current pain costs weekly hours or clear decisions
  • You have at least one reliable digital source (ERP, CRM, ecommerce)
  • Management or responsible parties request recurring visibility
  • The current process depends on a single person
  • There are measurable objectives that require frequent tracking
  • You have detected repeated errors due to inconsistent data
  • You want to scale without multiplying manual reporting
  • You need to align multiple areas with the same definitions

What can be built

01

Main panel

View with agreed KPIs, filters by period, and comparisons vs. objective. Designed for the weekly meeting, not to impress in a demo.

02

Alerts layer

Notifications via email or Slack when an indicator crosses a defined threshold with the business.

03

Drill-down

From summary to transactional detail without exporting to Excel.

04

Automated reporting

Scheduled reports with the same database as the panel.

05

Definitions catalog

Living documentation of KPIs, formulas, and owners.

06

Multi-source integration

Crossing systems without intermediate sheets or copy-paste.

How RUMAZA would build it

01
Diagnosis
Questions, sources, data quality, and users in 48–72 hours. Without this, there is no serious proposal.
02
KPIs and definitions
Written formulas validated with those who close the numbers.
03
Data model
Analytical tables with historical data and explicit business rules.
04
MVP of the panel
First usable deliverable with one or two sources.
05
Parallel validation
Compare with the current process before cutting Excel.
06
Automation
Scheduled refreshes, reports, and alerts with logs.
07
Training and handover
Session with the team, documentation, and maintenance plan.

Possible technologies

  • PostgreSQL
  • Python / dbt
  • Metabase / Power BI / Next.js
  • REST APIs
  • Celery / cron
  • Airbyte or ETL scripts
  • Slack / email

Application scenarios

Escenario 1

Sales team without clear prioritization

Everyone is chasing the same or the easiest. Panel with opportunities by value, age, and agreed probability.

Escenario 2

Commercial activity invisible to management

Calls, visits, and proposals not recorded. Dashboard that combines activity and results, not just final billing.

Escenario 3

Poorly distributed territories or portfolios

Overlaps and forgotten customers. Commercial view by responsible person, area, or segment with inactivity alerts.

Common mistakes

Evitar
  • Starting with the tool without defining business questions
  • Not validating numbers with those who close finances
  • Big bang without a parallel period with the current process
  • Ignoring permissions and exposure of sensitive data
  • Not assigning an owner for post-launch maintenance
  • Promising real-time without infrastructure or SLAs for sources
  • Copying metrics from another sector without adapting to the business model

Frequently asked questions

How much does it cost?

Between €3,000 and €12,000 depending on sources and integrations. Budget by milestones after a 48-hour diagnosis.

How long does it take?

MVP in 3–5 weeks with a limited scope. Complete multi-source system: 8–12 weeks with incremental deliveries.

Do I need to change my ERP or CRM?

Almost never at the beginning. We evaluate APIs, scheduled exports, or existing integration.

Can we keep Excel in parallel?

Yes, during validation. The goal is for the dashboard to be the source of truth when the numbers match.

Who maintains the system afterwards?

You can internalize it with documentation or hire maintenance. Without an owner, the dashboard dies.

Power BI or custom web panel?

It depends on the Microsoft ecosystem, permissions, and UX. We define it in the diagnosis, not by trend.

What if the data is dirty?

We prioritize metrics with sufficiently good data and iteratively clean the rest without blocking the MVP.

Related guides

Updated: 2026-06-29 · Author: Rubén Maestre

Do you have this problem in your company?

Tell me and I will tell you what system I would build.