Brand Experience
Semi-Private

Scaling Too Fast: Expensive Lessons from a 2016 Business

An expensive lesson about scaling a business: my ignorance as a young director, ambition without systems, and naivety that always said yes drained both capital and team morale.

Started: 2016-01-15
Ended: 2016-12-31
1 year
6 min read
Context

In early 2016, I was appointed as Operations Director at a transportation business. I was in my early 20s with minimal business experience, holding a director-level position but employee status with a salary. Investors demanded aggressive expansion within 6-12 months through purchasing hundreds of units at once. I led operations and execution.

Important admission: I wasn't ready to shoulder that level of responsibility. Naivety, embarrassment about asking questions, and ignorance made me approve nearly every directive without verifying what was actually needed.


Major Mistakes
1. Not Asking Questions Due to Naivety

A work plan was presented: acquire hundreds of units, break-even projection by month 6, profit by month 12. Basic questions I never asked:

  • "Has the unit economics been proven at small scale?"
  • "What if our assumptions are wrong?"
  • "How can we test this model with minimal risk?"

I said yes to too many directives, felt directors must always appear confident, and feared looking disruptive. Blind trust in projections without validation became the first expensive mistake.

2. Expansion Without Ready Systems

We bought hundreds of units at once. Capital flowed toward purchases, storage, logistics, and operational overhead.

What we didn't have:

  • Proven consistent customer acquisition channels
  • Tested operational workflows
  • Validated pricing strategy
  • Management systems ready to handle large capacity

After capital was absorbed, pressure emerged: execute fast, revenue must come in now. Decisions shifted from rational to emotional. We bet entirely on optimistic scenarios without cushions.

3. Ignoring Warning Signals

Entering months 7 through 9, reality diverged far from projections:

  • Customer acquisition costs tripled
  • Conversion rates far lower
  • Revenue only 40% of target
  • Operational costs 150% of estimates
  • Cash burn alarming

My response was wrong: push the team harder, seek external excuses, rationalize bad data. Naivety and lack of experience made me keep following the most optimistic advice instead of stopping for evaluation.

4. Cash Flow Crisis and Exit Decision

Months 11 through 12:

  • Capital nearly depleted
  • Revenue far behind
  • Cash burn impossible to sustain
  • Operating runway shrinking fast

We planned only for success. No plan B, no staged investment, no stop criteria. After honest evaluation: the model wasn't working, fixes would require more capital without certainty, team morale collapsed, and I had no solution. We accepted the loss and exited.


Core Lessons
1. Own Capital First, Funding Later

Investor money made us lazy about validation. With other people's money, I skipped assumption testing, didn't build solid systems, and delayed difficult questions.

Own-capital mentality preserves sanity:

  • Every dollar matters → rigorous testing
  • Limited cash → forces building systems that work
  • Can't hide behind funding → face facts faster

Healthy sequence: prove the model with your own money, then use external funding for acceleration. The less you need funding, the more ready you are to receive it.

2. Systems Before Expansion

Expansion without systems only amplifies dysfunction. What should have been done:

  • Validate at small scale
  • Prepare working systems for 10 units before buying 100 units
  • Test assumptions with cheap, low-risk experiments
  • Treat expansion as a reward earned by solid systems

Essential question: what must be true for expansion to succeed? Positive unit economics, reliable operations, repeatable customer acquisition, understood cash flow cycles.

3. Test Assumptions Systematically

Projections are just assumptions. Optimism bias exists in every plan.

Practical steps:

  1. Identify critical assumptions
  2. Rank by impact and uncertainty
  3. Design cheap tests
  4. Execute, record data
  5. Update confidence
  6. Repeat until confident or stop
4. Build Large Safety Margins

Reality tends to be worse than optimistic plans: revenue comes late, costs rise, surprises always exist.

Build safety margins:

  • Revenue: prepare for only 50% of projections
  • Costs: assume 150% of estimates
  • Time: multiply by two
  • Cash reserves: double them

If the business can't survive the bad scenario, delay.

5. Naivety Can Drain Capital

Naivety made me ignore warning signals and delay honest evaluation.

Practice intellectual humility:

  • Always potentially wrong
  • Seek what's being missed
  • Distinguish between facts and hopes

When data speaks, cut losses without shame. Sunk costs are already gone; future decisions must be based on future value. Have the courage to say "no" when data doesn't support it.

6. Cash Flow is Reality

Businesses die from cash flow long before a profit and loss statement records the cause. Projected revenue does not pay bills.

Obsess over cash flow:

  • Monitor daily cash balance
  • Know cash burn with precision
  • Calculate operating runway regularly
  • Set "circuit breakers": if cash < X, stop

Validated Patterns
Second-Order Effects

Actions trigger chain consequences:

  • Fast expansion → appears to win market
  • Without systems → operational chaos
  • Chaos → unsatisfied customers
  • Customers leave → reputation collapses
  • Bad reputation → death spiral
Negative Compounding Effects

Small ignored problems accumulate:

  • Week 1: assumptions slightly off → "it's okay"
  • Month 3: strategy built on flawed assumptions → "can be tuned"
  • Month 6: capital absorbed, poor results → "push harder"
  • Month 9: crisis phase → "how did we get here?"
Negative Feedback Loops

Bad results → pressure → worse decisions → worse results. Breaking the cycle requires honest evaluation, courage to change direction, even exit.


Reinforced Mental Models
  • First Principles Thinking: Break problems into elemental components. What must be true for this model to work? How to validate at lowest cost?
  • Inversion: Ask what guarantees failure. We did everything: expansion before proof, ignored customer feedback, no safety margins.
  • Margin of Safety: Plan for worst-case scenarios: revenue down 50%, costs up 50%, time doubles.
  • Second-Order Thinking: See layered consequences. Fast expansion only makes sense with solid foundations.

How I Work Now

Before taking opportunities, I ask:

  1. What assumptions support this plan?
  2. How to test cheaply?
  3. What's the worst-case scenario?
  4. Are safety margins sufficient?
  5. What signals mean we should stop?
  6. Am I seeing facts or wishes?

Current approach:

  • Start with small experiments
  • Validate model at minimal scale
  • Challenge assumptions aggressively
  • Set clear circuit breakers
  • Monitor cash flow itself, treating projections as secondary
  • Exit when data commands

Impact and Learning

Real losses:

  • Capital: hundreds of millions of rupiah (tens of thousands USD)
  • Time: 12 months
  • Revenue: only 40% of target
  • Profit: never achieved

Personal growth:

This experience forced me to master risk evaluation, first principles thinking, and building safety margins. This expensive lesson shaped how I evaluate businesses today.

Financially: not worth it. As learning: priceless, though painful.


Closing

This story is a record of my ignorance as a young director, ego that blocked learning, execution without foundation, and lessons born from failure, told without aiming to blame anyone.

Thanks to all parties who gave me opportunities despite my unreadiness. This experience taught things not found in textbooks.

For young professionals: don't repeat my mistakes. Know your knowledge limits, ask questions, learn fundamentals, and don't let ego block growth.

Key Lessons

  • Validate with your own capital before seeking external funding

  • Build systems first, then scale up

  • Test assumptions incrementally, don't trust raw projections

  • Prepare large safety margins for worst-case scenarios

  • Naivety is expensive; learning to say no and verify saves money and teams

Behind This Experience

Patterns Validated

Mental Models Applied

Share this experience:

Related Experiences

amhar
Loading...