Static Friction Almost Finished Me Before I Even Started

Running a business is a friction problem. Not a competition problem, not a motivation problem. Friction. The force that stops you from starting. The cash flow gap that turns revenue into a trap. The untested channel that quietly drains working capital. The manual process that taxes every working hour.

This is a collection of 4 essays drawn from six years of running a security services firm. Each piece stands alone. Read all four or just the one relevant to where you are right now.

• Why you haven’t started yet.
• Why big revenue can be a slow trap.
• Why you should test small before you commit.
• Why boring software beats a new client.

The Year I Planned Everything and Started Nothing

Crisis is a more reliable forcing function than motivation.

Static friction is always higher than kinetic friction. Once something is moving, it takes less force to keep it going than it did to start it. I did not learn this in a physics class. I learned it the hard way — by staying still for a full year.

In 2018, I quit my job with Rs 40 lakh saved. Living with my parents kept monthly expenses at Rs 30–50K. That gave me 26 months of runway. I spent none of it on actually starting anything.

Not because I lacked ideas. I had dozens. The problem was I kept searching for the perfect idea — venture-scale, defensible, elegant. So I planned. I read. I mapped markets. I built spreadsheets for businesses I had not started. I talked to people about ideas I had not tested. Every week felt productive. Every week, nothing moved. Planning is the most socially acceptable form of procrastination because it looks like work. It has deliverables. It has momentum. It just has no force behind it.

I was applying zero force and wondering why nothing moved.

Then my father died in 2019. He left behind a security services firm: Rs 1.45 crore in monthly revenue, 700 guards on payroll, clients expecting service by Monday. No time to find the perfect idea. No time to plan. Just move.

That forced movement taught me the thing I had spent a year refusing to learn.

External force overcomes static friction faster than internal motivation ever will. Crisis did in one week what personal discipline had failed to do in 12 months. I was not suddenly more focused or more disciplined. I simply had no option but to act. The friction did not disappear — I just stopped waiting for it to.

If I were starting again in 2018, I would not wait for a forcing function to arrive from outside. I would manufacture a smaller version of one. Start something on the side while still employed. Run it until it generates Rs 1 lakh in monthly profit for four or five consecutive months. Save 18 months of expenses before quitting.

The savings buffer is not excess caution. It preserves the risk appetite that a corporate salary was quietly providing without you noticing. Monthly expenses multiplied by 18 gives you the number. That is the only formula that matters before you quit.

The physics is simple. Static friction is always the highest point. The hard part is applying the first force — before crisis does it for you.

Rs 48 Lakh In. Rs 14K Out.

Revenue without cash flow is a liability disguised as growth.

In 2021, I spent two months negotiating a Rs 48 lakh monthly contract. It was 30% of my total revenue at the time. The headline numbers looked clean. I almost signed.

Revenue: Rs 48L per month. Capital expenses upfront: Rs 45L. Fixed costs: Rs 1.2L per month. Net profit on paper: Rs 1.5L per month. Any operator would look at that and nod.

Then I ran the actual cash numbers.

Tax deducted at source removed Rs 96K per month before I touched the money. Interest on the working capital loan I needed to deploy the contract cost Rs 40K per month. Actual cash in hand after both: Rs 14K per month. I had Rs 45 lakh locked up to earn Rs 14K monthly. At that rate, I needed 32 months just to recover the capital — and that assumed perfect execution with zero problems for nearly three years.

Revenue without cash flow is a liability disguised as growth.

I spent two more months trying to negotiate 15-day payment terms instead of 30-day. The client refused. I walked away from Rs 48 lakh per month.

Not because I am disciplined. Because the numbers showed I would suffocate. The contract looked like scale. It was actually a slow trap — one where a single missed payment or early exit by the client would have wiped out the working capital entirely.

The mistake most operators make is stopping at the revenue line. The real question is not what comes in. It is what stays liquid and when. Every contract has a cash conversion gap — the time between deploying your resources and receiving payment. That gap has a cost. Calculate it before you sign, not after.

For any large contract, I now run three numbers before anything else. Cash actually received per month after TDS and financing costs. Time in months to recover upfront capital. What happens to the business if this client exits in month six.

If the third number is “serious damage” — the contract is not worth taking regardless of the revenue figure.

Rs 48 lakh per month sounds like a win. Rs 14K in hand per month on Rs 45L deployed is a four-year trap. The difference lives entirely in the cash flow math.

