This change will cause data team into the bad pattern of trying to cram as much into a model as possible rather then splitting them up into sub models that can

This change will cause data team into the bad pattern of trying to cram as much into a model as possible rather then splitting them up into sub models that can be used for multiple use cases. From the docs https://docs.getdbt.com/docs/cloud/billing#what-counts-as-a-successful-model-built https://docs.getdbt.com/docs/cloud/billing#what-counts-as-a-... `Models are counted when built and run` so running a 200 model dbt project 3 times a day would just about hit the 20k limit a month. Given a year ago dbt cloud was $50 per seat without usage based pricing, building your own ci/cd system with github actions is the way to go with dbt these days.