Emily works in the background.You show up in the foreground.

What context reaches Emily?

Four things: meetings from your connected calendar, short notes you write, follow-ups you capture, and: optionally, an introduction form your team members fill in themselves.

That is the whole input surface, and it is deliberately narrow. Emily does not read your email, monitor your team's activity in other tools, join calls, or record audio. What she holds is what a manager chose to write down, plus the calendar that says who you are meeting and when. She can only help with context she has been given, which is also the reason she can never become something your team has to worry about.

• →Calendar meetings from Microsoft Outlook or Google Calendar
• →Notes you capture in the app or from inside Slack
• →Follow-ups and commitments you log, in one line
• →Introduction forms completed by your team members
• →Your own weekly reflections

What does Emily do with it?

She attaches each piece to the right person and keeps the thread connected, so the history of a working relationship accumulates in one place instead of scattering across tools. This is the memory layer, and everything else depends on it.

A note you write during a 1:1 lands on that person's profile. A follow-up you capture becomes a tracked item rather than a sentence in a document. A meeting on your calendar becomes an anchor the surrounding context hangs off. Nothing needs filing, tagging, or sorting into folders.

Emily then works over that context while you are busy elsewhere: assembling prep briefs, watching for commitments going overdue, spotting a theme that keeps recurring or a person nothing has been written about in weeks, and: on Pro: answering plain-language questions drawn from your own history with your team.

What comes back out?

Context, delivered before you need it rather than stored until you have the time and the presence of mind to go looking. That difference is the whole product: a record you have to remember to consult is competing for the attention you already did not have.

Before a 1:1 you get a prep brief: what you discussed last time, what is still open between you, and what has changed for that person. During the week you get quiet nudges about follow-ups that are aging, and a short list of things worth a second look. At the end of the week you get a reflection that looks across your whole team rather than one person at a time.

None of it is a score, a ranking, or a report about your team members. It is your own material, returned at the moment it is useful.

How does that actually make you a better manager?

By changing what happens in the conversation. A 1:1 that opens with "how did the resourcing thing land?" is a different meeting from one that opens with "so, what have you been up to?", and the difference is entirely in what you walked in holding, which no longer depends on what you happened to have room for that week.

Continuity is what turns a series of check-ins into development. Someone told you in March that they wanted more architecture work; if that is still in view in June, you can notice the design review they were not invited to and do something about it. If it is not, you have a pleasant conversation about this sprint and the year quietly passes without them getting closer to anything.

The same applies to the harder end. Feedback you gave and never returned to did not land: it evaporated. Knowing you gave it, and when, is what makes the second conversation possible.

Who acts on the output?

You do. Emily has no path to your team: she never sends messages, schedules anything, or speaks on your behalf.

This is a deliberate boundary rather than a missing feature. A tool that emails your report on your behalf makes the relationship worse, not better; the value of a manager remembering something is that the manager remembered it. Emily's job ends at putting the right context in front of you before the conversation.

She also does not judge, in either direction. Emily will tell you that a commitment has been open for five weeks. She will not tell you whether someone is performing, and she will not grade how you are leading. Facts and signals to you; the judgment stays with the human who knows the situation.

What happens over time?

The context compounds, and both kinds of growth start to become visible, the team member's, and your own.

After a month you stop re-asking questions people already answered. After a quarter you have an accurate record of what someone said they wanted, which makes career and development conversations concrete rather than a recollection contest, and you can see progress that is genuinely invisible week to week.

For you, the weekly reflection accumulates into something no one else keeps: where your attention actually went, which conversations you kept postponing, what you committed to and whether you closed it. Managers are usually wrong about all three, because nothing until now was writing them down.

The effect people notice first is smaller than any of that: they stop apologising at the start of 1:1s for not remembering.

How long does setup take?

A few minutes. Connect a calendar, add the people you manage, and start capturing a line after each conversation.

There is no data migration step and no configuration to plan. The first prep brief is thin because Emily has nothing to work from yet, the product gets useful over the first two or three weeks as real context accumulates, which is worth knowing before you judge it on day one.