← BackSee all toolsSigned Deal to Delivery: a Workflow with a Human Approval GateWorking demo · sample data · shows a method I used, not a real event
Workflow · interactive example

Signed Deal to Delivery

A won deal becomes delivery work without anyone re-keying it, and without anything risky happening before a person approves.

I led, governed and specified this workflow. Illustrative, with fictional data.

The example

One signed deal. Three sites. Seven steps.

Pick how sure the match is, then walk the deal through. Watch what changes at the approval gate. Nothing past the gate happens until a person says so.

Step 1 of 7

Deal marked won

Press Next to start.

Without JavaScript, every step is listed below in order.

The full path

Who does what, in order.

  1. 1
    System

    Deal marked won

    A deal moves to Won in the CRM. The workflow starts from the event, not from someone remembering to start it.

    Output Deal record, signed contract attached.

  2. 2
    AI

    Read the signed contract

    The AI extracts parties, term, sites, products, pricing schedule and special terms. Every field keeps a pointer back to the clause it came from.

    Output A structured summary with a source for each field.

  3. 3
    AI

    Match to existing records

    The extracted customer and sites are matched to the CRM, billing and project records. The match gets a confidence score.

    Output A proposed match and a confidence score.

  4. 4
    Person

    Human approval

    A named RevOps owner reviews the match and the delivery plan. High confidence arrives pre-checked. Medium shows the differences. Low is not proposed at all: it goes to a person to resolve.

    Output An approved plan, or a routed exception.

  5. 5
    Workflow engine

    Create the delivery work

    One project per site, tasks from the template, owners by role, default blocker classes. Record IDs are written back to the CRM. A re-run updates; it never duplicates.

    Output Projects, tasks and owners, linked to the deal.

  6. 6
    Workflow engine

    Provision downstream systems

    Customer-success account, billing customer with a drafted invoice schedule (not sent), support organization, team channel, and a procurement request for hardware.

    Output Every downstream record created and linked.

  7. 7
    System

    Watch the readiness gates

    A purchase order must be linked before hardware ships. An acceptance clock runs: green under 30 days, amber 30 to 45, red beyond that with escalation.

    Output A clock, a status and an owner for every site.

When it does not go cleanly

Exception paths are designed, not discovered.

No match

Duplicate or unknown customer

Nothing is created. A task goes to the account owner with both candidate records and a 2-business-day clock.

Conflicting terms

Contract and CRM disagree

The contract wins on terms, the CRM wins on ownership. The difference is shown to the approver and logged.

Missing PO

No purchase order linked

Hardware stays blocked, the blocker is classed as customer-side or internal, and the owner is notified daily until it clears.

Controls

What makes it safe to run unattended.

More in AI & Automation

See all tools