Reonic CRM Dashboard — KPIs explained

The CRM Dashboard is the rollup of your residential sales pipeline: six KPI tiles and nine chart cards, computed live from your requests. The numbers refresh every time you open the page or change a filter, so they always reflect your current pipeline.

This guide covers what the dashboard shows, what each KPI measures, how to slice the data with filters, how to compare against a previous period, how to drill into closed-won deals, and how to inspect the rows behind a tile.

Who this is for

• Installer admins with the admin role. The dashboard is an admin surface, so account managers, editors, viewers, and field workers see a permission-denied page if they open it.
• Admins running the weekly, monthly, or quarterly sales-review rhythm and wanting a single surface for closing volume, time-to-offer, time-to-signature, conversion, and deal-state distribution.

The dashboard is a Portal admin surface for the residential pipeline. The Mobile App is project-scoped for field workers.

Before you start

• The admin role opens the dashboard. If you have daily-use access elsewhere but the dashboard says "Permission denied," ask your admin to upgrade your role, or contact your Reonic account manager.
• The dashboard reflects your residential pipeline. A workspace running both residential and commercial sees the residential side rolled up here. Commercial-only workspaces work from their project surfaces rather than this dashboard.
• The dashboard reads live from your requests. Every time you open it, it re-reads the filtered request set, so the numbers are always current.
• The six KPI tiles and nine chart cards are fixed. Custom views (see below) save filter bundles, not the tile layout.
• Bookmark the URL with your default filter. Your filter state is captured in the page URL, so a browser bookmark re-applies your standard slice in one click.

Open the dashboard

1. Open the Portal in your browser.
2. Click Dashboard in the left navigation.
3. The page loads with default filters: time range = last 4 weeks, aggregation = Monthly, and no user, team, or tag filter.

You'll land on a page with a sticky filter bar at the top, a grid of six KPI tiles below, and a grid of nine chart cards under that. Hover any tile name for a glossary tooltip explaining the definition. The tooltip tells you exactly what each KPI counts, and is worth checking before you quote a number to a stakeholder.

Pro tip: If you regularly open the dashboard for the same time range, team, or lead source, save the URL as a browser bookmark. The filter state is captured in the URL, so the bookmark re-applies your slice instantly. Same idea as Copy view link below.

The six KPI tiles — what each one measures

Each tile name has a glossary tooltip (the ? icon next to the label) that explains the exact calculation. Most names are self-explanatory; two are worth a closer read, called out below.

