{"id":3234,"date":"2026-11-01T10:47:18","date_gmt":"2026-11-01T07:47:18","guid":{"rendered":"https:\/\/fluidcrm.io\/blog\/?p=3234"},"modified":"2026-11-01T11:00:17","modified_gmt":"2026-11-01T08:00:17","slug":"crm-dashboard","status":"publish","type":"post","link":"https:\/\/fluidcrm.io\/blog\/crm-dashboard\/","title":{"rendered":"CRM Dashboard: What a Small Team Should See Every Morning"},"content":{"rendered":"\n

You open your CRM dashboard, look at eleven charts and close it again, because none of them says who you owe a call today. Most dashboards are built to answer a manager’s question. On a team of four, the manager is also the person selling.<\/p>\n\n\n\n

A CRM dashboard is one screen of live numbers from your CRM. A small team’s should show overdue next steps, next steps due today, active deals, pipeline value and value by stage. Fluid CRM’s dashboard shows those five with no setup.<\/strong><\/p>\n\n\n\n

<\/span>What a CRM Dashboard Is and How a Sales Dashboard Differs<\/span><\/h2>\n\n\n\n

A CRM dashboard is the summary screen inside your CRM. It reads from your deals and reminders, so nobody has to build the numbers by hand, and they change as soon as someone updates a deal.<\/p>\n\n\n\n

A sales dashboard is the wider term. It means sales numbers on one screen wherever that screen lives, including a spreadsheet tab, a separate analytics tool or a TV on the office wall. In a team that keeps all its sales data in the CRM, the two are the same thing, so the rest of this post treats them that way.<\/p>\n\n\n\n

The word people mix them up with is report, and the difference is who reads it.<\/p>\n\n\n\n

<\/th>CRM dashboard<\/th>Sales dashboard<\/th>Sales report<\/th><\/tr><\/thead>
Where it lives<\/td>Inside your CRM<\/td>CRM, spreadsheet or a separate tool<\/td>Email, doc or chat message<\/td><\/tr>
Who reads it<\/td>The person doing the selling<\/td>Depends on who built it<\/td>Someone who wasn’t in the room<\/td><\/tr>
When you look<\/td>Daily<\/td>Daily to weekly<\/td>Weekly or monthly<\/td><\/tr>
Question it answers<\/td>What do I do now?<\/td>How are sales going right now?<\/td>What happened, and why?<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

If you need the written version, with new deals, wins and losses sent to a cofounder or a boss, use a sales report template<\/a>. A dashboard is for the person who still has calls to make today.<\/p>\n\n\n\n

<\/span>What a Small Team’s CRM Dashboard Should Show<\/span><\/h2>\n\n\n\n

Read a few guides on this and you’ll see the same split into rep, manager and executive dashboards, with leaderboards, quota gauges and activity counts in each. That split makes sense at a company with 40 sellers and a sales ops person. On a team of four, those screens answer questions nobody in the room needs to ask.<\/p>\n\n\n\n

My old agency, Fenixtal, booked 1,250+ sales calls and handed the leads over to clients, so I saw which ones got tracked. I never saw a lead die for lack of a chart. I saw plenty die in the weeks nobody opened the CRM.<\/p>\n\n\n\n

So put every widget through one test. If this number changes, what do I do differently?<\/strong> If you have no answer, it doesn’t belong on the screen you open each morning.<\/p>\n\n\n\n

Five numbers pass. Two of them are for today and three are for the week.<\/p>\n\n\n\n

Number<\/th>How often it matters<\/th>What you do when it moves<\/th><\/tr><\/thead>
Overdue next steps<\/td>Every morning<\/td>Clear them before anything else, or mark the reminder done and close the deal<\/td><\/tr>
Next steps due today<\/td>Every morning<\/td>That is your call list<\/td><\/tr>
Active deals<\/td>Weekly<\/td>Too few means prospecting this week, too many means closing out dead ones<\/td><\/tr>
Pipeline value<\/td>Weekly<\/td>Two falling weeks in a row means more new deals, not more chasing<\/td><\/tr>
Value by stage<\/td>Weekly<\/td>Too much value in one stage tells you which step to work on<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

These five are also what the home screen of Fluid CRM<\/a>, our sales team CRM<\/a>, shows. The test works on any CRM you already use.<\/p>\n\n\n\n

<\/span>1. Overdue next steps<\/span><\/h3>\n\n\n\n

This number goes first because each one is a promise you already missed. Without opening a tab, can you name the deal you said you’d call back yesterday?<\/p>\n\n\n\n

A count on its own isn’t enough. The number has to open the list of deals behind it, or you still have to search the pipeline for names.<\/p>\n\n\n\n

<\/span>2. Next steps due today<\/span><\/h3>\n\n\n\n

The second number is your plan for the day. If it reads 14 and you have 6 hours of calls in you, you find out at 9 a.m. instead of at 5 p.m., and you can move the least urgent ones on purpose.<\/p>\n\n\n\n

<\/span>3. Active deals<\/span><\/h3>\n\n\n\n

A plain count of open deals tells you how much one person is carrying. When it climbs and nothing is closing, some of those deals are probably dead and nobody has said so. Our guide to sales pipeline management<\/a> covers how to close them out.<\/p>\n\n\n\n

<\/span>4. Pipeline value<\/span><\/h3>\n\n\n\n

Add up the open deals in your sales pipeline<\/a> and you get the size of what’s open. Check it once a week and look at the direction, because a single large deal can make any one reading look better than it is.<\/p>\n\n\n\n

<\/span>5. Value by stage<\/span><\/h3>\n\n\n\n

One bar chart is worth keeping. If most of the money sits in Proposal, your problem is getting answers on proposals you’ve sent, and finding more leads won’t change that.<\/p>\n\n\n\n

<\/span>What to Leave Off a Small Team’s Sales Dashboard<\/span><\/h2>\n\n\n\n

Most widgets on a typical sales dashboard are useful somewhere, just not on the screen a small team opens first.<\/p>\n\n\n\n

Widget<\/th>Why a small team can drop it<\/th>Where it goes instead<\/th><\/tr><\/thead>
Rep leaderboard<\/td>With three sellers, everyone already knows who closed what<\/td>Nowhere, until the team is bigger<\/td><\/tr>
Calls and emails sent<\/td>Counts effort, and rewards busywork when it’s on show<\/td>A one-off check if a seller’s results drop<\/td><\/tr>
Win rate gauge<\/td>On 8 closed deals, one deal going the other way moves 50% to 62.5%<\/td>The monthly review<\/td><\/tr>
Revenue forecast chart<\/td>Barely changes from one day to the next<\/td>A monthly look<\/td><\/tr>
Lead source pie<\/td>Tells you nothing about today<\/td>Your marketing review each quarter<\/td><\/tr>
Quota gauge<\/td>You know your target and roughly where you stand<\/td>Your written report<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The forecast matters most of these, because it decides hiring and cash. It needs its own method, which I cover in sales forecasting for small teams<\/a>, and an hour once a month rather than a glance every morning.<\/p>\n\n\n\n

If your team grows to eight or more and a bit of competition would help, a free sales leaderboard<\/a> does that job without changing your CRM.<\/p>\n\n\n\n

<\/span>How many metrics a sales dashboard should have<\/span><\/h3>\n\n\n\n

Five is enough for a team under 10. HubSpot’s guide says five to seven for a first dashboard and Close says 6 to 10 data points at most. I’d stay at five, because on a team that size you can ask about anything else.<\/p>\n\n\n\n

<\/span>CRM Dashboard Examples for Three Small Teams<\/span><\/h2>\n\n\n\n

A small team needs far fewer dashboard types than most lists show. The table sorts the common ones by whether a team under 10 would use them, and the three examples after it show the screen that’s left.<\/p>\n\n\n\n

<\/span>Sales dashboard types by role<\/span><\/h3>\n\n\n\n
Dashboard type<\/th>What it shows<\/th>Does a team under 10 need it?<\/th><\/tr><\/thead>
Sales pipeline dashboard<\/td>Deals and value by stage<\/td>Yes, and it’s the base of everything else here<\/td><\/tr>
Sales rep dashboard<\/td>One seller’s deals and due work<\/td>Yes, in the form of each person’s own overdue and due-today list<\/td><\/tr>
Sales activity dashboard<\/td>Calls, emails and meetings per person<\/td>No, unless you are coaching a new hire<\/td><\/tr>
Sales manager dashboard<\/td>Team results against target<\/td>Rarely, since a 15-minute weekly talk covers it<\/td><\/tr>
Executive dashboard<\/td>Revenue trend and targets for leadership<\/td>No, your leadership is reading this<\/td><\/tr>
Sales leaderboard<\/td>Sellers ranked on one number<\/td>Not below about eight sellers<\/td><\/tr>
Sales forecast dashboard<\/td>Expected revenue by month<\/td>Monthly, not on the daily screen<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The examples below use made-up numbers. They show what a good screen looks like on a Monday and what the person does in the next hour. For whole CRM setups rather than single screens, see these CRM examples<\/a>.<\/p>\n\n\n\n

<\/span>Example 1: solo founder with 14 open deals<\/span><\/h3>\n\n\n\n
Number<\/th>Monday morning<\/th><\/tr><\/thead>
Overdue<\/td>2<\/td><\/tr>
Due today<\/td>3<\/td><\/tr>
Active deals<\/td>14<\/td><\/tr>
Pipeline value<\/td>$46,000<\/td><\/tr>
Largest stage by value<\/td>Proposal, $27,000 across 5 deals<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The founder makes the two overdue calls first, then the three due today. Five open proposals account for more than half the money, so the rest of the morning goes to chasing answers on them rather than writing new outreach.<\/p>\n\n\n\n

<\/span>Example 2: owner plus one salesperson<\/span><\/h3>\n\n\n\n
Number<\/th>Owner<\/th>Salesperson<\/th><\/tr><\/thead>
Overdue<\/td>1<\/td>4<\/td><\/tr>
Due today<\/td>2<\/td>6<\/td><\/tr>
Active deals (shared)<\/td>31<\/td>31<\/td><\/tr>
Pipeline value (shared)<\/td>$118,000<\/td>$118,000<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Each person works from their own two numbers and shares the last two. The owner doesn’t need a report on the salesperson. A quick “what’s behind those four?” over coffee does more than any chart, because it gets the reason along with the count.<\/p>\n\n\n\n

Tim Chorlton, a Fluid CRM customer who isn’t the person in this example, runs a real version of this setup. He handles his own enquiries while an outside salesperson sells, and he says he has used hundreds of sales CRMs and kept going back to spreadsheets.<\/p>\n\n\n\n

He called what he wanted a CRM that is “low touch but highly flexible”<\/em>, and a two-person dashboard should meet the same bar. If it takes setup and upkeep, you’re back in the spreadsheet by next quarter.<\/p>\n\n\n\n

<\/span>Example 3: four-person agency<\/span><\/h3>\n\n\n\n
Number<\/th>One seller’s Monday<\/th><\/tr><\/thead>
Overdue (own deals)<\/td>3<\/td><\/tr>
Due today (own deals)<\/td>4<\/td><\/tr>
Active deals (team)<\/td>52<\/td><\/tr>
Pipeline value (team)<\/td>$310,000<\/td><\/tr>
Largest stage by value (team)<\/td>Proposal, $190,000 across 19 deals<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Each seller clears their own list. The owner looks at the team numbers and sees that more than half the money is waiting on proposals, so this week’s sales meeting has one topic.<\/p>\n\n\n\n

Nobody in this example needed a chart of emails sent. The owner found the problem from one stage number and can get the rest by asking.<\/p>\n\n\n\n

<\/span>How to Build a Sales Dashboard in Five Steps<\/span><\/h2>\n\n\n\n

Building a sales dashboard takes less time than choosing what goes on it, so do these steps in order and pick your numbers before you connect anything.<\/p>\n\n\n\n

<\/span>Step 1: write down the question<\/span><\/h3>\n\n\n\n

For a small team, that question is usually “who do I need to talk to today, and is there enough in the pipeline for next month?” If a number doesn’t help answer it, leave it off.<\/p>\n\n\n\n

<\/span>Step 2: pick five numbers at most<\/span><\/h3>\n\n\n\n

Start from the table earlier in this post and swap only when your sales process gives you a real reason. A team with one-call closes might care less about stages, while a team with six-month deals will watch them closely.<\/p>\n\n\n\n

<\/span>Step 3: connect a source<\/span><\/h3>\n\n\n\n

You have three options, and I’d take them in this order.<\/p>\n\n\n\n