How to Give Away a Product You Built

I founded a platform, ran it for years, and then gave it to somebody else on purpose. The handover itself was not the hard part.

The hard part is the founder's shadow. A new product manager inherits your opinions, your rapport with the engineers, and a team that keeps routing decisions back to you out of pure habit. You can hand over the title on Monday and still be the actual decision-maker on Friday, and everyone will be perfectly happy with that arrangement except the person whose job you just took.

So I staged it, deliberately, over roughly two years.

First, execution against a roadmap that already existed. Nothing to invent, plenty to learn, and a low-risk way to build standing with the engineers. Then ownership of the roadmap itself. Then the technology and business partnerships, which is where most of the actual power in a platform role sits. Strategy and vision last, because that piece is impossible to hold before you understand the other three.

At each stage he had full autonomy to execute. I kept a close eye on where things were heading, and I was willing to let him fail on the ones that would not be expensive.

The challenge I set at the start was deliberately larger than the job: think about this at ten times the scale. Define what the next five years look like. Tell me what you would rewrite from scratch, and which user journeys you would revisit. Not because I expected all of it to happen, but because a person who has only ever executed someone else's roadmap does not develop the instinct to question one.

The mechanism that mattered most is small, and I would recommend it to anyone doing this.

Coach privately, then let them make the call in the room.

We would talk through a decision beforehand, alone. Then he would make it in the meeting, in his own words, and I would say nothing. The team saw the decision come from him rather than from me through him, and that distinction is the entire game. If people see you agreeing with him, they have learned that you still decide. If they see him decide and you follow, they have learned something else.

The advice I gave him repeatedly was to get technically savvy rather than just functionally competent. Use the product. Read the code. Build genuine rapport with the engineers. Once engineers trust you on the substance, you can drive a platform without needing the founder as a backstop — and the founder is the single largest obstacle to your credibility.

I should be honest about the cost, because it was real and I felt it.

I was giving away visibility and decision rights on something I had invented and was strongly opinionated about. There were calls I would have made differently, and I watched some of them play out. A few were better than mine. Some were worse and recoverable, which is what "willing to let him fail" actually means in practice rather than as a phrase in a performance review.

He was promoted to senior product manager and given a second PM to support him. The platform kept running and stopped needing me, in that order.

There is a version of this that reads as generosity. It is not. It is the only way to get your own next job, because as long as you are the single point of failure for a platform, you are also the reason nobody can move you to the next problem. The organization has every incentive to leave you exactly where you are.

The measure of a platform is not whether it runs. It is whether it runs without you.