About Us
Make Yourself AI · myai for short · pronounced “maya”
We built myai because we lived the problem.
Mark started as a quality engineer on the manufacturing floor — diagnosing defects, running kaizen events, and falling in love with what he calls the “beautiful and chaotic organism” that is manufacturing. Over 15 years he built the information systems his operations depended on — planning tools, visual management, process optimization. He was always driven by going to gemba: the real place where the work happens. That’s not theory for him. It’s how he kept a machine shop running by doing the planning himself, and how he saved a critical Microsoft Dynamics AX implementation at Gilbarco Veeder Root. He moved from process engineering into lean leadership, then spent nearly six years at Tulip leading product growth and ecosystem strategy. Every step was the same question: how do you equip the people on the floor to solve their own problems?
William’s path went engineering, consulting, product, platform. He started at GE Aerospace, then moved to PwC as a scrappy consultant who went to the shop floor and figured out when to talk, when to build, when to just analyze. Three years at Tulip followed, inside factories of every kind: metals, forges, defense primes, continuous manufacturing, medical device, biopharma. Same wall every time. The people who understood the problems best didn’t have the tools built for them. So he started building.
How We Work
Start with the problem, not the pitch. Nobody ever fixed a plant from a glass tower with a dashboard. Dashboards show the problem. They don’t fix it. We start where the work happens, solve one real problem, and let the pattern scale site to site, use case to use case. Top-down transformation is what you get when the bottom-up keeps winning.
Humble inquiry. We go to where the work is being done. We ask questions. We treat the person doing the work as the expert, because they are. We don’t show up like know-it-all consultants.
Build with, not for. Forward-deployed engineering isn’t a delivery motion for us. It’s how we learn what the operator needs. The best requirements come from the hardest customers. If we’re not inside your environment in the first 90 days, we’re guessing.
We dogfood. We use myai to run myai. It holds our product ontology, our internal wiki, our ticket management, and the flow from a PR to a changelog entry to a docs update on this site. If we wouldn’t reach for it ourselves, we wouldn’t ship it to you.
Problems live across functions. A real problem never sits in one department. Material flow touches engineering, supply chain, manufacturing, and finance. Value has to be created, tracked, and executed across all of them. Our platform assumes this because our customers live it.
Bring us the mess.
We’ll show you the map.
Every conversation starts with your problem, not our pitch. Book 30 minutes and we’ll explore whether myai fits.