A revenue number sounds decisive until a leader asks, “Compared with what?” A total on its own can’t say whether a segment is winning because more people are booking, or because each booking is larger.
“Beginner trips generated $1.14 million in booked value” is accurate. It’s also incomplete.
I learned that the hard way after taking over an 80-page monthly leadership deck that used to eat someone’s entire weekend to assemble. The reporting still needed the one thing it was missing: a comparison, and a decision it could inform.
That’s the job of The So What Framework. Give a number a baseline, a comparison, and a decision it can support.
Add context in three layers
1. Start with the headline number. Booked value shows the size of each difficulty segment.
2. Add the measure that explains it. Booking count separates a large audience from a high-price offer.
3. Compare before recommending action. Average booking value shows the premium position of advanced trips.
I ran this against the live Summit Adventures database, the fake adventure tourism company I created to help people learn business analytics, to put booked value in context by trip difficulty.
SELECT
e.difficulty_level,
COUNT(b.booking_id) AS bookings,
SUM(b.total_amount) AS booked_value,
AVG(b.total_amount) AS average_booking_value
FROM bookings AS b
JOIN expedition_instances AS ei
ON ei.instance_id = b.instance_id
JOIN expeditions AS e
ON e.expedition_id = ei.expedition_id
GROUP BY e.difficulty_level
ORDER BY booked_value DESC;
Results:
| Difficulty | Bookings | Booked value | Average booking value |
| — | —: | —: | —: |
| Beginner | 578 | $1,143,754.41 | $1,978.81 |
| Advanced | 354 | $1,105,286.89 | $3,122.28 |
| Expert | 283 | $773,339.96 | $2,732.65 |
| Intermediate | 385 | $764,169.43 | $1,984.86 |
Two different leaders. Two different stories:
Beginner trips lead in booked value. More people, more bookings.
Advanced trips lead in average booking value. Fewer people, larger tickets.
The total on its own could have pointed Summit toward beginner trips. The context tells a fuller story: volume in one segment, price in the other. Those call for different decisions about marketing, pricing, and guide capacity.
Turn a revenue total into a recommendation
Answer one or more of these before your stakeholder has to ask:
1. Baseline. The overall booking and value mix by difficulty.
2. Comparison. Advanced trips have fewer bookings than beginner trips but a larger average.
3. Trend. A time-series query would show whether either segment is gaining or losing momentum.
4. Decision. Summit might test whether advanced-trip demand supports more premium inventory.
SQL is only half the job. The other half is explaining what the result lets a team decide.
Don’t let the total do all the talking
A total needs a denominator. More booked value can mean more bookings, larger bookings, or both.
A comparison needs a purpose. Add a measure because it changes the decision, not because the query can produce it.
A recommendation still needs a test. Higher average value may support more premium inventory. Demand over time and available capacity still matter.
Say the comparison out loud
Try this in the meeting:
> “Beginner trips generate the most booked value because they bring more bookings. Advanced trips have fewer bookings, but each one is worth more on average. Let’s check demand and capacity before we choose which segment to expand.”
Total, explanation, next decision. Works better than sending a table and hoping the reader draws the same conclusion.
This Week’s Action Item
Find one metric you report often. Add a count, an average, or a segment comparison beside it. Write one sentence explaining the decision the added context makes easier.
Want More SQL Insights Like This?
Join thousands of analysts getting weekly tips on turning data into business impact.