Commercial Intelligence — Technical reference

This reference owns the implementation contracts of BND-COMMERCIAL. Read the package guide for usage, configuration, dependencies and upgrades. Generic execution, isolation and admission remain governed by Platform Documentation.

Data model and interfaces

DataModelPackage: DM-COMMERCIAL

Owned entities: account, opportunity, stakeholder, influence, buying signal, objection, commercial risk, forecast snapshot, CRM comparison.

InterfacePackage contributions: IF-COMMERCIAL-INTELLIGENCE.

Each business object and source reference remains tenant- and purpose-scoped. The package owns schema evolution and declared migration behavior; the platform enforces schema registration, authorization and versioned installation. Consumers reference this model rather than creating competing canonical copies.

Workflows

WorkflowPackage: WFP-COMMERCIAL-INTELLIGENCE

• Commercial Signal Classification
• Account and Opportunity Resolution
• Stakeholder Mapping
• Buying-Signal Evolution
• Objection Lifecycle
• Opportunity Health
• Evidence-Adjusted Forecast
• CRM Comparison
• CRM Update Draft

These are named definitions within the workflow package, not separate invented workflow IDs. Workflow runs resolve package versions, actor and purpose, authorized inputs, retries, review gates and output schemas through the environment lock. Temporal provides durable execution and Kafka carries declared lifecycle/domain events.

Policies, evaluations and tools

POL-COMMERCIAL-DISCLOSURE, EVAL-COMMERCIAL, CRM and proposal connector bindings.

Qualification covers the selected model/runtime profile, languages, access scope, failure handling and the package's domain-specific outcomes. Tool execution uses the platform gateway; package code cannot increase its own permissions or write directly to external systems.

Owned agents

B01 — Commercial Intelligence Agent

Agent ID: effority.commercial-intelligence

Purpose: Detects commercial needs, buying signals, objections, stakeholders, competitors, opportunity changes, expansion, stagnation, and risk of loss.

Triggers: Validated meeting structure, CRM change, proposal update, email context update, or scheduled opportunity review.

Inputs: Authorized meetings, email, CRM, proposal, stakeholder graph, opportunity history, and configured sales methodology.

Outputs: Field-level commercial findings, objection states, stakeholder map, opportunity health factors, next-best action, forecast range, and CRM update draft.

Tools: evidence.search, crm.read, proposal.read, graph.read, timeline.read, and artifact.derive.

Review and limits: It does not create a monolithic certainty score or overwrite the official forecast. External and CRM changes require owner approval.

Primary metrics: Signal precision and recall, objection-state accuracy, CRM conflict accuracy, forecast calibration, and accepted next-action rate.

Implementation profiles

Commercial Analysis Implementation

For each opportunity, the system builds a context package containing current CRM data, recent meetings, authorized email, proposal, stakeholders, and the configured sales methodology. AI extracts signals by field and does not create a monolithic score.

The pipeline:

1. identifies need, impact, budget, authority, process, timing, competitors, and criteria;
2. compares every field with CRM and marks it MATCH, STALE, CONFLICT, or MISSING;
3. detects objections and their OPEN, ANSWERED, ACCEPTED, or REJECTED status;
4. calculates longitudinal changes and expansion, stagnation, or loss signals;
5. generates the next action and an update draft;
6. validates that every suggestion cites a conversation or document;
7. submits changes to the approval workflow.

Assisted forecasting uses visible features—stage, age, activity, next steps, stakeholders, objections, date changes, and conversational signals—and returns a range, supporting factors, opposing factors, and confidence. It does not replace the official forecast until the responsible owner approves it.

Integration boundaries

The package supplies evidence-based intelligence; the connected CRM remains authoritative for its commercial records unless an approved change is synchronized.

Owned screen contracts: SCR-COM-01, SCR-COM-02, SCR-COM-03, SCR-COM-04, SCR-COM-05, SCR-COM-06, SCR-COM-07.

See solution workflows for cross-package behavior. Screens, agents and workflows keep one canonical owner even when other bundles invoke or enrich them.