For managers who care,and are out of room to hold it all.

Who is LetEmily designed for?

Managers who care about developing the people they lead, run regular 1:1s, and are responsible for a small number of individuals they know by name, and who have run out of room to hold all of it at once.

The caring part is not a flourish. Emily is built around continuity: holding what someone is working toward and picking the thread back up months later, and that is only worth anything to a manager who wants to help them get there. If 1:1s are a status meeting in your world, a shared agenda document will serve you better and cost nothing.

The rest is a narrower definition than "leaders" and deliberately so. The product assumes recurring conversations with specific people, context accumulating over months, and a real cost when your attention has to be somewhere else. If your role is closer to running a function through metrics than knowing a handful of individuals well, most of this will not land.

• →Team leads and first-time managers building the habits good leadership needs
• →Experienced people managers trying to keep their depth as the team grows
• →Engineering, product, and design managers running weekly 1:1s
• →Directors leading through other leaders, keeping the thread across a wider group
• →Founders who manage directly and have no HR function behind them

Is LetEmily for the manager, or for the team?

Both, though only one of them ever logs in. Emily works for the manager, from the manager's own notes, but what she is for is the growth on both sides of that relationship.

For the people you lead, it is continuity: someone who remembers what they said they wanted, builds on the last conversation, and does what they said they would do. That is most of what good management feels like from the receiving end.

For you, it is the only honest record of how you have actually been leading. Not a rating, a record. Where your attention went, which conversation you keep putting off, what you committed to and whether you closed it. Managers are usually wrong about all three, because until now nothing was writing them down.

When should someone start?

When the number of people you manage exceeds what you can reliably hold in your head, which for most managers is somewhere around four or five direct reports, or any number of reports plus a reorg.

The other reliable trigger is time rather than headcount. Context decays over months, so the manager who has had the same three reports for two years is holding a much larger history than the arithmetic suggests. If you have found yourself asking someone a question you know they already answered, that is the signal.

Does this replace leadership training or coaching?

No, and it is not trying to. A course teaches you what good looks like; a coach helps you work out what to do about your particular situation. Emily does neither.

What it does is the part both of those depend on and neither provides: keeping the record straight between one conversation and the next, so that the habits you are trying to build have something to hold on to. Learning a feedback framework does not help if you cannot recall whether you already gave the feedback.

Who is LetEmily not for?

Several groups, and it is worth being direct about them rather than letting someone find out after signing up.

If you need any of the following, this is the wrong tool and a different category will serve you better.

• →HR teams needing employee records, performance cycles, or compliance workflows
• →Executives wanting organisation-wide sentiment measurement or engagement scores
• →Anyone looking to monitor team members' activity, output, or messages
• →Teams wanting a shared 1:1 agenda that both people co-own and edit
• →Managers who need meetings recorded and transcribed
• →Project or task management for the work itself

Does team size matter?

It changes what you notice first, but not whether the product works. It is used the same way at three reports as at fifteen.

With a small team the value shows up as depth: you remember the specifics of what someone told you in March, and career conversations get concrete. With a larger team it shows up as coverage: knowing who you have not spoken to properly, and which commitments have been quietly aging across a group too big to audit from memory.

Does it work for managers outside engineering?

Yes. Nothing in the product is specific to software teams.

The mechanics: recurring 1:1s, commitments made in conversation, context that fades between meetings: are the same whether you manage designers, sales, support, operations, or research. The reason engineering and product managers come up often is that they tend to be early adopters of tools, not that the problem is theirs.

Do you need approval to use it at work?

Often, yes, and you should check. LetEmily holds notes about named colleagues, which most organisations treat differently from an ordinary productivity app.

A manager can sign up individually in a few minutes, but that does not make it a policy decision you get to skip. If your organisation restricts where employee information may be stored, that restriction applies here. The security and privacy page sets out what is held, which providers are involved, and how to export or delete everything.