Power BI for Small Business: Dashboards Without a Data Team

Power BI is Microsoft’s business intelligence tool — it pulls data out of the systems you already run, like Xero or Excel, and turns it into live dashboards. A small business can build genuinely useful reporting with it without hiring a data analyst, provided you start narrow and keep one set of numbers honest.

Most Melbourne SMEs we work with are drowning in spreadsheets. Sales lives in one workbook, the job costing in another, the helpdesk numbers in a portal nobody logs into, and the cashflow forecast in a file the bookkeeper updates monthly. Power BI’s pitch is simple: connect those sources once, and the dashboard refreshes itself. The trap is treating it as a magic spreadsheet. It is not. Used badly it just creates prettier confusion. Used well it gives a director a single screen that answers “how are we actually going?” before the morning coffee.

What Power BI actually is

Power BI is three things wearing one name. Power BI Desktop is a free Windows application where you build reports — connect data, shape it, write the odd calculation, design the visuals. The Power BI Service is the cloud side (app.powerbi.com) where you publish those reports, share them, and let them refresh on a schedule. Power BI Mobile is the phone app for viewing dashboards on the road.

If your business runs Microsoft 365 — and most Melbourne SMEs do — Power BI sits in the same tenant, uses the same logins, and respects the same security. That integration is the main reason it wins over standalone tools for a small business already inside the Microsoft ecosystem. We cover the broader 365 picture in our Microsoft 365 service.

Licensing: Desktop, Pro and Premium Per User

This is where people get confused and overspend, so be clear about it. Building reports is free. Sharing them with other people is what costs money. Pricing below is per user per month and subject to change by Microsoft — treat it as the shape of the decision, not a quote.

For a typical small business the answer is nearly always Pro. Everyone who needs to view a shared dashboard needs a Pro licence (or PPU), not just the person who built it — that is the line item people forget. Premium Per User only earns its keep once your data models get large or you need refreshes every few minutes. There is also a capacity-based tier (Fabric/Premium capacity) priced for larger organisations; if you are a 25-person firm in Hawthorn, you do not need it.

Connecting your data

Power BI ships with hundreds of connectors. The ones that matter for an Australian SME:

• Xero and MYOB — both connect, though the path differs. Xero has a native connector and also publishes its own pre-built Power BI reports; MYOB is typically reached through its API or a third-party connector. For deep accounting analysis, many firms export to a database or use a connector tool rather than hitting the accounting platform directly every refresh.
• Excel and CSV — the workhorse. Point Power BI at a workbook in SharePoint or OneDrive and it refreshes when the file changes. This alone replaces a lot of manual copy-paste.
• SQL Server and other databases — if you run a line-of-business app (job management, ERP, a practice system) on SQL, Power BI reads it directly. This is where the richest reporting comes from.
• Dataverse — the data layer behind Microsoft Dynamics and Power Apps. If you have built anything on the Power Platform, Power BI reads it natively.
• Web and SaaS APIs — helpdesk tools, CRMs and marketing platforms often expose data Power BI can pull.

One practical note: cloud sources (Xero, SharePoint, SaaS) refresh straight from the Service. On-premises sources like a local SQL server need the on-premises data gateway installed — a small piece of software that lets the cloud Service reach back into your network to refresh. It is a five-minute install but easy to forget, and it is usually the reason a dashboard “stopped updating”.

Building your first dashboard

The mistake is starting with the whole business. Start with one question someone actually asks every week. The build then goes:

1. Connect the source in Power BI Desktop using Get Data.
2. Clean and shape it in Power Query — rename columns, fix date formats, filter out junk. This step is 70% of real BI work and the part people skip.
3. Model the data — link tables together so, for example, every invoice knows which customer and which month it belongs to.
4. Visualise — drop in a few cards for the headline numbers, a line chart for the trend, a table for the detail. Resist the urge to add forty visuals.
5. Publish to a workspace in the Service and set a refresh schedule.

A clean dashboard answering one question beats a cluttered one trying to answer ten. You can always add a second page.

Sharing, workspaces and row-level security

You do not email a Power BI file around — that defeats the point. You publish a report into a workspace (a shared container in the Service), and people with the right licence and permission view it live. Workspaces are how you separate, say, the finance dashboards from the operations ones, and control who sees which.

