This guide details the features of Kondado's RD Station CRM report in Power BI: what each page and each visual shows, where the data comes from and how to use the report with your own data. Prefer Looker Studio? This same report is also available as a Looker Studio template — see the RD Station CRM Report Looker Studio documentation.

Table of Contents

1. Pipelines and Models
2. Accessing the Report in Power BI
3. Report Features
4. Comparison with the previous period
5. Overview of the 5 Pages
   1. Deals
   2. Deals List
   3. Tasks
   4. Tasks List
   5. Sales
6. Power Query and calculated columns
7. DAX Measures (Calculated Fields)
8. Benefits of Analyzing This Data

Pipelines and Models

This report uses Kondado's RD Station CRM data source. When you create the report through the Use your own data button, Kondado creates 7 pipelines of the data source and 2 data models in your account, which deliver the information already joined and ready for the charts — you don't need to write any query.

The 7 pipelines

In RD Station CRM a deal stores its owner, sales pipeline, stage, source and lost reason only as identifiers; the names live in the other pipelines. That is why there are 7 — and why the models exist.

The 2 models — they are what feeds the report

• Enriched deals (table rdm_deals) — one row per deal, with every field from the Deals pipeline plus the names already resolved: user_name (owner), deal_stage_pipeline_name (sales pipeline), deal_stage_name and deal_stage_order (stage and its order in the pipeline), deal_source_name (source) and deal_lost_reason_name (lost reason).
• Lost reasons (table rdm_motivos_perda) — lost deals summarized by date (deal creation date), user_name, deal_lost_reason_name, deal_stage_pipeline_name and deal_source_name, with tt = number of deals.

Power BI reads both models, the Tasks pipeline table and a calendar table created inside the file itself (dCalendário), which links the dates of every table to a single Period filter.

Need more history than the 90-day initial load? See How to change the savepoint in bulk and load more data.

Accessing the Report in Power BI

Just to look: the View the sample report button opens the published report in your browser, with fictitious data and a fixed period (07/24/2026 to 10/23/2026), so the sample keeps showing the same data over time. You don't need Power BI installed.

To use it with your own data:

1. Click Use your own data (top of this page) and sign in to your Kondado account.
2. Connect your RD Station CRM account.
3. Kondado creates the 7 pipelines and 2 models described above and runs the initial load (deals and tasks from the last 90 days). This can take from a few minutes to a few hours, depending on volume.
4. At the end of the flow, download the template file (RD CRM Report By Kondado.pbit) and open it in Power BI Desktop.
5. Power BI asks for a single parameter, the Token. Copy your token from the platform's Tokens tab (app.kondado.com.br/tokens, Copy token button), paste it and click Load.

In the file you download, each page's Period filter is set to “last 3 months” (relative to today), matching the 90-day initial load. At the top of the Deals page there is a “See how to load more data” badge that leads to the savepoint article for anyone who wants to load more history.

The report has 5 pages, available from the left-side menu: Deals, Deals List, Tasks, Tasks List and Sales.

Report Features

• Side menu — leads to the 5 pages.
• Owner and Sales Pipeline filters — at the top of every page.
• Period — one per page. On the deals pages it applies to the creation date; on the tasks pages, to the task date; on Sales, to the sale date.
• Deal or task search — on both list pages, filters by Id, name, stage, status and type.
• Comparison with the previous period on the cards of the Deals, Tasks and Sales pages (see the section below).
• Click to filter — clicking a bar, slice or row filters the other visuals on the page.
• Footer buttons — free trial and help.

Comparison with the previous period

The cards on the Deals, Tasks and Sales pages show, under the number, a “Previous period: N” line with the percentage change and an arrow (⬈ up, ⬊ down). When there is no value in the previous period, N/A is shown.

In Power BI the rule is always the same, in the published sample and in the file you download: the previous period is the same number of days immediately before the period chosen in the filter.

💡 The Looker Studio version of this report uses a different rule when the period is relative (it compares calendar months). If you use both tools, the percentages may not match for that reason — see the Looker Studio documentation.

The cards on the list pages (Deals List and Tasks List) have no comparison.

Overview of the 5 Pages

Page: Deals

Overview of the sales funnel: how many deals came in during the period, how many were won, lost, paused or are still ongoing, which stage the open ones are in, where they come from and why the lost ones were lost. This is the page that answers “how is my funnel doing?” — useful for the sales manager in the weekly meeting and for anyone who needs a quick picture of the team.

