Best Of

The "DISTINCT" in your COUNT(DISTINCT) will make it so each student is only counted once across whatever level of aggregation you are using in your card. Since students tend to be the same across fall/spring/summer, your count across the terms will be closer to the count of a single term than the sum of the terms. That might be the desired behavior in some cases, as it would be useful to know how many distinct students you have in a given year.

But students typically enroll/pay by term, so it sounds like you want to get a sum of the distinct students by term. If that's the case, you should add a "FIXED" to your beastmode. Something like this:

SUM(COUNT(DISTINCT STUDENT ID) FIXED(BY Term) )

As an addendum, I think those super wide tables with just a couple rows are hard to scan. To me, it's a lot easier to read across long lists of numbers in columns:

Here's an approach:

I think you should group your metrics by 'Revenue' and 'Costs'

Then, to get that Total row that is a different aggregation (% gross margin) than your value, a BeastMode that tricks the pivot table into doing that for you:

Then a pivot table:

One of the options on subtotals is to add padding, which acts to separate the categories and the total row. You can also play with the grid lines on the subtotals to create more visual separation from the raw values. Since Revenue only has one category, you can leave it collapsed. You can also suppress single-item groups, but then you lose your padding for revenue.