How to build realistic financial projections for your startup without sales history

If you’re just getting started, financial projections can feel like you’re making up numbers to please a bank, an investor, or even yourself. The problem is not projecting without history. The problem is projecting as if the future were a straight line.

A useful startup projection does three things: shows whether the operation fits the cash you have, indicates the sales pace the business needs to survive, and reveals where the weak points in the plan are. If it doesn’t help with those decisions, it’s just a pretty spreadsheet.

Where to start when you have no sales to look at

Without history, you don’t start from results. You start from assumptions. And good assumptions are specific, testable, and tied to real customer behavior.

The safest approach is to build the projection from the bottom up, instead of trying to guess a total revenue number for the end of the year. That means breaking revenue into simple variables:

• how many people enter your funnel each month;
• how many become leads, opportunities, or orders;
• the conversion rate into a sale;
• average ticket size;
• how often the purchase happens.

This logic works for a software startup, a service business, or a physical product company. The format changes, but the logic stays the same: volume × conversion × price.

How to estimate revenue without falling into optimistic guesswork

Revenue is usually the most poorly projected line. Founders look at the market opportunity and assume they’ll capture a large share of it quickly. In practice, the beginning is slower, more expensive, and more uneven.

A more realistic way to build the sales forecast is to work with three scenarios:

• conservative, with slow acquisition, low conversion, and a ticket closer to the floor;
• base, with execution aligned to the team’s current capacity;
• aggressive, with good traction, but still within what would be plausible.

The goal is not to pick the prettiest scenario. It’s to understand under which conditions the business survives and under which conditions it breaks.

Practical example: imagine a startup selling a recurring service for $300 a month. If it expects 40 qualified leads per month, converts 10%, and keeps churn low at the start, the first month may generate only 4 customers and $1,200 in new recurring revenue. That is very different from projecting “$30,000 in month one” just because the market looks large.

This kind of calculation forces you to face operational reality: how many leads you can generate with your current budget, how many meetings you can run, how many proposals you can send, and how many sales you can close.

Which market data helps you move beyond guesswork

Even without your own history, you can use external references to calibrate the projection. Not to copy numbers, but to define plausible ranges.

The most useful inputs usually come from four lines of reasoning:

• operational capacity: how much your team can serve, produce, or deliver each month;
• market pricing: what customers pay for similar solutions at a similar value level;
• buying behavior: decision cycle, repeat purchase rate, and price sensitivity;
• channel structure: how much it costs to generate demand, especially in paid sales or active outreach.

If you sell a physical product, you need to account for inventory turnover, replenishment lead time, and margin per unit. If you sell services, you need to consider available hours, productivity, and delivery capacity. If you sell software, the focus tends to be acquisition, conversion, retention, and revenue expansion.

The key point is this: the market is not there to prove your projection is right. It’s there to keep your projection from becoming absurd.

How to build a revenue projection in a simple spreadsheet

You don’t need to start with a sophisticated model. A lean structure is enough for the early stage.

Build monthly revenue with these lines:

1. lead or visitor volume;
2. conversion rate by stage;
3. number of new customers;
4. average ticket;
5. accumulated recurring revenue, if applicable;
6. total monthly revenue.

If it’s a subscription model, include churn as well. If it’s a one-time sale, include repeat purchases when that makes sense. If it’s a service business, account for seasonality and delivery capacity, because selling more than you can execute damages both the projection and the operation.

A simple way to test consistency is to ask: “Does the number of customers I’m projecting fit my commercial and operational capacity?” If the answer is no, the projection is inflated, even if the math works.

Which expenses you cannot forget

Another common mistake is to project revenue carefully and treat cost as a detail. In a startup, that usually gets expensive. Expenses don’t show up only in operations. They show up before operations become predictable.

Separate costs into three blocks:

• fixed: rent, salaries, software, accounting, founder compensation, internet, administrative structure;
• variable: commissions, fees, shipping, inputs, acquisition spend, delivery cost;
• initial investments: development, equipment, legal setup, branding, prototypes, initial inventory.

In practice, a realistic projection needs to show how much cash goes out before enough cash comes in to cover itself. That gap defines the initial capital requirement.

If you don’t know the exact cost of each item yet, use ranges. It’s better to work with an honest interval than with a precise number for a reality that is still uncertain.

How to turn assumptions into cash flow

Projected profit is not the same as cash available. That difference sinks a lot of startups early on.

Cash flow shows when money comes in and when it goes out. You can sell well and still run out of cash if customers pay in 30, 60, or 90 days and your expenses come due before that.

To build cash flow, track at least these points:

• date of revenue collection;
• date of payments to suppliers and staff;
• average collection period;
• average payment period;
• starting cash balance;
• monthly working capital need.

If your startup depends on installment payments or contracts billed after delivery, cash can get tight even while revenue grows. That’s why the projection needs to show the balance month by month, not just the annual total.

A realistic projection example for the first months

Let’s say we have a B2B service startup starting with a lean team and selling monthly contracts worth $2,000.

In the base scenario, it can:

• generate 60 leads per month;
• convert 10% into meetings;
• convert 25% of meetings into customers;
• close 1.5 new customers per month on average at the start;
• generate $3,000 in new monthly revenue.

If the operation loses a few customers along the way, recurring revenue grows slowly. By month three, it may have 4 to 5 active contracts, totaling somewhere between $8,000 and $10,000 in monthly recurring revenue, not $30,000 or $50,000 like the more optimistic spreadsheets often show.

Now look at the cost side. If the company spends $6,000 per month on structure, tools, and minimum operations, plus invests in acquisition, cash is still under pressure. The relevant question becomes: how long can this company last until revenue covers monthly costs?

This kind of example is useful because it shows the real business dynamic. The projection stops being an isolated number and becomes a sequence of decisions.

Which mistakes distort startup financial projections the most

Some mistakes show up almost every time. Avoiding them already improves the quality of the analysis a lot.

1. Confusing demand with sales. Not every sign of interest becomes a customer.
2. Projecting conversion too high. Early on, the real rate is usually lower than expected.
3. Ignoring the ramp-up period. Some sales take weeks or months to close.
4. Forgetting about cash. Accounting profit does not pay overdue bills.
5. Underestimating acquisition cost. Selling can cost more than it seems.
6. Treating a single scenario as truth. The business has to survive even when the base case does not happen.

If your projection only works with very favorable assumptions, it isn’t realistic. It’s fragile.

How to review your assumptions without starting over

A financial projection is not a document to file away and forget. It needs to be updated as real market signals appear.

Create a simple monthly or biweekly review routine. Compare projected versus actual across three dimensions:

• lead or opportunity volume;
• conversion rate by stage;
• average ticket and collection period.

If volume is below expectations, the issue may be acquisition. If leads are coming in but not converting, the problem may be the offer, the price, or the sales message. If sales happen but cash is tight, the issue may be collection terms or cost structure.

That reading is more valuable than trying to get the projection right on the first try. In a startup, the quality of the process matters more than the illusion of precision in an initial number.

When the projection is good enough to make a decision

You don’t need a perfect projection to move forward. It is good enough when it answers practical questions clearly:

• how much money I need to start and for how long;
• what minimum revenue the business needs to sustain itself;
• which scenario is still viable without new funding;
• which assumptions affect the result the most;
• what I need to validate first in the market.

If your spreadsheet answers those questions honestly, it has already done its job. The goal is not to predict the future with precision. It’s to reduce the chance of starting in the dark.

If you want to structure these assumptions faster, it’s worth setting up the projection from the start as a living scenario you can revise as you learn from the market. You can begin now, with the numbers you already have and the ones you still need to validate in the field. Start here.