Concepts

The Context Graph is the connected customer context Bigmind can use for a Deal or Account. It links CRM records and their relationships to conversations, communications, notes, signals, workspace configuration, and the artifacts Bigmind maintains.

What is available depends on the systems connected to your workspace, the data imported from them, and the associations that connect each record. Bigmind does not assume that unrelated activity belongs to a Deal or Account.

#Core concepts

Concept	Meaning
Record	An imported CRM object such as a Deal, Account, Contact, or Lead and its current fields.
Relationship	An association or attribution that connects records, people, and interactions.
Evidence	Customer information that can support a finding, such as a transcript, email, CRM activity, or linked note.
Workspace context	Your Frameworks, Playbooks, meeting configuration, and Library knowledge.
Scope	The Deal, Account, or meeting whose context is being assembled.
Artifact	A maintained result for a specific record, such as a Framework assessment, Deal summary, or Deal warning.

#Records and relationships

The graph starts with CRM objects and the links between them.

• Record state: current Deal, Account, Contact, Lead, and other imported CRM fields. For a Deal this can include owner, stage, amount, close date, pipeline, lifecycle flags, and custom fields. See the CRM integration overview.
• Associations: the CRM relationships connecting a Deal to its Account and people, or an Account to its Deals, contacts, activities, and notes.
• Identity and attribution: the participants, senders, recipients, organizers, and owners used to connect customer interactions to the right records. See Activity attribution.

CRM fields describe the current state of a record. Associations and attribution determine which other records and interactions belong in its context. They are separate from the activity itself.

#Customer evidence

Once records are connected, Bigmind can use evidence from the systems available in your workspace:

• Meetings and calls: participants, timing, recordings or transcripts when available, summaries, action items, and meeting-level analysis such as Scorecards and Trackers.
• Email and calendar: attributed inbound and outbound messages, threads, invitations, and scheduled or completed events from connected communication systems.
• CRM timeline records: imported calls, tasks, events, and other activity records that form part of the CRM history.
• Linked notes and documents: CRM notes and other records explicitly associated with the Deal, Account, or related people.
• Signals: relevant Account events and the context supplied by configured signal sources.
• User-provided context: corrections, edits, and information users intentionally add through Bigmind.

A source can only contribute what its connection and permissions make available. A meeting without a transcript can still provide metadata, but it cannot support conclusions that require conversation content.

#Workspace context

Workspace configuration tells Bigmind how to interpret evidence for your business:

• Frameworks are customer-configured assessments that define the Deal or Account components to track, their applicability, and any scoring rules. A workspace can start from a template or build its own MEDDICC, Deal Score, Account Health, or another assessment through the UI or MCP.
• Playbooks provide guidance for a GTM motion and can reference relevant Frameworks and Library resources.
• Meeting configuration defines Scorecards, Talking Points, Trackers, categories, and other meeting-level analysis.
• Library knowledge provides approved company, product, customer, and process context when it is relevant to the work being performed.

#Deal context and Account context

Scope	Context
Deal	The Deal record, its associated Account and people, Deal-linked records, and customer interactions attributable to that sales motion. Relevant Account context can inform the review without replacing Deal-specific evidence.
Account	The Account record and the broader customer relationship across associated people, Deals, meetings, communications, notes, and signals.
Meeting	One interaction and its participants, transcript or recording, meeting analysis, and associated CRM records.

#From evidence to artifacts

Evidence is the supporting customer information. Artifacts are the maintained results users review in Bigmind, such as Framework findings, Deal summaries, and Deal warnings. Existing artifacts are considered during a later review so Bigmind can preserve, update, or resolve prior findings instead of starting from an empty state.

See Deal and Account artifacts for the artifact model and Frameworks for configuration.

Next, see How it works for a concrete example and refresh behavior.