• **Total Closed-Won Volume — Sum of order value across requests that closed Won in the time range. One of two tiles with drill-down** (the other is # Closed-Won). — higher is better
• **# Closed-Won — Count of requests that closed Won in the time range. Same basis as Total Closed-Won Volume, as a count instead of a value. Also supports drill-down** (same closed-won list). — higher is better
• **Avg Time to Signature** — Mean duration from request creation to first signature. Shown in hours, and formatted as days when over 72 hours. — lower is better
• **Avg Time to Offer** — Mean duration from request creation to offer creation. Shown in hours, and formatted as days when over 72 hours. — lower is better
• **Avg Lead Quality* — The share of requests in the window that progressed to an offer (offers created / total requests). This is an offer-creation rate, not an incoming-lead score. See Things to know* below. — higher is better
• **Avg Conversion Rate** — Offers that closed Won / total offers in the window. Won offers are offers with a signature or a won deal state. — higher is better

What "Avg Lead Quality" measures

Despite the name, Avg Lead Quality does not score the quality of your incoming leads. It measures the share of incoming requests in the time range that progressed to an offer. The glossary tooltip states this. If a stakeholder asks about the "quality" of your leads, quote this number as the offer-creation rate instead.

Reonic's AI lead-scoring feature is a separate capability. This tile is purely the request-to-offer ratio.

Why "Avg Conversion Rate" is not the same as "Avg Lead Quality"

These two tiles look similar at a glance and are easy to confuse. They measure different stages of the funnel:

• Avg Lead Quality = requests-with-an-offer / total-requests. Stage: qualification. How many leads turned into offers?
• Avg Conversion Rate = won-offers / total-offers. Stage: close. How many offers turned into wins?

Both show how the funnel narrows, at different stages. If your Lead Quality is high but your Conversion Rate is low, you're qualifying well but losing on close. If your Conversion Rate is high but your Lead Quality is low, you're losing leads before they ever become offers. Read the two together to see where the funnel breaks.

The mode determines the delta-badge colour

Each KPI is tagged either higher-is-better or lower-is-better. When you turn on a comparison period (see below), the delta-badge colours follow this mode:

• Higher-is-better (closed-won volume, # closed-won, lead quality, conversion rate). Green ↑ when the current period is higher than the comparison; amber ↓ when lower.
• Lower-is-better (avg time to signature, avg time to offer). Green ↑ when the current period is shorter (faster); amber ↓ when longer (slower).

Green always means "better"; the arrow direction follows the metric's meaning, not the raw numeric direction. Hover the delta badge for a tooltip explaining "higher is better" vs "lower is better" for that specific KPI.

The nine chart cards — what each one shows

Below the KPI grid, nine chart cards roll up the same underlying data into time-bucketed and categorical views:

• **Total Deal Volume** — Sum of order value across all active deals (excluding Lost and Rejected) in the window, time-bucketed by aggregation level.
• **# Deals** — Count of all active deals (excluding Lost and Rejected) in the window, time-bucketed.
• **Total Weighted Pipeline Value** — Each deal's value multiplied by the confidence ratio set on its Kanban status, summed across the pipeline — the weighted-by-confidence pipeline number you'd quote in a forecast review.
• **Total Closed-Won Volume (chart)** — The closed-won volume as a time-bucketed trend chart.
• **# Closed-Won (chart)** — The closed-won count as a time-bucketed trend chart.
• **Avg Revisions Until Signature** — Mean number of signature requests per signed deal — how many drafts the average customer takes before signing.
• **Total Volume by Deal State** — Sum of order value bucketed by Kanban status / deal state.
• **# by Deal State** — Count of deals bucketed by Kanban status / deal state.
• **Sales Funnel** — The classic funnel: requests, offers, closed-won, in ratio. Each step shows the count and the ratio to the previous step.

Each chart card has its own glossary tooltip and, optionally, a headline number above the chart. Charts respect every filter on the bar, including the compare-to overlay (see below): when compare-to is on, charts show two series (current and comparison period) on the same axes.

Filter the dashboard

The filter bar at the top of the page is the primary daily interaction. Set any combination of these dimensions and every tile and chart re-computes against the filtered slice:

1. Aggregation level (default: Monthly). How time-bucketed charts roll up. Available levels: Daily / Weekly / Monthly / Quarterly / Yearly. This affects how the chart cards bucket data; it doesn't filter rows.
2. Time range (default: last 4 weeks). The start and end window for the "current" period. Pick from presets (last 7 days, last 4 weeks, this month, last month, this quarter, this year, all time) or set a custom start and end.
3. Compare-to. Overlay a "before" window. Appears when the time range is set to anything other than all-time. See the next section.
4. Users. Multi-select; filter to requests assigned to specific users. Useful for per-rep performance views.
5. Teams. Multi-select; filter to requests assigned to teams. Appears when your workspace has the Teams feature enabled.
6. Lead source. Multi-select from your configured lead-source list. If the list is empty, the dropdown is empty; ask your admin to configure lead sources if the picker is blank.
7. Tags (include) and Exclude tags. Multi-select tag include and exclude. Use to filter, for example, PV-only offers, or to exclude internal-test projects.
8. With archived. Toggle. Default off (archived requests are hidden). Toggle on to include archived requests in aggregates.
9. Search. Free text. Uses the same full-text search as the requests list.

Each picker click re-runs the view. If you're changing several dimensions in a row, set them all on a saved view and apply the view in one click.

Note: The dashboard always shows your active, won, and post-sale pipeline and excludes Lost and Rejected requests, regardless of your filter set. This is the most common reason the dashboard numbers don't match the requests list. If a stakeholder is comparing the two, set the matching exclusions on the requests list, or include Lost and Rejected on the list to see the gap.

Per-user / per-team performance views

Filter by Users or Teams to isolate a single rep's or team's contribution. The KPI tiles and charts re-compute against just that user's or team's assigned requests. Useful for monthly one-on-ones, team retros, and "who's closing what" reviews.

• Users and Teams compose independently. If you set both, the filter combines them with OR: a request assigned to that user or assigned to that team. Not AND.
• The Teams filter appears when Teams is enabled on your workspace. Ask your admin if you need it.
• The Users / Teams filter respects the same scoping as the rest of the Portal.

Period filters — week / month / quarter / year / custom

The Time range picker offers the standard presets plus Custom. Pick what matches the cadence of your review:

• Weekly stand-up. Set time range = last 7 days, compare-to = previous 7 days.
• Monthly review. Last month or this month, compare-to = same period prior year.
• Quarterly board update. This quarter or last quarter, compare-to = same period prior year.
• Annual planning. This year or last year, compare-to = previous year.
• Custom. Any start and end. Useful for a campaign window or a launch window.

Time-range presets follow your workspace's configured timezone: "this month" runs from the first of the month to today, "last month" from the first to the last of the previous month, and so on.

Save the filter combination as a reusable view

When you've found a filter setup you regularly need (for example, "weekly stand-up: last 7 days, Team A only, lead source Energyhouse"), save it as a named view so you don't re-pick the dimensions every Monday:

1. Set the filter and compare-to combination you want.
2. In the filter bar, open the saved-view picker and choose Save current view.
3. Name the view ("Weekly stand-up — Team A", "Monthly board view", "Q2 push").
4. Save.

To apply a saved view, open the saved-view picker and pick the name from the list. Filters and compare-to apply immediately, and the URL updates to include the view. To edit a saved view, apply it, change a filter, and either Save changes to overwrite or Save as new view to create a separate copy. To delete a view, find it in the picker and use the delete control.

Saved views are per-user: two admins on the same workspace have their own lists. To share a view, share its URL rather than a shared library.

Share a view with a colleague

Two options:

• Copy view link. With your filter set applied, click Copy view link in the filter bar. The URL — including all filter state, the optional view, and the compare-to window — is copied to your clipboard. Paste it into a message, email, or meeting note. The recipient clicks it and the dashboard loads on their side with the same filter applied, provided they have dashboard access.
• Bookmark and share the bookmark URL. Same mechanism, persisted in your browser instead of copied to the clipboard.

The URL captures the full filter state, so the recipient sees the same view without saving it. On their side the view is temporary: they see what you see, and it doesn't land in their saved-view list.

Pro tip: Build a saved view for each rhythm: weekly stand-up, monthly review, quarterly board update. Then copy the view link into your team's standing meeting agenda so everyone lands on the same numbers.

Compare against a previous period

Overlay a "before" window onto your current view to see this period's KPIs alongside last period's, with signed-percentage delta badges (green ↑ / amber ↓ / grey →). The compare-to picker is the primary trend-analysis tool on the dashboard.

1. Set a time range (default: last 4 weeks). Compare-to appears when the time range is anything other than all-time.
2. The compare-to picker appears in the filter bar next to the time range. Click it.
3. Pick the comparison window:
   • Previous period. Same duration immediately before the current window (for example, the previous 4 weeks before the current 4 weeks).
   • Same period, prior year. Same duration shifted back one year.
   • Custom. Pick any start and end dates for the comparison window.
4. The dashboard reloads. Each KPI tile now shows:
   • Big "now" value. The value for your current time range.
   • Small grey "before" value. The comparison-period value, labelled "in the comparison period."
   • Signed-percentage delta badge. Green ↑ when better, amber ↓ when worse, grey → when within ±2% of the comparison value.

The ±2% threshold

A delta within ±2% renders as a grey arrow (→), treated as "essentially flat." This suppresses noise when small absolute changes shouldn't be celebrated or alarmed. A green or amber arrow means the delta crossed the threshold; a grey arrow means the period was effectively flat.

Charts under compare-to

Chart cards show two series (one for the current window and one for the comparison window) overlaid on the same axes. Hover the chart for a tooltip showing each series' value at the hovered point.

What the compare-to covers

The compare-to is a straight period-vs-period comparison. The drill-down drawer always shows the current period: when you click into Total Closed-Won Volume (one of the two drillable tiles), the drawer lists the "now" period's rows. To inspect the "before" period's closed-won rows, swap your compare-to and time-range windows.

Drill down on Closed-Won Volume

The Total Closed-Won Volume and # Closed-Won tiles both support drill-down. Click either and a drawer opens with the list of underlying won deals.

1. With the dashboard loaded under your current filter set, click the Total Closed-Won Volume tile.
2. The drill-down drawer opens.
3. The drawer shows a paginated table of closed-won deals, typically 20 rows per page. Columns include customer name, deal value, signature date, and the assigned user.
4. Click any row to open the underlying offer in a new tab. Your dashboard tab keeps its filter and drill-down state.
5. Page through the list with the pagination controls at the bottom of the drawer.
6. Close the drawer with the close button.

Note: A deal counts as closed-won when it has a signature that's still in place. If a customer withdraws a signed offer, it drops out of the closed-won list. Each project counts once, at the date of its most recently signed variant; a manually set close date overrides that date.

Note: Total Closed-Won Volume and # Closed-Won are the two tiles with built-in drill-down. To see the rows behind any other KPI or chart, use the cross-reference approach below.

Cross-reference a KPI with the requests list

When a KPI other than Total Closed-Won Volume is worth a closer look (Avg Lead Quality dropped, Avg Time to Signature jumped, the funnel narrowed unexpectedly), replicate the dashboard's filter on the requests list and inspect the underlying rows there.

1. On the dashboard, note the current filter values: time range, users, teams, lead sources, tags, exclude tags, and with-archived. (Aggregation level only affects chart bucketing, so ignore it for cross-reference.)
2. Open the requests list in a new tab.
3. Apply the matching filters on the requests list. The filter names line up with the dashboard (same lead-source, team, and tag dimensions; same with-archived toggle).
4. Add the dashboard's implicit exclusions: filter out Lost and Rejected on the requests list, or keep them visible if you want to see the gap.
5. Scan the resulting row count and the rows themselves.

The row count on the filtered requests list approximates the basis behind most dashboard KPIs. The gap between the dashboard's count and the list's count is usually an archived-state difference or the Lost / Rejected exclusion. A difference of a few rows is normal; a large mismatch means a filter difference worth tracking down.

Pro tip: When a stakeholder asks "which deals are in Avg Lead Quality?", cross-reference: replicate the dashboard's time range and filters on the requests list, then inspect. The list view is the row-level surface for non-Closed-Won KPIs.

Refresh and data freshness

The dashboard re-computes every time you open the page, change a filter, or refresh the browser.

• Open the page. Full re-compute of the filtered request set.
• Change a filter. Full re-compute for the new filter slice.
• Refresh the browser. Re-runs the current view.
• Compare-to on. The view runs for both the "now" and the "before" windows on every refresh.

The numbers are always fresh. If a number looks stale, refresh the page and it re-computes.

Pro tip: For a recurring weekly summary, bookmark a saved view, set a calendar reminder to open the dashboard once a week, and screenshot the numbers into your meeting notes.

Get the data out of the dashboard

The dashboard lives in the browser. When you need the numbers elsewhere:

• Screenshot the page for a meeting deck, a board update, or an email. Save the URL alongside the screenshot so a colleague can re-open the same view.
• Cross-reference to the requests list to get the row-level data behind a KPI by replicating filters on the requests list (see above). The list view is the row-level surface.
• Contact Reonic support for an extract. Reonic can pull the underlying data from your workspace on request. Allow a few days of turnaround.
• Build downstream from the same data. If your workspace has a CRM integration or a planning-system integration, the same offers, requests, and signatures data may be available there for export.

The AI Sales Assistant reads the same numbers

Reonic's AI Sales Assistant (the in-app chat surface) reads the dashboard's KPIs and chart data. Ask it a question like "how did closed-won volume compare to last month?" and it pulls the same aggregated numbers the dashboard shows.

This means three things in practice:

• The assistant's numbers are the dashboard's numbers. If you and a stakeholder disagree on a value, refresh the dashboard and re-ask the assistant; both should match.
• The assistant respects the same filters. You can ask it to scope by user, team, or time range — the same dimensions as the filter bar.
• The assistant reads the same surface. It's a query interface over the dashboard, reading the same aggregated data, not a separate data source.

Things to know

• The tiles and charts are fixed. The six KPIs and nine charts are a set layout: every admin sees the same KPIs and charts. Custom views save filter bundles.
• The KPIs are backward-looking. Avg Conversion Rate and Total Weighted Pipeline Value are the closest forecast-style numbers, and both summarise past wins. The dashboard rolls up your own pipeline.
• Status confidence ratios drive the weighted pipeline. The confidence ratio you set per Kanban status in Settings → Kanban boards → Board management drives the Total Weighted Pipeline Value chart, and in turn any AI Sales Assistant queries that read weighted pipeline.
• Saved views apply the filters that still exist. If a filter dimension changes in a future release, an older saved view drops the changed filter the next time you apply it. Re-save the view if the numbers look subtly off.
• Large pipelines take a moment. The dashboard re-reads the filtered request set each time you open it, so a very large pipeline may take a few seconds to paint.

Related

• Contacts — the address book that backs every request the dashboard counts.
• Tasks — task management surface; not shown on the dashboard.
• Finalise an offer & request signature — the signature event that flips a deal to Won.
• Custom dashboard views — save and reuse the filter combinations described above.

Need help?

• Step-by-step questions about the dashboard → contact your Reonic account manager.
• Role or permission requests (dashboard access for non-admins) → ask your admin to upgrade your role, or contact Reonic support.
• Feature requests (export, custom KPIs, scheduled digests, alerts, drill-down on more tiles, a commercial dashboard) → send a note to your account manager.
• Bug reports (a KPI looks wrong, drill-down doesn't open, a delta badge is the wrong colour) → include a screenshot and the dashboard URL in your support email; the URL captures the exact view you were looking at.

Last updated on August 4, 2026