> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spineworkspace.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sales System Flow: Data Journey from Source to Workbench

> The ten-step system path for Sales: how Spine ingests CRM and engagement data, normalizes it, and projects it into pipeline and forecast views.

The Sales system flow describes how raw data from your CRM, conversation tools, and email becomes the unified context you see in SpineWorkspace. It runs continuously behind the scenes, but understanding the path helps you diagnose data delays and trust the projections.

<Steps>
  <Step title="Intake">
    Spine polls or receives webhooks from Salesforce, HubSpot, Outreach, Gong, Gmail, LinkedIn, and Slack.
  </Step>

  <Step title="Load">
    Raw records are ingested into Spine staging with source metadata and ingestion timestamp.
  </Step>

  <Step title="Normalize">
    Records are mapped to the Spine entity schema: Lead, Account, Contact, Opportunity, Activity, and so on.
  </Step>

  <Step title="Schema Mapping">
    Cross-system matching links records by email domain, account identifier, fuzzy name, or phone number.
  </Step>

  <Step title="Context Assembly">
    Spine builds deal graphs by joining opportunities to contacts, activities, transcripts, and engagement events.
  </Step>

  <Step title="Projection">
    The assembled graph is filtered and shaped into domain views: My Pipeline, Forecast, Deal Reviews.
  </Step>

  <Step title="OODA">
    Twin observes the projected state, orients to deal health models, and decides whether to surface an alert.
  </Step>

  <Step title="Governance">
    Every projected view respects source-system permissions and domain guardrails before rendering.
  </Step>

  <Step title="Execution">
    When you invoke a capability, Spine routes the call to the correct connector with the right authorization.
  </Step>

  <Step title="State Update">
    Writeback responses update the local projection, trigger events, and refresh dependent views.
  </Step>
</Steps>

## Related

* [Sales Overview](/internal-docs/domains/sales/index)
* [Spine Fabric](/internal-docs/domains/sales/spine-fabric)
* [Execution Flow](/internal-docs/domains/sales/execution-flow)
* [Spine Fabric Platform](/platform/spine-fabric)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.