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.
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.
5 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.
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.
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.
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.
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.
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.
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.
--- 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
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.
Documented by one of the vendors in the chain, and easier to design around than to discover.
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 each component bills on, and which line actually scales with your volume.
| Component | Billing | What drives it |
|---|---|---|
| HubSpot | Professional, for the automation | The trigger is a workflow. Starter's 50 simple workflows may cover it; fully customisable logic is Professional. |
| ClickUp | Per member | A Free Forever plan exists. Automations and their run limits vary by plan, so check yours against the volume of deals you close. |
| Slack | Free plan works | One channel and one message per closed deal does not need a paid workspace. |
| Middle layer | None | Both 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.
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.
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.
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.
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.
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.