From Markets to a Real Operating Plan: Economics & Financial Modeling

Economics gets taught as theory and used as intuition. The two ends of it that matter most to me are the most micro (how prices and quantities actually move in a market) and the most practical (how a company turns those forces into a plan it can afford). Here's the bridge between them.

The microeconomics you actually use

A market is just a group of buyers and sellers of a good or service. Buyers as a group set demand (how much they're willing and able to buy at a given price); sellers as a group set supply (how much they're willing to provide at a given price). Two laws govern the dance:

• Law of demand: quantity demanded rises as price falls, and falls as price rises.
• Law of supply: as price rises, suppliers become more willing to supply, because higher prices mean higher profits.

The concept that ties it together is elasticity — how responsive quantity is to a price change. When a 1% price change produces a less than 1% change in quantity demanded, demand is inelastic (people keep buying despite the price). That single idea explains most pricing decisions: inelastic demand means you have room to raise prices; elastic demand means you don't.

And the laws have real exceptions worth remembering, because they're where pricing intuition breaks:

• Demand exceptions — luxury/Veblen goods (higher price can signal status and raise demand), necessities, income changes, herd/demonstration effects, expectations of future price changes, and shifts in taste or fashion.
• Supply exceptions — perishables and agricultural products (which can't simply be held back for a better price), rare goods, and out-of-fashion goods.

Finally, distinguish a movement along the demand curve (a change in quantity caused by the good's own price — expansion/contraction) from a shift of the curve (caused by something else entirely — income, tastes, substitutes). Confusing the two is how people misread why their sales changed.

From theory to a plan you can afford

Most founders track exactly two numbers: revenue and bank balance. That's fine right up until the hard questions arrive — what if churn spikes for three months? what if the raise lands late but payroll doesn't wait? what if a new hire doesn't ramp on schedule? Those questions are where a real FP&A (financial planning & analysis) model earns its keep. It does three things bookkeeping can't:

1. Runway intelligence — how long the company lives at current and planned burn. 2. Resource allocation — what you can hire, launch, or spend, and when. 3. Investor credibility — whether your plan reflects how the business actually runs.

The line that reframed it for me: "Bookkeeping tells you where the money went. FP&A tells you what you can afford next, and when." That difference is everything when your decisions burn cash. When an investor asks "what happens if we cut growth by 20%?", a real model answers in thirty seconds.

What a "real" model actually has

A serious operating model isn't a single revenue line stretched across columns. It's a fully linked, three-statement model — Income Statement, Balance Sheet, and Cash Flow that all reconcile — typically run monthly over a multi-year horizon, with the moving parts wired together:

• Inputs & assumptions as a single control panel — business profile, scenario, growth rates, ARPU, churn, seasonality.
• A revenue schedule driven by the model type (subscriptions = subs × ARPU; transactional = units × AOV; capacity-based), handling deferrals properly.
• A headcount schedule with month-by-month hiring and loaded comp (salary + burden + raise cadence) — because people are usually the biggest, lumpiest cost.
• Opex, working capital (AR/AP/inventory timing), and capex (which auto-drives depreciation), all flowing into the statements.
• Finance events — equity raises and debt — hitting the right month and staying in balance.
• Scenario modelling built in (Base / Bull / Bear) so you can flip assumptions and watch the impact in real time.
• And Use-of-Funds + Valuation outputs that pull automatically, so the board deck isn't a copy-paste exercise.

The first-use flow is a clean cascade: set the global switches → populate the driver blocks → revenue calculates from drivers → costs and headcount build month by month → working capital and capex auto-calculate → finance events go in → and the three statements populate themselves. Drivers in, statements out.

A couple of disciplines that keep it honest: don't mix business models in one file (duplicate it and run clean assumptions instead), and update monthly — actuals versus plan, as part of the review cadence. A model you never reconcile against reality is just a nicely formatted guess.

The throughline

The two ends of economics meet here: markets tell you how price and quantity move (and elasticity tells you how much room you have); a real operating model tells you what those forces mean for what you can afford and when. Track more than revenue and bank balance, wire your assumptions to three reconciling statements, model the scenarios before they happen — and you replace anxiety with a plan you can actually defend.