Senior HubSpot Automation Specialist — Lead Intake/Routing, Task Escalations, Email + SMS Enablement
We’re hiring a senior HubSpot specialist to architect and implement an end-to-end, automation-driven lead handling system.
Objective
Build a Lead-First intake framework that enforces classification, routes ownership cleanly, triggers task escalations, and enables structured outbound via email + SMS—then hands off into our existing pipeline.
Requirements (System Behavior)
A. Lead Intake + Classification
Enforce a required Lead Type property:
Political | Corporate | Public Affairs | Franking
Apply standardized Lead labeling (lifecycle stage + internal lead status)
Associate lead to a Sub-Account structure (you propose best practice: Company associations vs Custom Object vs another approach)
Capture Services via multi-select property
Hand off to existing pipeline logic (including Won/Lost outcomes)
B. Task/Reminder Escalations (non-negotiable)
Trigger owner reminders after:
24 hours
7 days
Reminder suppression rules must be robust (stop conditions like reply, meeting booked, deal stage change, status updated, won/lost, etc.)
Design must avoid spam and duplicate task creation
C. Email + SMS Enablement
Implement outreach foundation:
templates
sequences / enrollments
segmentation lists
opt-out/suppression handling
SMS can be via HubSpot-native or integration (Twilio/Sakari/etc.) — propose the best option.
D. QA + Documentation
Test plan with sample lead paths
Loom walkthrough + short SOP documenting properties, workflows, and stop conditions
Must Have
Proven HubSpot workflow architecture experience (Sales Hub; Marketing Hub a plus)
Experience with task queues, branching logic, and workflow governance
Evidence of implementing email sequences + (preferably) SMS
Screening (Answer These)
How would you model “Sub-Accounts” in HubSpot and why?
How do you prevent runaway workflows / duplicate reminders?
What’s your testing approach before enabling in production?
Share 1–2 examples of similar builds (screenshots or Loom)
Start: ASAP
If you’re junior or still “learning HubSpot,” this will not be a fit.
Apply Now
Apply Now
Objective
Build a Lead-First intake framework that enforces classification, routes ownership cleanly, triggers task escalations, and enables structured outbound via email + SMS—then hands off into our existing pipeline.
Requirements (System Behavior)
A. Lead Intake + Classification
Enforce a required Lead Type property:
Political | Corporate | Public Affairs | Franking
Apply standardized Lead labeling (lifecycle stage + internal lead status)
Associate lead to a Sub-Account structure (you propose best practice: Company associations vs Custom Object vs another approach)
Capture Services via multi-select property
Hand off to existing pipeline logic (including Won/Lost outcomes)
B. Task/Reminder Escalations (non-negotiable)
Trigger owner reminders after:
24 hours
7 days
Reminder suppression rules must be robust (stop conditions like reply, meeting booked, deal stage change, status updated, won/lost, etc.)
Design must avoid spam and duplicate task creation
C. Email + SMS Enablement
Implement outreach foundation:
templates
sequences / enrollments
segmentation lists
opt-out/suppression handling
SMS can be via HubSpot-native or integration (Twilio/Sakari/etc.) — propose the best option.
D. QA + Documentation
Test plan with sample lead paths
Loom walkthrough + short SOP documenting properties, workflows, and stop conditions
Must Have
Proven HubSpot workflow architecture experience (Sales Hub; Marketing Hub a plus)
Experience with task queues, branching logic, and workflow governance
Evidence of implementing email sequences + (preferably) SMS
Screening (Answer These)
How would you model “Sub-Accounts” in HubSpot and why?
How do you prevent runaway workflows / duplicate reminders?
What’s your testing approach before enabling in production?
Share 1–2 examples of similar builds (screenshots or Loom)
Start: ASAP
If you’re junior or still “learning HubSpot,” this will not be a fit.
Apply Now
Apply Now