An artifact is a result Bigmind stores or presents for a specific customer record. Artifacts turn connected evidence into information a rep, manager, or agent can review and act on. Each artifact has its own purpose and lifecycle.
Deal and Account artifacts
| Artifact | Scope | Purpose |
|---|---|---|
| Framework assessment | Deal or Account | Maintains component findings, progress or structured answers, supporting evidence, and an optional score, band, and coverage. |
| Deal summary | Deal | Provides a concise rolling account of the Deal’s current situation, recent developments, and material next steps. |
| Deal warning | Deal | Keeps a material risk visible until it is resolved and can schedule a specific future checkpoint. |
| CRM update suggestion | Deal | Highlights a CRM value that may no longer reflect the available evidence. It is a recommendation, not a direct CRM edit. |
What this looks like on a Deal
The following example assumes the workspace has created and activated MEDDICC, Deal Score, and Account Health Frameworks. These are customer-configured Frameworks, not assessments that Bigmind automatically enables for every workspace.
After a customer meeting, one Deal might show:
- MEDDICC: Champion is now In progress, with the meeting linked as evidence and a finding that the contact is influencing the evaluation but has not yet demonstrated access to the Economic Buyer.
- Deal Score: 72% · Needs attention, with buyer engagement improving but the mutual plan and close-date confidence still incomplete.
- Account Health: 84% · Green for the associated Account, based on adoption, renewal, satisfaction, relationship strength, Customer Success execution, and business outlook.
- Deal summary: a concise update that the technical review completed and the next step is procurement approval.
- Warning: “Security review is not scheduled,” kept active with a checkpoint before the planned close date.
A pipeline view can show the Framework results side by side. Selecting a MEDDICC, Deal Score, or Account Health cell opens the component findings and sources.
Framework assessments
A Framework defines what should be assessed. Customers can start from a template or configure one through the Framework settings UI or MCP. Its assessment is the current result for one applicable Deal or Account.
- MEDDICC is typically a progress-oriented Deal Framework.
- Deal Score is a scored Deal Framework.
- Account Health is a scored or structured Account Framework that considers the broader customer relationship.
Assessment components can contain an answer or status, reasoning, and source references. A calculated assessment can also show its score, label, and coverage. Not scored means the available component results cannot currently produce an overall score; Conditions not met means the Framework does not apply to that record.
Deal summaries
A Deal summary is a rolling narrative, not a transcript archive. It captures the current Deal state and should change only when new evidence materially changes that state. The summary complements structured Framework findings rather than replacing them.
Deal warnings
Warnings are lifecycle-aware notes attached to a Deal. They keep material risks visible without treating every concern as permanent.
A warning contains:
- A concise warning and supporting reasoning
- Severity
- Active or resolved status
- When it was first and most recently observed
- An optional validity date or next checkpoint
During a Deal review, Bigmind reconciles the active warning set against current evidence. A continuing risk remains active and retains its history. A warning that is no longer supported can be resolved. Users and agents can also resolve a warning directly.
If a warning should be checked in the future, its checkpoint marks the Deal for one review at that time. It does not create a recurring daily or weekly evaluation. When the CRM marks a Deal as closed, active warnings are resolved and future checkpoints are cancelled.
Warnings remain notes on the Deal and are available in Deal context and pipeline views.
CRM update suggestions
When available evidence conflicts with a Deal’s CRM state, Bigmind can suggest a change for review. For example, a close date or stage may appear stale after a customer interaction. Suggestions do not silently overwrite the CRM record.
Evidence and traceability
Where supported, Framework findings show a source count that opens the meetings, messages, activities, notes, or CRM records behind the result. Reasoning explains how those sources support the finding. An artifact can remain unchanged after a refresh when the evidence does not justify a different conclusion.
How artifacts are maintained
- A relevant customer or CRM event can cause the affected Deal or Account to be reviewed.
- A user can request a broader review with Refresh now or Refresh account level from a pipeline view.
- Existing findings and user edits are considered during later reviews so the current artifact can be preserved, updated, or resolved.
- When a Deal is closed in the CRM, ordinary automatic Deal maintenance stops, active warnings are resolved, and future warning checkpoints are cancelled.
Meeting results are separate
Meeting summaries, action items, Talking Point answers, meeting Scorecards, Trackers, and coaching belong to a specific meeting. They can become evidence for Deal or Account artifacts when the meeting is correctly associated, but they remain meeting-level results.
Configuration is not an artifact
A Playbook, Framework definition, Scorecard definition, or Tracker definition configures how Bigmind should work. The stored result for a specific Deal, Account, or meeting is the artifact. This separation lets one configuration support many customer records without mixing their results.
See Concepts for the input model and How it works for the review flow.