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

# Discovery Call Script

> A practical first-call structure for understanding the problem before proposing a diagnostic.

## Opening

> I’d like to understand what prompted the conversation, how the process works today, where the friction is and what that means commercially. If there is a fit, we can then discuss a sensible next step.

## Why now?

* What prompted you to look at this now?
* What has changed?

## Current state

* Walk me through what happens today.
* Where does it slow down or break?
* Which work is still manual?

## Consequence

* How often does that happen?
* Who is affected?
* What happens downstream?
* How much time or cost is involved?
* If nothing changes this year, what happens?

## Previous attempts

* What have you already tried?
* Why has the problem survived?

## Decision context

* Who owns this problem?
* Who else needs to be involved?
* What would a useful diagnostic need to prove?

## Close

> What I’m hearing is \[summary]. I think the next useful step is \[specific next step]. Does that match your view?

Then agree owner and date.