The Base ARR table

• By
• Chris Burgner

  Chris Burgner

  12+ years of experience, most recently as a Director of Finance at Intercom.

  

This is the query’s building block. It’s where you’ll join across various other tables to bring in the comprehensive set of fields needed to power your ARR definitions.

Note that no calculations are made at this stage. Instead, think of the Base ARR table as a flat file with the raw material to power analysis later on in the query.

Here are some examples of the types of data you’ll want to include.

Date fields

The start and end dates associated with each primary object across the customer base.

Product and Price make-up

The IDs and names of product SKUs associated with the primary object and the frequency at which those products are billed (monthly, quarterly, annually, etc.). This detail also allows you to differentiate between service-based (e.g., implementation) and product-based revenue.

Customer and timing fields

Make sure your logic for defining a customer is included in this table. For this example, we’re assuming this happens based on the customer_id.

If you’ve decided to limit the dataset to only customers who have successfully paid an invoice, you’ll also want to bring payment data to this table.

Here’s an example of what the output should look like: