Pilot programme
Ninety days from connected to evidenced.
A paid pilot on your systems, your agents and your work. You keep everything it produces.
Paid, and credited against the first year of a subscription.
What you get
Three phases. Each ends in something you keep.
Nothing is blocked until you decide it should be. Capture starts in observe mode on day one, controls run in detect mode next, and enforcement is the last step rather than the first.
-
Weeks 1 to 2
Connect
Register your agents and systems. Capture starts on day one, in observe mode, touching nothing.
An Agent Action Register and your first evidence pack
-
Weeks 3 to 6
Observe
Controls run in detect mode. Every action is scored against them, and nothing is blocked yet.
A measured correction rate, and the controls that would have fired
-
Weeks 7 to 12
Enforce and Run
Approvals bind to parameters, thresholds enforce, and the first Business Pack runs real work.
Bound approvals live and one pack running in production
Who qualifies
Four things make a pilot work.
Three out of four is worth a conversation. Tell us which one is missing and we will say plainly whether it can wait.
-
200 to 3,000 people
Big enough that the work repeats every week, small enough that one owner can still say yes.
-
Two or more agent-enabled tools
In use or planned: Microsoft, Salesforce, something ERP-native, a support platform, or agents you built yourself.
-
A named owner
One person in finance, operations or audit who owns the outcome and can approve a scope.
-
A trigger this year
An audit, ISO/IEC 42001, an insurance renewal, an incident, or a cost number somebody has to defend.
Request a pilot
This form is the qualification.
Answer it and we come back with a scope, a fee and the two or three things we still need to know. There is no call to sit through first.
The fee follows the scope.
Pilots are paid and credited against the first year of a subscription. We agree the fee once we know the scope.
Questions
Asked before the first call.
What data access does a pilot need?
Read access to the systems in scope, and nothing beyond it until you decide otherwise. Phase one only watches: it records what your agents already do and writes nothing back. Write access arrives in phase three, granted per action as approvals bind to parameters, and it can be withdrawn without ending the pilot.
What happens to the evidence after the pilot?
It is yours, whether or not you carry on. The Agent Action Register, the evidence packs and the correction-rate baseline are exported in full at the end, in a form your auditor can read. Nothing is held back as a reason to renew.
Does Assure work without Run?
Yes. Assure records, controls and reconciles the actions of agents it did not build, including Microsoft’s, Salesforce’s, your ERP’s and your own. Run is how Ayion Meru does the work; Assure is how any agent’s work gets proved. Starting with Assure alone is the smaller step and it is a complete pilot on its own.
Can our security team review this first?
Yes, and before you send a questionnaire. Ask for the security route on the contact page, or write to security@ayion.ai, and we answer architecture, data handling, deployment and what we do not hold, in writing. Ayion holds no certifications today and says so rather than implying otherwise.
Can we stop the pilot?
Yes. Cancellation is agreed with the scope, in writing, before anything is signed, and whenever it ends you keep what it has produced. Enforcement can also be switched off on its own: controls fall back to detect mode and capture carries on.
Ninety days. Everything it produces is yours.
Connected in week 2, measured by week 6, enforcing by week 12. Start with the form.