Getting the Revenue team off contacts: what the six new workflows do

The problemMany of HubSpot's automatic jobs watch the contact (the person). The team works on deals, so those jobs fix the wrong record or miss things.
The changeSix new workflows do the same jobs from the deal. They replace 16 old workflows, and 6 more can simply be switched off: 22 old become 6 new.
Where it standsAll six are built and switched off. No old workflow has been touched. They go live only after Ishwarya's test passes.

1A lead typed in by hand gets a deal

When Reinie or Cass adds a new lead by hand (a call, WhatsApp, email, Mailer or social lead), HubSpot creates the deal and the company, and assigns the owner.

Today3 separate workflows: one for Revenue, two for MA.
→
After1 workflow. The same steps, copied exactly.
Team notices: nothing. Same deals, same owners. This one still starts from the contact, because a new lead is a contact before any deal exists.

2A re-routed lead gets a deal

When Reinie re-routes an existing lead (the Inbound Routing field) to Revenue, or to Cass in MA, HubSpot creates the deal in the right pipeline.

Today2 workflows, one per team.
→
After1 workflow. The same steps, copied exactly.
Team notices: nothing.

3A deal gets marked SQL

When a deal reaches Demo Scheduled or later, its Lead Stage becomes SQL.

Today3 workflows. Two watch the contact's Enquiry Status, which only mirrors the MA pipeline.
→
After1 workflow that watches the deal's own stage, in both pipelines.
Team notices: Revenue deals now get marked SQL too. The contact's Lead Stage stops updating. The part that sets the contact's lifecycle stage does nothing in practice, because HubSpot sets it itself, so I suggest dropping it.

4A deal's source and product get corrected

Five minutes after a deal is created, it fixes what the general channel workflow gets wrong: TikTok and BlueTap leads get the right channel, payment-terminal ad leads get PAYMENT TERMINALS added to products, and TikTok Revenue form leads go to Reinie.

Today6 small workflows, and each one fixes the contact, not the deal.
→
After1 workflow that fixes the deal.
Team notices: deals show the right channel. In the live test, BlueTap deals went from "Unclassified" to "Paid Social / Meta Ads". The contact's Original Source is no longer overwritten.

5Sending a Revenue deal to MA

When a Revenue rep sets "Referral to MA" to "Create New Deal", HubSpot creates a fresh MA deal for Qiao Yu, linked to the original, and drops the Revenue deal.

Today1 workflow that can also "move" the deal, changing its pipeline and owner.
→
AfterAlways a new MA deal. The Revenue deal stays in Revenue as Dropped.
Team notices: Revenue keeps its history and MA starts clean. This is the design agreed with Ishwarya on 6 Oct.

6Parent Industry gets filled in

Sets Parent Industry (F&B, Retail, Services or Others) on each Revenue deal, from the deal's Industry.

Today1 workflow that read the contact's industry and only covered deals created May to August. It stopped in September.
→
AfterCovers every Revenue deal, and can go back and fill in the ones it missed.
Team notices: Parent Industry reports work again. Since September only 33% of new Revenue deals have it, against 65% before.

The other old workflows

What I need from you