Turn meeting transcripts into instant 1:1 prep.

Drop in your meeting transcripts. Nexus links every meeting to the projects and people in it, so before a 1:1 you pull up any person and see every meeting you have had, every project they touch and every preference you noted, each cited to the transcript it came from.

Run Nexus
AuthorMariete
AgentNexus
Runtime~ 5 minutes to ingest a month of transcripts
IndustryPeople & Management
  1. 1

    Describe the task

    Nexus can take a folder of meeting transcripts, SRT files, text exports, pasted notes, and wire every meeting to the projects discussed and the people in the room. It extracts each person, the events they attended, the projects they own and the preferences they voiced, then links them, so before a 1:1 you open one person and see your entire shared history at a glance, every meeting, every project, every stated preference, each cited to the transcript it came from.

    The more consistently you name things, the tighter the joins. Tell Nexus where the transcripts live, which people and projects to track, and how you want each fact cited, and it resolves the same person across a dozen meetings to a single node instead of scattering them across the calendar.

    Index the meeting transcripts at drive://team/transcripts and connect meetings, projects and people. For every transcript: - Extract the people present and the projects discussed - Capture any preferences someone states, how they like to work, decisions they favour - Link each person to the meetings and projects they appear in When I ask about a person, show every meeting we have had, the projects they touch, and the preferences they voiced, and cite the transcript and date for each.

  2. 2

    Give Nexus context

    In a Nexus workspace, point the run at the folder of transcripts and tell it which people and projects matter. Nexus reads them together, so a teammate mentioned across ten weekly syncs resolves to one person node with the full thread of meetings behind them, not ten disconnected mentions.

    Give Nexus a short roster of names and handles if your transcripts label speakers inconsistently, “A. Reynolds”, “Ana”, and “AR” resolving to one person keeps a 1:1 history from splitting across three half-empty profiles.

    Required context
    A folder of meeting transcripts, SRT, text, or pasted exports, to index
    The people and projects that matter to you, so the right entities surface first
    Optional context
    A roster mapping speaker labels and nicknames to one person, so mentions resolve cleanly
    A Connected-mode team vault, so a manager and their lead share one meeting graph
    A list of the projects you own, so a person’s work surfaces grouped by initiative when you query
    team/transcripts folderroster.mdmy-projects.md
  3. 3

    What Nexus creates

    Nexus reads every transcript, extracts the people, projects and preferences, and links each person to the meetings and initiatives they appear in. You get a person-centred graph for 1:1 prep: open anyone and Nexus lists every meeting you have shared, the projects they touch and the preferences they voiced, each cited to the transcript and date, so you walk in with the full thread instead of scrolling your calendar.

    From Nexus: Indexed 96 meeting transcripts into a person-and-project graph, ready for 1:1 prep.

    96Transcripts indexed
    1,240Entities extracted
    100%Facts cited to a transcript
    Prep sheet for Ana Reynolds3 meetings
    MeetingProjectDateSource
    Weekly syncAtlas migrationJun 03sync-jun03.srt
    Design reviewAtlas migrationJun 12review-jun12.srt
    1:1Career growthJun 191on1-jun19.srt
    Preferences she voiced2 noted
    PreferenceSourceDate
    Prefers async design feedback over live reviewreview-jun12.srtJun 12
    Wants to lead the next migration phase1on1-jun19.srtJun 19

    "Ana appears under three speaker labels across these transcripts, I resolved them to one person using the roster. Want me to pull her open threads from the last 1:1 so you can follow up, each cited to the transcript?"

  4. 4

    Follow-up prompts

    Surface open threads before the next 1:1

    Nexus can walk a person’s recent meetings and surface the projects and preferences that came up but have no follow-up yet, so you walk into the next 1:1 already knowing what to pick back up, each thread cited to where it was raised.

    For Ana Reynolds, list the projects and requests she raised in our last three meetings that we have not followed up on, each cited to the transcript and date it came from.

    See how a project connects its people

    Ask Nexus to walk a project instead of a person and it returns everyone who has touched it across meetings, with the path of who raised what, so you can see the full cast of an initiative before a kickoff or a handover.

    Show me everyone connected to the Atlas migration across all transcripts, how each person is involved, and cite the meeting and date each connection came from.

    Fold in new transcripts as they land

    After each week of meetings, drop the new transcripts in the folder and re-point Nexus at it, the new meetings join the graph on your next run, extended onto the people and projects already there. There is no live sync, you re-run whenever you want the history current.

    Re-index drive://team/transcripts and fold in this week’s new meetings. Show me any new projects or preferences per person since the last run, each cited to its transcript and date.

  5. 5

    Tips and troubleshooting

    A roster keeps one person from splitting

    Transcripts label speakers inconsistently, initials, first names, full names. Without a roster Nexus may create three profiles for one teammate. A short name-mapping list is the single biggest lever on how complete each 1:1 history reads.

    Preferences are their own entity type

    When someone says how they like to work, Nexus captures it as a preference linked to that person, not buried in a transcript. Ask for a person’s preferences directly and you get the working-style notes you would otherwise have to remember.

    Nexus joins the notes, it does not write them

    Nexus links meetings, people and projects and cites the transcript for each, it does not summarise or draft the 1:1 agenda itself. When you want the prep note written up from the graph, pair it with Painter or Builder.

  6. Ready to try it yourself?

    Drop in your meeting transcripts, name the people and projects that matter, and open anyone before a 1:1 to see every meeting, project and preference you share, each cited to the transcript it came from.

    Run Nexus