NOT OUT LABS

What should a small-business dashboard track?

A practical reference from NOT OUT LABS.

A useful dashboard should help someone decide what to do next. If a metric does not change a decision, it may not deserve prime dashboard space.

Dashboards become cluttered when every available number is treated as important. A better approach starts with the decisions a business makes repeatedly and then identifies the smallest set of measures that makes those decisions easier.

Start with the operating questions

What needs attention today? Where are leads getting stuck? Which products are selling without enough margin? What stock is becoming risky? Which customer issues are repeating? The dashboard should answer questions like these before it tries to look impressive.

Sales pipeline

  • Open opportunities by stage
  • Overdue next actions
  • New leads and meaningful replies
  • Qualified conversations or meetings
  • Pipeline ageing
  • E-commerce

  • Revenue and order trend
  • Contribution margin or profit after relevant marketplace costs
  • Returns/cancellations where available
  • Out-of-stock or low-stock exposure
  • Listing or catalogue issues requiring action
  • Operations and customer support

  • Open tasks or tickets
  • Age of unresolved items
  • Recurring issue categories
  • Ownership and SLA/response exceptions where a service level applies
  • Use layers instead of one giant screen

    The first view should show exceptions and trends. Detailed tables can sit underneath. Leaders often need a different view from the person responsible for daily execution.

    Define every metric

    “Conversion”, “profit”, “active lead” and “resolved” can mean different things to different teams. A dashboard is only trustworthy when the definition and source of each important metric are clear.

    Where Not Out Labs fits

    Not Out Labs business systems builds practical dashboards, CRM-style trackers, profitability tools and workflows around the actual operating need rather than a fixed software template.

    Dashboard test

    For every metric, ask:

  • What decision does it support?
  • Who owns the action?
  • How often is it updated?
  • What is the source?