Business Plans With No Unit Economics at All — Why Reviewers Dock Points Immediately

#

Most founders who skip unit economics entirely aren't hiding anything on purpose. Far more often, they've decided 'I'll add this once the data builds up' or 'it's too early to know.' That judgment call is exactly the problem.

From a reviewer's perspective, a unit economics gap reads one of two ways. Either the founder doesn't know the concept at all, or they know it and avoided it because the numbers would look bad. Either way, it costs points — the first is a business-literacy problem, the second is a trust problem.

This matters most for subscription and platform businesses, where recurring revenue is the core strength — and unit economics is the only way to actually prove that strength. Skip it, and the strength never rises above an unsupported claim.

1. They decide there's no data yet because it's early, and skip the section entirely.
2. They confuse revenue projections with unit economics, treating them as the same thing.
3. They write revenue per customer but leave out customer acquisition cost.
4. They don't even recognize that they're supposed to state assumptions.
5. They mistakenly believe the financial plan section already covers it.

#

Government grant reviewers and investors read business plans differently. But they react to a unit-economics gap in almost exactly the same way. The moment a reviewer hits the financial plan page and sees a graph of revenue climbing sharply year over year, they automatically look for one thing: where is this growth actually coming from? Without an answer, the graph itself stops being persuasive.

Concretely, points get docked in two specific situations. One: there's a customer count target, but nothing on what it costs to acquire those customers. Two: there's a monthly subscription price, but nothing on how many months the average customer sticks around. Miss both, and the entire financial plan collapses into a list of numbers with nothing behind them.

When an investor spots this gap, they often won't even book the meeting. A government-grant reviewer will dock partial points on that item. In both cases, the founder gets the outcome without ever knowing exactly why they were turned down.

#

There's a pattern OpenSeed's analysis keeps confirming: a business plan with no unit economics at all tends to reveal similar gaps in other areas too. It's rare for unit economics to be the only thing missing. Usually, the signals below show up together, as a bundle.

1. Market size (TAM) is written up big, but there's no realistically reachable customer segment (SOM).
2. There's a marketing strategy, but no cost estimate for any channel.
3. There are year-by-year customer targets, but no retention assumption.
4. The revenue model states a price, but no assumption about transaction frequency or subscription length.
5. There's a claimed price advantage over competitors, but no explanation of the margin structure.
6. Customer acquisition cost is entirely absent from the cost line items in the financial plan.

When these signals show up together, reviewers land on one conclusion: this founder has never broken the business down to the level of a single customer. There's a total revenue target, but no sign that anyone traced how that revenue actually accumulates from the behavior of individual customers.

Platform businesses face a more complex version of this, because both suppliers and demand-side customers exist. Often, the phrase 'two-sided market' shows up without the plan ever deciding which side's acquisition cost should be calculated first. In these cases, reviewers start doubting whether the founder understands the platform structure at all.

#

When reviewers ask for unit economics, they're rarely expecting precisely measured, real numbers. They know as well as anyone that an early-stage startup can't have cohort data on hundreds of users. The problem isn't the lack of data — it's the lack of even an assumption.

What reviewers actually want to see is this: given what this founder currently knows, what assumption did they make, and how do they plan to validate it? A competitor's public numbers, an industry average, a small pilot's results — whatever the basis, as long as an assumption is stated explicitly, the logic survives even when the data is thin.

A business plan with no assumptions at all, missing the unit economics section entirely, ends up with a hole in its logical structure. The numbers in the financial plan become impossible to trace back to their origin, and reviewers lose any basis for trusting them.

#

Without unit economics, numbers that should connect to each other throughout the business plan end up isolated. Customer targets, revenue projections, marketing budget, breakeven point — these all need to tie together into one logic through unit economics as the connective tissue. Without that connector, each figure scatters into its own disconnected claim.

As reviewers read a business plan, they naturally trace this chain: how will you get 1,000 customers → how much ad spend does that take → how much does each customer pay per month, and for how long → so when do you break even. Without unit economics, that chain breaks. To a reviewer, that break reads as a credibility problem for the entire business.

This hits subscription businesses especially hard. The core strength of a subscription model is recurring revenue. But without knowing how long that revenue actually lasts, or how much needs to be spent upfront to generate it, the subscription structure can end up reading as nothing but risk — 'spend heavily now, recoup later, maybe.'

For the specific formulas and examples on how to build assumptions and honestly estimate numbers when data is thin, see the OpenSeed blog post 'Bottom-Up Revenue Estimation: Formulas, Examples, and a Practical Template.' If reading this article has confirmed that your own business plan is missing unit economics, we'd recommend that piece as your next step.

#

Here are the questions OpenSeed users ask most often about unit economics, along with the answers.

1. Q: We're B2B SaaS, and unit economics gets complicated because our customers are companies. Do we still need it? — A: Yes. Business customers still get calculated the same way — cost to acquire one account, and revenue generated over the life of that account. Complexity isn't a valid reason to skip it.
2. Q: We're a platform with both suppliers and demand-side customers. Which side should the numbers be based on? — A: Calculate for whichever side you need to acquire first (whichever side you're prioritizing in the chicken-and-egg problem), then present the other side alongside it. Simply stating, and explaining, which side comes first demonstrates that you understand your own platform.
3. Q: The government grant template doesn't have a dedicated unit economics field. Where should it go? — A: Even without a dedicated field, it fits naturally inside the revenue model or commercialization strategy section. Building a separate table or callout box for it also works well.
4. Q: I'm worried that writing out unit economics will make our numbers look bad. — A: An unfavorable number is less damaging than no number at all. Present even a currently unfavorable figure alongside a path to improving it, and it can actually earn you credit for transparency.
5. Q: Does an OpenSeed review flag a unit economics gap? — A: Yes. Whether unit economics is mentioned at all, whether assumptions are stated explicitly, and whether it logically connects to the financial plan are all part of what gets analyzed.