Test Small or Pay Full Price Later

Cheap experiments protect runway — test before you commit.

In 2021, I ran Google and LinkedIn ads for the first time. The logic was simple. Security contracts run Rs 3–4 lakh annually. If I could acquire a client for Rs 2–3K, I would recover that cost within two months from margins. Clean math. I put Rs 50K into the test.

Twenty leads came in. Two became paying customers. Actual cost per customer: Rs 25K — ten times my target.

Instead of a two-month payback, I was looking at 12 months per customer. And that assumed they stayed. In a competitive market where clients switch on price, one exit stretched payback to 18 months per acquisition. I stopped the experiment immediately.

Rs 50K tuition is acceptable. A Rs 5 lakh commitment to an untested channel would have put real pressure on working capital. That is the only reason I ran a small test first — not strategy, not discipline. I simply did not know if it would work.

Most operators skip the small test. The thinking goes: if the idea is good, go big. If it fails small, it will just fail slowly. Both assumptions are wrong.

A small test does not tell you if the idea is good. It tells you the real unit economics before you scale them. Twenty leads and two conversions sounds like a bad campaign. It is actually precise data: this channel, at this price point, in this market, costs Rs 25K per customer. Now I can decide with that number rather than the one I assumed.

The question to ask before any new channel or initiative is not “do I believe in this?” Belief is not a business metric. The question is: what is the smallest spend that gives me real conversion data? Run that. Read the number. Then decide.

For me that number was Rs 50K. For your business it may be different. But there is always a version of the experiment that costs less than a month of working capital. Find that version. Run it first.

Rs 50K told me the channel did not work for my business at my margins. A Rs 5 lakh commitment would have told me the same thing — six months later, with a real cash problem attached.

Nobody Celebrates This. It Worked Anyway.

Reducing operational friction compounds quietly — unglamorous fixes outperform new clients.

Nobody celebrates migrating to payroll software. There is no story in it. No moment of insight. You move data from one system to another, test it twice, and go back to work. I did it in 2020 during the COVID lockdown, when I could not go to the office and manual processes had nowhere to hide.

Before: Excel payroll, failing 5–10% of the time. Each error meant hours of correction and a guard who received the wrong amount. Guards talk. Credibility damage compounds faster than revenue. After: error rate under 0.5%. Twelve hours a week recovered. Guards stopped calling about payment mistakes.

Then I moved accounting to Zoho Books. Previously, we tracked in Excel, entered manually into Tally, and waited three days to know our cash position. After: real-time visibility into receivables, expenses, and cash balance. Three days became three minutes.

Neither of these felt like progress at the time. Both changed how the business actually ran.

With payroll handled reliably, I stopped being the error-correction layer. With real-time cash visibility, I stopped making decisions on three-day-old numbers. I did not hire anyone. I did not win a new contract. I just removed two friction points that had been quietly taxing every working hour.

The result: I could run 10–15 smaller contracts at Rs 4–5L each instead of depending on one large contract. More billing complexity, handled without adding founder hours.

Operational friction is the cost you pay every single day without seeing the invoice. A 5% payroll error rate across 700 guards is not one problem — it is hundreds of small problems landing weekly, each one stealing time and credibility. Software that reduces that error rate to 0.5% is not a technology decision. It is a compounding return on every future hour you would have spent fixing mistakes.

Current state after both changes: Rs 1.3 crore monthly revenue. Cash conversion at 37 days, down from 52. Founder hours the same despite more clients.

Same input force. More output. That is what reducing friction does — quietly, without anyone noticing, until the numbers are simply better.

Same Force, Less Resistance

Four observations. One idea underneath all of them.

Friction is not the enemy. It is information. Static friction tells you the minimum force needed to start. Cash conversion friction tells you which contracts will suffocate you. Acquisition friction tells you what a channel actually costs before you scale it. Operational friction tells you where your hours are quietly going.

Most operators fight the wrong battles. They chase new clients when the real problem is a 52-day cash cycle. They plan new channels when a Rs 50K test would give them the actual number. They hire when bad software is the real bottleneck.

The work is not glamorous. Walking away from Rs 48L per month is not a highlight reel moment. Migrating to Zoho Books is not a growth story. Running a small ad test that fails is not a win.

But each one removed a friction point. And friction removed compounds — in recovered hours, in working capital freed, in decisions made on real numbers instead of assumptions.

Find the friction. Remove it. Then move.