Owner (Slicer (drop-down))

Filters the page by the salesperson who owns the deal.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: user_name

Sales Pipeline (Slicer (drop-down))

Filters the page by RD Station CRM sales pipeline.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: deal_stage_pipeline_name

Period (Slicer (date range))

Slices every visual on the page by the deal's creation date (in the lost reasons chart, by the creation date of the lost deal).

• Pipeline / data model: The file's own calendar table (dCalendário), linked to the tables' dates
• Field(s) used: Data — linked to Dia Criação (from created_at) and to Dia Perda (from date in the Lost reasons model)

Deals Created (Card (KPI))

Number of deals created in the period, in every status. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measure Negociações Criadas (rows of rdm_deals)
• Aggregation: Row count

Deals In Progress (Card (KPI))

Deals created in the period that are still open (not won, lost or paused). Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: status = ongoing (measure Negociações em Andamento)
• Aggregation: Count

Deals Lost (Card (KPI))

Deals created in the period that are now lost. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: status = lost
• Aggregation: Count

Deals Won (Card (KPI))

Deals created in the period that are now won. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: status = won
• Aggregation: Count

Deals Paused (Card (KPI))

Deals created in the period that are paused in RD Station CRM. Paused is the fourth status a deal can have — without it, won + lost + ongoing would not add up to the total created. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: status = paused
• Aggregation: Count

Deals by Status (Combo chart (stacked columns + line))

Month by month (by creation date), the deals created split by status — ongoing, lost, won and paused — with a line for the month's total.

• Pipeline / data model: Enriched deals model (table rdm_deals) + calendar (Mês-Ano)
• Field(s) used: Mês-Ano, measures by status; line = Negociações Criadas
• Aggregation: Count

Stage (Table)

Of the ongoing deals, how many are in each funnel stage, in the order of the stages in your RD Station CRM, with a proportional bar and each stage's share.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: deal_stage_name; measures Nº Fase (stage position, by deal_stage_order), Negociações em Andamento and % das Negociações em Andamento
• Aggregation: Count and % of total

Deal Sources (Donut chart)

Where the deals created in the period came from (the source registered in RD Station CRM: website, referral, ads, event…), as a share of the total.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: deal_source_name; measure Negociações Criadas
• Aggregation: Count

Loss Reasons (Stacked horizontal bar chart)

Per month, how many deals were lost and for which lost reason. The month is the lost deal's creation month (not the closing month) — the same date criterion as the rest of the page.

• Pipeline / data model: Lost reasons model (table rdm_motivos_perda) + calendar (Mês-Ano)
• Field(s) used: Mês-Ano, deal_lost_reason_name; measure Negócios Perdidos (sum of tt)
• Aggregation: Sum

Page: Deals List

The same deals base, now row by row: each deal with its owner, sales pipeline, stage, status, value, the date of the next scheduled task and whether that task is on time. This is the page to act on — find the stalled deal, the deal with no next task or with an overdue task, and follow up with the owner.

Owner (Slicer (drop-down))

Filters the list by owner.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: user_name

Sales Pipeline (Slicer (drop-down))

Filters the list by sales pipeline.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: deal_stage_pipeline_name

Stage (Slicer (drop-down))

Filters the list by the deal's current stage.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: deal_stage_name

Status (Slicer (drop-down))

Filters by status: Won, Lost, Paused or In Progress.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: column Situação, which translates status

Period (Slicer (date range))

Slices the list and the cards by deal creation date.

• Pipeline / data model: The file's own calendar table (dCalendário), linked to the tables' dates
• Field(s) used: Data ↔ Dia Criação (from created_at)

Deal Id (Slicer (drop-down))

Finds a specific deal by its identifier.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: id

Deal Name (Slicer (drop-down))

Finds a deal by its name.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: name

Deals (Card (KPI))

Number of deals in the list, after filters.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measure Negociações Criadas
• Aggregation: Count

Lost (Card (KPI))

How many deals in the list are lost.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: status = lost
• Aggregation: Count

Won (Card (KPI))

How many deals in the list are won.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: status = won
• Aggregation: Count

Deal Value (Card (KPI))

Sum of the value of every deal in the list, in any status.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: total_price (measure Valor das Negociações)
• Aggregation: Sum

Deals List (Table)

