The full series
01 · The Journey Map
The maturity model. Why 71% of RevOps leaders consider themselves AI experts — yet fewer than 10% can prove real ROI.
02 · Revenue Source Audit
Where each deal comes from, conversion rate by channel, and how much revenue each source actually generated.
03 · Pipeline Overview
The first dashboard everyone reads the same way. Deals by stage, conversion rates, and revenue by period.
Coming soon
04 · Funnel + Ads
Cross-referencing acquisition source with conversion rate by stage. When Marketing and Sales stop arguing about MQLs.
Coming soon
05 · Lead Scoring
Lead prioritization based on historical conversion rate, not gut feeling.
Coming soon
06 · Revenue Forecast
A forecast the CFO can defend. Pipeline weighted by actual win rate per stage and source.
Coming soon
07 · Deal Health Score
AI flags deals that are off the winning pattern and suggests the next action. Not just a report — a recommendation.
Coming soon
08 · Deal Alert Agent
The first RevOps agent. Monitors stalled deals and triggers alerts automatically.
Coming soon
How to run the Skills
Connect your sources
Connect HubSpot, Google Ads, Meta Ads, and other sources to your Nekt workspace.
See available integrations →
Set up Nekt's MCP in Claude
Install Nekt’s MCP as a custom connector in Claude Desktop or terminal.
Setup guide →
Paste the Skill prompt
Each use case includes a ready-made prompt. Paste it into Claude — it generates the SQL and analysis automatically.
What are Skills
Each Skill is composed of:Prompt
Prompt
The text you paste into Claude. It understands the context, queries your data via Nekt’s MCP, and generates the analysis automatically — without you writing a single line of SQL.
SQL
SQL
The full query behind the prompt. Available for anyone who wants to run it directly in the Explorer, adjust filters, change the time period, or integrate into another workflow.
Variations
Variations
Filters by time period, pipeline, customer segment, or channel. Each Skill documents the main variations to cover the most common use cases.
Implementation notes
Implementation notes
Schema details the SQL uses — table names, relevant fields, and any connector specifics you need to know before running it.