Bottom-Up Revenue Forecasting: Build From Units Sold, Not Wishful Thinking

Why Top-Down Forecasting Fails#

A top-down revenue forecast starts with a target and works backward. "We want £500,000 this year" becomes the plan. But it doesn't interrogate how £500,000 gets achieved. How many customers per week? At what average transaction value? How many new customers vs returning? What product mix? Without these operational building blocks, the forecast is a wish — and wishes don't survive contact with a slow February. When you miss the month, you don't know what changed. Was footfall down? Average spend down? A specific product category underperforming? You can't course-correct what you can't diagnose.

The Bottom-Up Framework#

Bottom-up forecasting works from the smallest unit of revenue up to the total. For a retail shop: number of transactions per day × average transaction value = daily revenue. Daily revenue × trading days per month = monthly revenue. Build each component separately and the forecast explains itself. If your forecast shows average transaction value needs to be £34 to hit your target but your last six months averaged £28, you know you need a deliberate strategy — higher-value products, upselling, bundle pricing — not just hope that it goes up.

The Five Building Blocks for Any SMB#

Traffic (footfall, website visits, bookings, inbound enquiries), conversion rate (what percentage becomes a paying customer), average transaction value (revenue per transaction), purchase frequency (how often does the same customer come back), and new vs returning customer mix. Your POS history in AskBiz gives you all five numbers for the last 12 months, broken down by week, month, and season. Changing any one of the five by 5% shows immediately in your total forecast — so you can model the impact of a loyalty scheme (frequency) or a product range extension (transaction value) before you spend a pound on it.

Seasonal Adjustment That Actually Reflects Your Business#

A bottom-up forecast is only as good as its seasonal adjustment. Your December is not the same as your August — and neither matches your April. AskBiz applies your own historical seasonal index to your forecast: if December has historically been 142% of your annual monthly average, the December forecast is 142% of the base monthly estimate. Not a guess, not industry data — your own trading pattern, applied forward. This is the difference between a forecast that's useful in September and one that's embarrassingly wrong by November.

Presenting Your Forecast to a Bank or Investor#

A bottom-up revenue forecast is the only kind that passes scrutiny in a bank lending review or investor due diligence. "We expect 22% revenue growth" is a wish. "We expect to grow from 180 to 220 covers per week by Q3, supported by two additional dinner service seatings on Thursdays, at our current £31 average spend — producing £41,600 incremental annual revenue" is a plan. AskBiz exports your bottom-up forecast with the underlying assumptions visible — transaction count, average value, frequency — in a format that demonstrates operational credibility, not just optimism.

• Top-down revenue forecasting says "we did £400,000 last year, we'll do £440,000 this year." Bottom-up says "we served 320 covers per week at £28 average spend, we'll serve 340 covers at £29 average — that's £361,660 annual revenue." The bottom-up number is grounded in operational reality.
• AskBiz builds it automatically from your POS transaction history — no spreadsheet required.