Closeout Operator

Job description

Triggered on closed-won. Generates contract from template, creates order in ERP or CPQ, and fires provisioning or fulfillment webhooks. Single workflow from signature to handoff.

Systems it connects to

Operator capabilities

• Triggers on closed-won
• Generates contract
• Creates order
• Fires provisioning

Actions it can take

1. On closed-won event
2. Generate contract
3. Create order in ERP/CPQ
4. Trigger provisioning

Actions requiring approval

The following are queued for human approval before the operator executes.

• →Contract send
• →Order submit
• →Provisioning trigger

Boundaries — what it won't do

This operator does not perform the following automatically.

• Does not sign contracts
• Does not modify deal terms
• Does not provision without approval

Trial outcome promise

Results in first 7 days

Typical outcomes from trial runs. Results depend on your volume and configuration.

Install flow

Four steps: company info, choose systems to connect, set responsible approver, start trial.

1. 1Enter company name and work email.
2. 2Select which systems this operator will connect to (e.g. CRM, inbox).
3. 3Define who approves actions that require a human check.
4. 4Start your 7-day trial. Configure and run from your dashboard.

FAQ

• What happens when the trial ends?

  You get a summary of what the operator did during the trial. If you subscribe, it continues with the same connections and settings. No data is deleted.

• Can I change systems or approvers during the trial?

  Yes. From your dashboard you can add or remove system connections and change the responsible approver at any time.

• What if the operator doesn't fit our workflow?

  Cancel before the trial ends—no charge. Your data is yours; we don't lock in your systems.