Position A — PMs must prototype or be bypassed
- Operator: Aakash Gupta
- Card: PMs who keep outsourcing first artifact will lose to PMs who arrive at design review with a working prototype
- Claim: PMs who keep outsourcing the first artifact will lose to PMs who arrive at design review with a working prototype. The PM job has shifted toward making, not specifying.
Position B — At scale, PMs should up-level the why and what, not ship more
- Operator: Amol Avasare (Ramp)
- Card: At scale, PMs should up-level the why and what; not ship more features, Claude Code multiplies engineers 2–3x; PM and design become the bottleneck
- Claim: At scale, PMs should up-level the why and what; not ship more features. Claude Code multiplies engineers 2-3x; PM and design become the bottleneck — but the answer is up-leveling, not catching up via personal output.
Conditions distinguishing them
- Company stage: Gupta's prototype-or-be-bypassed is most acute at startup / mid-stage where one PM works with 5-10 engineers and personal artifact velocity is the limiting factor. Avasare's up-level claim is scale-stage (Ramp) where the PM is one of many and the bottleneck is alignment + prioritisation.
- PM seniority: Gupta speaks to early-career PMs whose contribution is artifact production. Avasare speaks to senior/staff PMs whose contribution is leverage across teams.
- Eng tooling: Both depend on AI eng productivity; Gupta sees the PM falling behind; Avasare sees the same gap and routes the answer to up-leveling.
Resolution / synthesis
The contradiction is on the prescribed move for the PM-bottleneck problem. Both diagnose the same condition (eng now ships faster than PM). They prescribe opposite fixes:
- Gupta: PM ships more (prototype personally).
- Avasare: PM ships less (up-level to the why and what).
Reconciliation by seniority + stage:
- Junior/mid PM in a small team → Gupta's prescription (prototype, become an artifact-producer).
- Senior/staff PM at scale → Avasare's prescription (refuse to ship; do the why-work).
The trap is doing the wrong one for your stage: a senior PM who personally prototypes everything fails to up-level; a junior PM who up-levels without ever shipping artifacts becomes vapor. Both cards remain true within their stage band.