Turn ops requests into written requirements (L1)
RevOps requests arrive as one line Slack messages. The assistant turns each into a structured requirement with the problem, affected process, requested change, and impacted systems, so triage happens on facts.
The steps
- 01
Fix the requirement shape
Tool: Manual
Problem, who is blocked, current workaround, requested change, systems touched. Five fields, always the same. Owner: RevOps lead. DoD: template published in the request channel.
- 02
Draft from the raw request
Tool: ChatGPT
The assistant drafts the structured version and explicitly lists what is missing. Missing information is the output that matters most here. Pitfall: the model inventing a plausible business reason. DoD: drafts include an explicit unknowns list.
- 03
Confirm with the requester
Tool: Slack
The requester confirms or corrects in thread before it enters the backlog. Thirty seconds of confirmation prevents weeks of building the wrong thing. Owner: requester. DoD: no backlog item without confirmation.
- 04
Triage weekly on impact
Tool: Jira
Rank by people blocked and revenue process affected. Publish the ranking so declined requests are visible and explained. Owner: RevOps lead. DoD: weekly ranked backlog published.
Tools in this playbook
Building the team behind this workflow?
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.