Most AI you've encountered in the last two years has wanted to be impressive. It wants to write your email, generate your image, and make a thirty-slide deck before you've finished your coffee. There is a place for that AI. It is not in your 1:1.
The AI inside Meetmora is named Mora. She is built on the same model class as the chatbot you used yesterday, but she has been given a very narrow job and asked to do it quietly. This post is a proper introduction.
What Mora does
Mora has read every note you've ever taken in a 1:1 with a particular direct report. She has read the agendas, the topics you've flagged, the goals you've set, the action items that closed and the ones that didn't. She has read what you wrote about the conversation last Thursday and the one in February.
This is not a small amount of text. A manager and a direct report, meeting weekly for a year, generate something like 20,000–40,000 words of context — promotion conversations, project frustrations, side comments about a sick parent, the quiet evolution of how the two people work together. That corpus is what most managers lose track of by month four. Mora doesn't.
What Mora does with it is small and specific. Three things, mostly:
- Drafts a starting agenda before the meeting. Not a generic checklist. A specific agenda built from last week's open threads, this week's goals, and the things you've flagged to bring up. You read it for thirty seconds and edit. It's a starting point, not a script.
- Surfaces the thread you'd otherwise forget. "You and Imani talked about her wanting more architecture work in November. The most recent project she's on is a feature build, not architecture. Worth checking back in?" This is the kind of observation a great chief of staff would whisper to you on the way into the meeting. Mora is your chief of staff.
- Remembers what you wrote it down to remember. Every commitment becomes a goal. Every theme gets tagged. When you sit down for next month's career conversation, the things you said three months ago are still there, in the language you used.
That's it. Mora doesn't have a personality you have to manage. She doesn't have an avatar that bobs in a corner of the screen. She doesn't ask if you'd like a haiku about Q3.
What Mora won't do
This is the more important section.
Mora won't score people. No sentiment ratings. No "engagement health" gauges. No traffic-light system that tells you who's red and who's green. People aren't RAG statuses, and the moment a tool starts insisting they are, the tool starts working against the relationship instead of for it.
Mora won't write performance reviews. This is the request we get most often, and we keep saying no to it. A performance review written from 1:1 notes would be a betrayal of the implicit contract of the 1:1 — that what was said there can be discussed there. The minute we make those notes feed an upward-facing review, the meeting starts feeling like surveillance. So Mora doesn't.
Mora won't generate fake empathy. She won't tell you "your direct report seems to be feeling X." That's not Mora's call. Mora can tell you what was said and when. The interpretation is yours.
Mora won't share what's in your 1:1 notes with the person you wrote them about. Your private notes stay private. The shared agenda is shared. The line is bright; we don't blur it.
Mora won't talk to your direct report's direct reports. Each 1:1 relationship is its own context. Mora doesn't smear information across them. If you're a manager-of-managers, Mora helps you manage your reports. She doesn't help you manage their reports.
These are not technical limitations. They are deliberate, opinionated, and load-bearing. Take any one of them out and the product becomes something different — and worse.
Three field notes from Mora
Here are three real things Mora has written in private beta. Names redacted; specifics paraphrased.
Last week you and {report} talked about her interest in moving into design management. You haven't surfaced it since. Today might be the right week — you have an opening on the agenda and the recent design crit she ran went well.
{Report} hasn't mentioned the on-call rotation in four weeks. He brought it up consistently in October. The rotation hasn't changed; he might just have stopped flagging it. Worth one specific question?
You set a goal in your January 1:1 with {report} to "find a way to give her more visibility with the leadership team." Three things have come and gone where she could have presented; she didn't. Is the goal still right?
These observations are not impressive. They are useful. The difference is the entire design philosophy of the product.
Why "quiet" is a feature
There is an aesthetic of AI right now that is loud — animated avatars, confetti when a task completes, a constant low hum of suggestions trying to be helpful. That aesthetic is wrong for the 1:1 because the 1:1 is the meeting where attention is the product. Anything that pulls attention out of the conversation, even toward something useful, is degrading the meeting.
So Mora is quiet by design. She speaks in the prep, when you're deciding what to bring. She speaks at the end, when she's helping you capture what was said. She is silent during the meeting itself. The cursor blinks once and waits for you to type. No suggestions. No autocomplete-as-you-go. The conversation is between two people, and the tool's job during the meeting is to stay out of the way.
This is the opposite of how most AI products are designed, and it's why we picked the name Mora. Mora, in Spanish and Portuguese, means delay — a pause, a holding. The AI in this product is the one that doesn't rush.
How to actually use her
A few practical notes:
- Read the agenda; don't accept it. Mora's draft is a starting point, not a verdict. Edit it in thirty seconds. The meeting is yours.
- Don't try to talk to her in the meeting view. That view is for typing notes. The Mora moments are in the prep view, the goal view, and the "between meetings" digest. We made this separation on purpose.
- Trust her recall, not her interpretations. When Mora says "you said you'd revisit this in three weeks," she's quoting you. When she says "this might be the right week to bring up X," she's making a suggestion based on patterns. Treat the first as fact, the second as a prompt for your judgment.
- Tell her when she's wrong. A small thumbs-down on a Mora moment changes how she draws from your context next time. The product gets better when you correct it.
What Mora has in common with a good chief of staff
The clearest description of Mora I've found is this: she is the chief of staff that, until now, only senior executives could afford. She knows your week, your people, and what was said two months ago. She doesn't make the decisions; she makes the decisions easier to make.
If we do our job, in six months you will not think of Mora as AI. You will think of her as part of how you manage. You won't say "the AI told me Imani brought up architecture in November." You'll just say "Imani brought up architecture in November" — because by then, you'll remember it. Because Mora made sure you did.
That's the bar. Not impressive. Useful. Quietly.
—
Try Mora — your first direct report is on us. Start a free trial →