How to find the right person at a partner company

How to find the person who can actually say yes at a partner company: partner manager vs PM vs alliances vs founder, title patterns, LinkedIn search, and who is only a router.

A dark navy poster with blue accents mapping partner titles (partner manager, PM, alliances, founder) to who can say yes versus who can only route.

You found the company. You still do not have a person. So you write to info@, or to a product marketer who posted about the ecosystem, or to a founder whose last post was three years ago. Sometimes that works. Often you get a polite bounce, a long silence, or a coffee chat with someone who cannot commit to a next step. The partnership did not fail. It never reached an owner.

Finding the right person is a research job with a commercial point: who can say yes to a first version, who can only introduce you, and who looks relevant and is not. You need the person measured on partner outcomes, the person who owns the surface you would build on, or, at a small company, the founder.

This guide covers the roles, the search patterns that actually surface them, how to tell a yes-person from a router, and what to do when there is no partner team at all.

The 60-second version

If you only read one section, read this one:

  • Optimize for someone who can commit a next step, not for the most senior title. A partner manager with a number beats a VP who will "stay close."
  • Partner manager and alliances own the relationship motion. Product owns the surface. Founders own both when the company is small.
  • Many titles are routers. Ecosystem marketing, developer advocates, and random PMs can help, and they usually cannot staff a partnership.
  • Search with role language, not just "partnerships." Alliances, ISV, technology partners, business development, platform, marketplace.
  • Confirm ownership on the first call. Ask who owns the integration or the referral path. If they cannot name that person, you do not have them yet.
  • At a company with no partner function, the founder or the product lead is the person. Do not wait for a hire that does not exist.
  • One named owner is enough to start. Add a second thread after they engage, not before you have anyone.

Who can actually say yes

"Yes" here does not mean a signed partnership agreement. It means: this person can put a date on a discovery call, introduce the engineer or PM, and not vanish when you send a one-pager. Business relationship management is the discipline of owning that relationship. Your first job is to find the human who already has that job, even if their title is messy.

Role What they usually own They can say yes to They usually cannot say yes to
Partner / alliance manager The relationship, the program path, internal routing A fit call, a process, a next owner Engineering time they do not control
Platform / marketplace owner Listings, app review, ISV motion A listing path, a review timeline Your product roadmap
Product manager (the relevant surface) The API, the workflow, the feature Scope on their surface, a build slot if they have one A company-wide partnership
BD / corp dev Pipeline of deals, sometimes partnerships An intro, a commercial conversation A product integration they do not own
Founder / CEO (small company) Everything A real yes or a real no Nothing, which is why they are the right door
Ecosystem marketing Stories, webinars, the logo wall A co-marketing experiment A build, a referral motion
Developer advocate / DevRel Builders, docs, community Technical context, an internal ping Staffing and commercial terms

Partner manager vs alliances. In many SaaS companies these are the same job with different heritage. Alliances often means larger and slower. Partner manager often means volume ISVs. Either can be the right first person if they own technology partners. If they own only resellers or agencies, they may still route you. Ask what book they run.

PM vs partner manager. If you need a build, you will need product eventually. You usually should not start there. A PM's inbox is a feature queue. A partner manager's job is to take partner conversations. Start with the relationship owner, then ask for the PM of the surface. Starting with a random PM is how you become an unsolicited spec.

Founder. Under ~50 people, the founder or a product lead is often the only person who can say yes. Titles like "Head of Partnerships" at that size may be one person doing events. Check headcount and who speaks about customers, not the LinkedIn headline alone.

Partnerships vs BD matters here. A BD title might mean they hunt corporate deals, not technology partners. If their posts are about M&A and logos, they are probably a router for your integration pitch.

Titles that look right and often are not

You will waste weeks on people who are adjacent to the work.

"Partnerships" in a sales org that only means channel sales or agency partners. They may want a referral agreement you are not offering.

Customer success partners who manage implementation firms. Wrong motion.

A PM of an unrelated product line. They will be polite if they have time. They cannot staff your workflow.

Marketing "ecosystem" people measured on webinars and logo counts. Useful later for co-marketing. They are a weak first owner for a commercial or build path.

A well-known executive who liked a tweet. They can sometimes open a route. They are not the working owner. Treat them as an optional warm path, then get a named manager.

The tell is always the same: can they name the process and the next internal person without guessing. If they say "I can loop in the team," ask which team and whether they will make the intro this week.

LinkedIn search patterns that work

You are looking for a person, not a perfect title. Search in combinations, then read the about line and recent posts.

