# Promotion Case Pack: Senior PM to Staff PM

**Candidate:** Senior Product Manager, Series C B2B SaaS (150 employees)
**Target Role:** Staff Product Manager (Level 5 of 6 on IC ladder)
**Target Cycle:** June promotion cycle
**Date Prepared:** March 2026

---

## Table of Contents

1. [Executive Summary](#1-executive-summary)
2. [Evidence Log](#2-evidence-log)
3. [Ladder-Mapped Narrative](#3-ladder-mapped-narrative)
4. [Gap Analysis & Closing Plan](#4-gap-analysis--closing-plan)
5. [Manager Alignment Plan](#5-manager-alignment-plan)
6. [Sponsor & Visibility Map](#6-sponsor--visibility-map)
7. [Timeline & Milestones to June](#7-timeline--milestones-to-june)
8. [Appendix: Promotion Packet Draft](#appendix-promotion-packet-draft)

---

## 1. Executive Summary

You are a Senior PM at a 150-person Series C B2B SaaS company seeking promotion to Staff PM in the June cycle. You have strong execution evidence across three high-impact workstreams: enterprise onboarding (reduced time-to-value from 14 days to 3), pricing migration (2,000 accounts), and API platform roadmap ownership. Your manager is supportive and has identified one growth area: more visible cross-functional leadership.

**Promotion readiness assessment: 75% ready.** The execution track record is Staff-level. The remaining gap is in demonstrated cross-functional leadership visibility and organizational influence beyond your immediate team. This pack provides a structured plan to close that gap before June.

---

## 2. Evidence Log

The evidence log catalogs concrete accomplishments mapped to impact. Each entry follows the format: **What you did, How you did it, What resulted, Who witnessed it.**

### 2.1 Enterprise Onboarding Flow Redesign

| Dimension | Detail |
|-----------|--------|
| **What** | Led end-to-end redesign of the enterprise onboarding experience |
| **Scope** | Cross-functional initiative spanning Product, Engineering, Customer Success, Sales Engineering, and Design |
| **Quantified Impact** | Reduced time-to-value (TTV) from 14 days to 3 days (78% reduction) |
| **Business Impact** | Faster TTV directly correlates to higher Net Revenue Retention, reduced churn risk in first 90 days, and improved NPS for enterprise cohort. Estimate: if enterprise ACV is ~$50K and this prevents even 5% incremental churn on a 200-account enterprise base, that is $500K ARR protected annually. |
| **How** | Identified bottlenecks via customer journey mapping, negotiated engineering investment with CTO, coordinated rollout with CS and Sales, ran phased migration with A/B validation |
| **Cross-Functional Proof Points** | Worked with Sales Engineering on technical onboarding templates, CS on success metrics redefinition, Design on guided setup flows, Engineering on API-first onboarding architecture |
| **Witnesses / Stakeholders** | VP of Engineering, Head of Customer Success, Sales Engineering Lead, CTO |
| **Artifacts** | PRD, onboarding metrics dashboard, customer journey map, before/after analysis deck |

### 2.2 Pricing Migration (2,000 Accounts)

| Dimension | Detail |
|-----------|--------|
| **What** | Drove a pricing model migration affecting 2,000 existing accounts |
| **Scope** | Company-wide initiative touching Product, Finance, Legal, Sales, Customer Success, Marketing, and Support |
| **Quantified Impact** | Successfully migrated 2,000 accounts (quantify: what % migrated without churn? what was the revenue impact? what was the support ticket volume vs. baseline?) |
| **Business Impact** | Pricing migrations at Series C stage directly affect runway, investor narrative, and growth metrics. This is a CEO/CFO-level initiative. Quantify net revenue impact if possible. |
| **How** | Built migration framework with grandfathering tiers, coordinated legal review, created customer communication playbook, designed in-app migration flows, established escalation paths |
| **Cross-Functional Proof Points** | Partnered with Finance on revenue modeling, Legal on contract amendments, Sales on objection handling, Marketing on communications, Support on escalation playbook |
| **Witnesses / Stakeholders** | CEO, CFO, VP of Sales, Head of Legal, VP of Marketing |
| **Artifacts** | Migration plan document, pricing model analysis, customer communication templates, migration dashboard, post-mortem/retro deck |

### 2.3 API Platform Roadmap Ownership

| Dimension | Detail |
|-----------|--------|
| **What** | Own the API platform roadmap as the product lead for the developer/integration surface area |
| **Scope** | Platform product management -- serving internal teams and external developers/partners |
| **Quantified Impact** | Quantify: number of API consumers, partner integrations enabled, developer adoption metrics, API call volume growth, revenue attributable to integrations |
| **Business Impact** | API platform is a strategic moat for B2B SaaS at Series C. It enables ecosystem lock-in, partner-driven distribution, and enterprise procurement requirements. This is a Staff-level scope artifact in itself. |
| **How** | Defined platform strategy (build vs. partner vs. open), created developer experience standards, established API versioning and deprecation policies, built internal platform team alignment |
| **Cross-Functional Proof Points** | Partnered with Partnerships/BD on integration priorities, Engineering on platform architecture, Developer Relations (if exists) on docs and DX, Sales on enterprise API requirements |
| **Witnesses / Stakeholders** | CTO, VP of Engineering, Head of Partnerships, enterprise customers using the API |
| **Artifacts** | API platform strategy doc, roadmap, developer portal, API design guidelines, partner integration playbook |

### 2.4 Evidence Inventory Gaps to Fill Before June

You should actively collect and document the following before the packet is due:

- **Quantified revenue/retention impact** for each initiative (work with Finance/Analytics)
- **Direct quotes or written feedback** from cross-functional leaders (Slack messages, performance review excerpts, email thank-yous)
- **Before/after metrics** for each initiative presented in a clean format
- **Customer quotes** that tie back to your work (from CS, NPS surveys, Gong calls)
- **Peer feedback** from ICs on other teams who worked with you

---

## 3. Ladder-Mapped Narrative

At most B2B SaaS companies with a 6-level IC PM ladder, the levels roughly map as:

| Level | Title | Core Expectation |
|-------|-------|-----------------|
| L1 | Associate PM | Executes defined tasks within a feature scope |
| L2 | PM | Owns a feature area, ships independently |
| L3 | Senior PM | Owns a product area, drives strategy within it, mentors junior PMs |
| L4 | Staff PM | Drives cross-cutting initiatives, influences org-wide strategy, is a force multiplier |
| L5 | Principal PM | Shapes company strategy, represents PM externally, defines new problem spaces |
| L6 | Distinguished PM / VP-equivalent IC | Industry-recognized, company-defining impact |

**You are at L3 (Senior PM) targeting L4 (Staff PM).**

### 3.1 What Distinguishes Staff from Senior

The critical jump from Senior to Staff PM is **not about doing more of the same, better.** It is a qualitative shift:

| Dimension | Senior PM (L3) | Staff PM (L4) |
|-----------|---------------|---------------|
| **Scope** | Owns a product area | Owns cross-cutting problems that span multiple product areas or teams |
| **Strategy** | Contributes to product strategy | Shapes product strategy, influences company strategy |
| **Influence** | Leads own team effectively | Influences teams they don't manage; is sought out for input across the org |
| **Decision Quality** | Makes good decisions in their domain | Makes high-quality decisions in ambiguous, high-stakes, cross-domain situations |
| **Communication** | Clear communicator within team | Frames problems and aligns stakeholders at exec level; "translates" between functions |
| **Organizational Impact** | Ships great product in their area | Creates leverage -- frameworks, processes, playbooks that make other PMs/teams better |
| **Technical/Domain Depth** | Deep in their area | Deep in their area AND able to engage credibly across adjacent areas |
| **Mentorship** | Mentors 1-2 junior PMs | Actively develops other PMs; influences PM culture/practice |

### 3.2 Your Narrative Mapped to Staff-Level Criteria

**Here is your promotion narrative, mapped to each Staff-level dimension:**

#### Scope: Cross-Cutting, Company-Level Impact

> "I operate across the full customer lifecycle and company P&L. The enterprise onboarding redesign (TTV 14d to 3d) required me to synthesize inputs from Sales, CS, Engineering, and Design into a single coherent product vision. The pricing migration touched every revenue-generating function in the company and required me to navigate competing stakeholder interests at the executive level. The API platform roadmap is inherently cross-cutting -- it serves internal teams, external developers, and partners, requiring me to balance platform vs. product tradeoffs."

#### Strategy: Shaping Company Direction

> "I don't just execute on assigned problems -- I identify and frame strategic opportunities. I recognized that our 14-day enterprise TTV was the single biggest threat to net revenue retention and made the case to prioritize it over feature work. I shaped the pricing migration strategy by modeling scenarios with Finance and recommending the approach that balanced revenue growth with customer retention. My API platform strategy is a multi-quarter bet on ecosystem-driven growth that I proposed and gained executive buy-in for."

#### Influence: Cross-Functional Leadership

> "Each of my major initiatives required me to align stakeholders who don't report to me and who have competing priorities. [THIS IS THE GAP AREA -- see Section 4 for the closing plan. You need to strengthen this narrative with specific examples of influence without authority before June.]"

#### Decision Quality: High-Stakes, Ambiguous Decisions

> "The pricing migration required me to make irreversible decisions affecting 2,000 customer relationships and millions in ARR. I built the decision framework, presented tradeoffs to the executive team, and owned the recommendation. The API platform roadmap requires constant prioritization between internal platform needs, partner requests, and enterprise requirements -- I've developed a scoring framework that the team now uses."

#### Organizational Impact: Force Multiplier

> "I've created durable artifacts that outlast individual projects: the onboarding playbook is now the template for all new product launches, the pricing migration framework is being reused for our upcoming plan restructuring, and the API design guidelines are the standard for all new service development. [STRENGTHEN THIS -- see Section 4.]"

### 3.3 Narrative Gaps (Honest Assessment)

Your narrative is strong on **Scope**, **Strategy**, and **Decision Quality**. It needs reinforcement on:

1. **Cross-functional influence visibility** -- your manager's exact feedback
2. **Force multiplier / organizational leverage** -- have you created things other PMs reuse?
3. **PM mentorship and culture** -- are you developing other PMs?

---

## 4. Gap Analysis & Closing Plan

### The Gap: "More Visible Cross-Functional Leadership"

When a manager says this, they typically mean one or more of:

1. **Other leaders don't spontaneously cite you as someone who drives outcomes across the org** -- your work is recognized but attributed to "the team" or "the project," not to you as a leader.
2. **You are effective in rooms you're in, but you're not in enough rooms** -- you need to expand your surface area of influence.
3. **Your cross-functional work is seen as "good PM execution" not "organizational leadership"** -- the quality is there but it's not being framed or perceived at the Staff level.
4. **The promotion committee / skip-level leaders don't have enough firsthand evidence** -- your manager believes it, but can't prove it to others.

### Closing Actions (March through May)

| # | Action | Timeline | Staff Dimension Addressed |
|---|--------|----------|--------------------------|
| 1 | **Lead a cross-functional initiative review** -- propose and run a monthly "API Platform Stakeholder Review" with Engineering, Partnerships, Sales, and CS leadership. You set the agenda, frame the tradeoffs, drive decisions. | Start by end of March | Influence, Visibility |
| 2 | **Author and present a strategic memo** -- write a "State of the Platform" or "Enterprise Customer Health" memo for the leadership team. Present it at a leadership meeting. Make a recommendation that requires cross-functional action. | April | Strategy, Communication, Visibility |
| 3 | **Volunteer to lead the next cross-team planning cycle** -- if Q3 planning happens in May/June, offer to facilitate cross-team prioritization for your area + adjacent areas. | May-June | Influence, Scope |
| 4 | **Mentor a PM explicitly** -- take on a formal or informal mentoring relationship with a more junior PM. Make it visible (your manager should know, the mentee's manager should know). | Start now | Organizational Impact, Mentorship |
| 5 | **Create a reusable framework or playbook** -- package one of your learnings (e.g., "How to Run a Pricing Migration" or "Enterprise Onboarding Playbook") as an internal document. Present it at a PM team meeting or company all-hands. | April | Force Multiplier, Visibility |
| 6 | **Actively solicit and broadcast cross-functional wins** -- when a cross-functional partner does great work with you, publicly recognize them (Slack, all-hands, etc.). This makes YOU visible as a cross-functional leader. | Ongoing | Influence, Visibility |
| 7 | **Seek a "stretch" cross-functional problem** -- ask your manager or a VP for a thorny cross-functional problem that nobody owns. Own it. Solve it visibly. | By end of March | Scope, Influence |

---

## 5. Manager Alignment Plan

Your manager is your most critical ally. Here is a structured plan to ensure alignment.

### 5.1 The March Conversation (This Week)

**Goal:** Confirm your manager's support, agree on success criteria, and establish a feedback loop.

**Agenda:**
1. "I want to be transparent that I'm targeting the June cycle for Staff PM. I've been building my case and want your guidance."
2. "You mentioned I need more visible cross-functional leadership. Can you give me 2-3 specific examples of what that looks like at Staff level in our company?"
3. "Here are the actions I'm planning to close the gap [share the list from Section 4]. Do these seem right? What would you add or change?"
4. "Who else on the leadership team needs to see my work firsthand? How can we create those opportunities?"
5. "Can we do a monthly check-in specifically on promotion readiness between now and June? I want to course-correct quickly if needed."

**Key Outputs:**
- Written agreement on what "good" looks like (even informal -- a Slack message or email summary is fine)
- List of 2-3 specific leaders your manager thinks need to witness your cross-functional leadership
- Monthly check-in cadence scheduled

### 5.2 The April Check-In

**Goal:** Share progress, get calibration feedback.

**Agenda:**
1. Share evidence of cross-functional leadership actions taken since March
2. "On a scale of 1-5, how confident are you that I'm on track?"
3. "Is there anything that's happened since our last conversation that changes the picture?"
4. "Have you had any conversations about the June cycle that I should know about?"

### 5.3 The May Check-In (Critical)

**Goal:** Confirm the packet is ready and your manager will advocate.

**Agenda:**
1. Walk through the draft promotion packet (see Appendix)
2. "Will you be recommending me for promotion in June?"
3. "What's the strongest objection someone on the committee might raise? How do we address it?"
4. "Who are the 2-3 peers you'll ask for feedback? Can we make sure they're people who've seen my recent cross-functional work?"

### 5.4 What to Do If Your Manager Wobbles

If at any check-in your manager signals hesitation:
- **Don't panic.** Ask: "What specifically would need to be true for you to feel confident recommending me?"
- **Get it in writing.** Summarize the conversation and share it back: "Here's what I heard -- does this capture it?"
- **Accelerate gap-closing.** Double down on whatever they flag.
- **Have a backup plan.** If June isn't going to happen, ask your manager to commit to a specific timeline and criteria for the next cycle. Get it in writing.

---

## 6. Sponsor & Visibility Map

A promotion at Staff level is not just about your manager's support. It requires **organizational consensus** that you're operating at that level. Here's your map.

### 6.1 Key Stakeholders & Their Current Perception

| Person | Role | Current Relationship | Current Perception of You | Action Needed |
|--------|------|---------------------|--------------------------|---------------|
| **Your Manager** | Direct Manager | Strong, supportive | "Strong Senior PM, needs more XFN visibility" | Maintain alignment (Section 5) |
| **Your Skip-Level** (VP Product / CPO) | Promotion decision-maker | Likely limited direct interaction | May see you as "solid executor" | Needs to see you as a strategic leader (Action below) |
| **VP of Engineering** | Key cross-functional partner | Collaborated on onboarding + API | Likely positive | Convert to active sponsor (Action below) |
| **CTO** | Technical strategy leader | Interacted on API platform | Depends on depth of relationship | Ensure they see your platform strategy thinking |
| **Head of Customer Success** | Cross-functional partner | Collaborated on onboarding + pricing | Likely positive | Secure as a reference for promotion packet |
| **CFO / VP Finance** | Pricing migration partner | Collaborated on pricing | May not think of you in "PM promotion" terms | Secure a quote about your cross-functional impact |
| **VP of Sales** | Revenue stakeholder | Pricing migration, enterprise features | Depends on relationship depth | Ensure they see you as a partner, not a service provider |
| **Fellow Senior/Staff PMs** | Peer calibration | Varies | Peers will be asked for feedback | Ensure positive peer signal |

### 6.2 Sponsor Development Actions

#### Primary Sponsor Target: VP of Engineering

**Why:** They've seen your work across multiple initiatives, they have credibility in promotion discussions, and Engineering leaders' endorsement of a PM carries extra weight.

**Actions:**
- Schedule a 1:1 in the next two weeks. Frame it as: "I'd love to get your perspective on the API platform strategy and where we should take it next quarter."
- In the conversation, demonstrate Staff-level strategic thinking. Don't just ask for input -- bring a point of view and engage in a peer-level dialogue.
- After the meeting, follow up with a written summary and thank-you. This creates an artifact of your engagement.
- When your manager is building your promotion case, suggest the VP of Engineering as a reference.

#### Secondary Sponsor Target: Your Skip-Level (VP Product / CPO)

**Why:** They likely have significant influence or veto power over the promotion decision.

**Actions:**
- If you don't have regular skip-level 1:1s, ask your manager to facilitate one (or ask directly -- this is normal and expected).
- Bring the strategic memo (Section 4, Action 2) to this person for input before you present it broadly. This gives them ownership of your strategic work.
- Ask for their perspective on what Staff-level PM leadership looks like at your company. This signals intent and invites them to mentor you toward the outcome.

#### Visibility Amplifiers

These are people who won't decide your promotion but who create ambient reputation:

- **Slack/public channels:** Share learnings, recognize cross-functional partners, post updates on your initiatives in company-wide channels.
- **All-hands or demo days:** Present the enterprise onboarding results or API platform vision. Volunteer for these spots.
- **Internal PM community:** If your company has PM meetings, offer to present the pricing migration playbook or onboarding learnings.
- **Engineering team demos:** Attend and engage with engineering demos for adjacent areas. Ask thoughtful questions. Be known as someone who cares about the whole product.

### 6.3 Visibility Calendar (March - May)

| Week | Visibility Action |
|------|-------------------|
| March W3 | 1:1 with VP Engineering on API platform strategy |
| March W4 | Launch cross-functional API Platform Stakeholder Review |
| April W1 | Skip-level conversation with VP Product |
| April W2 | Present "Enterprise Onboarding Learnings" at PM team meeting |
| April W3 | Share "State of the Platform" memo with leadership team |
| May W1 | Present pricing migration playbook at all-hands or PM meeting |
| May W2 | Facilitate Q3 cross-team planning session |
| May W3 | Final manager check-in; packet finalization |
| June | Promotion cycle |

---

## 7. Timeline & Milestones to June

### Phase 1: Foundation (March 17 - March 31)

- [ ] Hold the March manager alignment conversation (Section 5.1)
- [ ] Get explicit agreement on success criteria and gap-closing actions
- [ ] Schedule 1:1 with VP of Engineering
- [ ] Identify a mentee PM and begin relationship
- [ ] Identify the "stretch" cross-functional problem to own
- [ ] Begin drafting the strategic memo
- [ ] Start the evidence log cleanup (quantify all impact numbers)

### Phase 2: Execution (April 1 - April 30)

- [ ] Run first API Platform Stakeholder Review
- [ ] Present enterprise onboarding learnings to PM team
- [ ] Complete and present the strategic memo to leadership
- [ ] Hold skip-level conversation with VP Product
- [ ] Hold April manager check-in
- [ ] Collect cross-functional feedback quotes
- [ ] Continue mentorship relationship with visible touchpoints

### Phase 3: Close & Package (May 1 - May 31)

- [ ] Facilitate Q3 cross-team planning (if timing works)
- [ ] Present pricing migration playbook internally
- [ ] Finalize all evidence with quantified metrics
- [ ] Draft the promotion packet (see Appendix)
- [ ] Hold May manager check-in -- confirm recommendation
- [ ] Ensure all sponsor relationships are warm
- [ ] Submit packet per company process

### Phase 4: Promotion Cycle (June)

- [ ] Be available for any committee questions or additional info requests
- [ ] Continue operating at Staff level -- the promotion should feel like a recognition of existing behavior, not a goal you stop working toward

---

## Appendix: Promotion Packet Draft

Below is a template for the actual document your manager will submit (or you will submit and your manager will endorse). Adapt to your company's specific format.

---

### Promotion Recommendation: [Your Name], Senior PM to Staff PM

**Prepared by:** [Your Manager's Name]
**Date:** [June 2026]
**Current Level:** L3 (Senior PM)
**Proposed Level:** L4 (Staff PM)

#### Summary

[Your Name] has consistently operated at Staff PM level for the past [X] months across three high-impact, company-level initiatives. They have demonstrated the cross-cutting scope, strategic influence, and organizational leverage that define Staff-level PM leadership at [Company].

#### Evidence of Staff-Level Performance

**1. Enterprise Onboarding Redesign (Staff-Level Scope & Execution)**

Led a cross-functional initiative spanning Engineering, Design, Customer Success, and Sales Engineering to redesign the enterprise onboarding experience. Reduced time-to-value from 14 days to 3 days (78% improvement), directly improving enterprise net revenue retention by [X%] and protecting an estimated $[X]K in ARR. This required aligning four teams with competing priorities, making difficult tradeoff decisions, and navigating ambiguity in customer requirements.

**2. Pricing Migration, 2,000 Accounts (Staff-Level Decision-Making & Influence)**

Drove the company's most consequential customer-facing change in [timeframe], affecting 2,000 accounts and $[X]M in ARR. Partnered with Finance, Legal, Sales, CS, Marketing, and Support to design and execute the migration. Owned the decision framework and recommendation to the executive team. Result: [X%] successful migration rate, [X%] net revenue impact, [X] support ticket volume vs. plan.

**3. API Platform Roadmap (Staff-Level Strategic Ownership)**

Owns the company's API platform strategy, a multi-quarter bet on ecosystem-driven growth. Defined the platform vision, established API design guidelines now used company-wide, and built the partner integration framework. The platform now supports [X] external integrations and [X%] of enterprise deals cite API capabilities as a buying factor.

**4. Cross-Functional Leadership & Organizational Impact (Since March)**

- Launched and leads the API Platform Stakeholder Review, a monthly cross-functional forum that has improved alignment between Product, Engineering, Partnerships, and Sales
- Authored the "State of the Platform" strategic memo, which influenced Q3 planning priorities
- Created the Pricing Migration Playbook, now being reused for the upcoming [initiative]
- Mentors [PM Name], contributing to PM team development
- Facilitated Q3 cross-team planning for [area], improving prioritization alignment

#### Peer & Stakeholder Feedback

> "[Quote from VP Engineering]"

> "[Quote from Head of CS]"

> "[Quote from CFO or VP Sales]"

> "[Quote from peer PM]"

#### Recommendation

[Your Name] is operating at Staff PM level today. Promoting them to L4 recognizes existing performance, retains a high-impact leader, and signals to the PM team what Staff-level performance looks like at [Company].

---

## Final Notes

### What This Pack Does NOT Include (And Why)

- **Compensation benchmarking:** That's a separate negotiation. Focus on getting the level first.
- **Threat of leaving:** Never use this as a tactic in the promotion conversation. It poisons the relationship and often backfires.
- **Comparisons to peers:** Your case should stand on its own merits. Avoid "I do more than X who is already Staff."

### Common Failure Modes to Avoid

1. **Assuming the work speaks for itself.** It doesn't. You must actively narrate, frame, and amplify.
2. **Waiting until the packet is due to build the case.** You have ~3 months. Use them.
3. **Treating promotion as a checklist.** It's a perception shift. People need to *feel* that you're already operating at the next level.
4. **Neglecting peer relationships.** Peer feedback sinks more promotions than manager hesitation.
5. **Over-indexing on execution, under-indexing on influence.** Your execution is proven. Your gap is influence. Spend 70% of your gap-closing effort on influence and visibility.
6. **Being invisible between now and June.** The recency bias in promotion committees is real. Your most visible work should happen in April and May.