Finance playbook · AI Employee: Fin

Zip Portfolio Owner Change

Portfolio ownership transitions without approval gaps

Install this playbookBack to marketplace
The problem

Zip portfolio ownership (who owns which cost centers + vendor categories) drifts. Original owner leaves, changes teams, or gets promoted; portfolio ownership doesn't cascade. Vendors get orphaned; procurement decisions lack clear owner; renewal negotiations fall through the cracks. Manual ownership review takes days per portfolio; nobody has time until audit forces the issue.

At a glance
Trigger
Form
Approvals
Finance owner approval
What it does
Writes to your systems
Systems
Zip
How it feels in production

An hour-by-hour walkthrough.

Sarah leaves the platform team; her portfolio (12 vendors, $840K annual spend across Cloud + Dev Tools categories) needs new ownership. Fin detects the departure trigger + proposes portfolio owner change: - Current owner: Sarah (departing 2026-11-15) - Portfolio: 12 vendors, $840K annual spend, Cloud + Dev Tools categories - Proposed new owner: Kiran (Sarah's peer + engineering leadership) - Alternative: split portfolio (Cloud to Priya, Dev Tools to Ravi based on their usage patterns) VP Engineering reviews + decides on single-owner or split. Approves proposal. Fin executes: - Reassigns 12 vendors in Zip to new owner - Updates approval routing for these categories - Notifies vendors of primary-contact change - Reassigns any in-flight renewal negotiations - Updates portfolio reports + dashboards Continuity preserved through transition. Portfolio ownership drift prevented at leaver events.
How it works

Step by step.

  1. 01

    Detect ownership change trigger

    Departure, role change, reorg, promotion. Portfolio inventory identified from Zip.

    HRIS · Zip · Portfolio inventory
  2. 02

    Propose new owner with alternatives

    Peer or successor based on team + engagement history. Alternative: split portfolio based on usage patterns.

    Peer registry · Usage analysis · Reasoning
  3. 03

    Leadership approves proposal

    Portfolio owner change requires leadership approval per policy. Split vs. consolidated choice made.

    Web UI · Approval flow
  4. 04

    Execute reassignment across systems

    Zip vendor reassignment, approval routing, vendor primary-contact updates, in-flight negotiation handoffs.

    Zip · Vendor communication · Contract management
  5. 05

    Notify + verify + document

    New owner briefed with portfolio context. Vendors notified. Reports updated. Handoff docs archived.

    Slack · Email · Documentation
Systems and wiring

What you connect to make this run.

Zip · Procurement platform

read+write

Vendor + category ownership. Approval routing per portfolio.

HRIS

read

Employee lifecycle trigger for ownership review.

Vendor management + CLM

read+write

Vendor primary-contact updates. Contract negotiation handoffs.

Slack · Email

read+write

New owner briefing + vendor communication + team notification.

What changes

Before and after, honestly.

Time from ownership trigger to reassignment complete
Before
2-6 weeks
After
3-5 business days
Orphaned portfolios (no clear owner)
Before
15-30%
After
Under 2%
Renewal negotiations disrupted by owner change
Before
20-40%
After
Under 5%
Fin ops hours per portfolio transition
Before
8-20 hours
After
1-2 hours
Related

Playbooks that pair with this one.

HR

Employee Offboarding

Departures trigger portfolio ownership review.

Finance

Vendor Intake & Onboarding

Portfolio ownership established at vendor intake; adjusted through lifecycle.

Finance

License Cost & Renewal Tracking

Renewal ownership continuity managed through this playbook.

Frequently asked

Answers about this playbook.

What if there's no obvious successor?

VP-level review determines interim ownership. Search for permanent owner within reasonable timeline; interim ownership documented.

How does it handle portfolio splitting (multiple new owners)?

Split proposal supported. Different vendors + categories to different new owners based on usage + expertise.

What about M&A situations (acquired company's portfolios)?

M&A integration handled separately; portfolios join our procurement structure with owner-mapping from acquired team.

How does it handle vendor concerns about primary-contact change?

Vendor communication is professional handoff, not surprise. Prior owner introduces new owner where practical; continuity emphasized.

Can we transfer partial ownership (e.g., approval authority but not day-to-day)?

Yes — different roles supported: portfolio owner (strategic), approver (decisions), operator (day-to-day). Each transferable independently.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore Finance playbooks