Product teams learn to flinch when partnerships walks in. They have been burned by “the CEO met someone” scopes. Your job is to be the person who does not do that.
What you bring
A ranked request, not a list. Customer pull (named, counted). The workflow in user stories. A guess at build cost: sandbox quality, docs, objects, auth. What you are willing to cut. What happens if they say no (CSV, iPaaS, wait).
A PM can work with that. A PM cannot work with “we should be on their marketplace.”
Timing
Catch them in planning, not mid-sprint. A quarterly slot for “partner integrations” is the adult version. If no slot exists, that is the first conversation with the CEO, not a fight with a staff engineer.
You are not the PM
You do not write tickets in their voice. You write acceptance criteria and stay for questions. You do not re-scope in Slack at 6pm because the partner had a thought. Changes go through the same brief.
When they say no
Accept it on the record. Tell the partner. Offer the honest alternative. Coming back every week with the same logo is how you lose the room.
When they say yes
You own launch: listing, help article, seller sentence, the customers who asked. Product owns the code. If you disappear after the kickoff, you taught them that partnerships is a drive-by.
The best partner managers are boring to product: they arrive with a brief, they protect the scope, they show up at launch, they bring adoption numbers back.