Assembles proposals and SOWs from approved clause and pricing blocks — discount authority, legal boundaries, and payment-term rules enforced at composition time, then handed to e-signature with the approval chain as the audit trail.
The Proposal / SOW Assembly Agent composes proposals and statements of work from approved clause and pricing blocks, enforcing discount authority, legal boundaries and payment terms as the document is built, then hands it to e-signature with the approval chain as its audit trail. It is one of fifteen workflows in the Enterprise GTM Agent Stack, an Opsmarshal series on revenue operations.
How the flow runs — live
Policy violations can't be drafted — the un-draftable discount never becomes a negotiation.
Proposal assembly is where deals slow down and margin leaks out: reps clone old docs with stale terms, discounts get invented under quarter-end pressure, and legal finds the non-standard clause after signature.
Documents compose from the current block library only. Discounts beyond authority route to the right approver automatically; clause deviations route to legal before the buyer ever sees the doc.
| Decision | Choice | Rationale |
|---|---|---|
| Composition-time enforcement | Policy violations can't be drafted, not merely caught later | Catching a bad discount at approval is a delay. Making it un-draftable removes the negotiation-by-fait-accompli pattern entirely. |
| Tiered approval routing | Risk decides the approver, not the org-chart default | Flat “manager approves everything” creates rubber stamps. Discount depth, clause deviation, and payment terms each map to named authorities. |
Three curated scenarios — one that passes, one that flags for a human, one that the gate blocks. Watch the verdict, the evidence rows, and the audit log.
Governance audit log
Agents don't remove operators — they change what operators watch. Console spec: who owns it, what they check, what pages them, and how they pull the plug.
Big deals demand terms outside the library, and the workflow gets bypassed entirely. Mitigation: An explicit manual-mode lane with mandatory legal pairing — visible and logged, not shadow paperwork.
Pricing blocks lag a packaging change and quote last quarter's SKUs. Mitigation: Blocks carry effective dates; expired blocks hard-fail assembly rather than silently composing.
Tiered approvers click approve without reading, and the gate hollows out. Mitigation: Approval dwell-time telemetry — the same rubber-stamp detection pattern used on outbound first-touch review.
Opsmarshal builds workflows like this one inside client stacks — see revenue operations and GTM stack architecture, or book a call to walk through your own.
Revenue Operations and AI Agentic Workflows for B2B companies in transformation. We build the machine. You run the company.