Why a Power BI dashboard when Teamleader already shows margin?

Teamleader Focus already does a lot. If you track projects, hours and invoices in Teamleader, you can see per project how much budget has been used and what the profit is. According to Teamleader's help documentation (checked on 16 November 2026), the package calculates used budget as billable hours plus materials, times the sales price. For a project manager watching one project, that is exactly enough.

The questions of a managing director or operations manager sit one level higher:

  • Across all projects. Which three projects are running furthest over budget? Which type of job consistently earns less?
  • Over time. Is billability lower this quarter than last? Is the work still waiting to be invoiced growing?
  • Next to other sources. Does project revenue match what is in the accounts? How do the hours relate to the planning or the contract hours in your HR software?

That is what Power BI is for. Teamleader remains the place where the work happens; Power BI becomes the place where you steer it. If you are mainly interested in deals and pipeline, read sales dashboard in Power BI with HubSpot or Teamleader. This article is about the other half: what happens after the deal is won.

Which 5 KPIs belong on a Teamleader project dashboard?

These five answer most questions of a project-driven SME, such as an agency, consultancy or installer. The broader management overview is in the 10 KPIs every SME dashboard needs.

1. Billability

The share of billable hours in all registered hours, per employee, team and month. In Teamleader you mark every time entry as billable or not, so the source is there. Which target suits you depends on the role: an account manager books fewer billable hours than a specialist. Set an expectation per role rather than one number for everyone.

2. Work in progress

Billable hours and materials that have been delivered but not yet invoiced, expressed in euros. This is money you have already earned and not yet asked for. In the Teamleader API, a time entry has billing information next to the "billable" flag, so you can see whether an hour is already on an invoice. Show the total per customer and by age: work from two months ago is a different conversation than work from last week.

3. Budget usage per project

Used budget against planned budget, for all running projects in one list. Use the same calculation rule as Teamleader, so your dashboard matches what the project manager sees in the package. It gets interesting when you put usage next to progress: a project at 80 percent of its budget that is only halfway done is something you want to see now, not at the final invoice.

4. Project margin

Revenue minus costs per project, and then per customer and per type of job. Teamleader calculates the cost of hours with an internal cost price per user and the revenue with the external hourly rate. Non-billable hours increase costs but not revenue. For fixed-price projects the revenue is the agreed amount, so there you see straight away what overruns cost.

5. Lead time from work to invoice

The number of days between the moment work is delivered and the moment it is on an invoice, and then until it is paid. A long lead time means you are pre-financing your work. Put this number next to the outstanding invoices per customer and you see at a glance where your money is stuck.

Which Teamleader data do you need for this?

You do not need a full copy of Teamleader for these five KPIs. These parts are enough:

  • Time entries: who, when, how long, on which work type and subject, billable or not, and whether the hour has been invoiced. According to Teamleader's API documentation the duration is in seconds, so convert to hours before you add things up.
  • Projects: customer, status, billing method, budget and any phases.
  • Invoices: date, amount, status and customer. For payment behaviour also the due date and whether the invoice has been paid.
  • Users and teams: to link hours to people, roles and teams.
  • Cost prices and hourly rates: check during the inventory whether you can fetch them through the API. If not, record them in a small table of your own with a start and end date, so a rate change does not alter last year's figures.

One point of attention: Teamleader has a new projects module alongside the older one, each with its own parts of the API. There is a separate call to see which version your account uses. If your history sits partly in the old and partly in the new module, your data model needs to read both.

How do you get your Teamleader data into Power BI?

On 16 November 2026 we did not find a standard Microsoft connector for Teamleader Focus in Power BI. There are third-party connectors, and Teamleader has a public API. So you roughly choose between a third-party connector and your own data pipeline on the API. The trade-offs are covered in what a data pipeline is and how to set one up.

For a project dashboard one thing weighs extra heavily: volume. Time entries quickly become the largest table in your model, because every team books hours every day. A few practical facts from Teamleader's documentation (checked on 16 November 2026):

  • The API uses OAuth 2.0. You register an integration through the Teamleader Marketplace and grant only the permissions the dashboard needs.
  • There is a limit of 200 requests per minute per integration per Teamleader account. Lists are returned page by page.
  • Teamleader recommends using filters, so you only fetch what you need and do not run into that limit.

In practice this means: fetch old hours once and after that only a recent period, for example the last few weeks, because hours still get corrected afterwards. Store them in a data layer of your own and let Power BI read only from there. How we set up the integration itself is explained on the page connecting Power BI to Teamleader Focus.

An example: the project meeting at a communications agency

A fictional example. A communications agency with fourteen employees works entirely in Teamleader Focus: deals, projects, hours and invoices. The project managers know their own projects well. Even so, management only learns at the end of the quarter which customers have cost money.

The Power BI dashboard gets one overview page and one detail page:

  1. At the top: work in progress in euros, split by age: under two weeks, two to six weeks, older.
  2. On the left: billability per team per month, with the expectation per role as a line.
  3. On the right: all running projects with budget usage and progress, sorted by the largest gap.
  4. Detail page: margin per customer and per type of job over the past twelve months, with a drill-through to the project.

The weekly project meeting starts with the list on the right. Projects burning through their budget faster than they progress are discussed before they go over budget. And the monthly invoicing round starts with the work in progress, oldest first.

How do you start? A plan in five steps

  1. Decide on the questions. Pick two or three questions that pinch most right now, for example "where is our uninvoiced work?" and "which projects are overrunning?". Start there, not with all five KPIs at once.
  2. Write down the definitions. What counts as delivered work? Do internal projects count towards billability? Which cost price do you use for freelancers? Write it down and have a project manager review it.
  3. Check your setup. Are hours on the right project and marked correctly? Are cost prices and hourly rates filled in per user? Do projects have a budget? A dashboard makes gaps in the registration visible, but does not fill them.
  4. Build the integration and a first page. Fetch hours, projects, invoices and users and compare the totals with what Teamleader itself shows. Only when they match does the dashboard go into the meeting.
  5. Use it and refine. Take it to the next project meeting. What is missing, what is unclear, what is not used? Adjust it and only then expand.

Wondering which licences you need for this and what they cost? Read what Power BI costs in 2026.

Where does a Teamleader project dashboard usually go wrong?

  • Hours that change afterwards. Hours get corrected later, moved to another project or made non-billable after all. So do not only fetch new hours, but also refresh a recent period again.
  • Fixed price and time-and-materials mixed up. For a fixed-price project, work in progress means something different than for a project billed by the hour. Include the billing method in your model, or a fixed-price project will appear to have months of uninvoiced work.
  • Cost prices nobody maintains. A margin is only as good as the cost price behind it. If internal cost prices are still at the level of three years ago, every margin looks too rosy.
  • Billability as a scorecard. Hours per person are sensitive information. Teamleader itself can hide financial project information from users without admin rights. Carry that choice over to Power BI with permissions per role, and use the number to distribute work, not to judge people.
  • Two project modules. If your history sits in both the old and the new projects module, you quietly miss part of your projects when you only fetch one.

Help with your Teamleader Power BI dashboard

Want a project dashboard on your Teamleader data without working with APIs, tokens and data models yourself? We build the integration, the data layer and the dashboard, and agree the definitions with the people who will use it. See the Teamleader integration with Power BI, read what we do in dashboarding and data engineering, or read how we work.