For anything sensitive, learn row-level security (RLS) early. RLS filters the data by who is looking. The classic case: a sales manager in South Yarra should see only their own team’s pipeline, not the whole company’s, even though everyone opens the same report. You define roles in Power BI Desktop, assign people to them in the Service, and the data filters itself per viewer. Without RLS, “sharing the dashboard” means sharing everything in it — which is how payroll numbers end up in front of the wrong person.

Dashboards that earn their keep in an SME

The reporting that genuinely pays for itself in a small business is unglamorous:

• Cashflow — a live view of receivables ageing, upcoming payables and bank position, pulled from Xero or MYOB. This is the one most directors check daily once it exists.
• Sales pipeline — deals by stage, expected value, conversion rates, from your CRM. Replaces the weekly “where are we at” spreadsheet.
• Job profitability — quoted versus actual cost per job, margin by job type or client, from your job management or accounting system. For construction, trades and professional services this is the dashboard that changes behaviour.
• Helpdesk and operations metrics — ticket volumes, response times, recurring issues. We use Power BI on our own helpdesk data for exactly this.

None of these require a data team. They require someone who knows the business, a few hours in Power Query, and the discipline to keep the inputs clean.

One source of truth and the governance that protects it

This is the part that separates BI that helps from BI that causes arguments. The whole value of a dashboard is that everyone trusts the number. The moment two reports disagree on last month’s revenue, people stop trusting both and go back to their own spreadsheets.

One source of truth means the definitions live in one place — what counts as revenue, when a job is “complete”, how margin is calculated — and every dashboard inherits them. In practice that means a curated dataset (a shared, governed data model) that reports draw from, rather than ten people each connecting to Xero and each calculating “profit” their own way. It also means controlling who can publish, keeping a sensible folder structure of workspaces, and not letting a sprawl of half-finished reports accumulate. For a regulated firm — a financial planner under ASIC, a clinic under AHPRA — that governance discipline is also part of keeping client data handled properly. This is the kind of thing we help with under our virtual CIO services, where the question is less “which chart” and more “what should the business be measuring at all”.

When a spreadsheet is still fine

Plenty of times. If a number lives in one place, one or two people use it, and a fortnightly manual update is no burden, Excel is the right tool and Power BI is overkill. The honest test is whether you have a data assembly problem — the same figures stitched together from several systems, by hand, again and again, with someone always asking “is this current?”. That repetitive consolidation is exactly what Power BI removes. A one-off analysis is a spreadsheet job. A report you rebuild every Monday for the rest of your working life is a Power BI job.

A Melbourne example

A commercial fit-out company in Box Hill we work with — around 30 staff — was running its whole management view off three spreadsheets that the office manager rebuilt every Monday morning from Xero exports and the job management system. It took her half a day, and by Wednesday the numbers were stale. Worse, the director’s “job profitability” sheet and the accountant’s margin figures never quite matched, so every management meeting started with an argument about whose numbers were right.

We connected Power BI to Xero and their job system, built one governed model with agreed definitions of cost and margin, and produced three pages: cashflow, job profitability and a simple pipeline view. It refreshes overnight. The Monday rebuild is gone, the two sets of numbers now agree because they come from one model, and the director checks the dashboard on his phone from site. Nothing exotic — just the same data, assembled once and trusted.

Frequently asked questions

Do I need to be a developer to use Power BI?

No. Building a useful dashboard from Xero or Excel is closer to advanced spreadsheet work than programming. The harder calculations use a formula language called DAX, but a competent finance person picks up the basics, and you only need DAX once you go beyond simple sums and trends. Most SMEs get a long way without writing any.

Is the free version enough for a small business?

Power BI Desktop is free and fine if one person builds and views reports alone. The moment you want to share a live dashboard with colleagues, each person needs a Pro licence. For most SMEs the real cost is a handful of Pro seats, not the build.

Can Power BI connect to Xero and MYOB at the same time?

Yes. A single Power BI model can combine multiple sources — Xero, a SQL database, an Excel file and a SaaS API in one report. Combining sources into one trusted view is exactly the problem it is built to solve, though messy accounting data still needs cleaning in Power Query first.

How do we stop dashboards showing the wrong people sensitive numbers?

Use workspaces to separate reporting by audience, and row-level security to filter data by viewer within a report. Combined, they let a manager see only their team’s figures while everyone opens the same dashboard. Get this set up before you share anything financial.

Getting reporting that people actually trust

