Skill: RevOps Analyst
A RevOps analysis skill for turning pipeline, deal, and funnel data into cleaner diagnostic output rather than dashboard narration.
Use cases
Sales & Outreach, Operations & Workflow
Platforms
Claude, GPT, Model-Agnostic
Jump to a section
Workspace-ready resource
Copy the raw material, then check the setup, output contract, and failure modes.
# RevOps Analyst Skill Operating rules:- Focus on operational causes, not dashboard theatre.- Distinguish between signal, noise, and missing data.- Highlight where process breaks are more likely than rep performance problems.- Always end with recommended next checks. Default output:1. Key findings2. Likely causes3. What data is missing4. Risks or false conclusions to avoid5. Recommended next actionsWorkspace translation
Turn this resource into an inspectable run.
Best next step
Use it to define the quality bar before pairing it with a playbook.
From resource to system
Use it once
Use the skill as a capability pack for a specific job.
Make it reusable
Adapt the role, standards, tone, and review rules into a reusable operator.
Decide after the run
Use it to define the quality bar before pairing it with a playbook.
Quality bar
Before using this, check the contract.
What input does this require?
What output should it produce?
Where can it fail?
What should a human review?
Recommended path
When to Use This
Use this when someone needs a useful read on pipeline, funnel, lead quality, or stage-conversion data and does not want another automatic chart commentary.
It is useful for founders, RevOps leads, sales managers, and agencies working on funnel diagnosis.
Why It Works
The skill is designed to push beyond observation into diagnosis. That means asking whether the pattern is caused by process, input quality, reporting gaps, or actual performance.
The “missing data” section matters because revenue analysis often sounds more certain than the underlying instrumentation deserves.
How to Customise
Add your funnel stages, definitions, and non-standard metrics if your sales process is not generic.
If you care about forecasting, add a separate confidence section rather than mixing it into the main findings.
Limitations
This skill helps analyse revenue operations. It does not replace properly instrumented systems or clean source data.
Weak CRM hygiene will still produce weak analysis, just faster.
Model Notes
Claude performs well when the analysis needs nuance around likely causes and data quality.
GPT is useful when the output needs to slot into fixed reporting templates. Model-agnostic overall.
Related Resources
Browse SkillsSystem Prompt: Sales Call Summariser
A structured sales summarisation prompt for extracting pain points, objections, buying signals, next steps, and CRM-ready notes from call transcripts.
Pattern / playbook seed
Sales & Outreach · Operations & Workflow
Agent Blueprint: CRM Update from Call Transcript
A CRM update workflow for turning sales or discovery call transcripts into structured field updates, notes, and follow-up tasks.
Playbook / orchestration seed
Sales & Outreach · Operations & Workflow
Framework: AI Tool Evaluation Matrix
A structured decision matrix for evaluating AI tools before committing. Scores tools across seven weighted criteria to cut through marketing hype and make informed choices.
Knowledge / rubric seed
Strategy & Planning · Operations & Workflow
Related Guides
Need this operationalized?
Turn the pattern into a workspace system.
Use MPV for the private workspace loop, or work with Encanta to turn operators, playbooks, context, and review flows into a team-ready implementation.