We've been building Make Yourself AI for the better part of a year, mostly inside the four walls of industrial businesses. The work is public enough now that we'd rather you hear about it from us.
What myai is
Most AI products show up wanting to move your business into a chatbot. We built myai for the world that already exists in legacy ERPs, the spreadsheets your best people actually rely on, the tribal knowledge nobody wrote down. We meet you where you are.
At an aerospace manufacturer, we didn't migrate their thirty-year-old on-prem ERP. We built a bridge to it. What used to be a Monthly Operating Review someone retyped after the close became a live workspace that reasons with the nuance of their site controller. That's the shape of the work: the judgment that already runs your business, externalized and put on rails.
Users of myai
myai is built for people who know a lot about their domain but don't write code. It's also a context layer for developers who want integration and interface tooling without having to build it themselves.
If you're anywhere in operations across engineering, manufacturing, supply chain, and more, myai shows up as the colleague who already knows your stack. The reports that take three days. The spreadsheet that survives every IT memo because it's the only thing that fits. The expert whose retirement keeps quietly worrying the leadership team. myai connects to the work that exists and extends it without asking anyone to start over.
If you build agents, myai is the context layer. Your agent of choice still does the last mile. myai brings the memory, the judgment, the dimension graph of how you actually think.
Where to go next
Two doors:
→ If you're an operator with a messy problem across supply chain, finance, quality, or planning, start at /use-cases. The patterns we keep running into in customer engagements.
→ If you build agents and want to see how the engine actually works, start at /agents-101. Same operations question, three layers of harness, side-by-side. From there /platform walks through dimensions, artifacts, workflows, and the rest.
In Mark's words:
The most important thing when you use these tools is you. Your voice. Your intent. Not the connector to Excel or your ERP. This I think is undeniable. For proof: simply say nothing and see what happens. Or say something totally imprecise.