About
Built by people who spent years in M3 environments.
M3CloudSlam exists because the visibility problem in M3 is real, persistent, and underserved. We built the platform we wished we had.
In short
Why we exist
M3 environments are hard to understand from the outside.
Every M3 project we’ve been part of shared the same challenge: nobody had a complete picture of what was actually in the environment. Data quality issues lived in spreadsheets. Process documentation was out of date. Environment differences were discovered by accident.
The tools that existed were either too generic, too expensive, or required implementation projects of their own. We built M3CloudSlam to be none of those things - a focused tool that connects to M3 and tells you what’s there in hours, not months.
We started with the Cloud Edition and added the On-Premise Edition because the visibility problem doesn’t start when you go to the cloud. It starts the day you go live on M3 - wherever that is.
The person behind it
Built by someone who has lived in M3.
Alexander van der Kuijl
Founder · LinkedIn
M3CloudSlam is founded by Alexander van der Kuijl, who has spent 15+ years inside Infor M3 - on the technical side with integrations and technical solutions, and on the functional side with business blueprinting and process design.
He knows the M3 database intimately, and has run migration projects end to end: blueprinting the business, executing massive data migrations, and dealing with the cleanup that always follows. The same gap showed up every time - teams couldn’t see what was really in their environment until something went wrong.
M3CloudSlam is the product of that experience: the tool he kept wishing existed on every project. It’s being built now, with a first group of M3 teams shaping it ahead of general release this autumn. If that’s a problem you recognise, request early access.
How we work
Principles we hold onto.
First principle
Show, don’t tell. Especially for Process Intelligence.
The moment someone sees their actual M3 processes flowing through a live BPMN canvas - built from their own transaction data - everything clicks. No amount of describing that replaces seeing it. So we don’t try. We show it in the first demo.
One question per page.
Every page we build answers: do you understand my situation? Can you solve it? What do I do next? If it fails question one, nothing else matters.
On-premise is a first-class product.
Not a "lite" version or an afterthought. More companies run M3 on-premise than in the cloud. They deserve full capability.
No cloud lock-in.
On-premise settings, rules, and findings migrate to the Cloud Edition when you migrate. We shouldn't be an obstacle to your cloud journey.
Simple to approve.
The on-premise connector is outbound-only. We wrote the IT approval checklist. Getting M3CloudSlam past procurement shouldn't be a project.
Complexity when the problem requires it.
We add features when a customer problem can't be solved without them. Not sooner.
Contact
Questions, feedback, or a conversation about your M3 environment.
We’re a small team and we read every message. If you have a question about M3CloudSlam or just want to talk about your situation, get in touch.