The CRM dashboard examples below are four screens that a 10 to 250 person service firm actually uses: the owner's Monday view, the sales lead's pipeline view, the speed-to-lead view and the client retention view. Each one answers a different question for a different person. This article explains what is on each, why it works, and how to build any of them in Reporting on the levelpartner.ai platform in under an hour.
Why most CRM dashboards fail
A CRM can chart almost anything, so most dashboards end up charting almost everything. Twenty widgets, no hierarchy, and nobody quite sure which one matters. After a fortnight, people stop opening it.
Good dashboards are built backwards from a question and a person. "Is the pipeline big enough to hit next quarter?" is a question. "The sales lead" is a person. The widgets follow from those two choices, not from what the CRM can show.
Example 1: the owner's Monday view
The question: are we on track this month and this quarter. The person: the owner or managing director.
Four widgets: revenue won this month against target, weighted pipeline value for the next 90 days, new opportunities created this week, and the number of deals with no activity in 14 days. The last one is the early warning. A pipeline full of stalled deals looks healthy until it suddenly is not.
It works because it fits on one screen and takes two minutes to read before the Monday meeting.
Example 2: the sales lead's pipeline view
The question: where are deals stuck and who needs help. The person: the sales lead or head of business development.
Widgets: opportunities by stage, average days in each stage, stage-to-stage conversion, and open value by salesperson. This view works because it shows bottlenecks. If deals sit for three weeks between proposal and decision, that is the stage to coach.
Example 3: the speed-to-lead view
The question: are new enquiries being answered fast enough. The person: whoever manages the inbox or the sales development team.
Widgets: average response time, the share of conversations breaching your reply target, and booked calls from enquiries this week. It works because response time is one of the few things a team can improve tomorrow.
Example 4: the client retention view
The question: which clients are at risk and which are ready for more. The person: the account management or delivery lead.
Widgets: clients with no contact in 30 days, review requests sent and received, renewals due in the next 60 days, and upsell opportunities open. It works because it puts existing revenue on the same footing as new revenue, which most CRM dashboards ignore.
Before you start
- Opportunities with values, stages and owners assigned.
- Conversations connected so responses are recorded.
- One named person for each dashboard you build.
How to set it up
- Choose one example above and name the person it serves.
- Write the question that person needs answered each week.
- Go to Dashboard and open the Dashboard Selection Menu.
- Click + Add Dashboard and enter a Dashboard Name that states its question.
- Set the Private Dashboard toggle and access levels, then click Confirm.
- Click + Add a widget manually and add only that example's widgets.
- Click Save Changes and set the Date Picker to the review rhythm.
- Ask them after two weeks which widget they ignored, then remove it.
Suppose the firm builds the owner's view and the speed-to-lead view first. In week one, say the speed-to-lead view shows 14 of 52 enquiries waited more than an hour for a reply. If the team then adds an AI chat agent for out-of-hours enquiries and a daytime rota, the same widget is where you would watch that count fall, for example to 3 of 49 by week six. The point is that one specific widget, owned by one person, makes visible a problem a general dashboard hides. Numbers are illustrative.
What these dashboards replace
They replace the weekly export to a spreadsheet and the meeting spent arguing about whose figures are current. They also replace asking salespeople for verbal updates on every deal, because the stage and last activity are visible to everyone.
Time each one takes
Each dashboard takes 30 to 60 minutes to build if the CRM data is clean. Reading one takes two to ten minutes a week. The real cost is keeping the underlying data accurate: stages updated, values entered, activity logged. If salespeople skip that, every example above shows the wrong picture.
The mistake most people make
Building one dashboard for everyone. The owner, the sales lead and the delivery lead need different answers. A shared dashboard tries to serve all three and ends up serving none. Build one per person, even if some widgets overlap.
When not to use them
With fewer than five active deals at a time, a dashboard is slower than opening the pipeline board. Use the board directly. Dashboards also mislead when stages are used inconsistently, so fix the pipeline first.
For marketing-side screens, see the marketing dashboard and the marketing attribution dashboard. If you want the sales and marketing teams on one screen, read about building a joint sales and marketing view.
Troubleshooting
Pipeline values look too high. Lost deals were never marked lost. Run a clean-up and set a workflow to flag deals with no activity in 30 days.
Response times look impossibly fast. Automated replies are being counted as responses. Filter the widget to replies sent by a person.
Salesperson totals do not match their own count. Deals are owned by the wrong user. Reassign ownership and set the owner automatically when a deal is created.
Retention widgets are empty. No delivery pipeline exists. Create one for active clients so renewals and check-ins have somewhere to live.
Frequently asked questions
How many widgets should a CRM dashboard have?
Between four and eight. Fewer than four rarely answers a full question. More than eight usually means the dashboard is serving more than one person.
Can a salesperson see only their own deals?
Yes. Build a version of the pipeline view filtered by owner, or use user permissions so each person sees their own opportunities.
Should dashboards show targets?
Revenue and pipeline widgets should. Activity widgets usually should not, because activity targets encourage busywork.
Which example should I build first?
The owner's Monday view if leadership lacks visibility, or the speed-to-lead view if enquiries are going cold. Both show results within weeks.