Start with one process. Live once your ERP is connected.
We start with one process, connect your ERP, and work with your own orders. First your team reviews, then Mae books on its own.
One process, four steps. Small enough for control, real enough for results.
Recurring, with enough volume and representative exceptions.
Orders, documents, master data, and past cases. Only as much ERP access as needed.
Mae prepares. Your team decides on uncertain fields, exceptions, and every ERP handoff.
Similar cases compared: time, corrections, and adoption in the team.
Measured in live operation. With your own orders.
Before the start, we measure the baseline in your sales office. In the pilot, we measure the same three metrics with Mae. That way the pilot shows what Mae saves you.
Three metrics
- Orders per day
- Handling time per order
- Adoption in the sales office
Your control
- Your ERP stays.
- Your data stays with you.
- First your team reviews, then Mae books on its own.
Before the first case.
Which process is suitable?
A recurring workflow, driven by documents or messages, connected to ERP data, and demanding enough that the manual effort is visible. We start with a single process.
Do we need to replace or migrate our ERP?
No. Mae works inside your ERP and within the system landscape you already use. We define the integration for the selected pilot process.
What data is needed?
Representative incoming cases and the ERP context their handling needs, such as customer, item, price, address, or order history. We agree on the scope before any connection.
Who approves the result?
At first, your team. Unclear fields and exceptions stay visible. Once a type of case runs reliably, Mae books it into the ERP on its own. You decide where that line is.
How is the productivity gain measured?
We compare the active manual handling time of similar cases before and during the pilot, with baseline, case count, corrections, and evaluation period.
What happens after the pilot?
The results show which cases run reliably, which still need review, and whether extending the workflow creates enough value. The next step follows from that.
Bring us one process. We propose the scope.
A few details are enough. We review the process, the data involved, and the ERP context.
Prefer email: hello@normind.de