RUMAZA Studio
Dashboards & data

Sales Dashboard: numbers the sales team uses every Monday

Pipeline, conversion, invoicing, and team activity — without exporting the CRM at 11 PM on Sunday.

The problem: sales flying blind with outdated CRM data

The sales team lives in the CRM, but management wants consolidated numbers and finance wants actual invoicing. Without a unified sales dashboard, every sales meeting starts with exporting lists and arguing over definitions of 'won opportunity' or 'closed order'.

Many sales dashboards only show activity: calls, visits, emails. That doesn't indicate if you're on target or which deals are at risk. Activity without conversion is noise that tires the team.

The pipeline in the CRM is often inflated: dead opportunities that no one closed, unrealistic closing dates, and probabilities set 'by eye'. A dashboard that doesn't clean this up creates false expectations for management.

Without early alerts, you find out about gaps in the funnel when it's already halfway through the quarter. By then, recovering targets requires heroic sales efforts or discounts that kill margins.

Each salesperson has their way of recording data. Without rules and a common dashboard, comparing performance is unfair and creates internal friction.

The cost isn't just reporting time: it's losing deals due to lack of follow-up, misassigning leads, or not noticing that a channel stopped converting three weeks ago.

In practice, the problem doesn't 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's no shared system, each area optimizes its own indicator, and the overall result worsens without anyone noticing until the close. That's what a good dashboard should prevent: early visibility and a common language.

The good news is that a two-year project isn't 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 isn't just in saving hours of Excel: it's in detecting a margin drop, a customer at risk, or a channel that stopped converting earlier. That is worth more than any BI license.

In practice, the problem doesn't 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's no shared system, each area optimizes its own indicator, and the overall result worsens without anyone noticing until the close. That's what a good dashboard should prevent: early visibility and a common language.

The good news is that a two-year project isn't 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 isn't just in saving hours of Excel: it's in detecting a margin drop, a customer at risk, or a channel that stopped converting earlier. That is worth more than any BI license.

What is a sales dashboard

It is the panel where the sales team and management see the same status of the funnel, invoicing, and performance by person, channel, or product. It connects CRM with actual revenue sources when possible.

It includes pipeline by stage, conversion rate, closing speed, accumulated invoicing vs target, relevant activity (not vanity), and ranking of salespeople with fair criteria.

It should allow filtering by period, team, area, or product line. The sales director sees management; the salesperson sees their portfolio; management sees if the quarter holds up.

The key is to define what a valid opportunity is, when it is considered won, and how it reconciles with invoicing. Without that, the dashboard repeats the distortions of the CRM.

A good sales dashboard anticipates problems: deals without movement, excessive concentration on one customer, drop in conversion at a stage of the funnel.

It does not replace human sales management. It prioritizes where to focus attention today.

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

Cadence also matters: an operational indicator that moves every hour is different from 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 panel is just an opinion with graphs. With that, it becomes a management tool.

Cadence also matters: an operational indicator that moves every hour is different from 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 panel is just an opinion with graphs. With that, it becomes a management tool.

Cadence also matters: an operational indicator that moves every hour is different from 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
  • The 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 target. 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

Automatic 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 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

Salespeople with personal pipeline in Excel

Incomplete CRM and reality in private sheets. Sales dashboard fed by CRM + orders with stages you actually use.

Escenario 2

Closure forecast based on intuition

Without historical data or conversion by stage. Panel with funnel, aging of opportunities, and comparison with previous periods.

Escenario 3

Commissions calculated manually each month

Complex rules based on actual sales. Dashboard reflecting closed sales, returns, and targets with the same logic.

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 API, scheduled exports, or existing integration.

Can we keep Excel in parallel?

Yes during validation. The goal is for the panel 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 panel dies.

Power BI or custom web panel?

It depends on the Microsoft ecosystem, permissions, and UX. We define it in 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.