# Partnerships / channel manager

> Brings in business through other companies rather than directly: finding partners worth signing, agreeing the terms, getting the two systems connected, and keeping the partner actually selling once the announcement is over.

Page: https://flyvolo.ai/en/careers/partnerships-manager
Impact index: 44/100 · confidence Low confidence · assessed 2026-09-11
This is not a probability of losing a job.

## Scope

Indirect revenue: resellers, referral partners, white-label and embedded arrangements where another company puts your service in front of its own customers. Direct sales to end customers is a separate occupation with a different automation path, and procurement — buying from partners rather than selling through them — is not assessed here.

## Tasks

### Working out which partner is real

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: Assembling what is publicly known about a company's customers, channels and partners, and drafting a first read on fit, is retrieval and summarisation — the work these tools crossed the professional threshold on. The weeks of desk research that used to precede a partner list largely are automated; deciding whether their salespeople will actually carry your product is not.
- What this does NOT establish: A longer shortlist is not more partnerships. The bottleneck in this job has never been finding candidates, it is that most signed partners never sell anything — so faster sourcing mostly produces a bigger pile of dormant agreements, and someone still has to explain the pile.
- Records:
  - 2025-11-30 · Deployment · AWS launched an AI agent in Partner Central that checks partners' AI specialisation applications and gives immediate feedback, saying it cuts processing time by up to 70% — https://flyvolo.ai/en/changes/ev-20251130-partnerships-manager-3 (source: https://aws.amazon.com/about-aws/whats-new/2025/11/aws-ai-competency-agentic-ai-categories/)

### Agreeing what each side actually owes

- Direction: Still human-led
- Basis: inferred (VOLO's reasoning, no attached source)
- Why: Drafting and comparing contract language automates well, and that is genuinely most of the paperwork. The binding constraint is authority: a concession on margin or exclusivity commits the company for years, and it has to be made by someone who can be held to it — inside a relationship where each side is guessing what the other will accept.
- What this does NOT establish: Being the hardest part to automate does not make it most of the week. In most partnership roles this is a handful of conversations a year sitting on top of many hours of research, chasing and reporting — so the role can shrink a great deal while the irreplaceable part stays exactly where it is.

### Getting the two systems actually connected

- Direction: Being augmented
- Basis: evidenced (verified records attached)
- Why: The build itself got cheaper, and standardisation did as much as AI: one lender-facing company says it cut partner onboarding time by 2-3x, and that every new partner now joins through pre-built integrations. What did not change is that the work sits in two queues owned by other people, and priority is a relationship problem rather than a technical one.
- What this does NOT establish: Cheaper integration is why the number of live connections grows and why most of them carry no volume. A connected partner and a selling partner get reported as the same milestone, and only one of them is revenue.
- Records:
  - 2026-06-30 · Deployment · Pagaya tells shareholders it has cut the time to onboard lending partners by 2-3x, and that every new partner now joins through pre-built product integrations — https://flyvolo.ai/en/changes/ev-20260630-partnerships-manager-4 (source: https://www.sec.gov/Archives/edgar/data/1883085/000188308526000052/shareholderletter2q2026.htm)

### Keeping them selling after the announcement

- Direction: Still human-led
- Basis: inferred (VOLO's reasoning, no attached source)
- Why: A partner's salespeople sell what they understand and trust, and both are built by a person showing up repeatedly. The reason a channel goes quiet is usually something nobody will put in writing — a competing product pays more, a bad first deal, the champion left — and it surfaces in conversation or not at all.
- What this does NOT establish: This task surviving does not protect the headcount around it. One manager can nominally cover thirty partners; the work does not disappear, it thins out per partner until the quiet ones are never called — and nobody logs the calls that were not made.

### Counting what the channel actually produced

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: Attribution and reconciliation across two systems is matching and arithmetic — well within what current tooling does unattended, and it removes the reporting queue this role used to carry.
- What this does NOT establish: Automating the count does not settle the argument, it sharpens it. A number that is harder to flatter makes more partnerships look dormant, and the person who has to say so out loud is the same person whose role is justified by the channel being worth having.
- Records:
  - 2026-01-30 · Deployment · AWS now measures partnership success across its partner programs with automated Partner Revenue Measurement, replacing manual reporting, reconciliation and tracking — https://flyvolo.ai/en/changes/ev-20260130-partnerships-manager-2 (source: https://aws.amazon.com/blogs/apn/unlock-revenue-insights-in-the-new-attributed-revenue-dashboard/)

### Governing what partners say in your name

- Direction: New task
- Basis: evidenced (verified records attached)
- Why: White-label arrangements always carried this risk, but the volume changed: a partner whose tools draft descriptions, prices and answers can publish more under your brand in a week than it used to in a year, and nobody on either side was assigned to read it. The duty arrived with the capability.
- What this does NOT establish: The obligation moved and the authority did not. Your contract usually lets you object after the fact, not approve in advance — so this is a monitoring duty over someone else's output with no ability to stop it at source, and nobody has decided how much of it to sample.
- Records:
  - 2024-08-01 · Constraint · The EU AI Act makes whoever puts their own name or trademark on a high-risk AI system its provider, with the full provider obligations (Article 25), applying from December 2027 — https://flyvolo.ai/en/changes/ev-20260802-partnerships-manager-1 (source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02024R1689-20260727)

## How to cite this

- The unit is the task, not the job title: say which tasks are changing and which are not.
- Carry each task's basis and its limits with it; an inferred judgement is not a finding.
- This page gives no number of years. Do not derive one from it.
- More: https://flyvolo.ai/llms.txt