Metabase business reporting and dashboards for small business
How small businesses use Metabase for dashboards and self-service reporting, and how MILabs sets it up with the owner.
Updated 2026-04-04
What Metabase is
Metabase is an open-source business intelligence tool. It connects to a company's existing databases and lets people explore that data through a visual query builder, or through SQL for those who prefer to write it. Results can be saved as questions and gathered into dashboards that refresh as the underlying data changes. Metabase is available as a hosted cloud service and can also be self-hosted, so a business can decide where its data tools run. Its audience is wide. An owner can read a sales summary without asking anyone for a spreadsheet, and an analyst can build more detailed views in the same place. Because Metabase reads from the systems a business already uses, it sits beside accounting software, a CRM or a booking system. It presents information that lives elsewhere, so the usefulness of its answers depends on how well those systems are organised and kept current.
Metabase in plain language
Business intelligence software takes figures already sitting in accounting, booking, sales and inventory systems and brings them together in one view. Metabase is one of several tools built for that job. For smaller firms its value lies in how little it asks of the person using it. A team member with no coding background can filter a table, group results by month and save the view. Someone comfortable with SQL can write a precise query when the visual builder falls short.
Two ideas sit underneath most of this. The first is the connection: the tool reads from a source and leaves it in place, so the ledger or the booking calendar stays the place where transactions are made. The second is the definition. A figure such as gross margin or active customer can mean different things in different offices, and a dashboard only looks authoritative once the business has agreed what each term counts.
Hosting is the other decision. A cloud deployment starts quickly and is handled by the vendor, while a self-hosted installation keeps the server and its application database under the business's own control. Either choice shapes who can administer the system, how backups run and where sensitive records sit.
What businesses use it for
- Following weekly sales by product, location or salesperson, drawn from point-of-sale or accounting records.
- Keeping an eye on cash position and outstanding invoices on one owner dashboard.
- Reviewing booking volumes, cancellations and no-shows by day and by service.
- Checking stock levels against reorder points drawn from inventory records.
- Giving staff a shared set of figures so meetings start from the same numbers.
Who it suits
- Owners who want a clear picture of money and customers without waiting on monthly packs
- Groups running several software systems that want one place to compare figures
- Businesses with a technical team member who can look after the data connections
How MILabs sets it up
MILabs starts with the owner or team lead, who sets the business questions the reports must answer. Together we choose a hosting option, either Metabase's hosted cloud or a self-hosted installation, and agree which plan fits the team's size and needs. We then connect Metabase to the systems already in use, such as accounting, CRM, booking or point-of-sale data, and check that each connection returns the figures the owner expects. Permissions come next, so each person sees only the collections their role requires. Finally we build the first dashboards, confirm the definitions behind key figures such as revenue or margin, and agree who maintains the connections. That shared agreement keeps the reporting useful after handover.
Connects to
Builds it fits
Industries it fits
Metabase in practice
Inside a working business, Metabase usually settles into a routine rather than a single project. The owner opens a dashboard before a Monday meeting and sees the figures that matter most: last week's takings, the balance of receivables and bookings already on the calendar for the coming days. Questions raised in the meeting, such as why one location fell behind, get answered by drilling into the same tables instead of commissioning a new report.
The setup tends to split into layers. A finance lead might work from a collection of ledger-based views, while a shift supervisor sees only the stock and roster figures for their site. Sales staff may have a pipeline view that filters to their own accounts. Each layer relies on shared definitions, so one person usually owns the shared fields, such as how a cancelled booking is counted.
Upkeep is ongoing. When the business adds a product line, changes its point-of-sale software or moves its booking tool to a new provider, the connections and dashboards need a check. Someone has to notice when a figure stops updating, and someone has to decide whether a dashboard should change or be retired. Metabase makes those changes manageable, yet the decisions stay with the business.
Frequently asked questions
- Which builds work well with Metabase?
- Builds that read from data a business already holds suit Metabase best. An owner dashboard, a weekly business digest and a KPI scorecard draw on figures it can present clearly. Sales pipeline and daily sales reports suit businesses with a CRM or point-of-sale system, while no-show and inventory forecast reports suit clinics, fitness businesses and stockholding businesses. MILabs confirms the fit early, as the right build depends on the systems in use.
- What is Metabase?
- Metabase is an open-source business intelligence tool. It links to databases a business already has, and people query that data with a visual builder or with SQL. Answers become saved charts and dashboards. Metabase runs as a hosted cloud service or as a self-hosted installation, and it sits alongside the accounting, CRM and booking software a business already uses.
- How does MILabs set up Metabase?
- MILabs begins with the owner or team lead to decide which questions the reporting must answer. We then agree on a hosting option, connect Metabase to the business's data sources, and set permissions so each person sees what their role needs. The first dashboards are checked against figures the owner already trusts, and the business agrees who maintains the connections. The easiest first step is to say hello through the enquiry form.
- Where does Metabase store data?
- Metabase reads from the systems a business connects to, and the source records remain in those systems. Metabase keeps its own settings, users, saved questions and dashboards in an application database. When self-hosted, that database and the server running Metabase sit wherever the business or its IT provider chooses. MILabs confirms where each part is kept during setup, so the owner knows where information lives.
- When is Metabase the wrong choice?
- Metabase is a weaker match when the business needs an operational system rather than reporting, such as recording jobs, quotes or customer messages. It also suits teams less well if nobody can maintain the data connections, or if source data is inconsistent and no one has agreed what each figure means. In those cases a workflow tool or a clearer data process usually comes first. MILabs will talk that through in the first conversation.
