When people hear that I ran a company for nine years and then became a Program Manager, they usually ask one of two questions.
The first is: Was that a step down?
The second, from people who understand program management, is: How did the transition feel?
The answer to the first question is no. The answer to the second is: stranger than I expected, and more valuable than I could have predicted.
The acquisition
In 2022, Cedex Technologies — the company I founded in 2013 — was acquired by Centelon Solutions, an Australian enterprise software company. It was a good outcome. Nine years of work, 25 people, 85% international revenue, an AI practice that had done things I was genuinely proud of.
When the acquisition closed, I had a choice. I could take whatever exit proceeds there were and start something new. Or I could stay, roll up my sleeves, and lead program delivery in a much larger organisation with a much wider client portfolio.
I chose to stay.
Partly because the work was interesting. Partly because I respected the people at Centelon. But mostly because I was honest with myself about something: running a 25-person company had given me incredible breadth, but there were parts of enterprise-scale program delivery I had never experienced. I wanted to learn them.
What I thought I knew about program management
As a founder-CEO, I had always been the de facto program manager. I ran sprints, managed stakeholders, tracked budgets, hired teams, closed deals, and coordinated deliveries across multiple clients simultaneously.
I thought I knew what program management was.
I was partly right. The fundamentals — scope management, risk registers, stakeholder communication, sprint cadences — those transferred cleanly. I did not need to relearn them.
What I underestimated was the complexity of operating across a portfolio of large enterprise accounts simultaneously, each with their own governance structures, vendor ecosystems, compliance requirements, and internal politics.
At Cedex, I was the highest authority in the room for any project decision. At Centelon, I was one node in a much larger system. That required a different kind of influence — one built on trust, communication quality, and the ability to align people across organisational boundaries without direct authority over them.
The unexpected gift: depth
The most valuable thing that happened in my first year at Centelon was a project I did not choose: HDFC Bank's Developer Portal.
This was not a startup project. It was a 25+ member, multi-vendor, enterprise banking program with strict RBI compliance requirements, a 4-million-record database migration, and multiple agencies — UI/UX, UAT vendors, Salesforce integrators, client IT — all working in parallel and needing to be coordinated.
I had never managed a project quite like it.
The thing about enterprise banking is that there is no room for the founder's instinct of "move fast and fix it later." Every decision has to be documented. Every architectural choice has to be justified in writing. The compliance team will read the deployment runbooks. The security team will challenge the data migration approach.
It made me a better program manager. Not because the skills were new, but because the discipline was applied at a level of rigour I had not previously needed.
We delivered on time. Zero defects in production. 100% data integrity. The bank's compliance team accepted every document.
I was proud of that project in a different way than I had been proud of anything at Cedex. Not because it was technically harder, but because the constraints were tighter and the margin for error was smaller.
What founders bring to program management
If you are a founder considering a move into program management at a larger organisation, here is what I have found to be genuinely transferable:
Commercial instinct. Founders understand that projects exist to deliver business value, not just to close tickets. This changes how you prioritise, how you frame risks to stakeholders, and how you make trade-off decisions under pressure.
Hiring and team-building. I have built teams from scratch. I know what good looks like across different disciplines. That makes me faster and more accurate when assembling cross-functional delivery teams.
Client relationship ownership. At a startup, the founder is often the relationship. You learn to read clients, understand what they actually need versus what they say, and navigate difficult conversations without burning trust.
Tolerance for ambiguity. Founders spend years operating without complete information. That muscle is extremely useful in enterprise programs where requirements change, stakeholders shift, and clarity is always a work in progress.
What the transition taught me
The main thing I learned from moving from CEO to Program Manager is this: leadership is context-dependent, not role-dependent.
The same qualities that made me effective as a founder — clear communication, bias for outcomes over process, ability to hold complexity across multiple workstreams, willingness to have hard conversations early — those qualities made me effective as a program manager too.
The form changed. The substance did not.
I am glad I made the choice to stay. I am a better leader for having done it.
Mahroof K is a Senior Program & Product Manager with 12+ years of end-to-end delivery experience. He is currently available for senior roles in MNCs, product companies, and high-growth startups.