What does a Cirqll dashboard for contracts show?

In Cirqll you see for each contract what was agreed: with whom, for what amount and until when. That is fine for looking up a single contract. But the questions a business owner asks are about the whole. How much is fixed each month? What expires this quarter? Is the contract base growing or quietly shrinking?

For that you need a total across all contracts, with your own definitions and a comparison over time. That is the job of a dashboard. Where a Cirqll sales dashboard looks ahead at what might come in, this dashboard shows what has already been agreed and what you stand to lose if nobody acts.

Who is this for? Mainly companies with maintenance, service or subscription contracts, where a good share of revenue is recurring. If you only work on one-off projects, your management information is more likely to be in deals and assignments.

Which 5 KPIs belong in a contract dashboard on Cirqll?

Start small. These five numbers answer most questions:

  1. Recurring revenue per month. The total of all active contracts, with yearly amounts divided by twelve. Everything else depends on this number. Multiply it by twelve and you have the annual value.
  2. Value expiring soon. The monthly amount of contracts with an end date within 30, 60 and 90 days. Not just the count: one large contract weighs more than five small ones.
  3. Expiring contracts without owner action. Contracts expiring within 90 days while the customer has no open task or planned appointment. This is your work list.
  4. Inflow and outflow per month. How much contract value was added this month and how much dropped off. Together they say more than the total: a stable total can mean you are running hard just to stay in the same place.
  5. Share of your five largest customers. What percentage of your recurring revenue comes from your top 5? That shows how vulnerable you are if one leaves.

The third leads to action straight away. The first and fifth are mainly for the monthly management meeting. Keep those two uses apart: an overview page for the conversation, a work list for the account manager.

Which Cirqll data do you need?

Everything comes through the Cirqll API. According to the API documentation (as of 3 November 2026) a contract has these fields:

  • The customer and the user the contract belongs to.
  • Name and description.
  • Start date, end date and reminder date.
  • Price and price type. The price type determines whether the amount applies per month or per year.
  • A calculated price. The documentation does not explain how it is calculated, so do not trust it blindly. First compare it with a few contracts whose amount you know.
  • Archive date, creation date and update date.

Contracts also support custom fields. You can use those to record a contract type or product group, for example, and split your figures on it. For the work list you also need tasks and appointments, and for the customer analysis the customers.

How do you build the dashboard in Power BI?

If you already have a report on Cirqll, you build this on the same connection. How that connection works is explained in Connecting Cirqll to Power BI. A setup in six steps:

  1. Load contracts, customers, tasks and appointments and link them through the customer. Add a date table.
  2. Create a column with the monthly amount. If the price type is per month, take the price. If it is per year, divide by twelve. Check in your own environment which value belongs to which type before you start calculating with it.
  3. Define what "active" means. For example: the start date has passed, the end date has not, and the contract is not archived. Also agree what to do with a contract without an end date: does it count as ongoing, or is it an entry error?
  4. Calculate the position per month. A contract counts in every month in which it was active. That gives you a line over time, plus inflow and outflow.
  5. Build one overview page and one work list. The five KPIs at the top, the development per month below. On the work list, the expiring contracts sorted by value, with the owner next to them.
  6. Check and refresh. Have someone who knows the contracts recalculate the totals. Refreshing once a day is more than enough, because contracts do not change by the minute.

A few practical points up front. Cirqll returns dates in UTC, so an end date around midnight can look like the previous day if you do not correct for it. And the contract only holds the current price. If you later want to see what a contract delivered a year ago, including before a price increase, you have to store the position yourself. How that works is explained in Cirqll data in your own database.

Example: a facilities company with 120 contracts

A fictional example to make it concrete. A facilities service provider has 120 running maintenance contracts in Cirqll: 90 with a monthly amount averaging 450 euros and 30 with a yearly amount averaging 6,000 euros.

The first version of the report simply adds up the price fields and arrives at 220,500 euros. That looks like a nice monthly total, but it is wrong: monthly and yearly amounts have been added together. With the price type included, the sum looks like this:

  • 90 contracts x 450 euros = 40,500 euros per month
  • 30 contracts x 6,000 euros / 12 = 15,000 euros per month
  • Total: 55,500 euros in recurring revenue per month, or 666,000 euros per year

Then it gets interesting. Within 90 days, 18 contracts expire, together worth 9,000 euros per month. That is over 16 percent of recurring revenue. Seven of them have no task or appointment. That list goes to the account managers on Monday morning.

It also stands out that the five largest customers together make up 28 percent of the total. No drama, but a good reason to start the renewal conversation with those five well in advance, rather than waiting until the end date comes into view.

Where does a contract dashboard usually go wrong?

  • Mixing monthly and yearly amounts. As in the example: without the price type, every total is nonsense. Make the monthly amount the only column you calculate with.
  • Renewals that count twice. If your team creates a new contract on renewal and leaves the old one in place, the same customer counts double for a while. If the end date is simply moved instead, you see no inflow or outflow. Either can work, but choose one and agree on it.
  • Contracts that are never cleaned up. A contract cancelled long ago but still active inflates your total. Show a list on the dashboard of contracts without an end date, without a price or with an end date in the past.
  • Contract value is not revenue. The dashboard shows what was agreed, not what was invoiced. Cirqll does not invoice itself. To see the two side by side, combine Cirqll with your accounting, for example through the Moneybird integration.
  • Looking without acting. An expiring contract on a dashboard does not renew itself. If you want the owner to get a task automatically, that is a job for Make.com. We describe it in Automatically following up Cirqll contracts with Make.com.

Help with your Cirqll dashboard for contracts

Would you rather not build this dashboard yourself? On our Cirqll page you can read more about the Cirqll Power BI Connector and the dashboard template. The template focuses on pipeline, analysis and appointments; exactly which tables you need is something we align with your setup. Also see what we do in dashboarding and data engineering, or how workflow automation makes renewals independent of anyone's memory.