Core learning screen

Ravi Kulkarni

From Mechanical Engineer to SaaS Founder

Founder and CEO in SaaS · Pune, India

I want early professionals to understand that non-linear career paths are valid and often powerful.

View biography

Career Timeline

First Job2012 - 2015
Operations Engineer
PrimeMotion Industries
I started in manufacturing operations with intense process pressure and unclear visibility. The shop floor was a fast-paced environment where mistakes could halt production. I had…
Show moreShow less
ContextI started in manufacturing operations with intense process pressure and unclear visibility. The shop floor was a fast-paced environment where mistakes could halt production. I had to quickly learn how to manage teams, troubleshoot machinery, and ensure safety compliance. There was little room for error, and the stakes were high for both quality and efficiency. Communication between departments was often fragmented, making it hard to see the full workflow. Over time, I realized the importance of systems thinking and proactive problem-solving to keep operations running smoothly.
ChallengesI optimized local tasks without understanding upstream and downstream dependencies.
LearningsSystems thinking matters more than isolated optimization in operational roles.
OutcomeBuilt a strong operational base that later supported business and founder decisions.
Skills acquired
Operations ManagementProcess MappingTeam Coordination
AdviceUnderstand the end-to-end workflow before proposing improvements.
Education2016 - 2018
MBA Candidate
IIM Ahmedabad
I transitioned from engineering execution into business strategy and finance frameworks. The MBA program was a whirlwind of case studies, group projects, and networking events. I…
Show moreShow less
ContextI transitioned from engineering execution into business strategy and finance frameworks. The MBA program was a whirlwind of case studies, group projects, and networking events. I was exposed to new ways of thinking about markets, competition, and value creation. Balancing academics with internships and extracurriculars was challenging, but it helped me develop time management skills. I learned to analyze problems from multiple perspectives and present solutions to diverse audiences. This context broadened my understanding of how businesses operate and prepared me for leadership roles.
ChallengesI initially tried to master every domain at once, which diluted my execution depth.
LearningsDepth in one area with broad awareness is better than shallow generalization.
OutcomeExpanded from technical execution into strategic decision-making and product thinking.
Skills acquired
Business StrategyFinancial ModelingProduct Thinking
AdviceUse education as an acceleration layer, not a replacement for real execution.
Startup Launch2020 - Present
Founder and CEO
BuildPilot
I launched a SaaS startup in a competitive market with limited initial resources. The early days were filled with uncertainty, long hours, and constant iteration. I wore many…
Show moreShow less
ContextI launched a SaaS startup in a competitive market with limited initial resources. The early days were filled with uncertainty, long hours, and constant iteration. I wore many hats—product manager, salesperson, marketer, and customer support. Every decision felt critical, and mistakes were costly. Building a team and culture from scratch required patience and resilience. I learned to celebrate small wins and stay focused on solving real customer problems. This context was a crash course in entrepreneurship and personal growth.
ChallengesI overbuilt product features before proving willingness-to-pay from core users.
LearningsEarly founder success comes from solving one painful problem repeatedly and clearly.
OutcomeFound product-market fit direction and built a paying customer base.
Skills acquired
FundraisingFounder SalesProduct Iteration
AdviceValidate demand before scaling product complexity.
Failure and Lesson2021
Founder
BuildPilot
A major release was expected to improve retention during a sensitive growth phase. The team was under pressure to deliver quickly, and we made several assumptions without enough…
Show moreShow less
ContextA major release was expected to improve retention during a sensitive growth phase. The team was under pressure to deliver quickly, and we made several assumptions without enough user validation. When the release didn't meet expectations, it was a tough lesson in humility and the importance of feedback loops. We had to regroup, analyze what went wrong, and communicate transparently with stakeholders. This experience reinforced the value of learning from failure and iterating based on real data. It also strengthened our team's ability to handle setbacks and adapt our strategy.
ChallengesWe relied on internal assumptions and launched without enough customer validation.
LearningsFailure data is strategic input when teams perform root-cause analysis honestly.
OutcomeReset roadmap priorities and improved decision quality through direct customer interviews.
Skills acquired
Root Cause AnalysisCustomer InterviewsRoadmap Recovery
AdviceFailure is data. Use it to make the next decision better, not to stop building.

Mark if this helped you understand the journey.

Reflections & Questions from Readers

Share a thought, relate an experience, or ask a question. Reflections appear once reviewed (usually within 24 hours).

No reflections yet. Be the first to share what this journey sparked for you.

Ravi Kulkarni

Career Timeline

Operations Engineer

MBA Candidate

Founder and CEO

Founder

Reflections & Questions from Readers