Proposal approval loop (ABM / RevOps)

Runtime flow

| Stage | In this pattern | | --- | --- | | Provider | LLM drafts proposal sections from opportunity context, pricing guardrails, and legal snippets | | Loop + Guards | proposal.review — brand/compliance guards, margin checks, human-only on customer-send | | Channel | Slack — AE + legal approve; Docs comments for inline questions (work surface, not governance) | | Integration | Google Docs snapshot/hash evidence; Salesforce stage → Proposal Sent after approval | | Evidence + learning | Doc revision hash, approver IDs, discount exceptions for win/loss analysis |

1Provider drafts in Docs → Loop + Guards → Channel: Slack (+ doc comments) → Integration: SFDC + publish → Evidence

Operational scenario

1. AE triggers proposal.review from opportunity id — Docs template cloned to work surface.
2. Provider proposes pricing table and legal clauses — staged, not customer-visible.
3. Guards fail transition if margin < floor or missing legal ack.
4. Channel routes #deal-desk approval in Slack; legal may comment in Docs (context only).
5. Approved transition applies customer-visible publish + Salesforce stage advance.
6. Evidence links Slack actor, doc hash, and opportunity id for audit.

Workflows vs loops

| | Workflow (e.g. doc generation job) | Loop (Loop Engine) | | --- | --- | --- | | Job | Render PDF, sync attachments | Govern whether proposal may be sent | | Retry | Orchestrator retries API failures | Guards block illegal transitions |

Related

• Proposal path on dual-surface Docs
• Pricing exception loop
• Workflow + Loop