One row per deal: Id, Name, Creation Date, Closing Date, Owner, Pipeline, Stage, Status, Value, Next Task (date of the nearest open task — empty if the deal is already closed), Next Task Status (Overdue, On Time, No Task Scheduled or Deal Closed, color-coded) and the deal's Completed Tasks.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: id, name, Dia Criação, Dia Fechamento, user_name, deal_stage_pipeline_name, deal_stage_name, Situação, Próxima Tarefa, Status da Próxima Tarefa (columns computed from tasks); measures Valor (tabela) and Tarefas Concluídas dos Negócios
• Aggregation: Sum of value; count of completed tasks

Page: Tasks

Measures the team's follow-up discipline: how many tasks were completed, canceled, are overdue or on time, how long the team takes to give the first response to a new deal, how many tasks each deal gets and how many deals got no task at all. It answers “is the team working the opportunities that come in?”

Owner (Slicer (drop-down))

Filters the page by task owner.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: owner_names

Sales Pipeline (Slicer (drop-down))

Filters by the pipeline of the deal the task belongs to.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: column Funil (the task's deal pipeline, brought from rdm_deals)

Period (Slicer (date range))

Slices the page by task (due) date. Response and coverage indicators use the deal creation date.

• Pipeline / data model: The file's own calendar table (dCalendário), linked to the tables' dates
• Field(s) used: Data ↔ Dia Vencimento (from due_date) and Dia Criação

Completed Tasks (Card (KPI))

Tasks in the period with completed status. A canceled task does not count, even though it has a completion date. Shows the change versus the previous period.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = Completed (from status and completed_at)
• Aggregation: Count

Average Response Time (Days) (Card (KPI))

On average, how many days passed between the deal's creation and the first completed task on it. A deal with no completed task counts the days up to today — so the number grows by itself every day while there are unanswered deals. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: created_at and column Primeira Conclusão em (earliest completed_at of the deal's tasks)
• Aggregation: Average of days

Average Tasks per Deal (Card (KPI))

How many tasks, on average, each deal created in the period got (a deal with no task counts as zero). Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: column Tarefas da Negociação
• Aggregation: Average

Deal Coverage (Card (KPI))

Share of the deals created in the period that have at least one task. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measures Negócios com Tarefa ÷ Negociações Criadas
• Aggregation: Percentage

Canceled (Card (KPI))

Tasks in the period that were canceled. Shows the change versus the previous period.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = Canceled
• Aggregation: Count

Overdue (Card (KPI))

Open tasks (not completed, not canceled) whose date has already passed. Depends on today's date. Shows the change versus the previous period.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = Overdue
• Aggregation: Count

On Time (Card (KPI))

Open tasks whose date is today or in the future. Depends on today's date. Shows the change versus the previous period.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = On Time
• Aggregation: Count

Completed Tasks by Type (Stacked column chart)

Week by week, completed tasks split by type (call, email, meeting, task, lunch, visit, WhatsApp).

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: column Semana Conclusão (from completed_at), type; measure Tarefas Concluídas
• Aggregation: Count

Response Time (Days) (Line chart)

Average response time, week by week, by the deal's creation week — shows whether the team is answering faster or slower.

• Pipeline / data model: Enriched deals model (table rdm_deals) + calendar (Semana)
• Field(s) used: measure Tempo de Resposta Médio (dias)
• Aggregation: Average of days

Tasks per Deal (Combo chart (stacked columns + line))

By creation week, how many deals got a task (bars Deals w/ Tasks), how many got none (Deals w/o Tasks) and the average tasks per deal (line).

• Pipeline / data model: Enriched deals model (table rdm_deals) + calendar (Semana)
• Field(s) used: measures Negócios com Tarefa, Negócios sem Tarefa, Média de Tarefas por Negociação
• Aggregation: Counts and average

Overdue, On Time and Canceled (100% stacked column chart)

Week by week, the share of tasks that are Overdue (completed after the due date, or open and past due), On Time and Canceled.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: calendar Semana, column Pontualidade; measure Tarefas
• Aggregation: Count, as %

Page: Tasks List

CRM tasks row by row, with subject, owner, due date, completion date, type, sales pipeline, the deal they belong to and their status (completed, canceled, overdue or on time). This is the operational page to review the team's agenda and find what was left behind.

Task Type (Slicer (drop-down))

Filters by task type.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: type

Task Status (Slicer (drop-down))

Filters by Completed, Canceled, Overdue or On Time.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: column Situação

Owner (Slicer (drop-down))

