Lime CRM Power BI dashboard
We load customers, deals and renewals from Lime CRM into a single Power BI model. For DPG Media, we turned subscriber data into targeted actions.
With our analysis of subscriber data, DPG Media turned its data into actionable steps
“Working with DSL enabled us to turn our data into actionable steps, resulting in targeted and effective campaigns and activations.” Mascha Wijker, Communication Manager, DPG Media.
Who won’t renew, and could we have seen it coming?
Lime CRM records who your customers are, what’s in progress and when contracts expire. If you want to track churn, renewals and deals over time alongside revenue and usage, bring that data together in your own model.
Customer retention only becomes clear when you look at relationships, deals and usage side by side
Cancellations and renewals
Which customers cancel or renew, by segment and period, and which contracts are due to expire soon.
Deals by stage
How many deals are at each stage, how long they stay there and how many are won.
Usage alongside customer relationships
For DPG Media, we found patterns in product usage associated with a lower likelihood of cancellation.
One customer across all sources
Lime CRM alongside your accounting data and your product or online shop, with a single customer number as the key.
Your application's data model determines what we retrieve
-
Key and data model
An API key with read-only access, plus the objects and fields from your Lime application.
-
One question, figures cross-checked
For example, churn over one year, compared with your own figures in Lime CRM.
-
Expand and refresh
More objects and sources, permissions for each team, and a data-loading schedule that respects the limits.
Are Lime CRM’s own reports enough?
A good fit if
You want to track churn, renewals and deals over time, compare CRM data with revenue or usage, or stop circulating a monthly export.
Not a good fit if
There are few cancellations and renewals each year, or contracts aren’t recorded in Lime CRM. Then there isn’t enough data to spot a pattern.
What determines the scope
How many objects and custom fields your application has, whether you use Lime CRM Cloud or your own server, and how many other data sources are involved.
Will loading data affect our users?
Lime CRM Cloud has a limit per IP address. We therefore retrieve only what has changed, at a quieter time, so your colleagues won’t notice.
Lime views, an export or a model via the Query API?
Views in Lime CRM
Choose this if account managers mainly need to see what’s happening with each client and which contracts are due to expire.
An annual analysis
Choose this if you want to find out once a year why customers left. A one-off analysis is enough in that case.
A model via the API
Choose this if you want to track customer churn over time or include other data sources. Our advice: start with renewals and cancellations.
We worked with subscriber and fan data for media and ticketing
For DPG Media, we analysed subscriber data; for See Tickets, ticketing and behavioural data. Data Science Lab has been operating since 2016 and is a Microsoft Partner and Databricks Partner.

Our conversation starts with the customers you don’t want to lose
Stef Stoelwinder
Business DevelopmentStef is your point of contact. In our first conversation, we’ll discuss how you’ve set up Lime CRM and which customer metrics you’re missing.
E-mail info@datasciencelab.nl
Phone +31 (0)20 3636 724
Which customers do you want to find out about first: will they stay?
Tell us whether you use Lime CRM Cloud and where you keep contracts and invoices. We’ll reply by email or invite you to a conversation.
Message sent
Thanks for your message. We’ll be in touch as soon as possible.
Frequently asked questions
Through the Lime CRM REST API. According to Lime, the Query API is intended for complex queries and reading large amounts of data. We load the data at scheduled times, then build the Lime CRM Power BI model on top of it.
To learn where a dashboard starts, read about Power BI dashboards.
An API key. According to Lime, the key is tied to a user and that user’s permissions apply. We ask for a dedicated user with read-only access to the data the model needs.
Note that creating a new key invalidates the previous one, so we store it securely.
Each Lime application is configured for its organisation, with its own objects and fields, and therefore has its own API documentation. These objects often include organisations, people, deals, contracts or memberships.
That documentation is our starting point.
Churn and renewals by segment, deals by stage and salesperson, activities by customer, and revenue by customer alongside accounting data.
If you want to identify customers at risk of cancelling, read about predicting churn.
Yes. For Lime CRM Cloud, Lime specifies a limit per IP address; on a self-hosted server, the administrator sets the limit. We therefore load only what has changed.
We agree on the loading schedule with your administrator.
Yes. Usage often tells you the most about who will stay. For DPG Media, we found patterns in product usage associated with a lower likelihood of cancellation.
To do this, each customer must be identifiable in both sources.
Yes, deals by stage and salesperson are often included. If your focus is on the pipeline and campaigns, also read about the Efficy CRM Power BI dashboard.
Here, the focus is on customer retention.
If cancellations are recorded only in emails and not as a status in Lime CRM. In that case, there is nothing to count, and the starting point is data quality.
We’ll tell you that in the first conversation, too.