Power BI is one of the better value tools a small business can adopt, but only if it is set up with clean sources, sensible licensing and the governance to keep one set of numbers honest. Done wrong it is just another spreadsheet nobody believes. TechAssist is a Melbourne-based MSP, founded in 2014, with 13 Australian-employed engineers — not an offshore call centre — and we run Power BI across our own helpdesk and on client data every week. If your management reporting is a Monday-morning spreadsheet rebuild, get in touch and we will help you turn it into something that refreshes itself.

Power Automate is Microsoft’s workflow automation tool, bundled into most Microsoft 365 plans, that lets you build flows to handle repetitive admin — routing emails, saving attachments, chasing approvals — without writing code. For Melbourne SMEs already paying for Microsoft 365, much of it costs nothing extra. The catch is knowing where the free use rights stop.

Every business runs on small, dull tasks done by hand: copying form responses into a spreadsheet, filing invoices, pinging the team when a particular email lands. Power Automate takes that work off your staff. This post covers what it does, the licensing reality nobody warns you about, cloud flows versus desktop automation, the governance traps that bite when staff leave, and when you are better off hiring a developer instead.

What Power Automate actually is

Power Automate is part of the Microsoft Power Platform, alongside Power Apps and Power BI. At its core it is a trigger-and-action engine: something happens (a trigger), and it carries out a sequence of steps (actions) in response. “When an email arrives from a client with an attachment, save it to SharePoint and post a message in Teams” is a complete, useful flow — built by clicking through a designer, not by writing code.

It connects to hundreds of services through connectors. Outlook, Teams, SharePoint, OneDrive, Excel, Forms and Planner are the Microsoft ones most SMEs use, but there are connectors for Dropbox, Salesforce, SQL databases and more. The connector lets a flow read and write data in each service on your behalf.

The licensing reality

This is where most advice online falls apart, because it either pretends everything is free or scares you off entirely. The truth sits in between.

Most Microsoft 365 business and enterprise plans include seeded Power Automate use rights. That means you can build and run cloud flows using standard connectors — the Microsoft services you already pay for: Outlook, Teams, SharePoint, OneDrive, Excel, Forms, Planner. For a large share of genuinely useful SME automations, that included entitlement is all you need, at no extra cost.

You start paying extra the moment you cross one of three lines:

• Premium connectors. Connecting to a SQL database, Salesforce, an HTTP API or many third-party systems requires a premium licence. The designer marks these “Premium”, so you find out before you build.
• Per-flow plans. Licence a single business-critical flow that many people rely on, rather than every user. Sensible when one flow serves a whole department.
• Per-user plans. Licence specific staff who build and run many premium flows. Sensible for a power user or a small automation team.

The practical rule: scope early automations to standard Microsoft connectors and you will likely stay inside what you already pay for. Microsoft reshuffles plan names and inclusions regularly, so confirm the current entitlements against your specific subscription before assuming a flow is free. Our Microsoft 365 team checks this before building anything that might trip a licence.

Cloud flows versus desktop flows (RPA)

Power Automate comes in two flavours, and confusing them leads to building the wrong thing.

Cloud flows are what most SMEs should reach for first; they are reliable because they talk to applications through proper interfaces. Desktop flows — Microsoft’s robotic process automation, or RPA — automate the screen itself, mimicking a human clicking through a Windows program. They are useful for old line-of-business software that has no API, but they are brittle: change a button’s position or a field’s name and the flow breaks. Treat RPA as a last resort for systems you cannot reach any other way, not a default.

Common SME automations worth building

These flows deliver real time savings without exotic licensing, and none need a developer to maintain once set up properly.

• Email-to-Teams alerts. When an email lands in a shared mailbox from a key client, or with a matching subject, post a card in the relevant Teams channel. Stops important messages drowning in an inbox.
• Approval workflows. Leave requests, purchase orders, expense sign-offs. The requester fills a form, the approver gets a Teams or email prompt with Approve and Reject buttons, and the outcome is logged. No more chasing managers for a yes.
• Save attachments to SharePoint. When invoices or signed documents arrive by email, file the attachment in the correct SharePoint library automatically and consistently named. Ends the “where did that PDF go” hunt.
• Form-to-spreadsheet. A Microsoft Forms submission drops straight into an Excel table or SharePoint list — bookings, incident reports, supplier details — with no manual re-keying.
• New-client onboarding. One trigger kicks off a sequence: create the SharePoint folders, generate a Planner task list, send the welcome email, notify the account manager in Teams. A checklist people forgot half of becomes one reliable flow.

