Try Pro free for 14 daysHeyBrain is now live for general availability; join leading teams using HeyBrain!Start Free

SOLUTIONS · PROJECT MANAGERS

AI for project managers, with project history one question away

Use AI for project managers to ask about scope, risks and decisions. Keep project history beside the next status update.

  • Scope.
  • Ask from Claude, Cursor or Codex.
  • Keep private knowledge private.

Built for Project managers, Programme managers, PMOs, Delivery leads

What did we agree about phase two scope?

The scope note keeps reporting in phase two and excludes the data migration. The change log records the agreement. 1

Scope

Scope agreed. Risks logged. Decisions found.

Your project managers and programme managers share answers with sources.

  • Project managers

    Scope

    • What did we agree about phase two scope?

      On request

    • Which scope agreement defers reporting and excludes data migration?

      Before deciding

    Source answer: The scope note keeps reporting in phase two and excludes the data migration. The change log records the agreement.

    Sources: Scope (Google Drive); Hearth House · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Programme managers

    Past risks

    • Which risks did we log on the last migration?

      Weekly

    • Which mitigations worked for source-access and handover risks?

      Before deciding

    Source answer: The risk register lists source access and handover timing as the main risks. The retrospective records which mitigations worked.

    Recorded migration risks
    The risk register lists source access and handover timing as the main risks.
    Mitigation evidence
    The retrospective records which mitigations worked.

    Sources: Past risks (Notion); Hearth House · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • PMOs

    Sign-offs

    • Who signed off the budget change?

      On request

    • Who approved the budget change, and when?

      Before deciding

    Source answer: The change record names the budget owner and approval date. The supporting estimate is linked.

    • Open the current source before the next step

    Sources: Sign-offs (Google Drive); Hearth House · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Delivery leads

    Status summaries

    • Summarise this week's status notes

      Weekly

    • Who owns the next step after the current project dependency?

      Before deciding

    Source answer: The status notes identify the completed milestone, current dependency and next owner. Each point retains its source.

    Sources: Status summaries (Notion); Hearth House · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • Project managers

    Lessons learned

    • What would we do differently?

      On request

    • Which retrospective lessons are now in the next project checklist?

      Before deciding

    Source answer: The retrospective recommends earlier source-access checks and clearer handover ownership. The next project checklist includes both.

    • Earlier source-access checks
    • Clearer handover ownership

    Sources: Lessons learned (Google Drive); Hearth House · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Programme managers

    Internal notes withheld from clients

    • Can clients read our internal delivery and staffing notes?

      Weekly

    • Which status summary can the client read without internal staffing notes?

      Before deciding

    Source answer: The client status summary is available externally. Internal delivery and staffing notes remain restricted to the project team.

    Sources: Internal notes withheld from clients (Notion); Hearth House · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive

Less searching. More shared context.

Without HeyBrain

With HeyBrain

Search scope notes and change logs to check what phase two includes.

Find reporting in phase two, the excluded data migration and the recorded scope agreement.

Re-read the last migration’s risk register and retrospective before planning mitigations.

Find source-access and handover-timing risks, with the retrospective recording which mitigations worked.

Ask around for the budget-change approver, approval date and supporting estimate.

Find the budget owner and approval date in the change record, with the estimate linked.

Look back through retrospective notes before writing the next project checklist.

Find earlier source-access checks and clearer handover ownership, already carried into the next checklist.

ONE CONNECTED BRAIN

One question, across your tools

Bring Google Drive, Notion and your uploads into one cited answer.

Question
What did we agree about phase two scope?
Answer
The scope note keeps reporting in phase two and excludes the data migration. The change log records the agreement. (Source 1)
  • Source 1: Scope (Google Drive)
  • Additional source: Past risks (Notion)
  • Additional source: Sign-offs (Google Drive)

FOLLOW THE SOURCE

Review the evidence behind an answer

Open the citation. Read the original wording and surrounding detail.

Answer
The risk register lists source access and handover timing as the main risks. The retrospective records which mitigations worked. (Source 1)
Cited excerpt from Past risks (Notion)
The risk register lists source access and handover timing as the main risks. The retrospective records which mitigations worked.
  • Source 1: Past risks (Notion)
  • Source 2: Scope (Google Drive)

PERMISSIONS IN EVERY ANSWER

Share the context. Keep the boundaries.

Same question, different permissions. Review the request and sources in the access record.

Question
What is changing in the delivery plan?
Answer for Luca Moreau (Programme manager)
Dependencies and revised dates available. Change-order rate: $950 per day.
Answer for Mateo Navarro (Project contributor)
Dependencies and revised dates available. Restricted section withheld.
Section withheld from Mateo Navarro
COMMERCIAL TERMS · PROGRAMME LEADS
Access record
14:02 · Mateo Navarro · Source access checked · 1 SECTION WITHHELD · RECORDED

Company knowledge, under your control

Permissions you already have

Answers respect source access.

Every agent gets its own key

Set its scope. Revoke its key.

A record of every access

Review requesters, sources and access decisions.

Review provider data terms

Check provider data use and retention.

Bring your own model key

Connect your model to governed knowledge.

LESS CONTEXT. LOWER COST.

Send less context per task

HeyBrain sends only the context a task needs.

Repeated contextWhole documents
With HeyBrainRelevant passages

FAQ

Questions project managers ask

  • What did we agree about phase two scope?

    The scope note keeps reporting in phase two and excludes the data migration. The change log records the agreement. Ask follow-ups in the same conversation and open each citation to check the surrounding detail, then share the source with colleagues who can access the same collection.

  • Which risks did we log on the last migration?

    The risk register lists source access and handover timing as the main risks. The retrospective records which mitigations worked. Connect the relevant Drive folder or Notion pages, or upload documents, then follow citations to their original passages from the AI tools your colleagues already use.

  • Which sources and AI tools can we use?

    Connect Google Drive, Notion and document uploads; Claude, Cursor and Codex ask your company knowledge through HeyBrain MCP. Keep decisions and references available where your team works. HeyBrain supplies knowledge; agents use their own tools for actions requested by the user.

  • How does HeyBrain keep private knowledge private?

    People and agents receive answers from sources they can open. Workspace rules restrict the audience; each agent has its own key and scope. Administrators review requesters, times and source references in activity records alongside workspace membership and source access rules.

  • How do we get the team started?

    Connect your team’s current brief, decision notes and working guide, invite the people who need them and ask a familiar question. Open its source citations before expanding the collection. Align workspace membership and individual agent scopes with each team’s responsibilities.

  • How does HeyBrain reduce AI token cost?

    HeyBrain sends only the context a task needs instead of repeatedly passing whole documents to your AI tool. Use the context calculator to compare the amount you send and your input price. Your team shares the same connected knowledge across tools, so every new conversation can start with the relevant passages and their sources.

/ Get started today

Put your company knowledge
to work with HeyBrain