Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

CRM & Marketing Automation › Automation Workflows

Building a Closed-Won Workflow

How to build the workflow that runs when a deal is won: customer stage, prospect suppression, onboarding hand-over, team alerts and outcomes sent to ads.
Tutorialintermediate8 min readUpdated

What should change the moment a deal is won

The lead stages and pipeline guide ends the pipeline at the customer stage, where lifecycle marketing takes over. The automation governance guide adds the rule that current customers do not receive prospect sequences. Between those two statements sits a moment that most teams leave to memory: the deal is won, and several systems need to hear about it.

What changesWhereWhy it mattersCovered in
Lifecycle stage set to customerCRMEvery later condition and report reads itLead stages and pipeline guide
Pipeline workflows stoppedCRM and marketing platformDeal nudges and stage reminders endThis tutorial
Prospect sequences exitedMarketing platformNo demo invitations to people who already boughtGovernance guide; nurture sequences guide
Prospecting audiences clearedAd platformsNo acquisition spend on customersExcluding customers; customer lists guides
Onboarding hand-over task and alertCRMThe first weeks are owned by a named personThis tutorial
Onboarding started for each contactMarketing platform and productUsers reach first valueSoftware onboarding tutorial
Won outcome uploadedAd platformsBidding and reporting learn which clicks produce customersConnecting the CRM to ads guide
Customer exclusion lists refreshedAd platformsThe new customer is excluded everywhere, not only on one networkCustomer lists guide

Each row is simple. The failure is in doing them separately, at different times, by different people, so that some happen and some do not. A single workflow with an agreed trigger makes them happen together, and makes the missing one visible when it does not. When a customer has already received a prospect message, the diagnosis for customers receiving prospect messages traces which of these rows, or which gate, record or import, let it happen.

Before you start

Map the journey first. The customer journey mapping framework asks what the customer does, thinks and receives at each step; drawn for the first weeks after the deal, it lists every message, task and change the workflow has to produce and shows which ones are missing today. Do this with sales, customer success or account management, and whoever owns the ad accounts.

Gather four more things. The written definition of won from the pipeline guide, and the field that records it. The automation inventory, to find every workflow and sequence a new customer might still be enrolled in. The current conversion actions and customer lists in each ad platform, with their owners. And the consent fields on the contact, because both the outcome upload and the customer list upload depend on what the person agreed to; the guide to connecting the CRM to ads and analytics covers that check. Build the workflow paused and keep it paused until the test step passes. Give it a row in the automation inventory, with its owner and measure, before it is switched on.

The steps

  1. Agree the trigger and what counts as won

    Write down the single field change that starts the workflow: the deal entering the closed-won stage, a contract status, or an order or payment recorded by finance, whichever the stage definitions say means won. Use one trigger only, on the deal rather than the contact, so that a second deal for an existing customer runs the parts that apply and skips the rest. Add conditions for what does not count: test deals, internal deals and deals created only to record a renewal, which belong to the renewal process instead.

  2. Set the customer stage and stop the pipeline workflows

    For each contact and the company associated with the deal, set the lifecycle stage to customer and record the date, without moving a contact that is already a customer. Then end every pipeline workflow for the deal: stage reminders, stalled-deal nudges and proposal follow-ups. Where a workflow cannot be stopped from outside, add the customer stage as an exit condition to that workflow, so the change you just made is what ends it. The tutorial on automating lifecycle stage changes sets the earlier stages by rule in the same way and leaves this workflow as the only writer of the customer stage.

  3. Remove the deal's contacts from prospect sequences and prospecting audiences

    Exit every contact on the deal from nurture, demo-request and trial sequences, and add the customer stage as a suppression condition at entry and before each send in those sequences, as the governance guide requires, so a later form fill does not enrol them again. The nurture sequences guide covers exits for each sequence. Remove the contacts from any list or audience used for prospecting, so the next sync to the ad platforms drops them. This is a Suppression List by another name: an exclusion that every prospect workflow checks.

  4. Create the onboarding hand-over task and alert the account team

    Create a task for the person who will own the customer's first weeks, with a due date and the deal's notes, contacts and agreed scope attached. Assign it by rule (the account manager for the territory, or a customer success queue) rather than to whoever closed the deal by default. Notify the account team: the seller, the new owner and anyone else the journey map names. One alert with the essentials is better than several partial ones.

  5. Start onboarding for every contact on the deal

    Enrol each contact in the onboarding that fits their role: product onboarding for users, contract and account messages for signatories and finance contacts. The tutorial on software onboarding emails builds the sequence itself, including the split between service messages and marketing; this step only starts it, and only once. Contacts in other parts of the customer organisation who were not on the deal are not enrolled; the expansion and renewal marketing guide maps the account after the first sale and decides what they receive.

  6. Send the won outcome to the ad platforms

    Send the won deal and its agreed value to the ad platforms as the connecting guide describes. Google documents offline conversion imports from a CRM keyed to the click identifier stored on the lead, with the conversion time after the click and within the conversion action's window, and Enhanced Conversions for leads, matched on the hashed email or phone captured at the form. Meta documents CRM outcomes as server events through the Conversions API. Check the stored consent state before anything is sent, send only what the upload needs, and use the same conversion name and value rule every time, so reports and bidding read one consistent outcome.

  7. Update the customer exclusion lists

    Add the new customer to the lists that keep prospecting campaigns off existing customers, refreshed on a schedule or by the workflow. The guide to excluding existing customers describes the Google side, including that a customer list is refreshed by upload and is only as current as its last one. The guide to using customer lists across ad platforms keeps one definition of a customer for every platform, with the consent checks that come before any upload, and Meta's help on Custom Audiences, in this page's sources, describes the customer-list audiences that guide uses for exclusion.

  8. Handle reversals when a won deal is reopened or cancelled

    Decide what happens when a deal marked won is moved back, cancelled before it starts or was won by mistake. A second, smaller workflow triggers on that change: it restores the previous lifecycle stage where no other won deal exists, closes the onboarding task with a note, stops onboarding sequences, and alerts the account team. Decide with the ad account owner how a reversed outcome is handled in each platform's reporting, and record it in the change log; do not leave a cancelled deal counted as revenue in bidding. Keep the contact out of prospect sequences until a person decides where it belongs.

  9. Test with a dummy deal and watch the first live runs

    Create a test company, test contacts with clearly marked names and a test deal, and mark it won. Check every row of the table above: stage set, pipeline workflows ended, sequences exited, audiences cleared, task created, alert received, onboarding started, outcome handled as a test rather than uploaded as revenue, and exclusion lists updated. Then reopen it and check the reversal. Walk the email automation flow launch checklist for the email parts. Before activation, check how many existing won deals would enter and decide explicitly whether any should; the workflows hub describes that enrolment check alongside walking the paths and confirming the exits fire. Then switch the workflow on and read each of the first live runs, record by record, before trusting it.

