John Serra – Backend

Tag: Business Intelligence

  • How Much Should a Small Business Spend on Data Tools

    Start with the data tools already included in your office software, and spend more only when a specific reporting problem justifies the added cost. If you use Google Workspace, Sheets and the no-cost version of Looker Studio can cover basic reporting without another software subscription. If you use Microsoft 365, Excel and the free Power BI Desktop can cover local analysis; sharing through the Power BI service usually requires licenses. Pay for more when the likely benefit exceeds the full cost of the change: hours of manual data work every month, reports that arrive too late to act on, or people working from conflicting versions of the same file.

    The rest of this article covers what each level of spending buys and how to tell when you’ve outgrown the level you’re on.

    Why Vendors and Small Businesses See This Differently

    Much of the advice about data tools comes from companies that sell them, and it’s written with larger businesses in mind. A typical recommended setup has four parts: a data warehouse to store everything, a pipeline tool to copy data into it automatically, a transformation layer to clean it, and a business intelligence (BI) tool to show it. Each is billed separately, and the setup needs someone who knows how to run it.

    For a company with large data volumes and a data team, that setup may make sense. A 15-person business should first check whether its existing reports have clear owners, consistent definitions, and a decision attached to each number. New software alone will not establish those habits. A business that pays for a sophisticated stack before sorting them out gets the same unclear numbers, faster and at greater cost.

    The software is also only part of the cost. Setting it up, connecting it to your systems, and keeping it running takes someone’s time, whether that’s yours, an employee’s, or a consultant’s. How much a small business dashboard costs covers the build side.

    Level 1: No Added Cost

    My view is that small businesses should stay at this level as long as possible, and that the right tools depend on which office software you already use.

    If you use Google Workspace

    • Google Sheets holds and shapes the data. Pivot tables, QUERY, and IMPORTRANGE can cover many reporting tasks. Google sets a 10 million-cell file limit, though a practical workbook may become slow well before that limit.
    • Looker Studio turns the sheets into dashboards and shares them with a link. It connects directly to Sheets, Google Analytics, and other Google products, and the standard version is free. Looker Studio Pro adds organizational ownership, team workspaces, and support for teams that need those controls.

    If you use Microsoft 365

    • Excel holds the data, and Power Query, built into Excel, cleans and combines exports from different systems and repeats those steps each month with a refresh.
    • Power BI Desktop is free and builds full dashboards on your computer. Sharing them with others online through the Power BI service requires a paid license for the people publishing and viewing, typically Power BI Pro.

    What this level covers

    With either setup, a business can keep a monthly scorecard, combine exports from its accounting, sales, and operations systems, and build useful reports. Sharing options differ: Looker Studio can share online, while Power BI Desktop reports stay local unless the business uses an appropriate Power BI sharing license or capacity. The work may still include exporting data from each system and updating the spreadsheet each month. Track the time and errors in that routine before deciding whether automation would pay for itself.

    Before spending on anything, take stock of what your systems already give you. The business data you already have covers where to look.

    Level 2: Paying for Specific Gaps

    The first paid step isn’t a new platform. It’s paying for the one or two things your free setup can’t do. Three are common.

    Sharing licenses. In the Microsoft setup, publishers and viewers of shared Power BI reports generally need a Pro license: $14 per user per month as of September 2026, paid yearly. Microsoft 365 E5 and Office 365 E5 include Pro. Large Premium or Fabric capacity can allow free viewers, so check your licensing setup before buying separately.

    Automated connectors. Tools like Coupler.io and Supermetrics copy data from your accounting system, CRM, ad accounts, or e-commerce platform into Sheets, Excel, or a BI tool on a schedule, so nobody has to export it by hand. Pricing usually depends on the number of sources, accounts, and how often the data refreshes. Check current plans before comparing.

    Alerts and scheduled delivery. Automatic emails when a number crosses a threshold, or a report sent every Monday morning. Some of this is free with scripts or built-in features; paid tools make it easier to set up and maintain.

    Consider a made-up example. A 12-person firm on Microsoft 365 has five people who need to view shared dashboards. Five Power BI Pro licenses at $14 each come to $70 a month. It adds one connector to pull accounting data automatically, at a hypothetical $60 a month. Total: $130 a month. If it saves six hours of work each month, compare the value of those hours and the cost of setup and upkeep with the $130 fee. If the reports go unread, it’s $1,560 a year for nothing.

    That last point is the real test at this level. A paid tool is worth it when it solves a problem you can name and measure. It’s a waste when it’s bought in the hope that having better software will make people use the numbers.

    Level 3: A Full Data Platform

    At the top end is the setup vendors often lead with: a cloud data warehouse, automated pipelines from every system, a transformation layer, and a BI platform with detailed permissions. Software costs scale with data volume and users, and the larger cost is the person who builds and maintains it.

    It’s justified when:

    • Data volume outgrows spreadsheets. Transaction, sensor, or event data that no longer performs reliably in the current spreadsheet workflow.
    • Access needs to be controlled row by row. Different managers, locations, or clients should see only their own data, and a shared spreadsheet can’t enforce that.
    • Many systems need to be combined continuously. Not once a month, but daily or hourly.
    • Someone is there to run it. A data analyst or engineer on staff, or a committed outside partner. Without that person, the platform decays: pipelines break, definitions drift, and people go back to their own spreadsheets.

    Adopting this level early is expensive twice over: the subscriptions, and the time and attention taken from sales, delivery, and the rest of the business.

    How to Tell Whether a Tool Is Worth It

    Judge tool spending by what it lets you do, not as a percentage of revenue. Three questions work at any level:

    1. What problem does it solve? Name it. "Our month-end report takes three days to assemble" is a problem. "We should be more data-driven" isn’t.
    2. What does the problem cost now? Hours of staff time, late decisions, errors caught too late, customers or cash lost to something nobody noticed.
    3. Will anyone use the result? A tool that produces reports nobody reads costs its full price and saves nothing. Keep reporting focused on four to seven metrics that each lead to a decision, and the tool has a job to do.

    Compare the value of the improvement with the full cost: licenses, setup, maintenance, and staff time. Test a small purchase first when those numbers are uncertain.

    Signs It’s Time to Spend More

    Stay where you are if:

    • Monthly exports and updates are manageable.
    • The people who need reports can get them from shared files or free dashboard links.
    • You haven’t yet used what your office suite includes. Power Query, pivot tables, and Looker Studio go a long way.

    Consider paying for specific tools if:

    • Reports arrive so long after month end that the numbers are too late to act on.
    • Several people edit the same file and overwrite each other’s work, or keep private copies that disagree.
    • The same exports are copied by hand every week, and mistakes creep in.
    • People who need to see reports can’t, because your free setup can’t share them the way you need.

    Consider a full platform if:

    • The data won’t fit in spreadsheets, access needs row-level control, or systems must be combined continuously, and you have someone to run it.

    Keep a record of slow reports, version conflicts, and repeated manual work. Those observations will make the next software decision easier.

    Frequently Asked Questions

    Is Looker Studio really free?

    The standard version is free to build and share reports. Costs can come from paid third-party connectors for non-Google data, or from Looker Studio Pro for organizational and team features.

    Is Power BI free?

    Power BI Desktop, which builds reports on your computer, is free. Publishing and sharing reports online generally requires a paid license for the people involved, such as Power BI Pro.

    Should a small business use Tableau?

    Tableau may be worth comparing when your team already knows it or has requirements your current tools cannot meet. Include its licensing, deployment, and maintenance costs in the comparison.

    What should a small business spend on data tools as a percentage of revenue?

    There isn’t a useful percentage. Spending should follow specific problems, and for many small businesses the right answer for a long time is nothing beyond what they already pay for their office software.

    What’s more important than the tool?

    Clear definitions, an owner for each number, a regular review, and a short list of metrics that lead to decisions. With those in place, a spreadsheet does a lot. Without them, no tool helps much.

  • A Monthly Reporting Pack Template for Small Business

    A monthly reporting pack for a small business fits in five pages: (1) a summary with your core metrics and what’s off track, (2) financial results against budget, (3) operations and team capacity, (4) sales pipeline and customers, and (5) risks and the decisions leadership needs to make. Keep the layout identical every month so the pack takes hours to produce rather than days, and put supporting detail in an appendix.

    Below is a copyable five-page outline, followed by the layout choices and a monthly production routine. Each page has one job. Fill in the placeholders with your own numbers and remove lines your business does not use. For what belongs on each page, in detail, see What to Include in a Monthly Business Report.

    Why Five Pages

    A monthly pack exists to help people decide what to do next. That means reporting what happened briefly, explaining the variances that matter, and giving the most attention to the choices ahead.

    Five pages is enough for that and short enough to be read before the meeting. Long packs get skimmed or skipped, and the page nobody reads is usually the one that mattered. The limit also forces a useful discipline: when something new wants in, something old has to come out.

    The other rule is sameness. The same pages, in the same order, with the same charts in the same places, every month. Readers learn where to look, and the person producing it copies last month’s file instead of starting over.

    Copy This Five-Page Template

    Each page below is shown as a fillable table. Use the same layout in a document or slide deck: start a new page or slide at each page heading, and keep the bracketed prompts until you have real numbers and decisions to replace them. The five pages are the main pack; supporting detail goes in the appendix.

    Prefer a ready-made file? Copy the template as a Google Doc — File > Make a copy, then fill in your own numbers.

    PAGE 1 — SUMMARY AND CORE METRICS

    Reporting month: [month/year]  |  Books closed: [date]  |  Cash at month end: [amount]

    Core metricActualTargetLast monthOn track / Watch / Off track
    [Metric 1]
    [Metric 2]
    [Add only the metrics needed, up to seven]
    Went wellOff track
    [two or three short results][miss, reason, and owner for each item]

    Main decision: [one sentence; see page 5]

    PAGE 2 — FINANCIAL RESULTS

    LineActualBudgetVariance ($)Variance (%)
    Revenue
    Direct costs
    Gross profit ($)
    Operating expenses
    Operating profit
    Gross marginactual [ ]%; budget [ ]%; variance [ ] percentage points
    Cashopening [ ]; in [ ]; out [ ]; closing [ ]
    Receivablestotal [ ]; past due over 60 days [ ]

    Largest variances: [what changed, why, and whether action is needed]

    PAGE 3 — OPERATIONS AND TEAM

    Output this month / last month / target[ ] / [ ] / [ ]
    Backlog this month / last month[ ] / [ ]
    Current bottleneck and response[ ]
    Quality or rework measure[ ]
    Team workload and capacity risk[ ]
    Headcount changes and open roles[ ]

    PAGE 4 — PIPELINE AND CUSTOMERS

    StageOpportunity countValueExpected timing
    Qualified
    Proposal out
    Won this month
    Pipeline for next quarter / revenue target[ ] / [ ]
    Win rate this month / trailing three months[ ] / [ ]
    Customers gained / lost / active, or repeat purchase rate[ ]

    PAGE 5 — RISKS AND DECISIONS

    Quarterly priorityStatusWhat changedOwner
    [Priority]On track / At risk / Delayed
    Risk or blockerImpactOwnerNext check date
    [Risk]
    DecisionContext and company-specific costRecommendationDecision makerDue date
    [Decision]

    Use the same metric definitions and reporting periods each month. Before sending the pack, check that a figure repeated on two pages matches and that every requested decision has a named decision maker and date.

    Page 1: Summary and Core Metrics

    If someone reads only one page, this is it. It should tell them whether the business is on track and what needs their attention.

    Layout, top to bottom:

    • Header line: the month, the date the books closed, cash at month end.
    • Scorecard table: your four to seven core metrics. One row each, with columns for actual, target, last month, and status. My rule is four to seven, depending on the business, with no vanity metrics.
    • Two short lists side by side: “Went well” and “Off track,” two or three bullets each, one line per bullet.
    • One box at the bottom: the most important decision this month, in one sentence, with a pointer to page 5.

    Here’s what that scorecard might look like for a small services firm, with made-up numbers:

    MetricActualTargetLast monthStatus
    Revenue$168,000$180,000$174,000Off track
    Gross margin41%40%39%On track
    Billable utilization72%75%74%Watch
    Receivables over 60 days$9,500Under $10,000$14,000On track
    Qualified pipeline$410,000$450,000$395,000Watch

    Use words, not only colors, for status. Red and green are hard to tell apart for some readers, and printed packs often end up in black and white.

    The sample statuses are illustrative. Set your own watch and off-track thresholds before using the template, and keep their definitions in the appendix.

    If you keep a monthly scorecard in a spreadsheet, this table is a copy of it. How to build a monthly KPI scorecard shows how to set that up so the numbers carry over each month without retyping.

    Page 2: Financial Results Against Budget

    Every financial number sits next to what you expected.

    Layout:

    • Summary income statement, four numeric columns: actual, budget, variance in dollars, variance in percent. Rows: revenue (split by main business line if you have more than one), direct costs, gross profit, operating expenses, operating profit. Show gross margin as a separate percentage and its variance in percentage points.
    • Cash block: starting cash, cash in, cash out, ending cash. If cash is falling, estimate months of cash remaining at the recent average monthly net cash outflow.
    • Receivables line: total owed, and how much is more than 60 days late.
    • Variance notes: two or three bullets, each explaining one of the largest differences from budget in a sentence.

    One chart, at most: revenue by month for the past twelve months against budget. Twelve months shows seasonality, which a single month hides.

    Keep this page to summary lines. The full income statement, balance sheet, and ledger detail go in the appendix, where anyone who wants them can find them.

    Page 3: Operations and Team

    This page shows whether the business can deliver the work it’s selling. It combines two sections that are often split: operations and team capacity. In a small business they’re usually the same question, since the team is the capacity.

    Layout:

    • Output trend: one chart showing your main measure of delivered work (jobs completed, orders shipped, hours billed) over twelve months.
    • Backlog: committed work not yet delivered, with last month’s figure for comparison.
    • Bottleneck: one sentence naming what’s currently limiting delivery, and what’s being done about it.
    • Quality: one or two measures of rework, errors, or complaints.
    • Team: workload (utilization, overtime, or open work per person), people who joined or left, open roles, and any capacity risk worth naming.

    This page varies most between businesses. A manufacturer tracks throughput and scrap; a consultancy tracks utilization and project backlog; a service company tracks jobs per crew and callbacks. Pick the few measures that tell you whether operations can support next quarter’s plan, and keep them the same from month to month.

    Page 4: Pipeline and Customers

    In a business with a longer sales cycle, this month’s revenue often reflects work sold earlier. This page shows what may be coming next, alongside the timing and size of future revenue targets.

    Layout:

    • Pipeline by stage, as a short table or a simple bar chart: inquiries, qualified opportunities, proposals out, won this month. Show counts and values.
    • Pipeline against target: qualified or weighted pipeline value next to next quarter’s revenue target.
    • Win rate: proposals won as a share of proposals decided, this month and over the trailing three months (monthly win rates swing a lot when the numbers are small).
    • Customers: new, lost, and total active; or, for businesses that depend on repeat purchases, the share of customers who bought again.

    Avoid funnel graphics that look impressive but hide the numbers. A four-row table is easier to read and compare month to month.

    Page 5: Risks and Decisions

    The pack ends with what needs to happen next.

    Layout:

    • Priorities status: the three to five things the business committed to this quarter, each marked on track, at risk, or delayed, with a line of explanation for anything not on track.
    • Risks and blockers: a short list, each with a named owner.
    • Decisions table:
    DecisionContext and costRecommendationWho decidesBy when
    Hire a second project managerBacklog grew for three months; the current manager handles 14 projects against the team’s agreed capacity of 10. Cost: [company estimate]/monthApprove; post the role this monthOwnerOct 15

    Put the recommendation in the table. A decision presented without one tends to get deferred.

    This page sets up the meeting. What makes a reporting conversation useful is an action-oriented discussion about what the numbers mean, who will act on them, and by when. Every row here should leave the meeting with a decision or a date for one.

    The Appendix

    Everything that supports the five pages but doesn’t need to be read by everyone:

    • Full financial statements
    • Detailed receivables aging
    • Department or location breakdowns
    • Project or customer lists
    • Definitions of each metric and where its data comes from

    The definitions page is worth writing once. When someone asks why this month’s utilization differs from another report’s, the answer is already there.

    How to Produce It Each Month

    The goal is to produce the pack in a few hours rather than a few days. That comes from setting up once and repeating the same steps.

    Set up once:

    1. Build the five pages as a template, with every table and chart in place.
    2. Write down where each number comes from: which report, which system, which filter.
    3. Link the scorecard and charts to a spreadsheet where possible, so updating the data updates the pages.
    4. Assign an owner for each page’s numbers and notes.

    Each month:

    1. Close: the books close and the source reports are exported.
    2. Update: paste or refresh the data. The scorecard and charts update from it.
    3. Explain: each page owner writes the variance notes for their page. Keep it to a sentence or two per variance.
    4. Review: one person reads the whole pack for consistency, such as matching numbers on pages 1 and 2 and clear decisions on page 5.
    5. Send: distribute it at least a day before the meeting.

    Save each month’s pack as a separate, dated file. The history is useful, and nobody has to wonder whether the numbers they’re looking at have changed since the meeting.

    Slides or a Document?

    Either works. Choose by how the pack is used.

    • Slides (Google Slides, PowerPoint) suit a pack that’s presented in a meeting and read on a screen. Each page becomes one widescreen slide. The constraint is space: if a page doesn’t fit on one slide, it has too much on it.
    • A document (Google Docs, Word, a PDF) suits a pack that’s read in advance, printed, or sent to a lender or investor. It holds variance notes and tables more comfortably.

    Whichever you choose, send it in advance and expect people to have read it. The meeting then spends its time on the off-track items and the decisions rather than on reading. How to get your team to actually use your reports covers the meeting itself, including a short note each owner of an off-track metric brings.

    Monthly Reporting Pack Checklist

    • Five pages, in the same order every month
    • Page 1: header, four to seven metrics with target and status, went well / off track, main decision
    • Page 2: summary income statement against budget, cash, receivables, variance notes
    • Page 3: output, backlog, bottleneck, quality, team
    • Page 4: pipeline by stage, pipeline against target, win rate, customers
    • Page 5: priorities status, risks with owners, decisions table with recommendations
    • Appendix: statements, detail, and metric definitions
    • Sent at least a day before the meeting

    Frequently Asked Questions

    What’s the difference between a reporting pack and a dashboard?

    A dashboard is live and checked whenever someone wants to. A reporting pack is a fixed monthly snapshot with explanations and decisions. Many businesses use both: the dashboard for day-to-day checks, the pack for the monthly review.

    Can a very small business use a shorter version?

    Yes. A business with a handful of people can often fit pages 1 and 5 on one page and pages 2 through 4 on another. Keep the same order and the same sections.

    Should lenders or investors get the same pack?

    Usually a shorter version: pages 1, 2, and 5, with the appendix available on request. Internal operating detail rarely helps them and can raise questions without context.

    How long should the pack take to produce?

    Once the template and data sources are set up, much of the work is updating numbers and writing short notes. The first few months take longer while you settle the definitions.

  • What to Include in a Monthly Business Report

    A monthly business report should cover six things: a summary with your four to seven core metrics, financial results against budget, operations and capacity, sales pipeline and customers, team capacity, and the decisions leadership needs to make. Each number needs a target or a comparison, and each off-track number needs a short explanation. Everything else, including detailed ledgers and metrics nobody acts on, belongs in an appendix or nowhere.

    The checklist below goes section by section. At the end is a cut list: what to take out.

    What a Monthly Report Is For

    A monthly report answers three questions for the people running the business:

    1. Did we hit our targets?
    2. If not, why not?
    3. What do we need to decide or do next?

    Anything that doesn’t help answer one of those three is a candidate for cutting. Length is a design decision, not a sign of thoroughness. A 30-page pack gets skimmed, and the one number that needed attention gets lost among the ones that didn’t.

    The report also isn’t your accounting package. Financial statements tell you what happened. A useful monthly report adds what’s coming: the pipeline, the capacity, and the choices that need to be made while there’s still time to make them.

    1. The Summary and Core Metrics

    The first page should tell the whole story of the month. If someone reads only this page, they should know whether the business is on track and what needs their attention.

    Include:

    • The period and the basics. Which month, when the books closed, and your cash balance at month end.
    • Your core metrics. My rule is four to seven, depending on the business, and no vanity metrics: each one has to move the needle. Show each with its actual value, its target, and a status (on track, watch, or off track). How many KPIs a small business should track covers choosing them.
    • What went well. Two or three results worth knowing about, stated plainly.
    • What’s off track. The metrics that missed, with a one-line reason for each. Be as direct about misses as about wins; a summary that only reports good news stops being trusted.
    • The main decision. The single most important choice leadership faces this month, if there is one.

    If you already keep a monthly scorecard, this page is mostly a copy of it. How to build a monthly KPI scorecard shows how to set one up in a spreadsheet.

    2. Financial Results Against Budget

    A financial number on its own doesn’t tell you much. $180,000 in revenue is good or bad depending on what you expected. Show every financial line next to a target and a comparison.

    Include:

    • Revenue: actual, budget, and the difference, split by your main lines of business if you have more than one.
    • Gross margin: revenue minus the direct cost of delivering it, as dollars and as a percentage. For a service business, direct costs are mostly the labor that does the work.
    • Operating expenses: the overhead, with any line that moved noticeably called out.
    • Operating profit (or net income, if that’s what your books report).
    • Cash: cash in, cash out, and the ending balance. If cash is falling, estimate how many months the current balance would last at the recent average monthly net cash outflow.
    • Receivables: how much customers owe you, and how much of it is late. Revenue that hasn’t been collected isn’t cash yet.

    Add one or two sentences explaining the biggest variance. “Revenue was $12,000 under budget because two projects slipped into next month” is more useful than another table.

    Here’s what that might look like, with made-up numbers:

    LineActualBudgetVariance
    Revenue$168,000$180,000−$12,000 (−6.7%)
    Gross margin41%40%+1 point
    Operating expenses$52,000$50,000+$2,000 (+4.0%)

    Percentages and percentage points are different things. Revenue that falls 6.7% below budget is a percentage; a margin that goes from 40% to 41% has moved one percentage point. Label them so nobody confuses the two.

    3. Operations and Capacity

    Financials show the result. Operating metrics show how well the business is producing it, and they usually move first.

    Include what fits your business:

    • Output: the main measure of work delivered, such as jobs completed, orders shipped, hours billed, or tickets closed.
    • The bottleneck: the one step, team, or resource currently limiting how much you can deliver. Name it. If the answer changed since last month, say so.
    • Backlog: committed work that hasn’t been delivered yet, and whether it’s growing or shrinking.
    • Quality: rework, errors, returns, or complaints. Whatever you track that shows work having to be done twice.

    Keep it to the few measures that tell you whether operations can support the revenue you’re planning. A manufacturer, a consultancy, and a cleaning company will fill this section very differently, and they should.

    4. Sales Pipeline and Customers

    In businesses with longer sales cycles, this month’s revenue often reflects work sold earlier. The pipeline shows what may be coming next; compare it with the timing and size of future revenue targets.

    Include:

    • Qualified opportunities: how many, and their total value. If you estimate the chance of winning each, show the weighted value too.
    • Win rate: of the proposals decided this month, how many you won.
    • Sales cycle: roughly how long it takes from first contact to a signed agreement, if you track it.
    • New and lost customers: how many started and how many left, or, for repeat businesses, the share of customers who bought again.

    A pipeline that looks thin next to next quarter’s revenue target is the kind of early warning a monthly report exists to give.

    5. Team Capacity

    For most small businesses, people are the highest cost and the main limit on growth.

    Include:

    • Workload: whether the team is running at a sustainable level. For a service business, that’s often utilization (billable hours as a share of available hours). For others, it may be overtime, open work per person, or a simple manager’s assessment.
    • Headcount changes: people who joined or left, and open roles.
    • Capacity risks: a key person leaving, a team stretched thin before a busy season, a skill only one person has.

    This section is often left out, and it’s where hiring decisions should start. A team running over capacity for three months is a decision waiting to be made.

    6. Risks, Blockers, and Decisions

    End the report with what needs to happen next. A report that closes on numbers leaves the next step to chance.

    Include:

    • Risks: a large contract up for renewal, a supplier problem, a regulatory change, a customer that accounts for too much revenue.
    • Blockers: anything internal that’s stopping progress, such as a system problem, a missing approval, or two teams waiting on each other.
    • Decisions needed: a short table. Each row is one decision, the options, a recommendation, who decides, and by when.

    When I think about what makes a reporting conversation useful, it’s an action-oriented discussion about what the numbers mean, who will act on them, and by when. This section is where the report sets that conversation up. How to get your team to actually use your reports covers running the meeting, including a short off-track note each metric owner brings.

    What to Leave Out

    A good report is defined as much by what isn’t in it. When deciding whether a metric earns a place, I check whether it helps the business make more revenue, run more efficiently, or cut costs. If the honest answer is no, it goes.

    Take out:

    • Detailed ledgers and trial balances. Your accountant needs them. The leadership team needs the summary. Put them in an appendix if someone asks.
    • Vanity metrics. Social followers, impressions, and website traffic with no link to inquiries. They go up and down without anyone needing to act.
    • Numbers without context. A metric with no target, no prior period, and no trend can’t tell anyone whether to worry.
    • Every metric you can produce. If a number has sat on the report for six months without anyone acting on it, remove it and see whether anyone notices.
    • Unsettled arguments. Work out disagreements about what a number means before the report goes out, not in the margins of it.
    • Long narrative. One or two sentences per variance. If the explanation needs a page, it needs a separate conversation.

    Removing things is harder than adding them, because everything on the report was once someone’s good idea. Review the contents every quarter and cut anything that hasn’t earned its place.

    Monthly Business Report Checklist

    • A one-page summary with four to seven core metrics, each with a target and status
    • Wins and misses, stated plainly
    • Revenue, gross margin, operating expenses, and profit against budget
    • Cash position and receivables
    • A sentence or two on the largest variance
    • Output, bottleneck, backlog, and quality
    • Pipeline, win rate, and customers gained and lost
    • Team workload, headcount changes, and capacity risks
    • Risks, blockers, and a decisions table with owners and dates
    • Nothing without a target or comparison; no vanity metrics

    Frequently Asked Questions

    How long should a monthly business report be?

    Short enough that people read it before the meeting. A five-page starting point is a summary, financials, operations and team capacity together, pipeline and customers, then risks and decisions. Add detail only where the reader needs it to make a decision.

    Who should get the monthly report?

    The people who make decisions from it: owners, partners, and department leads. Lenders and investors often need a shorter version focused on financial results, cash, and risks.

    When should the monthly report go out?

    As soon after month end as the numbers are reliable. The later it arrives, the less time there is to act on it. If closing the books takes weeks, send the operating and pipeline sections early and follow with the financials.

    Should the report include forecasts?

    A short outlook helps: expected revenue for the next month or quarter, based on the pipeline and backlog. Label it as an estimate and compare it with what actually happened the following month.

    What’s the difference between a monthly report and a dashboard?

    A dashboard is something people check whenever they want. A monthly report is a fixed snapshot with explanations, sent at a set time, so decisions are made from the same numbers.

  • How Many Charts Should a Dashboard Have?

    There is no fixed number. The practical limit is the screen: a dashboard should fit on one laptop screen without scrolling and tell someone within a few seconds whether the business is on track. That usually means a row of number cards for your core metrics across the top, a few charts beneath them showing the trends behind those numbers, and a small breakdown or two at the bottom. Anything that doesn’t fit belongs on a second page.

    The better question is what each chart is for. A chart earns its place when someone looks at it regularly to make a decision and needs the shape of the data, not just the number. Start from those questions and the count takes care of itself.

    Why Does a Dashboard Need a Limit at All?

    A dashboard exists to be read quickly. Stephen Few, whose Information Dashboard Design is widely cited on the subject, defines a dashboard as the most important information needed to meet one or more objectives, arranged on a single screen so it can be monitored at a glance. Both parts of that definition limit the chart count: “most important” and “at a glance.”

    Every chart you add competes with the others for the reader’s attention. With three charts, a line that turns sharply down stands out. With fifteen, it looks like one more shape among many, and the reader has to search for it. The screen also runs out of room. Charts shrunk to fit lose their labels and axes, and a chart nobody can read hasn’t been included in any useful sense.

    Scrolling is the clearest warning sign. Once the dashboard runs below the fold, the reader can no longer see the headline numbers and the charts behind them at the same time. Anything below the fold is easy to miss.

    How Do You Decide How Many Charts You Need?

    Count Cards and Charts Separately

    A card shows one number: this month’s revenue, cash on hand, jobs completed. Add the target and last period’s value beside it, and a card answers “are we on track?” in a single glance.

    A chart shows a shape: how a number moved over time, or how it splits across categories. It answers “since when?” or “where is it concentrated?” A chart can show when a change started and which part of the business it sits in. Working out why it happened still takes someone who knows the business.

    Most of the confusion about chart count comes from treating these as the same thing. The cards carry your core metrics. My rule of thumb, depending on the business, is four to seven metrics, and no vanity metrics; each one has to move the needle. How Many KPIs Should a Small Business Track? covers how to choose them. Charts are a separate decision, and there should usually be fewer of them than cards.

    Give Each Chart a Question

    For every chart you’re considering, write the question it answers and who asks it. For example:

    • Is revenue running ahead of or behind last year, month by month?
    • Is weekly capacity keeping up with booked work?
    • Which customers owe us money, and how overdue is it?
    • Where are deals stalling in the pipeline?

    If you can’t write the question, the chart probably doesn’t belong on the main screen. If two charts answer the same question, keep the clearer one. If the answer is fully captured by a single number, use a card instead.

    Let the Screen Set the Ceiling

    Once you have a list of charts with real questions behind them, lay them out on the actual screen your team uses. On a typical laptop, a row of cards plus two rows of two or three charts at a readable size is often about as much as fits. Treat that as a starting estimate, not a rule. The real capacity depends on the viewport and browser zoom, how much room filters and labels take, and how complex each chart is. A simple line chart needs less room than a labeled breakdown. A larger monitor in a shared office fits more; a phone fits much less. Check on the screen your team actually uses.

    If the charts don’t fit, don’t shrink them. Move the lower-priority ones to a second page.

    What Should Go Where on the Screen?

    A simple three-part layout works for most business dashboards. Put the most important information at the top, where it is visible the moment the page opens.

    Top: The Headline Numbers

    A single row of cards across the top of the screen. Each card shows the current value, the target, and the change from the last period. This row should answer the main question, whether the business is on track, before the reader looks at anything else.

    Keep the cards in a consistent order, such as money first, then operations, then customers. If a card is out of range, color can flag it, but keep the rest of the screen in neutral tones so the color means something.

    Middle: The Trends

    The largest area goes to the charts that show how the headline numbers have moved over time. A typical small-business set might include:

    • A line chart of revenue or cash over the last twelve months, against target or last year.
    • A bar chart of weekly throughput: jobs completed, hours billed, or orders shipped.

    Each trend chart should connect to a card above it. If a trend chart doesn’t relate to any headline number, ask whether it belongs on this page.

    Bottom: The Breakdowns

    The bottom holds charts that split a number into parts, so the reader can see which part of the business a change sits in. Examples include receivables by age, sales by product line, or deals by pipeline stage. These are usually the first candidates for a second page if space runs short.

    Which Chart Types Work Best?

    A small set of chart types handles most everyday business questions. Using the same few types across the dashboard also makes it faster to read, because nobody has to work out how each chart works.

    Line Charts for Change Over Time

    Use a line chart when the question is about direction: up, down, flat, seasonal. Months or weeks run left to right. Two lines, such as this year and last year, are easy to compare. Each line you add after that makes the chart harder to read.

    Column Charts for Comparing Periods or Groups

    Vertical bars work well for comparing a small number of periods or categories, such as sales by month or jobs by team. Start the value axis at zero, because bar length is what the reader compares.

    Horizontal Bar Charts for Rankings

    When the categories have long names, or you want them ranked, turn the bars sideways. Top customers by revenue, overdue invoices by client, and product lines by margin all read well this way. Sort from largest to smallest.

    Sparklines Inside Cards

    A sparkline is a small, word-sized line chart without axes, a term introduced by Edward Tufte. Placed inside a card, it shows the recent direction of a number without taking up a chart’s worth of space. Sparklines are one of the easiest ways to show more trend information without adding charts.

    Tables, Sparingly

    A short table works for a specific list someone needs to act on, such as the five most overdue invoices. A long table of raw data belongs elsewhere. 7 Dashboard Mistakes Small Businesses Make covers raw tables on the main screen along with other common layout problems.

    Which Charts Should You Avoid?

    Some chart types take up a lot of space or make comparisons harder than they need to be.

    • Gauges and speedometer dials. A dial uses a large area to show one value. A card with the value, target, and prior period shows more in less room.
    • Pie charts with many slices. Comparing angles is harder than comparing lengths. A pie with two or three slices can work; beyond that, a sorted horizontal bar chart is easier to read.
    • 3D effects. Perspective distorts the size of bars and slices, so the chart misrepresents the numbers it shows.
    • Decoration. Heavy gridlines, background images, shadows, and gradient fills add nothing to the data. Tufte called this kind of non-data ink “chartjunk.” Remove it, and the numbers get easier to see.
    • Novel chart types for their own sake. Radar charts, bubble charts, and other less familiar types have legitimate uses, but on a dashboard for a general business audience, they usually take longer to read than a bar or line chart showing the same thing.

    A chart doesn’t need to look impressive. It needs to be understood quickly by the person who uses it.

    When Should a Dashboard Have More Than One Page?

    When the charts that pass the question test don’t fit on one screen, split the dashboard by audience or purpose instead of cramming everything in.

    A common structure for a small business:

    1. Overview. The headline cards and the few trend charts the owner or leadership team reviews. This page answers “are we on track?”
    2. Operations. Capacity, throughput, scheduling, and quality detail for the people running daily work.
    3. Finance. Receivables, cash timing, margin by product or service line, and the detail behind the money cards.

    Each page follows the same layout: cards at the top, trends in the middle, breakdowns at the bottom. Link the overview cards to the page with their detail, if your tool supports it. Looker Studio, Power BI, and Tableau all let you build more than one page or dashboard, and a spreadsheet can use separate tabs.

    The overview should stay stable. When someone asks for a new chart, the default home is a detail page. It moves to the overview only if it answers a question leadership asks regularly, and then something else should come off.

    How Do You Cut a Cluttered Dashboard Down?

    If you’re starting with a screen that already has fifteen charts:

    1. List every chart and card. Write the question each one answers and who uses it.
    2. Mark each one. Keep on the overview, move to a detail page, or delete. Duplicates and charts with no clear question are the first to go.
    3. Turn single numbers into cards. A chart whose only purpose is showing the current value can become a card, often with a sparkline.
    4. Rebuild the overview using the three-part layout, and check that it fits without scrolling on the screen your team actually uses.
    5. Ask the people who use it. Show the new version to two or three regular readers and ask what they’d look for first. If they can’t find it quickly, adjust.

    For a full renovation process that also covers data accuracy and ownership, see How to Improve a Business Dashboard You Already Have.

    Dashboard Chart Checklist

    • The overview fits on one screen without scrolling.
    • The top row holds four to seven cards, each with a target and prior-period comparison.
    • Every chart answers a written question that someone asks regularly.
    • No two charts answer the same question.
    • Trend charts relate to headline numbers.
    • Lines, columns, horizontal bars, sparklines, and short tables do most of the work; any other chart type is there for a reason.
    • No gauges, 3D effects, or decoration.
    • Anything that doesn’t fit lives on a clearly labeled detail page.

    Frequently Asked Questions

    Is there a standard maximum number of charts?
    No. Any fixed number would ignore the screen size, the audience, and how often the dashboard is used. The one-screen test and the question test are more reliable than a count.

    Should a spreadsheet scorecard have charts?
    Not necessarily. A monthly scorecard in rows and columns, with a status color for each metric, can do the job without any charts. How to Build a Monthly KPI Scorecard shows how to build one. Add a trend chart only if the team keeps asking how a number has moved.

    What about mobile?
    A phone screen fits far less, so don’t just shrink the desktop layout. If people will check the dashboard on their phones, build a mobile layout: the cards first, stacked vertically, then the one or two charts that matter most. On a phone, scrolling down is expected. Order the view so the most important items come first. Power BI and Tableau both let you design a separate phone layout.

    Does the tool matter?
    Less than the layout. Google Sheets, Excel, Looker Studio, Power BI, and Tableau can all produce a clean one-screen dashboard. A cluttered dashboard stays cluttered in any tool.

  • How to Build a Monthly KPI Scorecard

    Build it in the spreadsheet you already use. Put four to seven metrics on a Scorecard tab that shows, for the current month, the target, the actual, the variance, and a green, yellow, or red status. Keep the twelve-month history on a Trend tab, calculations on a Data tab, and each raw export on its own import tab. Start targets from your own recent history, and update the sheet the same way every month after the books close.

    That is the whole design. Most of the work is in the decisions behind each cell: which metrics earn a row, what counts as on target, and how the numbers get in without someone retyping them.

    What a Monthly Scorecard Is For

    A scorecard answers one question each month: is the business on track, and if not, where? It is not your accounting system and it is not a report. It is a single view that someone can read in a minute and act on.

    That purpose sets the rules:

    • Four to seven metrics. My rule of thumb, depending on the business, is four to seven, and no vanity metrics. Each one has to move the needle: when it changes, someone makes a decision. How Many KPIs Should a Small Business Track? covers how to choose them.
    • One screen. The Scorecard tab fits on a laptop screen without scrolling sideways. If it doesn’t, you have too many metrics or too many columns. The full history lives on another tab.
    • Metrics in rows, in the same order on every tab. Row 6 is the same metric on the Scorecard and the Trend tab, which keeps formulas simple to copy.
    • Every number has a comparison. A figure with no target beside it doesn’t tell anyone whether to act.

    Use Google Sheets if your business runs on Google Workspace, and Excel if it runs on Microsoft 365. My view is that a small business should stay with the tools it already pays for as long as they do the job, and a monthly scorecard is well within what either can do.

    Step 1: Choose the Rows

    Group the metrics so the sheet reads in a consistent order. A practical split for most small businesses:

    • Money (two or three rows): revenue, gross margin, operating cash flow.
    • Operations or capacity (one to three rows): billable utilization for a service firm, first-pass yield for a shop, jobs completed for a trade business.
    • Customers and pipeline (one or two rows): qualified pipeline value, on-time delivery, customer retention.

    Pick from these, don’t take all of them. If you already track seven metrics and want an eighth, one of the seven should go. For service-business examples with formulas, see KPIs for a Small Professional Services Firm.

    For each metric, write down four things before you build anything:

    • Definition, including where the number comes from.
    • Unit: dollars, percent, days, or count.
    • Direction: whether higher or lower is better. Revenue is better high. Days sales outstanding is better low. The sheet needs to know the difference, or it will color a collections problem green.
    • Type: a flow, a ratio, or a point-in-time figure. This decides how year-to-date is calculated in Step 3.

    Step 2: Lay Out the Tabs

    Build the workbook in layers, so the tab people read never touches raw data.

    Scorecard tab. This is what people read. A header block at the top holds the company name, the reporting month, the date last updated, and who updated it. Put the reporting month in its own cell (say, B2), because the formulas will use it. Below that, each metric gets one row:

    ColumnContents
    AMetric name
    BOwner
    CUnit ($, %, days, count)
    DDirection (higher or lower is better)
    EThis month’s target
    FThis month’s actual
    GVariance
    HStatus (green, yellow, red)
    IYear-to-date actual
    JYear-to-date target

    Ten columns fit on one screen. If a comparison with the same month last year matters in your business, add it after F, as long as the tab still fits.

    Trend tab. The same metric rows, with January through December in columns C through N and the month names in row 5. This is where people look when they want to know whether this month is a blip or a trend. Below the metric rows, keep the components that ratios need, such as monthly gross profit and revenue, or billable and available hours.

    Data tab. Calculations only. Each metric’s monthly value is calculated here from the import tabs, in a labeled block. Nobody pastes anything onto this tab.

    Import tabs. One tab per source: accounting, CRM, time tracking. Each month, the owner clears the tab and pastes that source’s standard export into cell A1. Nothing is typed or calculated on an import tab, so a longer or shorter export can’t overwrite a formula. On the Data tab, refer to whole columns or use lookups by label, so the calculations still work when the export has more rows than last month.

    Step 3: Add the Formulas

    These formulas behave the same way in Google Sheets and Excel. The examples use row 6.

    Pull this month’s actual. Rather than retyping, have column F on the Scorecard look up the month named in B2 from the Trend tab. The month in B2 has to be spelled exactly as it is in the Trend headers. With the month names in C5:N5:

    =INDEX(Trend!C6:N6, 1, MATCH($B$2, Trend!$C$5:$N$5, 0))

    The 1 tells INDEX to stay in the first (and only) row of the range, and MATCH supplies the column. Change B2 next month and every row updates.

    Calculate the variance. For dollars and counts, use the percentage difference from target:

    =(F6-E6)/E6

    For metrics that are already percentages, such as gross margin or utilization, use the difference in points instead:

    =F6-E6

    The two give different impressions. A margin target of 42% against an actual of 38.5% is 3.5 points below target, which is also 8.3% below it. “3.5 points” is the figure most people understand when they read a margin. Pick one convention per metric, label it, and keep it.

    Flip the sign for lower-is-better metrics. If D6 says “lower,” multiply the variance by −1 so that a negative number always means worse:

    =IF(D6="lower", -1, 1) * (F6-E6)/E6

    Handle zero targets. A percentage variance divides by the target, so a target of zero, such as zero overdue invoices or zero safety incidents, returns an error. Track those metrics in units instead: the variance is simply the count. Give that row its own status rule, for example =IF(F6="", "No data", IF(F6>0, "Red", "Green")), in place of the band formula in Step 5. Give “No data” a neutral style so a missing actual is never shown as Green.

    Calculate year-to-date by metric type. Averaging twelve monthly figures is right for almost nothing. Use the type you wrote down in Step 1:

    • For flows such as revenue, jobs completed, or operating cash flow, sum the months.
    • For ratios such as gross margin, utilization, or on-time delivery, recompute them from the summed components. Year-to-date margin is total gross profit divided by total revenue; year-to-date utilization is total billable hours divided by total available hours.
    • Point-in-time figures such as pipeline value, days sales outstanding, or cash balance: use the latest month-end value, or another method you define and write down.

    Retention depends on how you define it, so write the year-to-date rule into its definition. The year-to-date target follows the same rule as the actual.

    The ratio difference is real. Suppose January brings in $50,000 at a 40% margin ($20,000 gross profit) and February brings in $100,000 at 30% ($30,000). The average of the two percentages is 35%. The actual year-to-date margin is $50,000 ÷ $150,000, or 33.3%, because February’s larger month counts for more.

    Step 4: Set Targets, Starting From Your Own History

    A target picked because it sounds good gets ignored after the first miss. Start from what the business has actually done, then decide what it should do.

    1. Find a baseline. The trailing three-month average is a reasonable starting point, because recent months reflect your current staff, prices, and customers. If your business is seasonal, look at the same month last year as well.
    2. Turn the baseline into a target. Check it against your budget, your capacity, commitments you’ve already made, the season, and any improvement you’re planning. A baseline built from weak months will simply repeat them if you adopt it unchanged.
    3. Write down the reason for any difference between baseline and target, so the target can be explained later.
    4. Round to a number people can remember.

    Here is an example, not a client case. A business had revenue of $78,400 in June, $81,200 in July, and $76,900 in August. The three-month baseline is about $78,800. September is usually similar to the summer months; nothing unusual is planned, and the budget agrees, so the target is set at $79,000. September comes in at $72,600, which is $6,400 short, or 8.1% below target.

    Whether 8.1% is a problem depends on the band you set.

    Step 5: Set Tolerance Bands

    A tolerance band says how far a metric can move before anyone needs to act. Without one, every small dip gets discussed, and the meetings lose their point.

    I set bands from the business’s own history. I look at how much each metric actually moved over the last six to twelve months. Movement inside that normal range I treat as noise. Movement outside it means something changed. One caution: several months drifting the same way inside the band is still a trend, which is why the Trend tab matters.

    I also set them metric by metric, because metrics don’t behave the same way. A 5% miss on gross margin can be serious, while a 5% dip in inquiries may be an ordinary month.

    If you don’t have enough history yet, you still need a placeholder. There is no standard band. As a rough starting point, not a hard rule, some businesses could begin with something like:

    • Green: within 5% of target, or better.
    • Yellow: 5% to 15% worse than target.
    • Red: more than 15% worse than target.

    Replace it with bands from your own data once you have a few months. On that sample starting point, the September revenue example above (8.1% below) is yellow. A days sales outstanding target of 45 days against an actual of 52 is 15.6% worse, so it’s red.

    To fill the Status column, add a formula that returns a word:

    =IF(G6>=-0.05, "Green", IF(G6>=-0.15, "Yellow", "Red"))

    Then add three conditional formatting rules to column H: text is exactly “Green,” “Yellow,” or “Red.” Use the word as well as the color so the status still reads correctly in a printout or for anyone who has trouble telling the colors apart. Keep the rest of the sheet in neutral tones so the color means something when it appears.

    For percentage metrics tracked in points, the formula compares against point thresholds instead, for example −1 and −3 points. Record the band for each metric in a note on the Data tab so nobody has to guess later why margin turned red at a smaller miss than revenue did.

    A red status should trigger a short note from the metric’s owner: what happened, what it means, what we’ll do, and who does it by when. How to Get Your Team to Actually Use Your Reports covers that note and the meeting around it.

    Step 6: Update It the Same Way Every Month

    A scorecard that takes an afternoon to update gets skipped within a few months. If the update drags, the problem is usually how the data gets in, not the scorecard.

    Here is an example routine for a business that finishes its month-end bookkeeping within the first few business days. Adjust the days to your own close.

    1. Books closed. Wait until the month’s transactions are reconciled. Numbers pulled earlier will change, and the scorecard will disagree with your accounting.
    2. Exports in. Each metric owner clears their import tab and pastes the same standard export into cell A1. Save each export with the same filters and date range every month, and write those settings down.
    3. Record the month. Copy the Data tab’s results into that month’s column on the Trend tab using paste values, so next month’s imports don’t change them.
    4. Review. Change the reporting month in B2. Check the status column, then check that two or three headline figures match your accounting system before anyone else reads the sheet.
    5. Lock the month. Protect the finished month’s column on the Trend tab so nobody edits it by accident. In Google Sheets, use Protect sheets and ranges. In Excel, lock the cells and turn on Protect Sheet.

    When numbers do disagree, don’t adjust the scorecard to make them match. Find the cause. Revenue that differs between your payment processor, your bank, and your books usually has an ordinary explanation: payout timing, processor fees, or a different cutoff date. The Business Data You Already Have explains why those sources rarely line up.

    Monthly Scorecard Checklist

    • Four to seven metrics, each with a written definition, unit, direction, and type.
    • One owner per metric.
    • A Scorecard tab that fits on one screen, with a Trend tab, a Data tab, and one import tab per source behind it.
    • This month’s target, actual, variance, and status in adjacent columns.
    • Year-to-date figures calculated by type: flows summed, ratios recomputed from components, point-in-time figures taken at month end.
    • Targets that start from a baseline and account for budget, capacity, and season, with adjustments written down.
    • A tolerance band for each metric, and a separate rule for any metric with a zero target.
    • A written monthly routine, with each finished month recorded as values and locked.

    Frequently Asked Questions

    Should the scorecard be weekly or monthly?
    Both can exist. Weekly suits operating numbers people can act on quickly. Monthly suits numbers that only settle after the books close, such as margin and cash flow. Build the monthly scorecard first if your accounting only closes monthly.

    Can I download a template instead?
    Yes, if it’s close to what you need. Check that it lets you set your own four to seven metrics, keeps raw data away from the results, and uses formulas you can follow. If you’d have to delete most of it, building the tabs yourself may be simpler. Either way, make sure you understand every formula before something breaks.

    When should the scorecard move out of a spreadsheet?
    When the spreadsheet becomes the hard part: refreshing the data takes more time than acting on it, different people need different access, you need a record of who changed what, the data volume slows the file down, or keeping it working has become a job of its own. Until then, a spreadsheet is easier to change as you learn which metrics matter.

  • How Much Does a Small Business Dashboard Cost?

    There is no responsible single price for a small business dashboard, because "dashboard" covers everything from a spreadsheet scorecard to a multi-system software project. What you can judge is the work behind a quote. Four things drive it, and none of them is how the charts look: how clean your data already is, how many systems have to feed it, whether the numbers update on their own, and how many metrics you ask for. One tidy source in a spreadsheet is the cheapest build. Several automated feeds cost more. A build that needs a database or custom integration costs the most. Software licenses and upkeep are separate and ongoing.

    That is also why two honest quotes for "a dashboard" can differ widely. They are pricing different amounts of work, and most of that work happens before anything appears on a screen.

    What Actually Drives the Price

    How clean your data is. This is usually the biggest single factor. If the same customer appears three ways in your invoicing system, if products were never mapped to consistent codes, or if someone types entries by hand each week, that all gets sorted out before any chart is accurate. Clean, consistent records make a build straightforward. Messy ones turn it into a data project with a dashboard at the end.

    How many systems feed it. Each additional source adds more than a connection. It adds a definition to agree on and a reconciliation to maintain. Your accounting software, your payment processor, and your bank will each report a different number for what looks like the same month, for legitimate reasons, and someone has to decide which one the dashboard shows. The Business Data You Already Have covers why those three rarely agree.

    Whether it updates by itself. A dashboard you refresh by pasting an export is cheap to build and costs you time every week. An automated refresh costs more up front and less afterward, as long as someone maintains the connection when a source changes its format.

    How many metrics you ask for. This is the one you control most directly. My rule of thumb is four to seven metrics on the main view, and the question I ask about each one is whether it makes a difference: does it help bring in revenue, make the business more efficient, or cut costs? A request for twenty-five charts does not just add twenty-five drawings. Each metric needs its data found, cleaned, defined, and tested. Cutting the list is the cheapest change you can make to a quote. How Many KPIs Should a Small Business Track? covers how to choose them.

    Three Scope Tiers, Lowest to Highest

    One or two clean sources in a spreadsheet. Google Sheets or Excel, fed by exports you download from your accounting or payment system and paste in, with formulas doing the rest. This suits a business that wants a reliable monthly scorecard and can live with updating it by hand.

    Automated feeds in a reporting tool. Looker Studio or Power BI pulling from two to four systems on a schedule, with metric definitions agreed and built in. This is the common choice for a business that reviews numbers weekly and does not want anyone handling files.

    A multi-system pipeline. Five or more sources, a proprietary POS or ERP in the mix, data landing in a cloud database before it reaches the dashboard, and user permissions controlling who sees what. This is a software project, priced accordingly, and worth it mainly when the alternative is several people reconciling by hand.

    What a Comparable Quote Contains

    Quotes vary more because of scope than because of rates. Before comparing two numbers, make sure both describe the same work. A quote you can compare states, in writing:

    • Which systems get connected, and who provides the access.
    • Which metrics get built, and the agreed definition of each one.
    • How the data refreshes, and how often.
    • What happens when a source changes its export format.
    • Who owns the file or workspace when the project ends.
    • How ongoing maintenance is requested and billed.

    Hourly billing suits small changes and work where the scope is still unclear. A fixed price caps your cost for the work written into the scope, so ask how the quote handles changes you request later. A short paid scoping step before a fixed quote can reduce that risk, because it forces the definitions conversation early, when changing your mind costs the least.

    The Costs That Don't Stop

    Software licensing is separate from the build. Looker Studio is free for authoring and sharing reports. Power BI Pro is a paid per-user license, listed at $14.00 per user per month billed annually at the time of writing. If a system you use has no native connector, a third-party connector service may add its own monthly subscription.

    Maintenance is the easiest part to leave out of a budget. Upstream software changes column headers, an API updates, a new service line needs a new definition. Some businesses pay a fixed retainer; others handle changes as they arise, billed hourly or under a service agreement. What matters is agreeing in advance who does it, not how many hours it takes.

    Building It Yourself Isn't Free

    The tools can be free. Your time isn't. Estimate the hours you expect to spend building it, add the hours to keep it running every month, and multiply by what an hour of your own time is worth to the business. Use your own figures rather than a published average.

    Compare that against a quote before deciding. The common failure is not a bad decision either way. It is the half-built file that gets abandoned three weeks in, after the hours are already spent.

    Frequently Asked Questions

    Why won't anyone publish a price?
    Because "a dashboard" can mean a single spreadsheet tab or a multi-system software project. Most of the difference is in your data, which nobody can see until they look at it.

    Can I start small and add to it later?
    Yes, and it's usually the better path. Start with one source and the few metrics that pass the revenue, efficiency, or cost test. Adding a second source later is easier than removing four you never used.

    Should I fix what I have instead?
    Often, yes. If your numbers are accurate and the dashboard is just cluttered, renovation is often the smaller job. Have someone inspect how the current one is built before you decide. How to Improve a Business Dashboard You Already Have walks through that.

    Before You Spend Anything

    Check whether you already have what you need. Pull two or three headline numbers from your existing systems and see whether they hold up. If they do and the problem is presentation, renovate. If you're not sure whether you need outside help at all, When Should a Small Business Hire a Data Analyst? covers that decision.

  • KPIs for a Small Professional Services Firm

    A small professional services firm can run on five KPIs: billable utilization, realization, project gross margin, days sales outstanding (DSO), and qualified pipeline. Together, they answer the questions that decide whether a firm that sells time makes money. Are people spending their hours on billable work? Is that work getting billed and paid at the rates you set? Are projects finishing on budget? Is cash arriving on time? Is next quarter’s work lined up?

    What those numbers should be in your firm is a separate question, and it is where generic advice is weakest.

    Why Generic Benchmarks Don’t Fit Your Firm

    You’ll find plenty of published targets for utilization and margin. I wouldn’t lean on them. Setting a utilization target without looking at what a firm does and how it does the work is like generalizing about a family’s culture from the outside. A five-person engineering firm where the owner writes every proposal is a different business from a ten-person agency with a dedicated salesperson, even though both sell hours.

    Margin works the same way. What a healthy project margin looks like depends on the industry and the market you serve.

    So use the formulas below as written, but set your normal ranges from your own history: the last six to twelve months of time, invoice, and payment records, with seasonal periods compared like for like. The point is to notice when a number moves away from your normal and to know what to do about it. For why five metrics is enough, see How Many KPIs Should a Small Business Track?

    1. Billable Utilization

    Formula: billable hours ÷ available working hours × 100

    A consultant who records 30 billable hours in a 40-hour working week is at 75 percent. Define available working hours consistently by excluding company holidays and approved leave. Whether 75 percent is right depends on the role. Someone whose job is mostly client delivery will run higher than a senior lead who also reviews work and trains staff. An owner who writes proposals and runs the firm will run lower still. If an owner’s billable hours climb while the pipeline shrinks, check whether client delivery is crowding out business development.

    Set a normal range for each role based on what that role is actually expected to do, rather than one number for the whole firm.

    Watch for: utilization rising while realization falls. People are busy on work the firm isn’t getting paid for.

    2. Realization

    Realization shows how much of the work you record turns into revenue. Track it in two parts.

    Billed realization: fees invoiced ÷ (billable hours × standard rate) × 100

    If a team records 120 billable hours at a $150 standard rate, that work is worth $18,000 at standard rates. If the invoices total $15,300, billed realization is 85 percent. The missing $2,700 went to write-downs, discounts, or scope that never got billed.

    Collected realization: cash collected against a group of invoices ÷ the value of those invoices × 100

    Measure the same invoice group in the numerator and denominator, or use a rolling window long enough to absorb ordinary payment lag. Otherwise, this month’s collections divided by this month’s invoices can compare unrelated work. The measure catches disputes, deductions, and invoices that never get paid.

    On fixed-fee work, the same idea appears as an effective hourly rate: fees collected on the project ÷ all hours worked on it, including rework. A $10,000 fixed-fee project that took 100 hours earned $100 an hour. At a $175 standard rate, the same 100 hours have a standard-rate value of $17,500, leaving a $7,500 gap to investigate. That gap is not automatically lost profit; it may reflect deliberate pricing, scope growth, or delivery inefficiency.

    Watch for: billed realization dropping on the same clients or project types. The fix is usually tighter scope and change orders, not more hours.

    3. Project Gross Margin

    Formula: (project revenue − direct labor cost − direct project expenses) ÷ project revenue × 100

    Use burdened direct labor cost: wages plus employer payroll taxes and employee benefits for the hours spent on the project. Keep overhead separate unless your project-costing method allocates it consistently.

    Because margin expectations vary so much by industry and market, compare each project with its own budget. A project priced for a 55 percent margin that finishes at 38 percent tells you something went wrong in the estimate, the scope, or the delivery. Find out which before you quote similar work.

    Watch for: the same type of project repeatedly finishing below its budgeted margin.

    4. Days Sales Outstanding (DSO)

    Simple formula: ending accounts receivable ÷ credit sales for the period × days in the period

    With $90,000 in ending receivables and $270,000 in credit sales over the last 90 days, DSO is 30 days. If receivables swing sharply during the period, use average receivables instead of the ending balance and label the method so comparisons stay consistent.

    DSO estimates how long clients take to pay, but it lags. By the time it jumps, the late invoices are already late. I prefer to set up receivables so someone sends reminders and talks with clients around the due date. That way, the firm can identify payments that may lag and address issues before invoices drift past 60 days.

    Watch for: individual invoices getting close to 60 days, not just a rising average.

    5. Qualified Pipeline

    Definition: total value of qualified proposals and opportunities expected to close in the next 90 days

    Some firms weight each opportunity by its chance of closing. A simple total works too, as long as you count the same way every week.

    The first four KPIs describe the work you already have. Pipeline tells you whether there will be work next quarter, and it’s the number that suffers first when senior people are too busy billing to sell. Client retention matters as well, but it changes slowly; review it quarterly rather than weekly.

    Watch for: pipeline shrinking while utilization is high. That’s a firm that is busy now and will be short of work later.

    A Simple Scorecard Layout

    KPISource recordsReviewExample ownerWhen it moves outside your range
    Billable utilization, by roleTime trackingWeeklyOperations leadRebalance assignments; check who is overloaded
    Billed and collected realizationTime tracking and invoicingMonthlyManaging partnerLook for write-downs by client or project type; tighten scope
    Project gross marginTime, payroll, and project expensesAt milestones and closeProject leadCompare with the estimate; adjust pricing for similar work
    DSO and open invoicesAccounting receivables agingWeeklyOffice or finance managerFollow up on invoices near their due date
    Qualified pipelineCRM or proposal listWeeklyOwner or sales leadProtect time for business development

    Most of this data already lives in your time-tracking, invoicing, and accounting software. Start with a simple spreadsheet if you need to bring the sources together.

    If pulling these numbers together each week takes longer than acting on them, it may be time for outside help. When Should a Small Business Hire a Data Analyst? covers how to tell.

  • How to Get Your Team to Actually Use Your Reports

    Reports get used when they feed a routine that ends in decisions. Keep the report to one page with four to seven core numbers. Have each manager prepare a short note on any number that’s off track. Then run a short weekly meeting built around three questions: What do the numbers mean? Who will act on them? By when? Open the next meeting by checking whether those actions happened.

    To me, a useful conversation about the numbers is an action-oriented one: what the numbers mean, who will act on them, and by when. Most reporting routines stop at the first part. Without a name and a date, a team can discuss the same bad number every week and nothing changes.

    Why Doesn’t Your Team Read the Reports You Send?

    Often because reading them is not connected to a decision or a follow-up. A report emailed on Monday competes with customer calls, staffing problems, and everything else on a manager’s list. If no meeting depends on it and nobody will ask about it, reading it is optional, and optional work gets pushed to later.

    Two other problems make it worse:

    • The report makes the reader do the analysis. A ten-tab spreadsheet or a 15-page PDF asks each manager to find what changed and decide whether it matters. Most probably won’t.
    • The report describes the past without asking for anything. If a report never leads to a decision, people reasonably conclude it isn’t meant for them.

    If the problem runs deeper, and people don’t trust the numbers or can’t connect the metrics to their work, start with Why Nobody Looks at Your Dashboard. The routine below works best once people believe the numbers.

    What Should the Report Look Like Before the Meeting?

    One page. If it doesn’t fit on one page, each reader has to do the sorting the report should have done for them.

    A one-page weekly summary needs four parts:

    1. The scorecard. Four to seven core metrics, each with its current value, target range, prior period, and a simple on-track or off-track status. Four to seven is my rule of thumb for most small businesses; How Many KPIs Should a Small Business Track? covers how to choose them.
    2. What’s off track. The metrics outside their range this week, called out at the top so nobody has to hunt for them in a table.
    3. What went well. One to three things that improved, and why. This keeps the meeting from turning into a list of problems and tells people what to keep doing.
    4. Decisions needed. Anything that needs an approval, a trade-off, or resources from the owner this week.

    Everything else goes in an appendix or a linked file: full financial statements, transaction detail, breakdowns by customer or crew. People open it when they need to investigate. A monthly version can add that detail without crowding the weekly operating view.

    How Should Managers Prepare for the Meeting?

    They should read the one-page summary beforehand and write a short note for any metric they own that is off track. Meeting time is for deciding, and reading numbers aloud wastes it.

    Send the summary early enough to read: Friday afternoon for a Monday meeting, or first thing in the morning for a late-morning meeting. Put the notes in one shared document so everyone can see them before the meeting starts.

    The Off-Track Note

    Each note answers four questions in a few sentences:

    1. What happened? The number, its target, and how far off it is.
    2. What does it mean? The effect on cash, customers, delivery, or cost.
    3. What will we do? The specific action.
    4. Who, and by when? One name and one date.

    Here is a hypothetical example, not a client case:

    What happened: First-pass yield fell to 88% this week against a target of 95%.

    What it means: About 12 hours of rework, roughly $2,500 in scrapped material, and one order at risk of shipping late.

    What we’ll do: Recalibrate the tooling on the cutting station and review the new tolerances with the operators.

    Who and by when: Shop lead. Tooling done by Tuesday; operator review Wednesday morning.

    A short note like this changes where the conversation starts: with a proposed fix instead of an argument about what went wrong.

    One rule matters more than the format. Don’t penalize people for reporting a red number. Ask them to bring either a proposed next step or a clear request for help. If off-track numbers get people criticized in front of the team, expect to see numbers explained away instead of fixed.

    How Do You Run the Meeting?

    Keep it short, run it the same way every week, and end with names and dates. The agenda below is a 15-minute starting point for a small team; add time when several metrics need real decisions.

    Here is a starting agenda for a 15-minute meeting. Stretch the off-track section if you need a longer one.

    MinutesTopicWhat happens
    0–3Last week’s actionsEach owner says done, in progress, or missed; a missed action gets a new date
    3–5ScorecardWalk through the metrics and confirm which are off track
    5–12Off-track metricsEach owner gives their note in about a minute; the group agrees on the action, owner, and date
    12–15Decisions and blockersThe owner approves resources or settles conflicts between departments

    A few rules keep it on track:

    • Show the report itself. Put the one-page summary or the dashboard on the screen. A separate slide deck is one more document to maintain and one more place for numbers to disagree.
    • Skip what’s on track. If a number is in range, move on.
    • Take long problems out of the meeting. If something needs more than a few minutes, assign someone to work on it and set a date to report back.
    • Record every action before anyone leaves, with its owner and due date.

    How Do You Make Sure Actions Actually Happen?

    Keep a running action log and open every meeting with it. This step is easy to skip, but it is the one that shows people the routine matters.

    The log can be a simple table in the same shared document. The entries below are samples:

    RaisedMetricActionOwnerDueStatus
    Sept. 8Days sales outstandingCall the five largest overdue accountsOffice managerSept. 12Done
    Sept. 8Labor cost as % of salesAdjust Tuesday and Wednesday schedulesOperations leadSept. 15In progress
    Sept. 15First-pass yieldRecalibrate cutting station toolingShop leadSept. 16Open

    When you review the log each week:

    • Done: Check whether the metric responded. If it didn’t, the action didn’t address the cause, and the owner needs a new plan. Or, decide if the action did address the cause and the response needs more time to become indicative.
    • In progress: Confirm the date still holds.
    • Missed: Ask for a new date and what got in the way. If the same action slips twice, investigate whether the constraint is time, authority, resources, or an unclear assignment instead of sending another reminder.

    Over a few months, the log also shows which problems keep coming back. That pattern can be more useful than any single week’s report.

    What About Monthly Reviews and One-on-Ones?

    Use the same pattern at a different pace.

    A monthly review covers the numbers that only change meaningfully after the books close, such as gross margin, and looks at trends across several weeks. It uses the same off-track notes and the same action log, with additional financial and operating detail where needed.

    A one-on-one is where you help a manager with their own numbers. Start with the metrics they own, look at the trend, and ask what they need to bring an off-track number back into range: time, budget, help from another department, or a decision from you. Asked that way, the conversation becomes about solving the problem together rather than checking up on them.

    How Do You Keep Reports From Piling Up Again?

    Review every recurring report once a quarter and stop the ones nobody would miss. Reports accumulate: someone asks a one-time question, the answer becomes a weekly report, and nobody ever turns it off.

    For each scheduled report, ask the people who receive it: “If this report stopped tomorrow, what decision would you be unable to make?” If nobody can name one, stop sending it. If someone misses it later, you can bring it back.

    Apply the same test to the metrics on the weekly summary. If your dashboard has grown well past what the meeting can use, How to Improve a Business Dashboard You Already Have walks through cutting it down.

    Your First Four Weeks

    • Week 1: Cut the report to one page with four to seven metrics, and assign an owner to each.
    • Week 2: Send the summary before the meeting and ask owners of off-track metrics for their notes. Some notes will be missing; ask for them anyway.
    • Week 3: Open the meeting with the action log from week 2.
    • Week 4: Look back at the log. Which actions got done, which slipped, and did the numbers respond? Adjust the metrics, the timing, or the meeting length based on what you find.

    Expect the routine to feel mechanical at first. It starts to stick once people see that a number raised in one meeting leads to an action, and that the action gets checked in the next one.

  • Why Nobody Looks at Your Dashboard (and How to Fix It)

    People stop looking at a dashboard for a few predictable reasons: they don’t trust the numbers, the metrics don’t connect to their work, nobody has shown them what to do when a number changes, the screen is a hassle to use, or the person in charge ignores it too. Training alone will not fix those causes. What works is rebuilding trust in the numbers, cutting the dashboard down to metrics people can act on, and tying each one to a decision.

    I have seen reports get ignored for several of these reasons. A recurring one was that people didn’t understand what difference the numbers could make, or how to act on them. Once, the reason was simpler: the person in charge was sure they already knew the business better than any report could tell them.

    The good news is that each cause leaves a recognizable trail, so you can figure out which one you are dealing with before you change anything.

    How Does a Dashboard Go From Launch to Ignored?

    Usually gradually, and for reasons that started weeks before anyone noticed the drop in use. Abandoned dashboards tend to follow the same pattern.

    1. Launch. The dashboard is introduced in a meeting. People open it out of curiosity, click around, and say it looks useful.
    2. The first doubt. Someone notices a number that doesn’t match what they know: a sales total that looks low, a job count that seems off. Nobody explains the difference.
    3. The quiet return. Instead of reporting the problem, that person goes back to their own spreadsheet. Others follow for their own reasons: the dashboard is slow, or it doesn’t show what they need.
    4. Neglect. With fewer people looking, nobody notices when a data connection fails, or a metric goes stale. The out-of-date numbers confirm everyone’s decision to stop using it.

    The clearest sign you have reached step 3 or 4 is that managers arrive at meetings with their own spreadsheets. A dashboard that has lost to private spreadsheets has usually lost on trust, relevance, or both.

    Why Do People Stop Trusting the Numbers?

    At some point, a dashboard number disagreed with something they knew was true, and nobody could explain why, or worse, could figure out why. That single discrepancy erodes confidence entirely.

    Take a sales manager who knows the team closed about $55,000 in new work last month. The dashboard says $42,000. There may be a perfectly good reason. The dashboard might count invoiced revenue, while the manager counts signed contracts. It might use a different month-end cutoff, or leave out a job still waiting on an invoice. Without an explanation, though, the manager concludes the dashboard is wrong and stops trusting the other numbers on the screen, too.

    Numbers drift apart for a handful of common reasons:

    • Different definitions. “Sales” can mean booked, invoiced, or collected. Each is legitimate, and each produces a different total.
    • Timing. Cash and accrual accounting put the same transaction in different periods. Payment processors deposit money days after the sale.
    • Unmapped categories. A new product, service code, or customer type gets added to the source system but never mapped into the dashboard, so its revenue disappears from the totals.
    • Silent failures. A data refresh fails, or a formula breaks, and the dashboard keeps showing old numbers without any warning.

    Most of these aren’t errors in the usual sense. They are definitions and rules that were never written down where the people using the dashboard could see them. Tracing a mismatch starts with documenting which system, definition, date range, and cutoff produced each number.

    Why Don’t the Metrics Feel Relevant to the Team?

    Because the dashboard shows what the owner wants to know rather than what the people using it can influence.

    A shop supervisor can’t do much with quarterly net profit. They can act on the number of jobs waiting for inspection or the parts that failed first inspection this week. A service coordinator can’t move company-wide revenue directly, but they can act on unbilled hours or open slots in next week’s schedule.

    When the main view shows only company-level results, frontline managers reasonably decide the dashboard isn’t for them. They aren’t resisting data. They are ignoring numbers they can’t do anything about.

    Each person should see the few metrics they can move, alongside the company results those metrics feed. For choosing those metrics, and keeping the list short enough to act on, see How Many KPIs Should a Small Business Track?

    What If People Don’t Know What to Do With the Numbers?

    Then the numbers are trivia, and people stop checking trivia. In my experience, this is a recurring reason reports get ignored: nobody understood what difference the number could make or how to act on it.

    Suppose a dashboard shows that days sales outstanding rose from 38 to 47 over two months. To an owner who watches cash closely, that is an obvious warning: customers are paying more slowly, cash will be tighter, and someone should start calling the largest overdue accounts. To a manager who has never had that explained, it is just a number that went up.

    A practical fix is to write one line for every metric on the main view that answers three questions: what it means when the number moves, what usually happens next, and who does it. Put those lines on a notes tab or beside each card.

    Here is what that looks like for a few metrics. The metrics, triggers, and owners are illustrative; set your own.

    MetricWhen it moves the wrong wayWhat usually happens nextWho
    Days sales outstandingRises two weeks in a rowCall the five largest overdue accounts; review payment terms on new workOffice manager
    Gross margin by jobA job finishes below targetCompare actual hours and materials with the estimate; adjust the next quoteOperations lead
    Qualified inquiriesFalls below the monthly rangeCheck whether the source changed (referrals, website, repeat customers) before spending more on marketingOwner
    Booked hours next weekBelow available capacityContact customers with pending work; move maintenance tasks into the open timeScheduler

    Writing these lines also tests the metric. If nobody can say what action would follow a change, the metric probably doesn’t belong on the main view.

    Is the Dashboard Too Much Trouble to Use?

    It may be. Every extra login, filter, click, and scroll makes it easier to just ask someone for the number.

    Watch for these signs:

    • People email or message you asking for figures that are already on the dashboard.
    • Getting to the dashboard requires a login people forget, or a link buried in an old email.
    • Each visit starts with setting date ranges and filters before anything useful appears.
    • It loads slowly, or the important numbers are below the fold.

    Most of these have simple fixes: save a default view with the right filters already applied, share one bookmarked link, and fit the main metrics on one screen. For the design problems that make dashboards hard to read, see 7 Dashboard Mistakes Small Businesses Make.

    What If the Person in Charge Doesn’t Use It?

    Other people are unlikely to use it for long too. One of the reports I have seen ignored went unused for exactly this reason: the boss believed they already knew better and didn’t need it.

    People take their cues from what the person in charge pays attention to. If the owner makes decisions from instinct and never mentions the dashboard, managers learn that keeping the numbers current is wasted effort, and they stop.

    This doesn’t mean experience and instinct should be ignored. An experienced owner often does know things a report can’t show. But when instinct and the dashboard disagree, that disagreement is worth resolving. The data may be wrong, the instinct may rely on context the dashboard does not capture, or an old assumption may need another look.

    If you are the person in charge, three habits change the signal you send:

    1. Ask about the numbers first. Start conversations with managers by looking at their metrics together.
    2. Say which number informed a decision. “We’re holding off on the new hire because booked hours dropped for three weeks” teaches more than a memo about being data-driven.
    3. Treat disagreement as a question. When a number surprises you, ask why before dismissing it.

    How Do You Get People Looking at the Dashboard Again?

    Fix trust first, then relevance, then habit. Redesigning the layout before people trust the numbers produces a better-looking dashboard that people still ignore.

    Step 1: Reconcile the Numbers in the Open

    Sit down with the managers who use the dashboard. Pick the headline numbers and compare each one with its source: bank deposits, accounting reports, payroll, or the scheduling system. For every gap, either fix it or explain it. Then write each metric’s definition in plain language where everyone can see it, such as “Revenue = invoiced amounts by invoice date, excluding sales tax.”

    Step 2: Let Managers Challenge Their Metrics

    If a manager says a metric doesn’t reflect their work, take it seriously. Either the definition needs to change or the metric needs to be replaced. Separate two kinds of objections, though: “this is measured wrong” gets fixed, while “I don’t like what this shows” doesn’t.

    Step 3: Cut the Main View Down

    Keep four to seven metrics on the main screen, which is my rule of thumb for most small businesses. Move the rest to a detail tab. How to Improve a Business Dashboard You Already Have walks through the cleanup step by step.

    Step 4: Attach an Action and an Owner to Every Metric

    Write the one-line action notes described above, and put one person’s name on each metric.

    Step 5: Put the Dashboard on a Meeting Agenda

    A dashboard that people are only invited to check will keep sliding back toward neglect. Make it the first thing a regular meeting opens, and ask each owner to speak to their number: what changed, what it means, who will act, and by when.

    Which Problem Do You Have?

    Match what you see to the likely cause and the place to start:

    What you noticeLikely causeStart with
    Managers bring their own spreadsheets to meetingsThe numbers aren’t trustedStep 1: reconcile in the open
    “That’s not really my number”Metrics don’t fit their workStep 2: let managers challenge metrics
    People look at the numbers, but nothing changesNo action attachedStep 4: write action notes
    People ask for figures that are already on the dashboardToo much trouble to useDefault views, one link, one screen
    Decisions get made without mentioning the numbersLeadership doesn’t use itAsk about the numbers first
    Nobody opens it between meetings, or there are no meetingsNo routineStep 5: put it on the agenda

    Most ignored dashboards have more than one of these problems. Start with trust. Nothing else sticks until people believe the numbers.

  • 7 Dashboard Mistakes Small Businesses Make

    The most common dashboard mistakes are showing too many metrics, featuring vanity metrics that don't lead to decisions, displaying numbers without targets or comparisons, pasting raw tables onto the main screen, paying for real-time updates nobody acts on, leaving metrics without an owner, and mixing headline results with detail. Each one makes the dashboard harder to read quickly, and reading quickly is the whole point of a dashboard.

    Most of these mistakes start the same way: the dashboard gets built around what the software can show instead of the decisions the business needs to make. Use the seven below as a checklist against your own screen.

    1. Too Many Metrics on One Screen

    What it looks like: Twenty or thirty charts, cards, and gauges, and you have to scroll to see them all.

    Why it hurts: When everything competes for attention, the number signaling a real problem looks the same as the twenty that don't. People skim, then stop opening it.

    What to do instead: Keep four to seven core metrics on the main view. That's my rule of thumb for most small businesses, and the reasoning is in How Many KPIs Should a Small Business Track?

    2. Vanity Metrics in the Top Row

    What it looks like: Page views, social followers, total sign-ups, or revenue booked sit in the most prominent spots.

    Why it hurts: These numbers can climb while margins shrink or cash gets tight. They feel like progress and give you nothing to act on.

    What to do instead: Ask whether each metric makes a difference. Does it help bring in revenue, make the business more efficient, or cut costs? Then ask who would do what if it dropped 20 percent next week. A metric that fails both questions doesn't belong at the top.

    3. Numbers With No Context

    What it looks like: A card that says "Revenue: $45,000" or "DSO: 48 days" and nothing else.

    Why it hurts: The reader has to remember last month, recall the budget, and do the math. Is $45,000 a good month? The card can't say.

    What to do instead: Show each number beside a target and the prior period: "$45,000 against a $50,000 target, up from $41,500 last month."

    4. Raw Tables on the Main Screen

    What it looks like: A 50-row export of invoices or transactions embedded on the dashboard.

    Why it hurts: A large raw table usually has to be read line by line, which makes trends and outliers harder to spot at a glance.

    What to do instead: Summarize on the main view with a number card or a small trend line. Keep the table on a separate detail tab for when you need to investigate.

    5. Real-Time Updates for Weekly Decisions

    What it looks like: Live feeds refreshing every few minutes for sales, pipeline, or margin that the team reviews once a week.

    Why it hurts: Real-time connections can add cost or maintenance complexity, and they can invite overreaction to swings that even out by the end of the week.

    What to do instead: Refresh as often as you act. A scheduler may need daily capacity data, while a closed-month margin calculation only needs to update after the accounting period ends.

    6. Metrics Nobody Owns

    What it looks like: Everyone can see the dashboard, but when a number turns red, nobody is sure whose job it is to explain it.

    Why it hurts: Problems get noticed and discussed but not fixed. After a few weeks of that, people stop taking red numbers seriously.

    What to do instead: Put one person's name on each metric. That person explains the number when it moves and says what they'll do about it. Build that ownership into a regular meeting and follow-up routine.

    7. Headline Results Mixed With Detail

    What it looks like: Gross margin and cash runway sit beside ad cost per click and scrap at a single workstation, all the same size.

    Why it hurts: This can happen even on a dashboard with only a handful of metrics. When detail gets the same weight as headline results, reviews drift into the detail and nobody steps back to ask whether the business is on track.

    What to do instead: Use two tiers. The main view holds the headline metrics. Detail lives on a separate tab you open when a headline number moves. The two-tier setup is explained in How Many KPIs Should a Small Business Track?

    A Quick Dashboard Check

    Open your dashboard and answer yes or no:

    1. Does the main view show seven metrics or fewer, without scrolling?
    2. Does every metric on it help bring in revenue, improve efficiency, or cut costs?
    3. Does every number show a target and a prior period?
    4. Are detailed tables kept off the main view?
    5. Does the refresh schedule match how often you act on the numbers?
    6. Does every metric have one named owner?
    7. Is detail kept on a separate tab from headline results?

    Each "no" points to the matching mistake above.

    Next Step: Fix What You Found

    Once you know which mistakes your dashboard has, How to Improve a Business Dashboard You Already Have walks through repairing them in order, starting with whether the numbers can be trusted. If the dashboard is in good shape and people still ignore it, investigate trust and routine rather than redesigning it again.