See Menorad OS in action before you buy.
In the demo, you do not simply see a few screens, isolated features, or a handful of AI responses. You see Menorad OS as one complete, understandable path from problem to learning.
You see how a problem enters the product and moves from problem definition and information through understanding, Human Decision, Action Plan, Outcome, and Learning.
Along the way, you can evaluate:
whether the product’s logic fits your organization’s problem and conditions;
where AI can help you and where its authority stops;
how the final decision, acceptance of important outputs, and activation of actions remain under human control;
how the path from information and Formulation through decision, action, and Outcome remains traceable;
and what limitations and level of readiness apply to the version you are seeing.
The demo shows only capabilities that actually exist and have been accepted in the version being used. Anything still on the Roadmap, under development, or awaiting acceptance is not presented as a current product capability.
The demo does not begin with the assumption that Menorad OS is right for your organization. It gives you the opportunity to examine the product itself, how it works, and whether it fits a real problem in your organization.
If, after the demo, you conclude that there is a fit, you can move into the next stage of the commercial path and discuss scope, proposal terms, and purchase.
The demo is a point for seeing the product, assessing fit, and making an informed decision about whether to continue.
When is requesting a demo the right starting point for you?
If you are dealing with a real organizational problem or decision and want to see whether Menorad OS fits your situation before buying, a demo request can be a useful starting point.
A demo is usually worth requesting when:
You have a real role in the problem or decision
You may be responsible for the decision, moving the problem forward, Strategy, Transformation, PMO, Innovation, or evaluating the purchase. Your job title alone does not determine fit; what matters is that you have a real connection to the problem and the decision path.
You can explain the problem at a high level
You do not need to have fully analyzed the problem in advance. It is enough to explain what situation led you to consider Menorad OS, what kind of decision you are facing, and why it matters to your organization.
You want to assess fit before buying
The demo lets you see the product logic, the path from problem to learning, the role of AI, human authority, available capabilities, and current limitations before deciding whether to continue.
Your organization can continue the conversation if there is a fit
If the initial review is positive, other people in your organization who are connected to the problem, the decision, the purchase, or technical requirements may need to join the conversation.
You do not need to enter a long purchasing process or provide every organizational detail just to submit an initial request. At this stage, the aim is simply to determine whether continuing the evaluation of Menorad OS makes sense.
If your need is only for a general-purpose chatbot, personal use, automated AI decision-making, or immediate purchase without a fit review, a demo request is probably not the right starting point.
Request a DemoIn the demo, you see the complete Menorad OS path—not just isolated features.
In the demo, you follow a controlled Case from the beginning of the problem to the end of the cycle so you can see the real product experience.
The main path follows the same seven stages of Menorad OS:
1. Define the problem
You see how the problem is clarified and how the scope of the work around it is established.
2. Information
You see how observations, narratives, interpretations, and hypotheses are kept distinct and why that distinction matters before analysis.
3. Understand the problem
You see how information develops into a reviewable Formulation of the problem. If the relevant AI capabilities are active and accepted in the deliverable version, you can also see AI’s role in analysis, hypothesis generation, drafting, or critique.
4. Human Decision
You see where AI can support analysis and where its authority stops. The official decision is made and recorded by a human.
5. Action Plan
You see how the decision connects to action and how its relationship to the basis of the decision is preserved.
6. Outcome
You see how what actually happened after action is recorded and compared with earlier expectations and assumptions.
7. Learning
You see how the Outcome returns to the earlier understanding so you can identify what was confirmed, what needs reconsideration, and what can contribute to further learning.
During the demo, you can also evaluate several other important questions:
where AI helps and which outputs require human review or acceptance;
how human authority is preserved in Decision and other formal points in the cycle;
how the path from information and understanding through decision, action, Outcome, and Learning remains traceable;
why tracing the Provenance of information does not mean that information is necessarily true;
what limitations and maturity level apply to the version you are seeing;
and, at the level needed for your evaluation, what needs to be clear about trust, data, and governance.
Anything that exists only on the Roadmap or is still under development is not presented as a current capability in the demo. Any AI capability, control, behavior, or feature is presented as available only when it has actually been implemented, tested, and accepted in the Release being used.
If a capability has not yet reached that state, its status is stated clearly rather than being recreated in a demo scenario as though it already existed.
After you request a demo, we first review fit with you.
Submitting a demo request does not move you directly into a purchase. We first carry out a short human review to determine whether Menorad OS appears to fit your organization’s needs and conditions.
At a high level, we discuss several areas with you:
Your organization and your role
We want to understand the type of organization you work in and how you are connected to the problem, the decision, or the evaluation of Menorad OS for purchase.
The problem or decision you are dealing with
You only need to explain at a high level what situation led you to consider Menorad OS and what kind of problem or decision you are facing.
Whether your need fits the product logic
Together, we consider whether your problem needs a structured, traceable path or whether a simpler or different tool would be a better fit.
What you expect from AI and the role of people
If you expect AI to make the final decision for you or your organization, Menorad OS is not designed for that purpose. Formal decision authority remains human.
What you expect from the product’s current state and maturity
What you see in the demo must match the version that can actually be delivered. If your organization has specific expectations around capabilities, maturity, or controls, it is better to surface them from the beginning.
The context needed for a meaningful evaluation
To keep the demo from becoming a generic presentation, we learn enough about the problem, the type of decision, and your intended use to make the evaluation relevant.
You are not expected to complete a long purchasing questionnaire for the initial request. The purpose is simply to determine, before more time is invested, whether continuing the evaluation makes sense for both you and Menorad.
If there is an initial fit, the demo is prepared around the context of the problem and the topics that matter most to you. If more information is needed to understand the situation, we may have a short follow-up conversation before scheduling the demo.
Submitting a demo request does not mean automatic acceptance, creation of access, purchase, or guaranteed entry into a Pilot.
At this stage, no fixed response time or scheduling commitment is promised unless Menorad has formally defined and can operationally support such a commitment.
If you want to continue after the demo, how does the purchase path work?
The demo does not commit you to a purchase. If, after seeing the product, you conclude that Menorad OS fits your organization’s problem and conditions, you can continue through the commercial path step by step.
1. Commercial review
After the demo, we clarify the conditions of the intended use with you:
who will use the product;
what problem or context you want to use Menorad OS for;
who in your organization is responsible for or makes the purchase decision;
what you need for initial Onboarding;
whether you need further review of data, security, or governance;
and whether you genuinely need a Controlled Evaluation or Pilot before purchase.
2. Commercial proposal or order
If you decide to continue, a specific commercial proposal or order is prepared for your purchase.
It defines the scope of use, what you are purchasing, the relevant terms, the approved amount, and what is needed to begin using the product.
Until a separate public pricing policy is approved, the amount for your purchase is determined by the valid commercial proposal for that specific purchase—not by a public price on the website.
3. Payment
Once your proposal or order is defined and approved, you can move into the Payment stage.
Your payment is tied to that valid order, and an order is considered “paid” only after the transaction has been validly confirmed.
4. Onboarding and start of use
After the purchase and payment have been validly confirmed, you move into initial Onboarding, preparation of the required access, and start of use.
The details of this stage are communicated based on the scope of your purchase and Menorad’s actual operating process. The website does not promise a timeframe or service level that has not been formally committed.
In summary, your path is:
Demo→Human & Commercial Review→Proposal or Order→Valid Payment→Onboarding & Start of Use
A Pilot is not a prerequisite for purchase. If it is needed to reduce risk or support further evaluation, it can be considered with Menorad on a case-by-case basis.
Simply seeing this path on the website does not create a contract, order, or commercial acceptance for you.
Before you pay, you know what you are buying and on what terms.
If, after the demo and commercial review, you decide to continue with the purchase, you receive a specific commercial proposal or order before making any payment.
The purpose of this stage is straightforward: before you pay, it should be clear what has actually been agreed.
Depending on that purchase, the proposal or order specifies the relevant items:
What you are purchasing
You can see what scope of Menorad OS the purchase covers and what type of access, use, or related services are included.
Scope of use and key assumptions
If your purchase defines a number or type of users, a usage period, or another commercial assumption, it is stated explicitly there.
Related Onboarding and support
If initial Onboarding, training, support, or another service is part of the purchase, its scope is clarified before payment.
Amount and any discount
The amount you pay is the amount approved in your proposal or order. Any discount must also be stated explicitly and separately in that same commercial reference.
Payment terms
Before paying, you know which order the payment relates to, what amount is due, and what stage begins after valid payment.
Assumptions, limitations, and out-of-scope items
If the purchase depends on a specific assumption or some capabilities or services are outside the purchase scope, that should be visible before payment.
Proposal validity, if defined
If the proposal has a defined validity period, it is stated there. The website does not assume one fixed validity period for every proposal.
Next step
Before paying, you should know what happens after the purchase is confirmed—for example, initial Onboarding, access preparation, or coordination of the start of use.
The scope, amount, and terms of your purchase are determined by that valid proposal or order, not by a fixed public price list on the website.
The text on this page also does not replace the commercial or legal terms of your proposal or order. Final purchase details are defined in the documents and process for that specific purchase.
Once these items are clear and approved, you can move to the Payment stage.
Before you pay, your order needs to be defined and approved.
By the time you reach the Payment stage, the amount and subject of your purchase have already been defined in a valid commercial proposal or order. You are not expected to enter an arbitrary amount on a public page and make a purchase without a specific order behind it.
Before proceeding to the payment gateway, you should be able to see:
which order or proposal the payment relates to;
exactly what you are purchasing;
the approved amount;
and what happens next after the payment has been successfully and validly confirmed.
After a bank payment, simply returning to the Menorad website does not mean the payment has been successfully finalized.
Menorad considers an order “paid” only when the transaction result has been confirmed through the valid payment process.
If the payment fails or is cancelled, or if the result is still uncertain, you should be shown that actual status. Until the payment result has been confirmed, the order should not be recorded as paid.
After valid confirmation of payment, you can move into the next stage: initial Onboarding and start of use.
Technical statements about payment security, transaction integrity, or final gateway readiness are published as confirmed capabilities only after the relevant implementation and tests have been formally accepted.
What happens after your payment is confirmed?
Once your payment has been validly confirmed, you move into initial Onboarding and preparation to begin using Menorad OS.
What happens during this stage depends on the scope of your purchase, but it should be clear how you move from “purchase completed” to actually starting to use the product.
Your access is prepared
Based on what is defined in your order, the required access for the relevant people or roles is prepared.
You get ready for first use
If starting requires initial account setup, an introduction to the product environment, or preparation of the first Case, those steps are coordinated within the scope of your purchase.
You know where to start
Before real use begins, you should know where to begin, what to do first, and how to bring your first problem or Case into the Menorad OS path.
Your expectations around AI and data are clarified
If your use includes AI capabilities, you should understand where those capabilities assist you, where human authority remains, and what requirements or limitations apply to the use of data and Context.
You know how to seek support
It should be clear which defined route you can use if you have a question or encounter an issue while getting started.
Initial Onboarding is not intended to create a complex, lengthy process. The aim is to move from purchase to first real use with clear expectations and without unnecessary ambiguity.
Specific timeframes, support levels, training details, or exact account-preparation procedures are stated on the website only if they have been formally defined and can be operationally supported by Menorad.
What you receive during Onboarding must also remain consistent with the scope and terms approved in your proposal or order.
If you need more evaluation before buying, a controlled path can be considered.
The primary Menorad OS path is to see the product in a demo, evaluate how well it fits your problem and organization, and, if you decide to buy, move into the commercial proposal and order process.
In some situations, however, you or your organization may need a more limited, controlled evaluation—a Pilot—before making the final decision.
For example, before buying you may want to:
evaluate how Menorad OS would be used in a more specific context;
involve particular organizational stakeholders in the product evaluation;
resolve a specific uncertainty about fit with your conditions;
or reduce part of the evaluation risk before making a commercial decision.
In such situations, a Pilot or Controlled Evaluation can be considered on a case-by-case basis.
A Pilot is not a mandatory stage of purchase.
If the demo and the necessary reviews are sufficient for your decision, you do not need to complete a Pilot before buying.
A Pilot is not automatically offered with every demo request.
Whether this path is needed depends on the actual conditions of your evaluation and discussion with Menorad.
If a Pilot is used, its scope should be clear from the beginning.
Before it starts, it should be clear what is being evaluated, who is involved, what context or Case will be used, what limitations apply, and which questions the evaluation is intended to answer.
A Pilot does not guarantee an organizational outcome.
Its purpose is to provide a limited opportunity to evaluate the product and reduce some uncertainty before the purchase decision—not to prove in advance that Menorad OS will be successful in your organization.
Completing a Pilot also does not, by itself, mean a purchase, full deployment, or a later commercial commitment. If you decide to continue after the evaluation, the purchase terms are defined through the commercial process for your order.
So if the demo is sufficient for your decision, the path can continue directly toward purchase. If you genuinely need further evaluation, a Pilot can be an optional, controlled path—not a prerequisite for purchase.
Before you buy, know what Menorad OS does not guarantee.
To evaluate Menorad OS properly, it is not enough to know what the product can do. You should also know from the beginning what you should not expect from the product or the purchase path.
Menorad OS does not guarantee a specific organizational outcome
The product helps keep the path of problem understanding, decision, action, Outcome, and Learning structured and reviewable. But what happens in your organization still depends on the quality of the information, human judgment, participation, actual organizational conditions, and how the decision is carried out.
Not every problem is a fit for Menorad OS
After review, you may conclude that your problem does not need this kind of structure or that another tool is better suited to your need. A demo request—or even initial interest in the product—does not mean automatic confirmation of fit.
A demo request does not create immediate access to the product
Fit is reviewed first, and the next step is determined based on your actual conditions. Submitting a request does not mean an account has been created, use has begun, or a purchase has been accepted.
The demo does not promise capabilities beyond the version that actually exists
A capability still on the Roadmap, under development, or awaiting acceptance should not be treated as a current product capability when you make your decision.
You should not infer a fixed public price from the website
Until Menorad approves and publishes a specific public pricing policy, the amount and terms of your purchase are defined in the proposal or order for that purchase.
Purchasing Menorad OS does not guarantee successful execution of a decision in your organization
The product can keep the decision connected to an Action Plan and then to Outcome and Learning, but it does not execute the decision, manage people, deliver organizational change, or produce the desired result on your behalf.
Using AI does not mean transferring decision responsibility
AI can broaden the field of analysis and support parts of the path, but responsibility for the official decision remains human.
These boundaries are not intended to reduce the value of the product. Their purpose is to give you a clear, realistic picture—before the demo or purchase—of what Menorad OS does for you and what it does not do.
If, after considering these limitations, your problem still fits the logic of Menorad OS, the next step can be to see the product in a demo.
If you want to see whether Menorad OS fits your problem, request a demo.
If you are facing a real problem or decision in your organization and want to see Menorad OS itself before buying and evaluate how well it fits your conditions, start with a demo request.
You do not need to have fully analyzed the problem before you begin. A high-level description of your organization, your role, and the problem or decision you are facing is enough.
After we receive the request, the initial fit is reviewed by a person. If continuing the evaluation makes sense, the next steps for arranging the demo are followed with you. If more information is needed to understand the situation, there may be a short follow-up conversation before the demo.
Submitting a demo request does not mean a purchase, guaranteed acceptance, or creation of product access. It is simply the starting point for seeing the product and evaluating whether Menorad OS is the right fit for your problem.