Filters by task owner.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: owner_names

Sales Pipeline (Slicer (drop-down))

Filters by the pipeline of the task's deal.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: column Funil

Period (Slicer (date range))

Slices the list by task date.

• Pipeline / data model: The file's own calendar table (dCalendário), linked to the tables' dates
• Field(s) used: Data ↔ Dia Vencimento

Deal Name (Slicer (drop-down))

Shows only one deal's tasks, by name.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: column Nome da Negociação

Deal Id (Slicer (drop-down))

Shows only one deal's tasks, by identifier.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: deal_id

Task Id (Slicer (drop-down))

Finds a specific task.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: id

Tasks (Card (KPI))

Total tasks in the list.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: measure Tarefas
• Aggregation: Count

Completed (Card (KPI))

Tasks in the list with Completed status.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = Completed
• Aggregation: Count

Canceled (Card (KPI))

Canceled tasks in the list.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = Canceled
• Aggregation: Count

Overdue (Card (KPI))

Open, past-due tasks in the list.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = Overdue
• Aggregation: Count

On Time (Card (KPI))

Open tasks in the list that are within the due date.

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: Situação = On Time
• Aggregation: Count

Tasks List (Table)

One row per task: Task Id, Subject, Owner, Task Date, Completion Date, Type, Sales Pipeline, Deal Id, Deal Name and Task Status (color-coded).

• Pipeline / data model: Tasks pipeline (table rdstationcrm_v2_tasks)
• Field(s) used: id, name, owner_names, Dia Vencimento, Dia Conclusão, type, Funil, deal_id, Nome da Negociação, Situação

Page: Sales

The funnel's outcome: how much was sold (won deals), how many sales, average ticket, how long a deal takes from creation to being won and the win rate among closed deals, month by month. It answers “how much did we sell, how fast and how efficiently?”

Owner (Slicer (drop-down))

Filters the page by salesperson.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: user_name

Sales Pipeline (Slicer (drop-down))

Filters the page by pipeline.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: deal_stage_pipeline_name

Period (Slicer (date range))

On this page the period applies to the sale date (closing date of the won deal), not the creation date.

• Pipeline / data model: The file's own calendar table (dCalendário), linked to the tables' dates
• Field(s) used: Data, applied by the sales measures to Dia Fechamento (from closed_at)

Sales Value (Card (KPI))

Sum of the value of the deals won in the period. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measure Valor de Vendas (total_price, status = won, Dia Fechamento within the period)
• Aggregation: Sum

Number of Sales (Card (KPI))

Number of deals won in the period. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measure Número de Vendas
• Aggregation: Count

Average Ticket (Card (KPI))

Average value per sale: Sales Value ÷ Number of Sales. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measure Ticket Médio
• Aggregation: Division

Average Cycle (Card (KPI))

On average, how many days a won deal took from creation to sale. Shows the change versus the previous period.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: column Ciclo (dias); measure Ciclo Médio (dias)
• Aggregation: Average of days

Sales Value (chart) (Combo chart (columns + line))

Month by month, the value sold (columns) and the number of sales (line).

• Pipeline / data model: Enriched deals model (table rdm_deals) + calendar (Mês-Ano)
• Field(s) used: measures Valor de Vendas and Número de Vendas
• Aggregation: Sum and count

Average Ticket (chart) (Line chart)

Average ticket over time, month by month.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measure Ticket Médio
• Aggregation: Division

Average Cycle (Days) (Line chart)

Sales cycle over time, month by month — whether sales are closing faster or slower.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measure Ciclo Médio (dias)
• Aggregation: Average of days

Win Rate among Closed Deals (Line chart)

By closing month: of the deals closed in the month (won + lost), how many were won.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: measures Número de Vendas ÷ Negociações Fechadas
• Aggregation: Percentage

Sales (Table)

One row per sale in the period: Deal Id, Name, Sale Date, Owner, Pipeline and Value.

• Pipeline / data model: Enriched deals model (table rdm_deals)
• Field(s) used: id, name, Dia Fechamento, user_name, deal_stage_pipeline_name; measure Valor de Vendas (tabela)

Power Query and calculated columns

Internal column and measure names in the file keep their original names (shown below in code or bold); the values they produce and every label you see in the report are in English.