A clinic software firm's first closed-won workflow (illustrative)

Illustrative example — not a real result

Nubrastow Clinic Software builds its closed-won workflow

Nubrastow Clinic Software, an invented maker of appointment booking software for physiotherapy and dental clinics, reviews its last quarter's 48 new customers and finds that 31 were still enrolled in the demo-request nurture a fortnight after signing, 22 were still in the prospecting customer list used for ads, and 9 had waited more than a week for an onboarding call because nobody had been told the deal had closed. Its first closed-won workflow triggers on the deal moving to closed-won, sets the customer stage on the 3 contacts a typical deal carries, exits them from all 4 prospect sequences and the prospecting audience, creates an onboarding call task for the territory's customer success manager and starts product onboarding for the clinic's users. It uploads the first year's contract value to Google Ads as an offline conversion and sends the same outcome to Meta as a server event, both only where the contact's consent allows. The test deal finds one gap: a reopened deal left the onboarding task open, which the reversal workflow now closes. In the next quarter none of the 52 new customers receives a prospect email after signing.

Common mistakes

  • Triggering on several fields. The workflow runs twice, or not at all. One agreed field on the deal.
  • Changing the stage but not the sequences. The customer stage is set and the demo nurture carries on. Exit the sequences and add the stage as a suppression condition.
  • Forgetting the ad platforms. Prospecting ads keep spending on people who already bought. Clear the audiences and refresh the exclusion lists.
  • Onboarding only the person who signed. The users who need the product onboarding never receive it.
  • Uploading without checking consent. The outcome upload depends on what the person agreed to at the form.
  • No reversal path. A deal won by mistake stays a customer, counted as revenue and cut off from nurture.
  • Assigning the hand-over to whoever closed the deal. The onboarding owner should be chosen by rule.
  • Testing on a real deal. Use a dummy deal with marked names, and read the first live runs by hand.

Frequently asked questions

Should the workflow trigger on the deal stage or on a signed contract?

On whatever the business has agreed means won, written in the stage definitions, and on one field only. For some businesses that is the deal moving to closed-won; for others it is a signed contract, a first payment or an order number arriving from finance. What matters is that the trigger is a single, testable change on the deal, that sales knows marking a deal won starts the workflow, and that a deal marked won by mistake has a clear way back, which is why reversals get their own step.

Should every contact on a won deal become a customer?

Every contact associated with the deal should leave prospect sequences and prospecting audiences, because they now belong to a customer account. Whether each one receives onboarding depends on their role: a user needs the product onboarding, a signatory may need only the service messages that come with the contract, and a contact from another part of the organisation may still be a prospect for expansion. Map the roles first, then decide what each receives.

Which value should be sent to the ad platforms for a won deal?

The value the business uses to judge acquisition, applied the same way every time: the first contract value, the first year's value or the deal amount, chosen once and written down. The connecting guide describes the outcome uploads: Google documents CRM outcomes keyed to the click identifier or to the hashed details captured at the form, and Meta documents CRM outcomes as server events. Send the value with the outcome only where the stored consent state allows the upload at all.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. About enhanced conversions — Google Ads Help
  2. About the Conversions API — Meta Business Help Centre
  3. About Custom Audiences — Meta Business Help Centre

Related