> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The Journey Map

> Why most RevOps transformations fail, the maturity model from chaos to autonomy, and how this series will build each stage hands-on.

## Why most RevOps transformations fail

Most RevOps transformations fail for a simple reason: companies try to jump to the exciting part before having the foundation in place.

A recent study of over 300 RevOps leaders found that 71% consider themselves AI tool experts. Fewer than 10% can prove real ROI from those tools.

They want AI-powered forecasting before having a clean definition of what an MQL is. Churn prediction before product usage is tracked anywhere. Autonomous lead routing before anyone has agreed on what a qualified lead looks like.

The order matters. The foundation — structured, clean, ready-to-use data — is step zero. It's a prerequisite for everything else. And most B2B companies live here longer than they'd like to admit.

***

## The maturity model

Each post in this series follows a real stage in this progression. Most companies sit between stage 0 and 2. Skipping stages is the main reason things break down.

<Steps>
  <Step title="00 · Chaos" icon="triangle-exclamation">
    No reliable data. Every team has a different number. Every meeting starts by debating which number is right.
  </Step>

  <Step title="01 · Visibility" icon="eye">
    Data warehouse. One dashboard. Everyone reads the same number for the first time.
  </Step>

  <Step title="02 · Diagnosis" icon="magnifying-glass-chart">
    Funnel analysis, cohort analysis, attribution. Understanding *why* things happen — not just what happened.
  </Step>

  <Step title="03 · Predictive" icon="chart-line">
    Lead scoring, churn prediction, statistically-grounded forecast. First real AI.
  </Step>

  <Step title="04 · Prescriptive" icon="wand-magic-sparkles">
    AI suggests actions: deal coaching, pricing, next best action. Not just insights — guidance.
  </Step>

  <Step title="05 · Autonomous" icon="robot">
    Agents that detect, decide, and execute. Revenue processes that self-optimize.
  </Step>
</Steps>

***

## The data stack

We're building this with real data, using the tools most B2B revenue teams already have.

<CardGroup cols={2}>
  <Card title="CRM" icon="hubspot">
    The CRM backbone. Deals, contacts, companies, and the full sales funnel.
  </Card>

  <Card title="Financials" icon="stripe">
    Subscription and payment data. Recurring revenue, charges, and invoices.
  </Card>

  <Card title="Ad platforms" icon="bullhorn">
    Meta Ads, Google Ads, and LinkedIn Ads for acquisition signals — spend, impressions, clicks, and conversions.
  </Card>

  <Card title="Product & support" icon="headset">
    Product usage for engagement signals. WhatsApp, Slack, and Intercom for customer health and satisfaction.
  </Card>
</CardGroup>

We'll connect all of it, transform it, and activate it — sharing the control panel we build along the way to see how far we can go.

***

## What makes this series different

This isn't a theoretical framework. Each post delivers a hands-on **Skill** — an AI prompt + SQL query you can run on your own data right away.

The goal is to show what becomes possible when you have structured data. Not to prescribe a single way of doing RevOps, but to build each stage in the open and share everything: the prompts, the SQL, the results, and the reasoning behind each decision.

***

## The path ahead

<CardGroup cols={1}>
  <Card title="Chaos → Visibility" icon="arrow-right">
    Where does revenue actually come from? The first reliable answer to the most basic RevOps question.
  </Card>

  <Card title="Visibility → Diagnosis" icon="arrow-right">
    Why are things happening? Funnel analysis, conversion by source, and the end of Monday morning arguments.
  </Card>

  <Card title="Diagnosis → Intelligence" icon="arrow-right">
    Lead scoring, churn prediction, and a forecast the CFO can defend.
  </Card>

  <Card title="Intelligence → Autonomy" icon="arrow-right">
    Agents that detect stalled deals, flag churn risk, and act without waiting for someone to check a dashboard.
  </Card>
</CardGroup>

***

## Next up

The first stage: Chaos. What it looks like when your data lives in 5 disconnected tools, why the Monday revenue meeting turns into a debate about which number is right, and the first concrete step to get out of it.

<Card title="02 · Revenue Source Audit" icon="magnifying-glass-dollar" href="/use-cases/revops-series/revenue-source-audit">
  **Stage 00 · Chaos** — Where each deal comes from, conversion rate by channel, and how much revenue each source actually generated.
</Card>