Remember every conversation with the people you manage
A second brain for the people you manage. Tainure remembers what each person said in your 1:1s, then preps the next one with what you promised and coaching made for them and their career. Private to you.
Request an invite
Sarah Chen
1:1 prep
- You said you would intro her to Maya on 10 Sep. Still open.
- Raise: ask about the reorg.
- L6 expectations: what a first step looks like.
Tainure knows
- Leading the onboarding redesign; step 3 ships before the year-end freeze.
- Owes you the Q4 scope at your next 1:1.
- Building the step 3 prototype for Tomás’s interviews next month.
and 3 more from your notes
- Came from a startup where she did everything herself.
- Joined as L4 in April 2023; L5 since January.
and 1 more from your notes
- Runs a design crit better than anyone on the team.
- Tells the story of a flow end to end, from research to metric.
- Priya asks her first when she is stuck.
and 3 more from your notes
- Delegation: used to redo Priya’s screens the same evening.
- Named in May; Priya ran the crit alone on 16 Oct.
- Next step: let Priya own the outcome, not just the meeting.
and 2 more from your notes
- L6 within a year, first named in May.
- Wants onboarding to be the project people remember her for.
- Would lead the onboarding research strand if research stays with product.
and 2 more from your notes
Nora Bakker
Meeting prep
- She owes you the intro to Maya, promised 10 Sep.
- You owe her the Q4 scope for the onboarding redesign.
- Flag it: the step 3 review falls the week you move.
Tainure knows
- Onboarding activation up five points by year end.
- Step 3 shipped before the year-end freeze.
- Asked you on 16 Oct for the Q4 scope and the step 3 prototype.
and 4 more from your notes
- Nothing here yet.
- Paste a note about her past roles and Tainure fills this in.
- Nothing here yet.
- Paste a note about what she is great at and Tainure fills this in.
- Nothing here yet.
- Paste a note about what she is working on in herself and Tainure fills this in.
- Nothing here yet.
- Paste a note about where she wants to go and Tainure fills this in.
How Tainure works
Bring the notes you already take
Capture. Paste notes from a meeting, a conversation or a moment worth remembering.
Keep every conversation together
Remember. Find the context, commitments and progress you’ve captured over time.
Prepare. Ask. Take the next step
Use it. Generate a brief, recall a detail, or work through a situation with guidance.
All of it lives in your head. Until it doesn’t
- You walk into 1:1s unprepared.
- You forget what you promised two weeks ago.
- You lose track of what changed since you last met.
Walk into every 1:1 already prepared
Your prep is ready before each 1:1
What each person said, what you promised, and what to raise next, ready before you walk in.
What you owe, and what to raise next
Promises are tracked from the moment you make them, so nothing quietly slips.
What changed since your first 1:1
Every note you paste becomes a dated moment on their page.
Sarah Chen
Tainure knows
- Current work
- Background
- Strengths
- Growth areas
- Career direction
Walk into your next 1:1 with Sarah knowing where things stand, what’s moved, and what to bring up.
Sarah is leading the onboarding redesign with two deliverables due, a delegation arc that has moved from fixing Priya’s screens to coaching her, and an L6 conversation she has asked for repeatedly.
To discuss
- Ask about the reorg
- L6 expectations: what a first step looks like
- Onboarding redesign: scope for Q4
Since your last 1:1
On 16 Oct, Sarah let Priya run the design crit alone and it went well, the delegation goal named in May Oct 16. She asked again for the intro to Maya on the platform team, open on your side since 10 Sep Sep 10.
Coaching signals
- Delegation arc: in June she was fixing Priya’s screens at night Jun 4; by October she was coaching Priya instead of redoing her screens, and Priya ran the crit alone Oct 16.
Nora Bakker
Tainure knows
- Current work
- Background
- Strengths
- Growth areas
- Career direction
Walk in knowing who owes what and what you’re asking Nora for.
The step 3 prototype is now the priority, the Q4 scope is due at your next 1:1, and the intro to Maya is still open on Nora’s side.
They owe you
- Introduce you to Maya (platform PM), promised on 10 Sep Sep 10.
- Share the L6 expectations doc.
You owe them
- Write the Q4 scope for the onboarding redesign before the next 1:1 Oct 16.
- Deliver the step 3 prototype for Tomás’s interviews next month.
Your asks & updates
- Flag early: the step 3 review is planned for the week you move flats.
- Ask who owns the step 3 API spec; Jonas has been waiting five weeks.
- Ask for the L6 expectations doc she promised.
Since you last met
On 16 Oct, Nora made the step 3 prototype for Tomás’s interviews the priority and asked for the Q4 scope by the next 1:1 Oct 16.
Action items
Sarah owes
- Write the Q4 scope for the onboarding redesign before the next 1:1.
- Deliver the step 3 account-setup prototype for Tomás’s interviews next month.
You owe Sarah
- Send Sarah the intro to Maya (platform PM).
- Share the L6 expectations doc with Sarah.
Action items
Nora owes you
- Introduce you to Maya (platform PM).
- Share the L6 expectations doc.
You owe Nora
- Write the Q4 scope for the onboarding redesign before the next 1:1.
- Deliver the step 3 account-setup prototype for Tomás’s interviews next month.
Timeline
1:1
- WinLet Priya run the design crit alone; it went well: the delegation named in May.
- GrowthDelegation: coaching Priya instead of redoing her screens; she caught herself this week.
- CareerWants to discuss L6 expectations before year end.
- ActionWrite the Q4 scope for the onboarding redesign before the next 1:1.
- TopicAsked again for the intro to Maya on the platform team.
1:1
- TopicOnboarding step 3 (account setup) is stuck on the platform API spec; nobody on platform owns it.
- CareerAsked whether L6 is realistic next year.
- StrengthRuns crits with less preparation now and they still land.
1:1
- WinShipped onboarding step 2 to 100%: activation +5%, first-session support tickets down a third.
- WinPresented the full onboarding flow at the studio review; Elena asked for the deck.
- GrowthDelegation: still rewrote one of Priya’s screens the same evening; caught it after, not before.
Timeline
1:1
- TopicNora made the step 3 prototype for Tomás’s interviews the priority.
- ActionWrite the Q4 scope for the onboarding redesign before the next 1:1.
- ActionDeliver the step 3 prototype for Tomás’s interviews next month.
- TopicAsked again for the intro to Maya; still open on her side.
1:1
- TopicStep 3 is stuck on the platform API spec; who owns it is Nora’s call.
- ActionNora to introduce you to Maya on the platform team.
- ActionNora to share the L6 expectations doc.
Your second brain remembers.
It also helps you think it through
Start with a question. Tainure brings together your context and coaching resources relevant to the situation.
Chat
Coaching
Daniel Okafor
Daniel is eight months in. Why does he still go quiet instead of deciding?
On 25 Aug you asked him to write the token naming proposal rather than decide alone. On 22 Sep he was “still thinking”, and on 6 Oct the migration was “fine”.
Your notes do not say whether he knows the token decision is his to make. Does he?
I said I wanted a proposal first, so I could review it.
Then the decision may still look like yours. Try a clear boundary for this piece:
“You decide the token names. Bring me the two you are unsure about. We look at them together on Friday.”
Then ask what he decided and why. That gives him room to act, and you a way to see his judgement.
Situations
Illustrative scenarios with fictional notes. Not live AI responses.
Is this different from asking an AI assistant?
Your context, already in place
Tainure keeps your ongoing relationship history in one place. Start from the context you’ve already captured, without rebuilding the background each time.
Approaches for your situation
A library of coaching approaches gives Tainure resources for specific workplace situations, including onboarding, feedback, collaboration, career growth, and much more.
Better questions. Clearer next steps
Combined with your notes, those approaches help Tainure explore the right question, consider a different perspective and suggest a practical next step that fits your situation.
It works the other way up, too
You don’t need to manage anyone to have people worth remembering.
Keep the thread with your peers, your stakeholders, your manager
One place for everyone you work with, and what you last talked about.
Prepare every discussion before you walk into the room
What they asked for, what you wanted to raise, ready before the sync starts.
Own your growth, with coaching you drive yourself
Everything that was said about you, and what to do with it next.
Security, by default
Your notes are about the people you work with, so Tainure is built to keep them private from the start.
How Tainure handles your notesOne database per workspace
Each workspace has its own database, opened only with your address and password.
Never used to train AI
Tainure does not use your notes to train AI models, and Anthropic does not either.
Medical details removed
Tainure removes medical details before saving, and keeps only what the work needs.
GDPR compliant
Your database is hosted in Ireland, and you can export or delete your data at any time.
FAQ
The questions people ask before they request an invite. Anything else, write to beta@tainure.com.
Who is Tainure for?
Managers who want to remember what each person said in their 1:1s, and individual contributors who keep the thread with their peers, their stakeholders and their manager. It is the same product, seen from either chair.
How do my notes get into Tainure?
Paste the notes you already take, or tell the chat what happened. Tainure picks out what is worth keeping and files it on the page of the person it is about.
Does it work with my calendar?
Connect your calendar’s sharing link, from Outlook for example, and the dashboard lists the day’s 1:1s, each with its prep. Tainure reads the day’s events without saving them.
Who can read my notes?
No colleague can open your workspace. Nobody at Tainure reads your notes unless you ask for help with a problem, and you are told when that happens. The privacy page has the details.
Where is my data stored?
Each workspace has its own database, hosted in Ireland, and Tainure’s servers run in Frankfurt. Requests to Anthropic, which runs the AI models, may be processed in the United States.
What about health details?
Tainure removes medical details before saving, and keeps only what the work needs, such as an absence.
Can I take my data with me, or delete it?
Yes. You can download your whole workspace at any time as one readable file. When you leave the beta or ask us to, we delete its database, and backup copies expire after a limited period.
What happens after I request an invite?
Tainure is in private beta, and invites go out in small batches. When yours is ready, you get an email to set up your own workspace.
Make your next conversation a better one
A small private beta.