---
summary: "Recurring customer stakeholder needs by role: Finance, Department leaders, Procurement, Legal, and Customer Success each have distinct priorities that should inform product and positioning decisions."
usage_mode: auto
sort_order: 0
tags:
  - product
  - customer-success
  - orbit
refs:
  - orbit-company-overview
  - orbit-product-review-checklist
---

## Customer Stakeholder Needs by Role

**Source:** Notion - Product & Customers, last edited 2026-05-07

---

## Policy

These are recurring, role-specific customer needs observed across accounts. Use them to inform product prioritization, positioning, and CS engagement strategies.

## Stakeholder Map

| Role | Primary Need | Implication |
|---|---|---|
| **Finance** | Committed spend visibility earlier in the procurement cycle | Surface budget commitments at request approval, not at PO creation |
| **Department leaders** | Request speed - faster time from request to approval | Reduce approval routing friction; minimize back-and-forth |
| **Procurement** | Supplier file complete before the first invoice | Supplier onboarding must be finished before PO is issued, not after |
| **Legal** | Fewer emergency reviews | Route contracts with legal implications earlier; avoid last-minute escalations |
| **Customer Success (internal)** | Renewal risk visible before the account is already annoyed | CS needs leading indicators of dissatisfaction, not lagging ones |

## Usage Notes

- These needs are recurring patterns, not one-off requests. They should be treated as standing assumptions until explicitly updated.
- When prioritizing roadmap items, map each item to the stakeholder(s) it serves and verify the need is still active.
- When positioning Orbit to a new prospect, use this map to tailor the value proposition to the roles present in the buying committee.

---

See also: [[orbit-company-overview]], [[orbit-product-review-checklist]], [[orbit-known-product-gaps]]
