Closed won to delivery

A closed-won deal that creates the work, carries the terms across, and reports back when delivery moves.

Handover is where sales stacks usually stop, and it is a strange place to stop. Everything up to closed-won is instrumented, automated and reported on. The step immediately after, where the thing that was sold becomes the thing that gets delivered, is very often a person copying a deal name into a project tool and typing what they remember of the terms.

This is the one workflow on the site with no data layer in it, and it is here for that reason. Not every gap in a sales stack is an enrichment problem. This one is a plumbing problem, both vendors have already built the plumbing, and most teams have simply never switched it on.

Why this pair is unusual

Most integrations are built by one side and tolerated by the other, which shows up as one direction working well and the other being a webhook you maintain. Here, ClickUp actions appear in the HubSpot workflow action list and HubSpot actions appear in ClickUp automations. Both directions are first-class and neither is yours to keep alive.

The pipeline, step by step

5 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.

01

A deal reaches closed won

The trigger. A deal-based HubSpot workflow, which means Professional for a fully customisable one; Starter covers this with one of its 50 simple workflows if the logic stays simple.

the triggerdeal stage change
↓
02

ClickUp creates the delivery work

A ClickUp action inside the HubSpot workflow. Create a list from a template, or a task per line item, with the deal context attached rather than summarised.

nativeno middle layer
↓
03

The line items travel with it

What was sold goes across, not just the deal name. This is the whole point of doing it properly: the delivery team should not have to open the CRM to find out what the customer bought.

line itemsand products
↓
04

Slack tells the delivery team once

One message, to the channel that owns onboarding, naming the account and linking both records. Not a message per task, which is how this becomes noise inside a fortnight.

1 messagenot one per task
↓
05

Work status reports back to the deal

A ClickUp automation updates the HubSpot record when delivery moves. This is the direction teams forget to build, and it is what stops the CRM going stale the moment the deal closes.

two-waythe forgotten half

Build it with an agent

This workflow ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it, and how to check it worked. Point an agent at it and it has what it needs without reading 3 sets of vendor docs first.

closed-won-to-delivery/SKILL.md agent skill
---
name: closed-won-to-delivery
description: Build a closed-won handover: a won deal creates delivery work with the lin
  e items attached, and work status reports back to the CRM record. Use when t...
---

# Closed won to delivery

## What you are building
## Prerequisites
## The tools, and how to call them   → HubSpot, ClickUp, Slack
## Build it                         → 5 steps
## Gotchas
## What breaks, from the vendors' own docs
## How to verify it works           → 4 checks
markdown Verified 2026-09-18
Drop it into Claude Code

mkdir -p .claude/skills/closed-won-to-delivery curl -o .claude/skills/closed-won-to-delivery/SKILL.md https://www.reversecontact.com/integrations-hub/skills/closed-won-handover.md

For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it https://www.reversecontact.com/integrations-hub/skills/closed-won-handover.md directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.

3 of the joins in this chain have a full guide behind them, HubSpot and ClickUp and HubSpot and Slack among them. The chain crosses 2 of the seven layers a stack splits into, from the CRM layer outward, which is why no single vendor owns it.

What will bite

Documented by one of the vendors in the chain, and easier to design around than to discover.

Custom fields are the ceiling
The native integration covers common objects well. Workflows that depend on custom fields are where teams move to Make, which has fuller custom-field support on the ClickUp side. Check your specific fields before you design around the native path.
The automated half needs Professional
Manual linking works lower down, but "when a deal closes, do this" is a workflow, and fully customisable workflows start at HubSpot Professional. On Starter you get up to 50 simple workflows and should check yours fits inside one.
Two automation engines, two places to debug
Half the logic lives in HubSpot workflows and half in ClickUp automations. That is the price of both directions being native. Write down which side owns which rule before you build the second one.
Writing to the same field from both sides is a loop
One rule per direction. HubSpot owns "a deal changed, create or update work"; ClickUp owns "work changed, update the deal". The moment both write to the same field on the same event you have built a loop, and loops between two automation engines are unpleasant to unpick.

All four are documented by a vendor rather than observed by us, which is the useful part: a limit you can read is a limit you can design around before it costs you a week.

What it costs to run

What each component bills on, and which line actually scales with your volume.

ComponentBillingWhat drives it
HubSpotProfessional, for the automationThe trigger is a workflow. Starter's 50 simple workflows may cover it; fully customisable logic is Professional.
ClickUpPer memberA Free Forever plan exists. Automations and their run limits vary by plan, so check yours against the volume of deals you close.
SlackFree plan worksOne channel and one message per closed deal does not need a paid workspace.
Middle layerNoneBoth halves are native. Make only enters the picture if custom fields are load-bearing.

This is the cheapest workflow on the site, because there is no metered line in it at all. What it costs is an afternoon of deciding which side owns which rule, which is the part that determines whether it survives.

Built by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, limit and sync direction in this chain was read from a vendor's own documentation, through the integration records each step rests on. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
8 vendor documents
Paid placement
None

Most workflows here need a data layer underneath

Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score your logic can branch on. The free trial takes no card and runs until the 500 credits a new account starts with are spent, which is enough to run this end to end before anyone signs anything.

Free trial, no card required, and 500 credits to start.

Questions

Does ClickUp integrate with HubSpot both ways?

Yes. ClickUp actions are available inside HubSpot workflows and HubSpot actions are available inside ClickUp automations, which is unusual: most pairs have one good direction and one you maintain. Companies, contacts, deals, line items, products, tasks and tickets can all be created and linked.

Can I do this without HubSpot Professional?

Partly. Linking records by hand works on any tier, and Starter includes up to 50 simple workflows which may cover a straightforward "deal closed, create list" rule. Anything conditional is Professional. If you are close to the line, write the rule out first and check whether it fits inside a simple workflow.

What should actually travel across at handover?

The line items, the owner, the close date and any delivery-relevant custom properties. The failure mode is sending only the deal name, which means the delivery team opens the CRM anyway and you have automated a notification rather than a handover.

Why is there no enrichment in this workflow?

Because the data is already yours. Everything this workflow needs was entered by your own team during the deal. Not every gap in a sales stack is a data problem, and pointing an enrichment tool at this one would add cost without adding anything.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant