How to work with a partner manager so the relationship ships
How to work with a partner manager: what they are measured on, how to make their job easier, a cadence that ships, and what never to dump on them.
A partner manager is not your project manager, your salesperson, or your lawyer. They are the person inside the other company whose job is to route, prioritize, and sometimes champion partner work. If you treat them like a catch-all inbox, the relationship slows down. If you treat them like a customer, you will pitch when you should be making them look competent.
Working with a partner manager is a craft: know what they are measured on, give them artifacts they can forward, keep a cadence that produces dates, and never dump work they cannot do. Business relationship management is the name of the discipline. In practice it is quieter. You make their week easier, they make your next step real.
This guide covers incentives, the artifacts and cadence that help them ship, the list of things you should never put on them, and how to escalate without burning the only person who answers you.
The 60-second version
If you only read one section, read this one:
- They are measured on program activity and, if you are lucky, outcomes. Give them numbers and a story they can report, not a pile of open questions.
- Your job is to be easy to champion. One-pagers, a named owner, a small first version, and dates they can put in a tracker.
- Cadence should produce artifacts. A weekly or biweekly of 25 minutes with a written next step beats a long monthly catch-up.
- Never dump legal, raw customer lists, or an unscoped build on them. Bring the smallest packet they can route.
- They rarely control engineering. Ask them who does, and give that person a scope page.
- Escalate through them first. Going around a partner manager is how you lose the only map of the building.
- Make them look right in front of their internal team. Share credit, send a written recap, and do not surprise them with a public announcement.
What a partner manager is actually measured on
Incentives explain the behavior. Many partner managers sit in a channel or alliances function with a scorecard that mixes activity and, later, revenue. Harvard Business Review's work on motivating salespeople is a useful reminder: people do what the scorecard pays or promotes.
Typical pressures, even when the title is "partnerships": new partners launched, listings and enablement sessions, sourced or influenced pipeline if they track it, executive satisfaction, and not creating mess (legal surprises, support load, public complaints).
| Their scorecard | What they need from you | What does not help them |
|---|---|---|
| Launches and listings | A complete, boring launch packet | A visionary deck with no assets |
| Pipeline | Closed-loop on referred deals, CRM hygiene | Vague "we had a good call" |
| Partner count | A path they can onboard without heroics | A custom process every week |
| Internal reputation | You showing up prepared with their PM | You surprising their exec on social |
| Low mess | A named support path and a small v1 | An open-ended integration idea |
Your outcomes and theirs overlap, they are not identical. You want adopted product and revenue. They may get credit for the launch even if adoption is quiet. Bring adoption numbers to the partner QBR. Help them look good on the metrics they have, and give them outcome metrics they can start using.
Ask, once, in plain language: "What does a good quarter look like for you with a partner like us?" Then build your working style around that answer.
How to make their job easier
A partner manager's real job is internal selling. They take your request into a company that did not ask for it. You can make that sell cheap or expensive.
Give them forwardable objects. A one-page scope, a one-page joint value, a launch checklist, a recap email they can paste. If they have to rewrite you, they will delay you.
Be one owner. One person on your side who answers. A thread with four of your colleagues asking different questions makes them look unorganized inside their own company.
Shrink the first yes. "Certified integration with a 12-month roadmap" is a hard sell. "A v1 that covers this workflow, then a review" is a yes they can take to product.
Do the homework they would otherwise do. App-review requirements, a test account, a draft listing, a short FAQ. Partner enablement is not only for their sellers. It is also how you enable the partner manager to enable everyone else.
Close the loop on anything they sent you. If they introduced a customer or a PM, write back what happened. Silence makes them look careless to the person they pulled in.
Keep partner communications boring and dated. When the pitch changes, tell them the same day, in one paragraph they can forward to their field. Do not bury it in a newsletter they might not open.
| You send | They can do | Time they save |
|---|---|---|
| Scope page | Route to PM | They do not run a discovery from memory |
| Recap with owners and dates | Paste into their tracker | They do not reconstruct the call |
| Launch assets, complete | Submit the listing | They do not chase you for screenshots |
| Deal status on referrals | Report pipeline | They do not guess |
| A single ask per note | Get a yes or a no | They do not parse a bundle of requests |
If you only change one habit, change this: every meeting ends with a three-line recap in writing. Partner managers live in trackers. Feed the tracker.
Cadence that ships, not just talks
Cadence is a calendar with a job. If the meeting does not produce a date, an owner, or a decision to pause, it is social.
A default that works when the partnership is in motion:
- Weekly or biweekly, 25 minutes, while you are scoping or launching. Agenda in the invite: last action, blocker, next action.
- Async the rest of the week. One thread or one channel, not Slack plus email plus a second Slack.
- Monthly when live and quiet, until there is a deal or a change.
- Quarterly QBR only if there is a plan, not as a ritual for a dormant logo.
Cancel if there is no agenda. A cancelled meeting with a written "nothing moving, next check on this date" is healthier than a catch-up that invents work.
When they go quiet, do not stack reminders. Send one note that restates the next action you need from them, and what you have already finished. Then give them room. They may be in a launch, a reorg, or a quarter close. Your urgency is not their scorecard.
What never to dump on them
Respect is operational. These dumps are how you become the partner they dread.
Do not send legal as a first packet. Bring commercial intent. Let them tell you which paper they need. A 20-page redline in week one makes you look like a cost center.
Do not send a raw customer list. Even if overlap is the point. Ask how they want to do account mapping. Permission and privacy are their risk, not only yours.
Do not send an unscoped "can your engineers look at this." Send a page: workflow, v1, out of scope, questions. They cannot create a Jira ticket from a vision.
Do not use them as your support team. Give partners a path for product issues. The partner manager can escalate a pattern. They should not be ticket number one every time.
Do not surprise them in public. No joint announcement, no "excited to partner with" post, no using their logo, until they have signed off. Surprise is how they get yelled at.
Do not CC their executive "for visibility" on a working thread. If you need an exec, ask the partner manager to set that meeting. Going around them is remembered.
Do not bundle five asks. One note, one ask. List the rest as a backlog they can schedule.
If you already dumped one of these, repair it: apologize once, send the smaller artifact, and do not repeat.
Escalation without burning the relationship
Sometimes you need more than they can give: a blocked review, a silent PM, a deal that needs an exec. Escalate with them, not around them.
- Name the blocker and the date it has been stuck.
- Ask what would help on their side (a note from your exec to theirs, a customer quote, a smaller v1).
- Offer to draft the internal note they would have to write.
- Only then, if they agree, involve a second person.
If they are the blocker (no replies, no owner, no dates for weeks), that is information. Park the partnership or reduce it to a watch list. Do not punish a busy manager with a surprise exec email. You may still need them if the company restarts later.
Common mistakes, and the fix
Treating the partner manager as the engineer. The fix: ask who owns the surface, and send that person a scope page through the partner manager.
Showing up with a vision and no artifacts. The fix: one-pager, recap, checklist. Make them easy to champion.
Running a long catch-up cadence with no dates. The fix: 25 minutes, three lines in writing, cancel when idle.
Going around them to an executive. The fix: ask them to set the room. If they will not and the work is real, that is a stall signal, not a reason to blind-copy.
Announcing before they are ready. The fix: written approval, assets they approved, a date they chose.
Hiding bad news (a slipped build, a missed referral). The fix: tell them early, with a new date. They can manage internals. They cannot manage a surprise.
FAQ
What does a partner manager actually do all day? They route, track, sell you internally, protect the program from mess, and report a scorecard. The good ones also coach you on how their company decides. They do not, by default, write your spec.
How often should I meet them? As often as there is a dated action to review. Weekly in build or launch, lighter when live. A standing hour with no agenda wastes the hour.
What if they will not introduce me to product? Ask what would make that intro easy (a smaller v1, a customer request). If the answer is never, you do not have a build path. Stop promising one.
Should I put them on commission-style deal registration? If that is how their program works, yes, and close the loop so they get credit. If they are not on a sales plan, still send deal status. Credit is currency even when it is not cash.
Can I work with two partner managers at the same company? Yes, if they split region or product. Tell both. Do not run duplicate threads that contradict each other.
What do I do if they leave? Ask for a handoff while they are still there. Get a second contact and a written status. If they already left, restart with a one-page recap to whoever inherited the book.
How do I know I am a good partner to work with? They answer, they bring you into rooms, and they use your artifacts without rewriting them. Silence and repeated "let me check" with no date are the opposite signal.
Further reading
- How to run a partner QBR for the meeting where you align scorecards and next-quarter work.
- Partner enablement 101 for the kit that makes a partner manager look prepared.
- Partner communications for how you keep them current without flooding them.
- SaaS partnership agreements so legal is a later, narrow step, not a dump.
- Harvard Business Review, Motivating Salespeople: What Really Works, on scorecards and behavior.
- Wikipedia, business relationship management, on owning the relationship as an operating practice.
- Wikipedia, channel partners, on the org a partner manager often sits in.
The short version
Work with a partner manager by making them easy to champion. Learn what they are measured on. Send forwardable pages, keep one owner on your side, and run a short cadence that produces dates. Do not dump legal, raw lists, unscoped builds, or public surprises on them.
Escalate through them. Recap in writing. Share credit. If they cannot name a next step after you have done your part, that is a stall, not a reason to try harder in the same messy way. The relationship ships when their internal sell is cheap and your next action is obvious.
If you want help with working partner managers so relationships ship, that is exactly what a Partner Audit is for. We review your product, your partner book, and the commercial motions that can actually produce revenue.