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

# Deep Dive

> Reads every quote, affected customer and CRM record on a single topic, then reports what the underlying problem behind them actually is.

Investigates one topic in depth. It reads every matching quote in full, looks up the affected customers, and reports what the underlying problem is rather than listing what it found.

```
/closedloop-deep-dive SSO support
```

## Arguments

| Argument                  | Required | Default |
| ------------------------- | -------- | ------- |
| Topic, feature or problem | yes      |         |

Matched on meaning, not keywords. Give it several topics and it asks which to take first.

## What you get

```
DEEP DIVE: SSO support

THE REAL PROBLEM
  Not one problem. Three, and only one of them is SSO.
  Enterprise buyers need SAML to clear procurement. Existing
  customers want to stop resetting each other's passwords. Two
  accounts asked for SCIM provisioning, which is a different
  project with a different owner.

EVIDENCE
  31 insights, 24 customers, growing. 4 deal blockers, 2 stated
  churn reasons.

WHAT CUSTOMERS SAY

  Procurement blocker (11 customers)
    "Security review failed on day one. We can't buy without SAML."
      Northwind Trading, Enterprise, deal blocker

  Password fatigue (8 customers)
    "I reset four people's passwords last week. That's my Monday."
      Contoso Retail

WORKAROUNDS
  Fabrikam Group shares one password-manager vault across the team.

WHAT WE DON'T KNOW
  No closed-lost deals are attributed to this, so we can't tell
  whether deals were lost or the attribution is simply missing.
```

## Your topic is usually three topics

"Booking confirmations" comes apart into delivery failures, missing fields, localization gaps and reseller branding. Different customers, different severity, different owners.

The split is the finding. A keyword search misses it, because the four groups rarely use the same words.

## What it reads

* Every matching insight and context record in full, not the truncated preview.
* The CRM record for each affected customer, so revenue is looked up rather than estimated.
* The call transcripts behind the three or four most important quotes, for the exchange around a line.

Synthesis is written last, after all of it.

## What it will not do

* **Does not prioritize.** It sees one topic, so it cannot rank yours against the ones you did not investigate.
* **Does not score.** The customer count and the deal blockers are the score.
* **Does not recommend build or don't build.**
* **Does state its gaps.** No usage data means you know what customers say, not what they do.