PM Role Charter Example: SaaS
Role: Product Manager, Route Optimizer (Fieldlight) Why this example exists: the PM was told they "own revenue" for an add-on but didn't control pricing, packaging, or the sales motion. The charter made the gap visible instead of personal.
**Role:** PM, Route Optimizer · **Reports to:** Director of Product · **Reviewed:** Nov 13 · **Next:** Feb
1. **Outcome:** Dispatchers at mid-size service companies run their day with the optimizer, and enough accounts adopt it to justify the investment.
2. **Scope:** In: Route Optimizer (roadmap, onboarding, proof). Out: base platform, billing engine, pricing model.
3. **Decisions owned:** what the optimizer's roadmap includes; what ships in a release; the onboarding experience; which proof points we publish.
4. **Decisions shared:** price and discount bands (**VP Product** decides; PM drives the analysis); launch go/no-go (**VP Product**); customer-specific commitments (VP Sales inside bands, VP Product outside).
5. **Interfaces:**
| With | PM provides | PM gets |
|---|---|---|
| Engineering | Problem, priority, acceptance | Feasibility, sizing |
| Sales | Narrative, proof, battle cards | Deal feedback, objections |
| Support | Release notes, runbook | Ticket themes |
| Finance | Attach and margin assumptions | Margin floor |
6. **Success measures:**
| Measure | Type | Influence | Target |
|---|---|---|---|
| Trials reaching first optimized route in 7 days | Leading | Onboarding, defaults | `[NEEDS SOURCE]` |
| Seats activated / purchased | Leading | Onboarding, CS enablement | `[NEEDS SOURCE]` |
| Attach rate at 180 days | Lagging | Product + proof (not price, not sales motion) | 15% (business case) |
**Gap:** attach depends on sales motion and pricing, which the PM does not control. Manager to confirm
the attach target is shared with the VP Sales.
7. **Not this role:** project management (delivery lead), quota or pricing decisions (VP Sales / VP Product), customer support (Support lead), release scheduling (engineering manager).
**Confirmed by:** manager ☑ · VP Sales ☑ · engineering manager ☑What to learn from this
- The gap is written on the page, so the conversation is about the structure, not the person.
- The PM drives the pricing analysis but doesn't decide it, which is honest and still useful.
- "Not this role" names four real tasks, and who owns each.