The file has only 5 items in Power Query: the Token parameter, the tables rdm_deals, rdm_motivos_perda and rdstationcrm_v2_tasks, and the dCalendário calendar. The model has 4 relationships, all with the calendar: Dia Criação and Dia Fechamento (deals — the latter inactive, used only by the sales measures), Dia Vencimento (tasks) and Dia Perda (lost reasons).

Columns created in Power Query from the pipeline fields:

• Deals (rdm_deals): Dia Criação and Dia Fechamento (dates of created_at/closed_at); Situação (Won, Lost, Paused, In Progress, from status); Ciclo (dias) (days from creation to closing of won deals); Tarefas da Negociação and Tarefas Concluídas da Negociação (task counts); Primeira Tarefa em and Primeira Conclusão em (first task / first completion); Próxima Tarefa (earliest due date of open tasks, empty if closed) and Status da Próxima Tarefa (Deal Closed, No Task Scheduled, Overdue, On Time); Ordem da Fase (hidden, sorts stages as in your pipeline).
• Tasks (rdstationcrm_v2_tasks): Dia Vencimento and Dia Conclusão; Situação (Canceled, Completed, Overdue, On Time); Funil and Nome da Negociação (brought from the task's deal); Semana Conclusão; Pontualidade (Overdue — completed after the due date or open and past due —, On Time, Canceled).
• Lost reasons (rdm_motivos_perda): Dia Perda (from date) and Ordem do Motivo (hidden: largest total first, “Outros” last).
• Calendar: Data, Ano, Mês, Nome do Mês, Trimestre, Mês-Ano, Semana (weeks starting on Monday), from January of the oldest date's year to December of the newest date's year.

⚠️ The Situação and Status da Próxima Tarefa columns (Overdue / On Time) use today's date at the moment the data is refreshed.

DAX Measures (Calculated Fields)

Deals

• Negociações Criadas (deals created) — counts deals (rows of rdm_deals).
• Negociações Ganhas / Perdidas / em Andamento / Pausadas — count by status (won, lost, ongoing, paused).
• Valor das Negociações (deals value) — sum of total_price.
• % das Negociações em Andamento and Nº Fase — each stage's share and position in the Stage table.
• Negócios Perdidos (lost deals) — sum of tt from the Lost reasons model, honoring the Owner and Pipeline filters.

Sales

• Valor de Vendas, Número de Vendas, Ciclo Médio (dias) — deals with status = won and Dia Fechamento within the period (on this page the period applies to the sale date).
• Ticket Médio — Valor de Vendas ÷ Número de Vendas.
• Negociações Fechadas and Taxa de Ganho entre Negociações Fechadas — deals closed in the period (won + lost) and Número de Vendas ÷ Negociações Fechadas.

Tasks

• Tarefas, Tarefas Concluídas, Tarefas Canceladas, Tarefas em Atraso, Tarefas no Prazo — count tasks by Situação.
• Negócios com Tarefa / sem Tarefa, Média de Tarefas por Negociação, Cobertura das Negociações — from Tarefas da Negociação.
• Tempo de Resposta Médio (dias) — average, per deal, of the days between created_at and Primeira Conclusão em (or today, if none).
• Tarefas Concluídas dos Negócios — completed tasks of each deal, in the Deals List table.

On the tasks views, the Sales Pipeline filter also filters the deal measures (Response Time, Average, Coverage), so the page's numbers tell the same story.

Previous period comparison

• <measure> PA — the measure's value in the previous period (same number of days, immediately before). One exists for each card with a comparison.
• <measure> Evolução — (current − previous) ÷ previous.
• <measure> Evolução_texto — the change formatted with an arrow (⬈/⬊) or N/A.

Formatting measures

Valor das Negociações_texto, Valor de Vendas_texto, Ticket Médio_texto, Valor (tabela), Valor de Vendas (tabela) and Negociações (barra) repeat a measure above only to format it in a specific visual.

Benefits of Analyzing This Data

• The whole funnel in one place. Created, won, lost, paused and ongoing deals, by pipeline, owner and stage — no CRM spreadsheet exports.
• Know why you lose. Lost reasons month by month show whether the problem is price, competitors or customer fit — and where to act.
• Follow-up backed by data. Response time, coverage and overdue tasks show which opportunities are cooling down without contact.
• Act on the right deal. The Deals List points to deals with no next task or with an overdue task.
• Track the outcome. Value sold, average ticket, sales cycle and win rate month by month, compared to the previous period.
• Automatic updates, no code. Kondado's pipelines and models keep the report up to date; you don't write or maintain any query.