How Revenue Scenario Modeling Improves Decision Making

What building a fintech pricing model taught me about evaluating decisions, not just making them

I built a revenue scenario model for a hypothetical fintech product․ No client‚ no team․ Just raw financial data and a question: if you had to choose between five different pricing and product strategies‚ how would you actually know which one was worth betting on? By the end of it I realized that the really interesting part was what you do with the model․ It was what the model forced me to do before I could even build it - define what "better" meant‚ in numbers‚ before making a single decision․

The Setup

I started with raw data and used SQL and Python to extract‚ clean and prepare the data․ I then built an Excel scenario model to determine the financial impact of 5 different pricing and product strategies on revenue․ I boiled this down to a two-page Power BI executive summary and a 12-slide presentation that a non-financial professional could look at and understand the trade-offs in under five minutes․

What Scenario Modeling Actually Does

One misconception about a revenue model is that it's a prediction machine: if you just put in the right assumptions‚ it'll spit out a number that tells you what to do․ That's not really what happened here․ The model didn't give me an answer‚ it forced all of the assumptions behind each strategy into the open․ Before I could even see my five different pricing strategies on paper‚ I had to think through my churn assumptions‚ adoption rates‚ and cost structure․ Much of the work was completed before the first output․

I compared strategies side by side in the form of trade-offs․ Rather than intuitively deciding whether a premium-tier strategy 'feels' stronger than a volume-based one‚ this approach compared the projected revenue‚ risk and assumptions of different business models against each other․
It exposes which assumptions actually drive the outcome․ Small changes in churn or adoption rate shifted the ranking between strategies more than I expected - which is important‚ as it tells us where to focus our due diligence as we make commitments‚ not after․
However‚ this reframes the question from 'which strategy is best' to 'which strategy is best under which conditions'‚ which is a more honest question as it is impossible to predict the future․

Why This Matters for Decision Making, Not Just Analysis

If it's a model that only an analyst can read‚ it doesn't inform the decision that is made․ It just sits in a folder․ That's why I built the two-page summary and the slide deck alongside the model itself: the goal was to get five strategies and their trade-offs in front of a non-technical decision-maker in a form they could actually act on․ A scenario model is only defensible if someone not involved in the analysis can look at it and see the trade-off clearly enough to defend a choice․

That's the shift in how I think about analyst work now․ All that technical stuff - SQL‚ Python‚ the model itself - is necessary but not sufficient․ The harder‚ and ultimately more valuable‚ challenge is putting those five spreadsheets of assumptions down into a single page for the decision maker to hold in their head․

The Honest Caveat

This was a self-built portfolio piece exploring some theoretical strategies․ No one ever used it to arrive at a pricing strategy‚ and I don't know how the scenarios would have played out with real customers․ What I do know is that the process taught me to think about pricing strategy in a different way: make the assumptions explicit and comparable before anyone has to commit to one․

The Takeaway

Good decisions are not a result of better guessing․ Good decisions come when we've made the trade-offs visible enough that a reasonable person‚ having other opinions‚ can challenge our assumptions․ That's what a good scenario model does: it doesn't try to predict the future‚ but rather makes the bet you're placing on it legible to everyone who has to live with the outcome․