Home market
Fractional CTO for Indian Startups
India is where I live and where I built most of my six ventures, so this is the one market where I am not the remote option. I have hired here, lost good engineers to attrition here, sat with hardware manufacturers here, and shipped products that had to survive Indian network conditions and Indian payment rails. Most searches for a fractional CTO in India come from two kinds of founders: an Indian founder with a funded company and no senior technical leadership, or a US, UK, or Gulf founder who wants to build their engineering team in India and needs someone senior on the ground.
I work with both. What I do not do is compete with the dev shops. If you want the cheapest possible build, there are hundreds of agencies who will quote you a number. If you want someone who owns the technical decisions, hires and runs the team, and answers to you as a CTO would, that is the engagement. Some founders here call this a virtual CTO or a part-time CTO; the work is the same.
How this actually works
What is different about building in India
The DPDP Act is now an engineering requirement
The Digital Personal Data Protection Act moved consent, purpose limitation, data principal rights, and breach notification from good practice into law, and the rules put concrete obligations on how you store and process personal data. Most early-stage products in India were built before any of this existed and have no consent ledger, no deletion path, and no way to answer a data principal request. I design these in from the start, or retrofit them before they become a funding diligence problem.
RBI localisation and the payments stack
If you touch payments, RBI's data localisation rules mean payment data stays in India, full stop, and your gateway, your database region, and your analytics pipeline all have to respect that. UPI changes the product too: recurring mandates, autopay limits, and settlement behaviour are different from cards, and building for cards first then bolting UPI on is how you end up with a checkout that half your Indian users abandon.
Scale arrives earlier and cheaper than you planned for
Indian consumer products can go from a few hundred users to a few hundred thousand on one good week, often on low-end Android devices over patchy 4G. Payload size, offline tolerance, and cost per request matter here in a way they simply do not in the US. My largest single production run was 500,000 assessments in one hour on infrastructure I designed; I know what breaks first.
Hiring is easy, retaining is the hard part
India has the deepest engineering talent pool in the world and one of the highest attrition rates. A fractional CTO who has hired here knows which signals actually predict a good engineer, how to structure ESOPs and titles so people stay through a Series A, and how to keep a Bengaluru, Pune, or Hyderabad team coherent when half of it is remote. If you are a foreign founder, I will also tell you honestly what a senior engineer actually costs here now, which is not the number from five years ago.
GST, invoicing, and the compliance surface nobody budgets for
GST e-invoicing, TDS on vendor payments, and the paperwork that comes with taking money from Indian customers all end up as engineering work sooner or later. It is unglamorous, it is mandatory, and it is far cheaper to model in the schema on day one than to bolt onto a live billing system.
Building for India, or from India, are different products
A product for Indian users needs regional languages, low-bandwidth tolerance, and UPI. A product built in India for US or UK customers needs SOC 2 readiness, US data residency, and a team that can work on a US calendar. I have done both, and the biggest mistake I see is founders in one lane copying the architecture of the other.
How an engagement runs
Week one, month one, month three
Week 1
I find out what is actually true
Architecture review, codebase read, and honest conversations with every engineer you have. You get a written assessment at the end of it: what is solid, what is risky, what is going to break, and what it costs to fix each one. No slide deck, just a document you can act on.
Month 1
The bleeding stops and the roadmap becomes real
I fix or contain the things from week one that were actually urgent, and rebuild the technical roadmap so it has dates you can believe. If you are hiring, the role is written and the interview loop exists. If you are pre-launch, scope gets cut, usually by a lot.
Month 3
It runs without me in the room
Ship cadence is predictable, the team knows the standard, security and infrastructure are at the level your customers expect, and the decisions are documented. If the engagement is a bridge to a full-time CTO, this is where I start hiring my replacement.
Why me, for this specifically
Experience, not a capabilities deck
Plenty of people can advise on india startups. Fewer have shipped in it, been wrong in it, and had to fix it with their own name on the commit. Here's what I'm bringing.
- Based in India, working in IST, with real overlap for US mornings and UK afternoons
- Six ventures as technical co-founder across India, the UAE, and the USA, several built with Indian engineering teams
- M.Tech in Cybersecurity from NIT Kurukshetra, directly relevant to DPDP and RBI expectations
- Have hired and run engineering teams in India, and know what it takes to keep them
Engagement
Scoped on a call. Not from a rate card.
Every engagement here is shaped around the stage of the company, the size of the team, and how many days a week you actually need. Thirty minutes on a call is enough for me to tell you what I would do, how I would structure it, and whether I am the right person for it.
Questions
India startups, specifically
Is a fractional CTO the same as a virtual CTO or a part-time CTO?
In practice, yes. Fractional CTO is the term used in the US and UK; in India the same engagement is often searched for as a virtual CTO or a part-time CTO. In every case it means a senior technical leader who owns your architecture, hiring, and delivery for a fixed number of days a week, without a full-time salary or equity grant.
What does a fractional CTO engagement cost in India?
For Indian founders I scope and quote each engagement individually, because the right structure for a seed-stage startup and a Series A company are not the same. Book a call, tell me where the company is and what you need, and we will work it out on that call.
I am a US or UK founder. Can you set up and run my engineering team in India?
Yes, and this is one of the engagements I enjoy most. I hire the team, set the engineering standards, run the delivery, and report to you. You get a senior person on the ground who has done this before, rather than an agency account manager.
Do you work with Indian startups that are not yet funded?
Sometimes, usually as a technical advisor rather than a fractional CTO, and occasionally as a technical co-founder for equity if the problem is right. The honest answer is that a fractional CTO retainer only makes sense once there is enough money and enough product for senior technical leadership to change the outcome.
More general questions about cost, commitment, and how this compares to a full-time CTO are answered on the main fractional CTO page.
Earned, Not Claimed
What the founders and teams I build with say
Kunal Vohra, founder of Panicletech, has been an incredible technology partner and a great friend. His dedication is rare. Whether it's solving an unexpected challenge, brainstorming a complex feature, or stepping in when something needs urgent attention, Kunal is always there. He approaches CashMyCell as if he were building his own business, and that level of commitment has been invaluable.
Jitendra Mansharamani
Founder, CashMyCell
Kunal is one of those technical leaders whose work you can't help but follow. Even without having worked directly alongside him, the impact of his engineering vision and the standard of execution he brings to the tech community are clear. He consistently demonstrates what high-level technical direction should look like: sharp, innovative, and focused on real business value.
Raman Sawhney
AWS Architect
We worked with the Panicle team in our early stages. They've been helpful and collaborative. They understood our early requirements and helped us go live.
Jeevant Sarma
Co-Founder, Thought Pudding
Building in india startups? Let's talk.
Thirty minutes. Tell me what you're building and where it's stuck, and I'll give you a straight answer on whether I can help.
Book a 30-min callSend me a message