1. Install and sign in
In ChatGPT or Claude, find CRE Brain in the app or connector directory, choose Connect, and complete the browser sign-in. Your firm must already have given you a CRE Brain seat: connecting links your own account, and a workspace stays reachable only by the people invited to it.
The listing and that sign-in are the whole setup. If CRE Brain does not appear in your directory, whoever administers your ChatGPT or Claude workspace may need to approve it first. No seat yet? Ask for an invitation — workspaces open in order, as capacity allows.
Publication status. The public directory listings are subject to OpenAI and Anthropic review. Invited pilots may receive an administrator-provisioned connection while that review is underway; the normal released experience remains directory install, sign in, done.
2. Recall firm knowledge
Ask naturally: “What do we know about Harborview Plaza?”, “Why did we pass on 88 Elm?”, or “What changed this week?” CRE Brain searches only what you are cleared to see and returns the relevant records with who wrote them, when, how solid they are, and where they came from. A record you keep private stays visible to you alone.
Every result cites its source. Most assistants draw it as an evidence card; where a surface cannot render one, the same answer arrives as plain text.
3. Capture and correct
There is no save command to learn. Work the way you already do, and when the conversation produces something worth keeping — a quote, a decision, a pass reason — your assistant offers to file it. Nothing is stored until you say yes. Every record it stores stands on its own, with an author, how solid it is, the property, person or company it is about, and a source you can see. Anything secondhand or inferred has to be confirmed before it joins shared memory.
A correction supersedes the record it replaces instead of erasing the history. Deleting for good is possible only for a live record you wrote yourself, and only if you ask for it outright. Raising something to firm policy is its own deliberate step, and only the author of a private record can open it to the team.
4. Evidence and confidence
Every claim uses one of four evidence classes:
- Filed
- Supported by a document of record.
- Stated
- Said directly by a person positioned to know.
- Heard
- Secondhand information that remains visibly unconfirmed.
- Assumed
- The team’s inference, labelled for verification before reliance.
A claim taken out of a document waits in the review queue with the passage it came from, which document that was, and which version of it. Approving the claim files the record and keeps that trail attached to it, so a line lifted out of a document never becomes firm policy on its own.
5. Governed improvement
Two kinds of suggestions wait for a person, and both live on the dashboard’s review page. Knowledge changes are facts your assistant proposes adding to the record; each waits with its evidence until someone approves it. Workflow changes start when you tell your assistant an answer helped or missed: it keeps that note on the record, and a proposed fix has to cite your feedback, show a test run somebody else can repeat, and be approved by a second person. Approval clears the change for a reviewed release; nothing about how CRE Brain behaves changes on its own. That is what lets a team build on what it learns without one conversation rewriting how everyone works.
6. Access and privacy
Who you are, which firm you belong to, what you are allowed to see, and whether a record has expired, been deleted or been superseded are all checked every time CRE Brain answers. If any of that is unclear, you get nothing rather than somebody else’s knowledge. We do not sell customer information, and we never train a general-purpose AI model on a firm’s knowledge.
Results returned into ChatGPT, Claude, Codex, or another assistant become part of that conversation, which is then also covered by that assistant’s own retention and workspace settings. See the Privacy Policy for how data is handled end to end.
7. Help and administration
Organization administrators control invitations, seats, connector availability, and review workflows. For access, retrieval, privacy, or security help, use the support guide or email paul@pacificsoftwareventures.com. Never send a password, invite link, MFA code, or OAuth credential in a support request.