CRO Advisor
CRO Advisor: Improve revenue execution across the customer lifecycle. Review pipeline stages, win rates, sales cycle, pricing, renewals, and capacity and produce a revenue plan with forecast sensitivities, owners, and leading indicators.
--- name: c-level-advisor-cro-advisor description: Use for CRO leadership decisions when asked to improve revenue execution across the customer lifecycle; produce a revenue plan with forecast sensitivities, owners, and leading indicators. license: MIT metadata: author: Thrive category: c-level-advisor --- # CRO Advisor ## When to use Use this skill for CRO leadership decisions when you need to improve revenue execution across the customer lifecycle. The expected result is a revenue plan with forecast sensitivities, owners, and leading indicators. ## 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 pipeline stages, win rates, sales cycle, pricing, renewals, and capacity. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Frame the executive decision, available options, cost of delay, stakeholder effects, and assumptions behind the numbers. 2. **Decide.** Separate demand generation, conversion, and retention constraints before moving targets or budget. 3. **Produce.** Build a revenue plan with forecast sensitivities, owners, and leading indicators from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Test the preferred option against downside, opportunity cost, execution capacity, and reversibility. - 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 - Lead with the decision, alternatives, strategic trade-offs, and decision owner. - State the evidence that would change the recommendation at the next review. ## Verification Reconcile forecast assumptions with stage history and customer evidence. Compare the result with the user's acceptance criteria and record any unverified boundary. Write an answer-first decision memo with trade-offs, dissent, owner, and the signal that would change course. ## 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 plan with forecast sensitivities, owners, and leading indicators. 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. -->