A construction firm in Box Hill we work with was losing supplier invoices that arrived in a shared mailbox and got buried. We built a cloud flow that saved every invoice attachment to a dated SharePoint library and posted a notification to their accounts channel. It used only standard connectors, so it ran inside their existing licensing, and it removed a recurring source of disputes with subbies over unpaid invoices. That is the shape of a good first automation: narrow, boring, previously done by hand.

The governance and security angle

This is the part MSPs care about and most “just build a flow” tutorials ignore. A flow runs with someone’s permissions, often unattended, sometimes touching sensitive data. Left ungoverned, it becomes a liability.

Flow ownership when staff leave

Here is the scenario that catches businesses out. A capable staffer builds a dozen flows under their own account, then resigns. You disable their account during offboarding, and every flow they owned silently stops — invoices stop being filed, approvals stop routing, and nobody knows why. Critical flows should be owned by a shared service account or have co-owners, never tied to one person’s personal login. Offboarding should include checking what a leaver automated.

Data loss prevention policies

Power Automate moves data between services, which means it can also move data out of places it should stay. Microsoft’s data loss prevention (DLP) policies in the Power Platform admin centre classify connectors as business or non-business and block flows from combining the two — stopping, say, a flow that quietly copies SharePoint data to a personal Dropbox. Setting sensible DLP policies before staff start building is far easier than unwinding a mess later. Under the Privacy Act 1988 and the Australian Privacy Principles, you remain accountable for personal information your automations handle, so this is a compliance control, not just IT hygiene.

Service accounts and sprawl

Without guardrails, every department builds undocumented flows, and within a year nobody can tell you what automation is running across the business or what it touches. Govern it like any other production system: shared ownership for anything important, a naming convention, an inventory, and DLP policies set centrally. This is the same discipline behind our cybersecurity services work — who can build what, and where the data can flow.

When to use Power Automate versus hiring a developer

Power Automate is brilliant for connecting Microsoft 365 services and orchestrating standard business processes. It is not a replacement for proper software development, and pushing it past its comfort zone produces flows that are slow, hard to debug and impossible to hand over.

The honest limits: flows can be slow on large data sets, error handling is clunky compared to real code, and a flow with fifty steps and nested conditions is a maintenance nightmare that one staff departure can orphan. If you are fighting the tool to force complex logic into it, that is the signal to step back. A well-scoped flow that saves an hour a day is a win; a sprawling flow only its author understands is a future incident. Where that line sits for your business is exactly what our virtual CIO conversations are built to answer.

Frequently asked questions

Is Power Automate free with Microsoft 365?

Largely, yes — most business and enterprise Microsoft 365 plans include seeded use rights to build and run cloud flows using standard Microsoft connectors such as Outlook, Teams, SharePoint and Forms. You pay extra only for premium connectors, or per-flow or per-user plans. Confirm current entitlements against your subscription, as Microsoft adjusts inclusions regularly.

What is the difference between a cloud flow and a desktop flow?

Cloud flows run on Microsoft’s infrastructure and talk to apps through connectors and APIs — reliable, and the right default. Desktop flows are robotic process automation (RPA): they run on a Windows machine and mimic a human clicking through software, which suits legacy systems with no API but is fragile and breaks when screens change.

Do I need a developer to build flows?

For standard automations — approvals, alerts, filing attachments, form-to-spreadsheet — no. A capable staff member or your MSP can build them in the designer. You need a developer when the logic gets genuinely complex, performance on large volumes matters, or you are integrating a system with no connector.

What happens to flows when a staff member leaves?

If a flow is owned by an individual’s account and you disable that account during offboarding, the flow stops. Business-critical flows should be owned by a shared service account or have co-owners so they survive staff changes. Reviewing what a leaver automated should be a standard offboarding step.

Where TechAssist fits

We are a Melbourne MSP, founded in 2014, with thirteen Australian-employed engineers — not an offshore queue. We help SMEs identify which manual tasks are worth automating, build the flows inside your existing licensing where possible, and set the DLP policies and ownership rules so automation does not become a security hole or a single point of failure when someone resigns. If you are paying staff to do work a flow could handle, or you have a tangle of flows nobody owns properly, get in touch and we will map the quick wins before you spend a dollar on premium licences you may not need.