https://github.com/dbt-labs/mrr-playbook

https://github.com/dbt-labs/mrr-playbook

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/dbt-labs/mrr-playbook
• Owner: dbt-labs
• Created: 2019-11-15T14:45:35.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2022-10-11T03:51:03.000Z (over 1 year ago)
• Last Synced: 2024-04-13T18:38:33.943Z (2 months ago)
• Language: Makefile
• Homepage: https://blog.getdbt.com/modeling-subscription-revenue/
• Size: 479 KB
• Stars: 82
• Watchers: 4
• Forks: 56
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Lists

• awesome-dbt - mrr-playbook - A worked example to demonstrate how to model subscription revenue. (Sample Projects)
• awesome-dbt - mrr-playbook - A worked example to demonstrate how to model subscription revenue. (Sample Projects)
• awesome-dbt - mrr-playbook - A worked example to demonstrate how to model subscription revenue. (Sample Projects)

README

        
# Monthly Recurring Revenue (MRR) playbook.

This dbt project is a worked example to demonstrate how to model subscription

revenue. **Check out the full write-up [here](https://blog.getdbt.com/modeling-subscription-revenue/),

as well as the documentation site for this project [here](https://www.getdbt.com/mrr-playbook/#!/overview).**

Note that this project is not a package -- it is not intended to be installed in

your own dbt project, but instead provides a good starting point for building

similar data models for your own business.

The SQL in this project is compatible with Snowflake¹.

If you want to run this project yourself to play with it (assuming you have

dbt installed):

1. Clone this repo.

2. Create a profile named `playbook`, or update the `profile:` key in the

`dbt_project.yml` file to point to an existing profile ([docs](https://docs.getdbt.com/docs/configure-your-profile)).

3. Run `dbt deps`.

4. Run `dbt seed`.

5. Run `dbt run` -- if you are using a warehouse other than Snowflake, you may

find that you have to update some SQL to be compatible with your warehouse.

6. Run `dbt test`.

-----

1. We decided to _not_ make the SQL multi-warehouse compatible since this project

is intended to be a demonstration, rather than a package. Making this project

multi-warehouse compatible would complicate the SQL.