Most startups that fail between Seed and Series A do not fail because the market was wrong. The market is often exactly what the founder believed it to be. They fail because the company ran out of money before the market materialised — and they ran out of money because of five financial decisions that were made, or not made, in the first 18 months.
These are not exotic mistakes. They are common, predictable, and almost always avoidable. The founders who make them are not financially illiterate — they simply did not know what they did not know.
Confusing bookings with revenue.
A booking is a signed contract or a verbal commitment. Revenue is cash received (or earned under a delivered contractual obligation). The gap between the two has destroyed more founder confidence than any other accounting distinction.
A founder who counts a signed annual contract as "₹24 lakhs ARR" from day one — when the customer has not yet gone live, the implementation is incomplete, and the payment schedule is quarterly — is reporting a number that does not exist yet. When the board asks for a cash position update and the founder says "we're at ₹80L ARR," and the bank account shows ₹12L, the credibility problem is not the cash balance. It is the ARR number.
Use recognised revenue (delivered and earned) for financial reporting. Use bookings and ARR for business momentum reporting. Keep the two in separate columns and never let one substitute for the other in a cash planning conversation.
Building a cost structure for the plan, not the likely outcome.
The plan shows revenue growing from ₹20L to ₹1.2 Cr in 12 months. The founder hires to match that trajectory: 8 salespeople, 4 engineers, an office, a marketing budget. The revenue comes in at ₹45L. The cost structure, built for ₹1.2 Cr, has been running at full rate for 11 months.
This mistake has a specific name in startup finance: over-hiring ahead of revenue. It is the most common way a pre-Series A startup burns through a Seed round in 14 months instead of 24. The right discipline: hire to what you can confirm, not to what you plan. Add capacity in 2–3 person increments, triggered by demonstrated revenue milestones. A lean team at ₹45L ARR that hits ₹80L ARR in 6 months can hire rapidly from a position of strength. A bloated team at ₹45L ARR is managing a performance improvement plan while watching the runway shrink.
Every hire before product-market fit is a bet. After PMF, it is an investment. Know which one you are making.
Ignoring unit economics until the Series A process.
Unit economics — CAC, LTV, payback period, contribution margin per transaction — are not investor metrics. They are operational health indicators that tell you whether the business model works at the level of a single customer or transaction. Founders who do not track them operationally discover the truth in the worst possible context: sitting across from a Series A investor who has spent more time with their data than they have.
The typical scenario: a founder walks into a Series A process with 18 months of growth data. The investor asks for cohort data. The founder produces blended averages. The investor finds, on closer examination, that the 6-month cohort retains 40% of revenue while the 12-month cohort retains 22%. The LTV, calculated properly, is 35% of what the pitch deck suggested. The process slows, or stops.
Track CAC by channel, LTV by customer cohort, and contribution margin per transaction from month one. Not for investors — for yourself. These numbers tell you which acquisition channels to double down on, which customers to prioritise, and whether the business model is improving or deteriorating as you scale.
| Mistake | How common | Cash impact | Recovery difficulty |
|---|---|---|---|
| Booking vs revenue confusion | Very common | High | Moderate |
| Over-hiring ahead of revenue | Very common | Very high | Hard (headcount cuts) |
| Ignoring unit economics | Common | Medium | Hard (process build) |
| No 13-week cash forecast | Very common | High | Easy (build one now) |
| Fundraise timing error | Common | Terminal risk | Sometimes impossible |
Not running a 13-week cash forecast.
A 13-week rolling cash forecast is the most important financial document a pre-Series A startup can maintain. It is not a budget (annual targets) or a financial model (3-year projections). It is a week-by-week view of when cash comes in, when it goes out, and what the closing balance is at the end of each week for the next 3 months.
Without it, founders discover cash crises when they arrive, not before. With it, you see a problem 8 weeks out and have time to act: slow hiring, chase receivables, approach investors with momentum rather than desperation, or negotiate a short-term bridge from existing investors.
The discipline is minimal: one person, two hours per week, updating actuals from the bank statement and rolling the forecast forward. Every startup that has run one consistently tells the same story: it saved them once, usually at a moment they did not realise they needed saving.
Starting the fundraise 3 months before you run out of money.
Fundraising at the pre-Series A stage takes 3–9 months in most cases. The process of finding investors, running meetings, entering due diligence, negotiating term sheets, and closing legal documentation is not a 6-week exercise. Founders who begin serious fundraising when they have 90 days of runway are fundraising from a position of visible desperation. Investors know. The term sheet that arrives — if it arrives — reflects that knowledge.
The rule: begin your Series A process when you have 9–12 months of runway remaining and 6 months of demonstrated metrics growth. Arriving at an investor conversation with 9 months of runway and a clear inflection in your numbers is a completely different dynamic than arriving with 90 days and a story about why the next quarter will be different.
The financial mistake is not starting the fundraise too late — it is not tracking the runway precisely enough to know when 9 months remaining actually is. That requires the 13-week cash forecast from mistake four. The five mistakes are, in the end, connected. They compound each other. Avoiding one makes the others easier to avoid.