How I Run Enterprise SaaS Execution
Sprint cadence, PRD structure, stakeholder alignment, prioritisation.
Enterprise SaaS execution is mostly about not breaking a customer's quarter. The cadence is steady, the writing is precise, and the prioritisation has to handle a steady stream of competing must-haves from clients with budgets.
Two-week cycles, kicked off on a Wednesday, demoed on a Friday. The Wednesday start protects the first day from week-start chaos; the Friday demo creates a hard write-up deadline.
A one-page front (problem, decision, scope, non-goals) followed by detail. Most exec readers stop at page one — that page has to stand alone.
Async-first written updates, synchronous only when a decision is genuinely blocked. I publish a weekly note that reads as if the reader missed every meeting that week.
Some flavour of RICE, but with an explicit line for 'enterprise risk' — the cost of not doing the thing for the loudest paying customer. That risk is real but should never silently dominate the score.
- My PRD template (front page only — the part that gets read).
- How I handle three competing enterprise feature requests in the same sprint window.
- The Friday note format I use to keep stakeholders aligned without meetings.
Managed multiple products simultaneously for a large-enterprise client base, leading cross-functional engineering teams across multiple sprint cycles. The work involved feature releases, contract renegotiations on scope, and steady customer-success ops — without breaking the existing customer base.
A one-page PRD scaffold — Problem, Decision, Users impacted, Scope, Non-goals, Open questions, Owner. The detail goes in subsequent pages, but this page alone is what circulates with execs.
Enterprise execution rewards clarity over cleverness. The team that ships steadily and writes precisely beats the team that pivots brilliantly every quarter.