Workflow

Delivery and Kickoff: post-sign execution and change request control

Move from signed proposal to execution with clear handoff logic and controlled scope-change behavior.

Cross-step flow page connecting actions, signals, and handoffs.

In this guide

Ownership and review discipline

ProductSupport
Last reviewed 2026-03-12Review cadence 30 days

Change signals to watch

  • package schema changes
  • pricing generation logic updates
  • commercial review policy updates
  • send modal behavior changes
  • buyer signing flow updates
  • deal room experience changes
  • execution next action changes
  • kickoff and handoff logic changes
  • change request workflow updates

Operator guidance

What this means in QuoterAgent

Use this guide as the operating reference for Delivery and Kickoff: post-sign execution and change request control. It explains what this surface controls, what good execution looks like, and which teams should keep it trustworthy over time.

  • This workflow guide explains how QuoterAgent supports post-sign delivery alignment and change-order discipline.
  • Strong post-sign control protects margin, keeps trust, and avoids silent scope expansion.
  • Primary owners currently covering this area: Product, Support.

What to do

Treat this as a working checklist, not background reading. Use it before you change settings, publish external material, or hand work to another operator.

  • Use this after acceptance and whenever scope change pressure appears during delivery.
  • After establishing delivery control, align billing and admin operations to support repeatable governance.
  • Review workspace/admin controls for ownership and auditability.
  • Keep glossary terms shared across delivery and commercial teams.

Where it shows up in the workflow

This guide matters most when work moves between setup, authoring, buyer delivery, and post-sign execution. Use the linked guides to follow the full path instead of solving one surface in isolation.

  • Delivery behavior depends on how clearly the proposal documented scope boundaries and acceptance criteria.
  • Review the related guide "Sending and Signing: buyer-facing flow and acceptance confidence" when this step depends on another surface.
  • Review the related guide "Packages and Pricing: commercial structure and proposal clarity" when this step depends on another surface.

Common failure modes and risks

Most quality problems here come from drift: outdated setup, weak commercial boundaries, or teams skipping the review moment before customer-visible delivery. Use these signals to catch issues before they reach the buyer.

  • package schema changes
  • pricing generation logic updates
  • commercial review policy updates
  • Keeps delivery aligned with approved commercial terms.
  • Improves communication quality in change conversations.

What this is

This workflow guide explains how QuoterAgent supports post-sign delivery alignment and change-order discipline.

  • Signed proposal handoff into kickoff actions.
  • Change-request handling tied to assumptions, exclusions, and deliverables.

When to use

Use this after acceptance and whenever scope change pressure appears during delivery.

  • At kickoff preparation and execution planning.
  • When client requests extend beyond agreed scope boundaries.

Why it matters

Strong post-sign control protects margin, keeps trust, and avoids silent scope expansion.

  • Keeps delivery aligned with approved commercial terms.
  • Improves communication quality in change conversations.

How it connects

Delivery behavior depends on how clearly the proposal documented scope boundaries and acceptance criteria.

  • Inherits risk posture from proposal authoring and pricing.
  • Links back to reference terms for disputes and governance.

Next steps

After establishing delivery control, align billing and admin operations to support repeatable governance.

  • Review workspace/admin controls for ownership and auditability.
  • Keep glossary terms shared across delivery and commercial teams.

Related guides