01 · Access
Read-only first
The first workflow can begin from agreed reports and exports. Any deeper access is separately scoped and approved.
Security and data
Controls are agreed before retailer data is connected.
A pilot begins with one bounded workflow and the minimum data it needs. Access, hosting, retention, deletion and approval rules are documented with the retailer before work starts.
Outturn does not ask a retailer to trust a vague “AI layer.” We map the data flow, show where models are used and keep accountable calculations and approvals inspectable.
Pilot controls
Start narrow. Make every boundary explicit.
02 · Data handling
Purpose-limited
The pilot documents what data is used, where it is hosted, who can access it, how long it is retained and when it is deleted.
03 · Execution
Human-approved
Outturn prepares and routes decisions. No external write is released without the named approval agreed for that workflow.
The AI boundary
Models help with messy context. They do not own the commercial decision.
Retailer data is not used to train shared models. Models may read documents, retrieve similar records and draft wording; deterministic services calculate the numbers and enforce workflow checks.
1
Every commercial figure opens to its inputs.
The formula, assumptions and source rows remain inspectable. A model does not invent or calculate sales-at-risk, recovered value or other accountable money.
2
Uncertain facts stop for review.
Extracted, conflicting or unusual facts are proposed for a person to confirm. They do not silently become operating policy.
3
Decisions keep their evidence and approval history.
The Decision Record preserves what triggered the issue, which context was used, who chose, what action followed and how the outcome was measured.
A practical next step
Bring one workflow and your security questions.
We will explain the exact inputs, boundaries and approvals before asking you to connect anything.