> ## 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 Execution Flow: From Intent to Source-System Write

> The fifteen-step execution path for Sales actions: how an intent like stage advance becomes a governed, receipted write to Salesforce with full audit trail.

The Sales execution flow turns your intent into a governed, receipted action. Whether you are updating a deal stage, sending a quote, or submitting a forecast, the same pipeline runs: intent is captured, context is resolved, a proposal is built, and the action writes back with proof.

<Steps>
  <Step title="Intent">
    You choose an action, such as advancing an opportunity stage or requesting a discount.
  </Step>

  <Step title="Context">
    Spine resolves the current deal graph, permissions, and guardrails relevant to the intent.
  </Step>

  <Step title="Decision">
    Twin or the domain agent confirms the action is valid and suggests any prerequisites.
  </Step>

  <Step title="Proposal">
    A capability proposal is generated: what will change, in which system, and what the outcome will be.
  </Step>

  <Step title="Capability Resolution">
    Spine selects the correct capability, such as `crm.opportunity.stage_update`, and checks authorization.
  </Step>

  <Step title="Handoff">
    If approval is required, the proposal routes to a manager or compliance agent.
  </Step>

  <Step title="Tool Selection">
    Spine picks the connector: Salesforce REST API, HubSpot API, or email gateway.
  </Step>

  <Step title="MCP/Connector">
    The connector translates the capability into the target system's native API call.
  </Step>

  <Step title="Authorization">
    OAuth tokens or API keys are injected. The call is signed and scoped to the user.
  </Step>

  <Step title="Human Approval">
    For high-risk actions, a final approval panel is shown with diff and impact summary.
  </Step>

  <Step title="Workflow Execution">
    The API call is executed. Spine waits for confirmation and handles retries.
  </Step>

  <Step title="Source-System Write">
    Salesforce or HubSpot records are updated. Dependent triggers may fire in the source system.
  </Step>

  <Step title="Receipt">
    Spine generates a receipt: actor, timestamp, input, output, and sync status.
  </Step>

  <Step title="Event">
    A domain event is emitted. Views refresh, agents observe, and continuity tokens update.
  </Step>

  <Step title="Continuation">
    Your session context and the deal graph are updated. Twin monitors for the next trigger.
  </Step>
</Steps>

## Related

* [Capabilities](/internal-docs/domains/sales/capabilities)
* [Workflows](/internal-docs/domains/sales/workflows)
* [System Flow](/internal-docs/domains/sales/system-flow)
* [Governed Actions](/how-it-works/governed-actions)


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