Revenue Operations
Revenue Operations: Diagnose pipeline and forecast performance. Review stage definitions, bookings history, conversion rates, and revenue targets and produce a revenue operations analysis with corrective actions.
--- name: business-growth-revenue-operations description: Use for revenue operations when asked to diagnose pipeline and forecast performance; produce a revenue operations analysis with corrective actions. license: MIT metadata: author: Thrive category: business-growth --- # Revenue Operations ## When to use Use this skill for revenue operations when you need to diagnose pipeline and forecast performance. The expected result is a revenue operations analysis with corrective actions. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect stage definitions, bookings history, conversion rates, and revenue targets. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Trace the growth proposal through audience size, acquisition path, conversion, retention, unit economics, and delivery capacity. 2. **Decide.** Reconcile pipeline numbers and identify the largest forecast variance. 3. **Produce.** Build a revenue operations analysis with corrective actions from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Prefer a test that distinguishes demand from channel noise. Model the cost of success as well as the cost of failure. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Show the revenue mechanism and costs behind a growth recommendation. - Test whether customer value and delivery capacity support the proposed scale. ## Verification Show calculation assumptions and compare at least two scenarios. Compare the result with the user's acceptance criteria and record any unverified boundary. Return a growth experiment or decision memo with baseline, target, spend limit, and stop or scale rule. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a revenue operations analysis with corrective actions. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->