Which HubSpot workflows can I build without Operations Hub Professional?

What this bundle builds

The question underneath this page is a budget question. Someone read a blog post, saw a custom coded action in the screenshots, and now believes the automation they need costs another line on the renewal. Usually it does not.

This bundle is the working set of a portal that runs on Sales, Marketing or Service Hub Professional. Leads get an owner within minutes and the owner gets a task. Deals pick up the right next step at each stage, chase their own missing fields, and hand off cleanly the moment they close. Contacts move from lead to MQL to SQL on a documented threshold, with the sales ping attached. Tickets route by product and by channel, and a missed first response wakes somebody up. Feedback gets acted on instead of read.

The last component is the one people skip and then regret. Six flags catch the records that quietly break everything else: a contact with no company, a deal with no company, a ticket with no contact, a company with no domain, a contract with no end date. None of them needs code. All of them need a real owner on the other end of the queue.

How the pieces fit together

Routing first, because almost everything downstream assumes a record has an owner. Start with the flat rotation, then add the territory version once the territory field is reliable, then the lifecycle and trial-tier routes on top. The deactivated-owner cleanup comes last and depends on an admin habit, not on a property.

Deal hygiene next, since stage tasks and forecast category both branch on your pipeline’s internal stage names, which you should confirm once and reuse everywhere. The closed-won specs share three properties, Onboarding Owner, CS Handoff Notes and a sent flag, so build the handoff task before the summary email and the checklist.

Lifecycle sits beside that and depends on one number, the score threshold, kept in a single workflow so sales gets one answer. The ticket set needs SLA goals configured on the help desk pipeline first, or the breach alert enrolls nothing and fails quietly. Leave the flags for last: they depend on nothing, and by then you know which gaps your portal actually has.

What you get

• 40 specs, each as PDF and Markdown, with enrollment criteria, step list, diagram, test plan and the known pitfalls written out.
• Properties JSON: 52 property definitions across contacts, deals, companies and tickets, including the status and flag properties that stop these workflows re-triggering on their own writes.
• Workflow JSON in Automation API format, switched off, so nothing runs before you have read it.
• Custom coded actions: none. No private app token, no secret to store, no execution limit to watch.
• Tier stated per spec, at the top: 23 Sales Hub Professional, 9 Marketing Hub Professional, 8 Service Hub Professional.
• Static lists and review queues named and specified, not left as an exercise.
• Test plans that cover the negative path, the unowned record, the blank field, the ticket created in a later stage.
• Install in one click for Full and Agency buyers.

Who it is for, and who should skip it

This is for the admin or RevOps person who inherited a Professional portal and needs it working this quarter, and for the consultant who rebuilds the same twenty workflows on every new client and would rather not retype the pitfalls. Roughly nineteen hours of build sits in here, at an honest pace with testing.

Skip it if you are on Starter, where only simple automation exists and most of these specs will not load. Skip it if you already own Operations Hub and came for the code, since the power pack is the page you want. And if you want both sides plus the other nine categories, the full library costs less than three packs.