Dashcipe
Back to recipes
Previous dashboardNext dashboard
SaaSIntermediateFree during launch

CRM Pipeline Dashboard

A CRM dashboard for leads, conversion, deal stage, and forecast.

55 minNext.js / Tailwind / RechartsSales lead

Recipe Workspace

Preview the layout, understand the KPIs, copy the starter

Review the dashboard at a practical desktop ratio first, then use the KPI rationale, code starter, and AI IDE prompt below.

Live Recipe Preview

CRM Pipeline Dashboard

A CRM dashboard for leads, conversion, deal stage, and forecast.

Free launch recipeOpen live view

Live Recipe

CRM Pipeline Dashboard

A CRM dashboard for leads, conversion, deal stage, and forecast.

Overview · Free launch recipe
Dark CRMdensesidebardark sidebarpipeline cardsactivity feed

Leads

18,420+8.2%

Conversion

34.8%+2.1%p

Pipeline

$84.2K+12.4%

Forecast

ReadyTracked

Leads trend

Nivo

Pipeline Activity

Recharts
1

Leads

Sample data

18,420
2

Conversion

Sample data

34.8%
3

Pipeline

Sample data

$84.2K

Watch List

LeadsWatch
ConversionWatch
PipelineWatch

Detail Table

Leads

Sample data

18,420

상태

Conversion

Sample data

34.8%

상태

Pipeline

Sample data

$84.2K

상태

Top

Four KPI cards

Middle

Primary trend and segment view

Bottom

Priority table and alerts

KPI Ingredients

Leads

Leads belongs in the primary row when an owner can act on it this week.

Alternative KPI: Leads segment

Conversion

Conversion belongs in the primary row when an owner can act on it this week.

Alternative KPI: Conversion segment

Pipeline

Pipeline belongs in the primary row when an owner can act on it this week.

Alternative KPI: Pipeline segment

Forecast

Forecast belongs in the primary row when an owner can act on it this week.

Alternative KPI: Forecast segment

Code Starter

Copy component starter

const metrics = [
  { label: "Leads", value: "18,420", change: "+8.2%" },
  { label: "Conversion", value: "34.8%", change: "+2.1%p" },
  { label: "Pipeline", value: "$84.2K", change: "+12.4%" }
];

export function CrmPipelineDashboardPreviewCards() {
  return <section className="grid gap-3 md:grid-cols-3">{metrics.map((metric) => <article key={metric.label} className="rounded-xl border border-zinc-200 bg-white p-4"><p className="text-xs font-bold text-zinc-500">{metric.label}</p><strong className="mt-1 block text-2xl font-black">{metric.value}</strong><span className="text-xs font-black text-emerald-600">{metric.change}</span></article>)}</section>;
}

AI IDE Prompt

Paste into your AI IDE

Create a CRM Pipeline Dashboard. Put KPI cards for Leads, Conversion, Pipeline, Forecast, trend and segment charts, a priority table, and empty/loading/error states.

Decision System

Why this dashboard should exist before it is designed

AdSense-quality pages need original explanation, not only screenshots. This section documents the decision, data model, failure patterns, and implementation alternatives.

Operating decision

CRM Pipeline Dashboard answers this operating question: Which sales motion drives forecast movement?. The primary row is not a vanity summary; it decides what an owner should do this week.

The recipe is designed for Sales lead, Early product builders who need to choose data definitions, chart priority, and bottom-row actions quickly.

Data sources and event definitions

  • CRM leads, deals, stages

Before implementation, define event names, owner, refresh cadence, and missing-data behavior for each source.

Required KPIs and removal rules

Leads

Leads belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Leads segment

Conversion

Conversion belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Conversion segment

Pipeline

Pipeline belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Pipeline segment

Forecast

Forecast belongs in the primary row when an owner can act on it this week.

Alternative or removal signal: Forecast segment

Common failure patterns

Treat isolated movement in Leads as a signal to inspect data definitions or operating bottlenecks.

Treat isolated movement in Conversion as a signal to inspect data definitions or operating bottlenecks.

Treat isolated movement in Pipeline as a signal to inspect data definitions or operating bottlenecks.

Treat isolated movement in Forecast as a signal to inspect data definitions or operating bottlenecks.

Alternative layout

For an MVP, keep Four KPI cards. As data matures, expand Primary trend and segment view into segment comparison or cohort analysis.

Implementation Blueprint

KPI audit protocol before implementation

Use this table before designing the UI. Without a formula, review cadence, and action trigger, a dashboard can look polished but still fail to support an operating meeting.

Leads

Leads = source event aggregate / comparison baseline. Start segmentation by Leads segment.

Daily morning

If Leads moves more than 10% week over week, inspect the causal segment and action table together.

Conversion

Conversion = source event aggregate / comparison baseline. Start segmentation by Conversion segment.

Weekly review

If Conversion moves more than 10% week over week, inspect the causal segment and action table together.

Pipeline

Pipeline = source event aggregate / comparison baseline. Start segmentation by Pipeline segment.

After campaign end

If Pipeline moves more than 10% week over week, inspect the causal segment and action table together.

