Before You Scale: Ten Checks From Five Real Stories

Headline and Overview

This series has looked at a quick-commerce company whose revenue and losses both grew sharply, three rivals that scale in different ways, a year of layoffs, a CEO's call for efficiency and an investor's case for going global early. This piece turns them into ten checks. It is our framework, intended as a discussion tool, not a guarantee.

1. Is each unit profitable before overhead?

Zepto's filings, as read by Inc42, showed goods costing more than they earned before delivery and rent. Compute the contribution margin on one order, customer or project. If it is negative, growth magnifies the problem.

“Scale is a multiplier. Make sure you are multiplying something that works.”

2. Which cost falls with scale?

Delivery cost per order was nearly flat for Zepto across three years of rapid growth. List your costs and mark which ones should drop as volume rises. If they do not, find out why.

3. How productive is each existing unit?

The store comparison showed a wide spread in orders per store per day. Before opening another branch, line or team, check how busy the current ones are.

4. What is the value of each transaction?

A 26% gap in revenue per order between rivals changes how much can be spent on delivery. Raising average value, through bundles, minimum orders or better mix, can be cheaper than raising volume.

5. What is your runway at today's burn?

Know it in months, weekly. The analysis of Zepto estimated a runway of three to three and a half quarters without major store additions, which shows how quickly the position changes.

6. Is your hiring tied to revenue?

The 2025 layoff data, with more than 9,500 reported cuts, showed the cost of hiring for funding that did not arrive. Link headcount to milestones achieved, not to hoped-for rounds.

7. What single rule could end your model?

Real-money gaming firms found out when a law changed. Write down your regulatory dependency and a plan for if it shifts. The Code on Social Security levy discussed in SC1 is another example of a rule that changes unit costs.

8. Where is your retention?

Opinion pieces like Amit Jain's put customer retention among the markers of success. Track repeat purchase, churn and referral rates from the beginning.

9. Do you have one proven market before you add another?

The global-expansion essay was optimistic, but its examples built a position at home first. Add a second city or country only when the first is working without your constant attention.

10. How will you treat people if it goes wrong?

Plan for the worst case: how you would reduce costs, communicate, pay what is owed and help people move on. Companies that have done this well retain trust; those that have not become examples in the layoff tables.

Using the checks

Score each one red, amber or green with evidence. Do not scale while any check is red. Two ambers are worth a conversation with your board or advisers. Review quarterly.

What the checks cannot do

They do not predict success. Some good companies fail for reasons outside their control, and some poorly run ones are lucky. They do reduce the chance of avoidable mistakes, which are the ones founders regret most.

For MSMEs

A small manufacturer or service provider can use the same list with simple tools: a spreadsheet for unit costs, a weekly cash balance, a hiring rule tied to confirmed orders, and a note of legal dependencies. The discipline, not the size, is what counts.

Our reading

The stories point the same way. Scale is a multiplier: it multiplies good unit economics into a strong business and weak ones into a large loss. The founder's job is to decide which one to multiply.

A sample quarterly review agenda

Spend the first twenty minutes on the numbers: contribution margin per unit, units per site, cash runway in months and retention. Spend the next twenty on the red and amber items: who owns each, what is the next action and by when. Close with a decision log recording what was decided and why, so that six months later you can see whether the reasoning held. Teams that keep such a log tend to learn faster, because they can compare their expectations with what happened instead of rewriting history.

When to ignore the checklist

Occasionally, a window opens that will not stay open: a regulatory change, a competitor's failure, a supplier shortage. Moving fast can then be right even if some checks are amber. The condition is that you do it knowingly, with the risks written down and a limit on how much you will commit before the evidence arrives.