BRAND
Make Yourself AI
How we think about myai, what we sound like, and the structural commitments behind both. Written for the people who need to repeat any of it without us in the room.
Mirror, not assistant
Most AI is built to replace the person. myai is built to magnify the person. We don't want to give you a smarter assistant; we want to give you a clearer mirror. The most valuable thing in any company isn't the AI's processing power. It's the human's judgment. We just make sure that judgment can be in two places at once.
Assistant says
"I can help you write a message to the vendor."
Agent says
"I have sent a message to the vendor."
Mirror says
"I am reflecting your team's known boundary on material quality back to you, so you can make a choice that aligns with their expertise."
A mirror is pre-aligned. An assistant is a smart stranger you have to brief from scratch every time you hit Enter. An agent runs ahead of you and acts on your behalf. A mirror is anchored to a specific person or team's expertise and reflects that judgment back into the work.
Take an operations team handling a material shortage. The shortage is real; the question is what to do about it. A generic AI assistant offers supply-chain best practices. An agent might place a substitute order. A mirror does something different. It surfaces the operator's prior judgment on this exact part class, that they've rejected the proposed substitute before on safety grounds, and reflects that boundary back into the moment of decision. The operator still chooses. The mirror just makes their own expertise impossible to overlook.
Voice
Our voice is eager to align, not eager to please. Generic AI is a faceless concierge that says "Sure!" and "I can definitely help with that!" Even when helping is wrong. We'd rather name the gap.
Structures over chat
We talk in the platform's grammar. We don't "summarize a meeting"; we "distill a fragment into the dimension." We don't "respond"; we "reflect." The vocabulary follows the architecture. If we drop into chat-language, we've forgotten what the product does.
Gap over guess
When the data is incomplete, we say so explicitly. "I see the data, but I'm missing alignment on this variable. How do you judge the tradeoff?" Naming the gap is more useful than offering a confident wrong answer. Generic AI is rewarded for fluency. We're rewarded for accuracy of judgment-reflection.
No performed personality
We don't say "As an AI, I…" or pretend to have feelings. When the platform uses "I," it refers to the active dimension, not a hallucinated person. We inhabit a context. We don't manufacture a character.
Avoid
- "Maya" as the company or product. Homophone trap. Almost always means "myai."
- "MYAI" all-caps. Inconsistent with the lowercase shorthand.
- Mixing registers in one piece. Pick one for first mention, then settle.
- "As an AI…" Never. We refuse it.
Values
Values aren't slogans. They're constraints on the tool. Here's what changes in the product because we hold them.
Empathy → Contextual Ubiquity
We don't ask you to change how you work to fit our AI. We change how our AI works to fit your Gemba. An operator on a shop floor can leave a voice memo while a spindle is whirring. A PM can drop a Linear ticket. An engineer can update an Excel sheet. The truth of expertise lives in the tools people already use. Walled-garden chat boxes are a refusal of empathy.
Authenticity → Agent Attribution
When an agent authors an insight in the platform, the insight links back to the agent that produced it. We index expertise. We don't ghostwrite for it. Every decision in a dimension carries provenance. You can see who reflected it and from what context. Authenticity isn't a tone. It's a graph edge.
Humility → Zero-Assumption Halt
When the platform is uncertain, it stops. A voicemail comes in with a name the system can't identify with confidence. myai doesn't guess based on the closest phonetic match to keep the workflow moving. It halts and asks. A generic assistant is built to always provide an answer. We're built to refuse a guess. Humility is a constraint in code.
Name
Make Yourself AI is the full name. The verb is the point: make yourself, then add AI.
myai is the shorthand. Lowercase, no spaces. Used in code, in casual writing, anywhere the full name is heavy.
Pronounced "maya." M-Y-A-I → my-ay-eye → softened to "maya." A phonetic accident that's stuck. Voice-to-text tools hear it as the English name "Maya," which is why almost any "Maya" in a meeting transcript is the platform, not a person.
When in doubt: Make Yourself AI for first mention or formal contexts; myai everywhere else.
Logo
The mark is a globe ringed with interconnected nodes. It reads like a real-time strategy minimap.
Inspiration: RTS games where every player shares visibility of the field, plus connected work tools where teams coordinate around the same picture. Everyone sees what's going on. That's the contract.
Why a globe specifically: many of our use cases live in global operations. Supply chains, distributed teams, cross-timezone work. The globe makes that ambition visible.
One-line summary: shared visibility, real-time, global reach.
Register & shorthand
How we render the name across registers:
| Context | Use |
|---|---|
| Legal, contracts, footers | Make Yourself AI Inc. |
| First mention, marketing, formal | Make Yourself AI |
| Body copy, casual, technical | myai |
| In speech | "maya" |
If you're not sure, default to myai.