How a pilot works

Small, measured and on your terms

Pilots are deliberately small: one workflow, approved data, agreed success measures and no changes to your systems.

1. 1. Try a demo

   Use a live demo on synthetic data to see how the assistant behaves, including how it handles unknowns.

2. 2. 15-minute discovery call

   We confirm the workflow, the data you can share, success measures and whether a pilot makes sense. Sometimes it doesn't — we'll say so.

3. 3. Agree a written pilot scope

   Scope, data, responsibilities, acceptance criteria and price are agreed in writing before work starts. Drafts generated on this site are only a starting point.

4. 4. Build and evaluate

   We configure a read-only assistant on your approved data and run it against an agreed test set. Results — including failures — are reported.

5. 5. Decide together

   You decide whether to stop, extend or move toward production based on measured results.

What we never do in a pilot

• Give the assistant permission to change records, send messages, book or buy.
• Use personal information you haven't explicitly agreed to provide.
• Claim savings or ROI that haven't been measured.