Institutional pilots
Let’s start with your workflow.
Tell us about one workflow. We’ll explore the fit in a private conversation.
Alpha · Private discussions
What a pilot involvesStart the conversation
Talk to us.
A few lines about your team and the workflow are enough. No documents needed.
Email Ma’atOr copy the address into your email service.
Walkthroughs take place in private meetings, not on this website. Please don’t include confidential data.
What a pilot involves
One workflow.
A clear purpose.
We start with a conversation, not a deployment. A pilot only proceeds once its scope, participants, data boundaries and terms have been agreed.
Understand the problem
Bring a recurring review or coordination problem, the teams involved and the outcome you need. Start with a high-level description; no customer data is needed.
Meet privately
Where there is a fit, we arrange a private discussion and product walkthrough. We do not publish walkthrough recordings or offer unrestricted public product access.
Agree a bounded test
Define the workflow, owners, success measures, duration and commercial terms together. Start with fabricated information; real data requires the appropriate controls and agreements.
Review and decide
Compare the outcome against the agreed measures, record what remains unresolved, and decide together whether to extend, change or stop the evaluation.
Who should join?
A person who owns the workflow and someone who does the day-to-day work. Involve legal, security or procurement when the proposed scope requires them.
What is agreed separately?
Availability, pricing, duration, data processing and support. An enquiry is not a promise of onboarding, a free trial, or approval for confidential institutional use.