Service vs Product: The Biggest Problem in Indian Tech

Services are an amazing business for the first decade of an ecosystem. They provide cash flow, training, international exposure, and jobs. They built Infosys, TCS, Wipro. They employed millions. They are the reason Bangalore is Bangalore.

After that first decade, services become something else — a ceiling dressed as a floor. They keep you comfortable while quietly preventing you from ever capturing the real value you are creating. We are somewhere between year 25 and year 30 of Indian tech. We have been standing on the ceiling for a while.

The economic math, honestly

Let me run the numbers, because the gap is bigger than most people realise.

A services engineer bills, say, $40 an hour. Forty hours a week is $1,600. Maybe 80% utilisation is $1,280 effective per week. Scale that to a year, decent senior engineer, maybe $75k–$100k revenue per head to the company. Company takes maybe 40%. Engineer gets a percentage of the margin as salary.

A product engineer at a company whose product has 10,000 paying users at $50/month — $6M ARR — contributes meaningfully to that $6M ARR. If the company has 20 engineers, that is $300k of ARR per engineer, generated continuously, with compounding. Same engineer, same skill — completely different economics.

It gets worse. Product revenue compounds. Services revenue has to be re-earned every quarter. Over a decade, a product engineer is generating $3M+ per head; a services engineer is generating $1M. Same person. Different wrapper.

Why the transition is hard

If the math is that obvious, why does everyone not just switch? Because the switch is painful in very specific ways that nobody talks about.

• Cash flow from services is addictive — monthly, predictable, no sales cycle. Products are lumpy
• Product bets kill margins for quarters at a time. Services companies have shareholders and investors who hate that
• Founders who know how to sell hours do not always know how to sell licenses. Different sales motion, different org structure
• Hiring changes — product teams need PMs, designers, data people. Services companies have delivery managers
• The entire company culture is optimised for billable utilisation. Product culture is optimised for bets and iteration. These do not coexist easily

The three failure modes of the transition

I have watched this transition go wrong three ways:

• "We'll build a product on the side while running services" — the services always win for attention, the product dies
• "We'll spin up a separate product team inside the services company" — they starve for talent and priority
• "We'll turn our best client project into a product" — almost never works, because what one client needs is not what the market needs

The pattern that works is harder: treat the product as a separate company, separate P&L, separate culture, separate team. Let it live or die on its own merits. Do not subsidise it forever from the services cash flow, and do not let the services culture infect it.

Why the transition is worth it anyway

Because the ceiling of services is a fraction of the ceiling of products. The largest Indian services company is about $50B market cap. The largest Indian product companies are a small fraction of that, but growing at rates services companies can never match. In ten years, the market cap rankings will look different.

More importantly — products create leverage. One great product can serve millions with marginal cost near zero. No services engagement scales like that. The 25-year-olds who build in products instead of services will have careers that look nothing like their parents'.

What this means for you personally

• If you are at a services company and comfortable, question whether comfort is the right goal for your next decade
• If you are at a services company, try to work on a product-shaped engagement — one where you own outcome, not hours
• If you are starting out, strongly consider joining a product company over a services one, even for less pay early on
• If you run a services company, at least one serious product experiment is your responsibility to your team

The generational framing

Services built this industry. They were the right bet for the first generation. Products will define the next generation. The people who bridge the gap — who took services money and built products with it, or who jumped from services to products early — will be the ones with the most interesting careers in 2035.

Services are how we started. Products are how we scale.