Most startups use HubSpot like a spreadsheet with email. Contacts go in, deals get updated manually, and someone on the team spends three hours a week doing data entry that should take three minutes. The problem isn't HubSpot. It's that nobody built the workflows that make it useful.

Workflows are HubSpot's automation layer. They trigger actions based on contact behavior, deal stage changes, form submissions, and dozens of other enrollment criteria. When you set them up correctly, they eliminate the repetitive work that keeps RevOps teams stuck in admin mode instead of building systems that scale.

This post covers eight workflows every startup should automate, with templates you can implement today. These aren't advanced edge cases. They're the core automations that separate a functional Go-to-Market (GTM) system from a glorified contact database.

Lead assignment by territory or product line

Lead assignment breaks at scale when it's manual. Someone fills out a demo form, gets routed to the wrong Sales Development Representative (SDR), and the SDR either ignores it or passes it along three days later after the lead has gone cold.

The workflow fixes this by routing leads automatically based on criteria you define upfront: company size, region, product interest, or any custom property in your HubSpot instance.

Enrollment trigger: Contact submits a form or imports into a specific list

Actions:

1. If contact property `company_size` is greater than 500 employees → assign to Enterprise SDR

2. If contact property `country` equals UK, France, or Germany → assign to EMEA SDR

3. If contact property `product_interest` equals Product A → assign to Product A SDR

4. Default assignment → round-robin to General SDR team

Why this works: The contact gets followed up within the Service Level Agreement (SLA) you set, and SDRs don't waste time debating who owns what. You can layer in additional logic for industry, lead source, or deal size if your GTM motion requires it.

MQL to SQL progression with notification

Most startups define Marketing Qualified Lead (MQL) and Sales Qualified Lead (SQL) stages but never build the handoff process. Marketing marks someone an MQL in HubSpot, then Slack pings Sales manually, or worse, nobody pings anyone and the lead sits.

This workflow automates the handoff and creates accountability on both sides.

Enrollment trigger: Contact lifecycle stage changes to MQL

Actions:

1. Create a task for the assigned SDR: "Qualify this lead within 24 hours"

2. Send a Slack notification to the SDR's channel with contact name, company, and form submission details

3. Wait 24 hours

4. If lifecycle stage has not changed to SQL → send a Slack notification to the Sales Manager

5. If lifecycle stage changes to SQL → mark task complete and send confirmation to Marketing

Why this works: The workflow creates visibility into the handoff and surfaces when leads aren't being worked. It also closes the loop with Marketing so they know what happened to the MQL they passed over.

Deal stage stall alerts

Deals stall. An Account Executive (AE) moves a deal to "Proposal Sent" and then it sits for three weeks because the champion went on leave or the deal got deprioritised. Without visibility, the pipeline looks healthy but nothing is closing.

This workflow flags stalled deals before they die quietly.

Enrollment trigger: Deal enters a specific stage (customise based on your sales process)

Actions:

1. Wait 7 days (or whatever your typical stage duration is)

2. If deal stage has not changed → create a task for the AE: "Follow up on stalled deal"

3. Send a Slack notification to the Sales Manager with deal name, stage, and days in stage

4. If deal stage changes → unenroll from workflow

Why this works: Stalls become visible before they turn into losses. The AE gets reminded to follow up, and the Sales Manager can coach on deals that aren't moving without manually auditing the pipeline every week.

Contact data enrichment from form submissions

When someone fills out a demo form, you get the fields they completed. Usually that's name, email, and company. You don't get company size, industry, revenue, or any of the qualification data you need to route and prioritise the lead properly.

This workflow enriches the contact record immediately after form submission so the SDR has context before they make the first call.

Enrollment trigger: Contact submits a specific form

Actions:

1. Send contact email to Clay for enrichment (via webhook or Clay's HubSpot integration)

2. Wait for Clay to return company size, industry, revenue, employee count, and LinkedIn URL

3. Update contact properties in HubSpot with enriched data

4. If enrichment returns no data → flag contact as "Needs manual research" and assign task to SDR

Why this works: The SDR doesn't waste time Googling the company before the call. Enrichment happens in seconds, and the contact record is complete before anyone touches it. Clay's HubSpot integration is available on Growth and Custom plans. If you're on a lower tier, you'll need to route through Zapier or Make.

Post-demo follow-up sequence

Most demos end with "I'll send you a follow-up email" and then the AE either forgets or sends a generic message three days later. The deal cools off and the champion loses momentum.

This workflow automates the post-demo sequence so every demo gets consistent follow-up, regardless of who ran it.

Enrollment trigger: Contact attends a demo meeting (tracked via HubSpot Meetings or Calendly integration)

Actions:

1. Wait 1 hour

2. Send a personalised follow-up email (template includes demo recording, next steps, and case study link)

3. Create a task for the AE: "Send custom proposal within 48 hours"

4. Wait 3 days

5. If deal stage has not moved to "Proposal Sent" → send reminder email to contact

6. If deal stage moves to "Proposal Sent" → unenroll from workflow

Why this works: Every demo gets followed up on time, with the same quality of materials. The AE gets reminded to move the deal forward, and the contact doesn't go cold while waiting for next steps.

Churn risk flagging based on product usage

If your product integrates with HubSpot (or you push usage data into HubSpot via API), you can automate churn risk alerts before the customer starts ignoring renewal emails.

This workflow monitors product usage and flags accounts that drop below a threshold you define.

Enrollment trigger: Contact property `last_login_date` is more than 30 days ago (or custom usage metric drops below threshold)

Actions:

1. Update contact property `churn_risk` to "High"

2. Create a task for the Customer Success Manager (CSM): "Reach out to re-engage"

3. Send a Slack notification to the CS team with account name and usage trend

4. Wait 7 days

5. If usage has not increased → escalate to Account Manager for intervention

Why this works: Churn signals surface early, before the customer has already decided to leave. The CSM can intervene while there's still time to fix the problem.

Lead nurture by engagement score

Not every inbound lead is ready to buy. Some are researching, some are months away from budget, and some are just collecting information. Assigning all of them to Sales wastes time.

This workflow sorts leads by engagement level and nurtures the not-ready-yet contacts until they hit a threshold that signals buying intent.

Enrollment trigger: Contact submits a form but does not meet MQL criteria

Actions:

1. Add contact to a nurture email sequence (weekly educational content, case studies, product updates)

2. Track email opens, link clicks, and website visits

3. If contact engagement score reaches 50 (customise based on your scoring model) → change lifecycle stage to MQL and trigger lead assignment workflow

4. If contact does not engage after 8 emails → unenroll and mark as "Cold"

Why this works: Sales doesn't waste time on unqualified leads, and Marketing doesn't lose contacts who aren't ready yet. The workflow keeps them warm until they signal intent.

Internal notification for high-value deal milestones

When a high-value deal moves to "Closed Won", the entire GTM team should know immediately. Implementation needs to kick off, CS needs to prep onboarding, and Finance needs to recognise the revenue. If this happens manually, someone always gets missed.

This workflow automates the notification so the whole team moves together.

Enrollment trigger: Deal amount is greater than $50,000 (customise based on your deal size threshold) and deal stage changes to "Closed Won"

Actions:

1. Send a Slack notification to the GTM team channel with deal name, amount, and AE

2. Create an onboarding task for the CS team

3. Update a shared Asana board with implementation kickoff details

4. Send an email to Finance with contract details and expected revenue recognition date

Why this works: High-value deals don't fall through the cracks between Sales and the rest of the company. Everyone knows what closed, and the handoff happens immediately.

How to prioritise which workflows to build first

If you're starting from zero workflows, don't try to build all eight at once. Pick the two that eliminate the most manual work or fix the biggest gap in your current process.

Start with:

1. Lead assignment (if Sales is complaining about bad routing or slow follow-up)

2. MQL to SQL progression (if Marketing and Sales aren't aligned on handoffs)

Once those are stable, add:

3. Deal stage stall alerts (if pipeline visibility is a problem)

4. Post-demo follow-up sequence (if demo-to-proposal conversion is low)

The rest can layer in as your GTM motion matures and your team has bandwidth to maintain more complex workflows.

FAQ

What HubSpot plan do I need to build workflows?

Workflows are available on Professional and Enterprise plans. Starter and Free tiers don't include workflow automation. If you're on Starter, you'll need to upgrade or use Zapier as a workaround (but Zapier doesn't integrate as cleanly with HubSpot properties and lifecycle stages).

How do I know if a workflow is working correctly?

Check the workflow history tab in HubSpot. It shows every contact or deal that enrolled, which actions triggered, and where contacts unenrolled or failed. If a workflow isn't firing, the history log will show why.

Can I connect HubSpot workflows to tools outside HubSpot?

Yes. Use webhooks to send data to tools like Clay, Slack, Asana, or Lemlist. HubSpot's native integrations cover most GTM tools, but webhooks give you flexibility for custom setups or tools that don't have a direct integration.

Partner UP works with GTM and RevOps teams on HubSpot workflow builds, data enrichment setup, and full RevOps system design. If you're running HubSpot but spending more time on manual work than automation, reach out at hello@partneruphq.com or book a call at calendly.com/eleilademir.