Title strings to try (Boolean-style thinking, even if you type them one at a time):

  • "partner manager" plus the company
  • "alliances" or "strategic alliances"
  • "technology partner" or "ISV" or "ecosystem"
  • "business development" plus "partner" in the about text
  • "platform partnerships" or "marketplace"
  • "head of partnerships" / "director of partnerships" at smaller companies
  • "product manager" plus the platform or API name, only after you know the surface

Signals in the profile, not just the title:

  • They mention ISVs, integrations, app review, co-sell, or a named partner program.
  • They post about partner stories or program changes.
  • They are in the same geography or segment as the program you need (some large companies split by region or industry).

Signals they are the wrong person:

  • Pure sales quota language, no ecosystem.
  • Agency, affiliate, or influencer partnerships only.
  • Campus, talent, or "people partnerships."
  • They left the company. LinkedIn will still autocomplete them.
Search move What you are trying to find Next step if it hits
Partner manager + company Working owner of ISVs Read about line, then outreach
Alliances + company Owner of larger relationships Ask which book they run
ISV or marketplace + company Listing and program path Confirm review ownership
Founder + small company The actual yes Short, specific note
PM + named surface Build owner, second After a partner manager engages

If the company is large and you still cannot find anyone, look at their public partner page, a marketplace listing, or a webinar, and capture names from speakers. Sourcing technology partners includes this kind of artifact hunt. Five plausible people and one good note to the best one is the method. If they bounce you to the right owner, thank them and go.

How to approach once you have a name

Write as if they will forward the note. The first partner call is what you are trying to book, not a coffee.

In the first conversation, confirm:

  • What they own (technology partners, channel, a region, a product line).
  • Who owns the build or the referral path if it is not them.
  • What a good partnership looks like from their seat this quarter.
  • The name of a second person you should know.

If they cannot answer those, you may have a friendly router. Ask for the owner by function: "Who runs ISV integrations?" is a fair question. "Who is the best person?" is how you get another router.

When there is no partner team, say so in the note to the founder or product lead: you know they do not have a program, you have a specific customer job, you want 20 minutes to see if a first version is even interesting. That honesty is how small companies still reply.

Common mistakes, and the fix

Writing to the most famous person at the company. The fix: write to the person measured on partners or on the surface. Use an executive only as a last-resort intro.

Stopping at the first "partnerships" title. The fix: read the book they run. Channel, agencies, and ISVs are different jobs.

Starting with a random PM. The fix: start with the relationship owner, then ask for the PM of the relevant surface.

Treating DevRel as a commercial owner. The fix: use them for technical context and an internal ping, then get a partner manager or founder on the thread.

Waiting for a partnerships hire that does not exist. The fix: at a small partner, the founder or product lead is the person. Pitch a small first version.

Collecting ten names and emailing all of them the same day. The fix: pick the best owner, send one specific note. Add a second person after you have a conversation, on purpose.

FAQ

What title should I look for first? At a company with a program: partner manager, alliances, ISV, or platform partnerships. At a small company: founder or product lead. Confirm the book they run.

Can a product manager say yes to a partnership? They can say yes to scope on their surface if they have a slot. They rarely own the relationship. Use them as the build owner, not as the only contact.

Who says yes to a listing on a marketplace? Usually a platform or marketplace owner, sometimes a partner manager who owns ISVs. App review can block you and still not be the commercial owner.

What if two partner managers cover the same company? Ask who owns your category, region, or segment. Duplicate outreach to both looks sloppy.

Is corporate development the right door for a tech partnership? Usually no. Corp dev is for deals, investments, and acquisitions. They may route you. They are not the working owner of an integration.

How do I find the person if LinkedIn search is empty? Use public artifacts: partner directory, webinar speakers, job posts, and a customer who already works with them. A hiring post also tells you the function exists.

Should I ask my customer who their account team is? Yes, if the customer is willing. An account manager is often a router, but a good one will name the partner or platform owner. Do not use the customer's name without permission.

Further reading

The short version

The right person at a partner company is the one who can commit a next step, not the most senior name you can find. That is usually a partner or alliances manager, a platform owner, the PM of a specific surface, or, at a small company, the founder. Many nearby titles can only route you.

Search with several role phrases, read what they actually own, and confirm it on the first call. Start with one owner. Add a second thread after they engage. If you cannot find a partner function, stop waiting for one and write to the person who can still say yes.

If you want help with finding the right people in a partner book, 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.

Ready to turn partnerships into a real growth channel?

Start with a Partner Audit. We review your product, your partner book, and the commercial motions that can actually produce revenue.

Book a Partner Audit