# Why product and risk need the same LLM quality numbers

When a pilot stalls, product and risk often argue past each other. Product has a demo that “feels good.” Risk has a list of fears with no pass mark. Without shared metrics, the debate never ends.

## Agree the scoreboard first

Write thresholds before the next prompt or model change:

- Task success on labeled cases  
- Groundedness or faithfulness to allowed sources  
- Refusal and policy on abuse scripts  
- Latency (p95) and unit cost under realistic load  

Put the suite in CI or on a fixed schedule. Averages alone hide failure modes. Keep examples next to every score.

## What go, hold, and no-go mean

A one-page executive summary should state a verdict, the top risks, and the next step. Hold is not failure. It means remediate before unsupervised scale.

## How Arviser helps

AI Readiness Check (from €2,900) drafts the gates and the 90-day roadmap. LLM Quality Audit (from €8,000) scores a live surface and leaves a suite you can re-run. 100% of the Readiness fee credits toward the next signed Arviser engagement within 90 days. Audit is billed on its own and is not credited forward.

**Next:** [Request audit scope](/#scope) · [How we score](/guides/how-we-score) · [Cost and latency](/guides/cost-latency-gates) · [Sample](/sample)