Forecast

Forecast = source event aggregate / comparison baseline. Start segmentation by Forecast segment.

Monthly report

If Forecast moves more than 10% week over week, inspect the causal segment and action table together.

Event and table starter

When starting from an AI IDE, lock event and table names first. It makes generated components and queries much more consistent.

crm_pipeline.viewed

Source event for Leads. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

crm_pipeline.converted

Source event for Conversion. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

crm_pipeline.risk_flagged

Source event for Pipeline. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

crm_pipeline.resolved

Source event for Forecast. Keep owner, occurred_at, segment_key, value, and source_system as baseline fields.

Weekly review sequence

  1. 1Separate whether the Leads movement is a real operating issue or short-term noise.
  2. 2Read it with Conversion to narrow the cause to acquisition, conversion, quality, or throughput.
  3. 3Use the bottom table to choose one owner, one segment, and one action for this week.
  4. 4At the next review, adjust the layout based on recovery after the action, not on the same chart alone.

Frequently asked questions

Which KPIs should CRM Pipeline Dashboard prioritize?

CRM Pipeline Dashboard should prioritize Leads, Conversion, Pipeline, Forecast. Keep Leads in the primary row only when an owner can act on it this week.

What data sources are required?

CRM leads, deals, stages are the baseline sources. Define event names, refresh cadence, owner, and missing-data behavior before implementation.

Can this layout be used for an MVP?

For an MVP, start with Four KPI cards and Primary trend and segment view. Add bottom tables and alerts when operating actions become clear.

Which metrics should be removed?

Remove metrics that cannot trigger an action within one weekly review cycle, have unstable definitions, or behave like vanity metrics without adjacent context.

How should the AI IDE prompt be used?

Use the prompt as a starting point, then add real field names, table names, state UI requirements, and accessibility requirements for your project.

Market Pattern

Marketplace-proven dashboard pattern, rewritten for Dashcipe

This section documents the public preview pattern behind the layout and how Dashcipe changes it into original KPI guidance.

dark-crm-suite / dark
dark sidebarpipeline cardsactivity feeddeal table

Observed pattern

CRM and project templates often use dark sidebars, pipeline cards, activity feeds, and priority tables for dense workspaces.

Dashcipe adaptation

This recipe maps those ideas to bottlenecks, owners, and next actions for the vertical.

Originality guard

It extracts general CRM patterns visible in public previews without pixel-copying any original layout.

Free Resources

What you can use for free

Use the KPI logic, layout, code starter, prompt, Figma SVG, schema, and tokens directly.

requestRequest/VotepromptAI PromptKPI logicAI promptRequest queue

Use this recipe when

  • The vertical metrics are already roughly known
  • You need to prioritize charts and tables quickly

Skip this recipe when

  • No events or data definitions exist yet
  • You only need a marketing landing page

Expert Notes

How a real operator should read these KPIs

These notes turn each metric into an operating decision, data source, and removal rule.

Sales lead

Why it matters
Leads is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Leads as a signal to inspect data definitions or operating bottlenecks.
Data source
CRM leads, deals, stages
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Sales lead

Why it matters
Conversion is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Conversion as a signal to inspect data definitions or operating bottlenecks.
Data source
CRM leads, deals, stages
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Sales lead

Why it matters
Pipeline is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Pipeline as a signal to inspect data definitions or operating bottlenecks.
Data source
CRM leads, deals, stages
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Sales lead

Why it matters
Forecast is not a vanity number; it decides the next operating action.
Failure signal
Treat isolated movement in Forecast as a signal to inspect data definitions or operating bottlenecks.
Data source
CRM leads, deals, stages
When to remove
Remove it from the primary row if no owner can act within one weekly review cycle.

Recipe Flow

Move through recipes without returning to the list

All recipes
Previous recipeFintech Portfolio DashboardA portfolio dashboard for assets, return, risk, and rebalancing signals.Next recipeSupport Ticket DashboardA support starter kit for SLA, backlog, first response, and repeat issues.

Related Recipes

Similar dashboard recipes

Recipes from the same category or stack.

bootstrap-analytics
Free resourceBeginner

AdMob Revenue Dashboard

Is a revenue drop caused by traffic, pricing, or placement?

Free downloadQuality checkedStarter KitNext.js3 screensSchemaFigma SVGNext.jsTailwindChart.js
Market patternbootstrap-analytics
Layout: topbarSurface: lightstat cardsbar chart
4 KPIsDetails
enterprise-suite
Free resourceIntermediate

GA4 App Analytics Dashboard

Where do users come from, convert, or drop off?

Free downloadQuality checkedStarter KitNext.js3 screensSchemaFigma SVGNext.jsTailwindRecharts
Market patternenterprise-suite
Layout: splitSurface: hybridKPI rowtrend chart
4 KPIsDetails
ops-workbench
Free resourceBeginner

Play Console Operations Dashboard

Where does store quality change appear first?

RequestableHTMLTailwindChart.js
Market patternops-workbench
Layout: sidebarSurface: darkstatus wallmap/list panel
4 KPIsDetails