The question we hear is "should we hire an agency for HubSpot automation". The useful answer is by workflow type, because a task reminder and a two-way ERP sync have nothing in common except the tool they are built in. This is the split INSIDEA recommends, including the parts we tell teams to keep.
Every HubSpot fact below was read in HubSpot's own documentation on 2 October 2026, with the page's last-updated date.
Which HubSpot workflows should you outsource, and which should you keep in-house?
Keep in-house anything a trained admin can build, test and explain in an afternoon: notifications, task creation, simple nurture. Outsource what needs code, another system's API, or an evaluation method: cross-system syncs, custom-coded actions and the first build of AI steps. Share routing and scoring, where a partner builds and your team owns the rules.
| Workflow type | Who should own it | Why |
|---|---|---|
| Notifications and task creation | In-house | Low risk, changes weekly, and the person who feels the gap can fix it |
| Lead routing | Shared | The rules are yours; rotation, fallbacks and territory logic are where builds break |
| Lifecycle stages and scoring | Shared | Needs a sales and marketing agreement first, then a careful first build and in-house tuning |
| Data hygiene | In-house for simple fixes, partner for formatting and deduplication at volume | A bad bulk edit is hard to undo |
| Cross-system syncs | Partner | Retry logic, rate limits and two sources of truth need an engineer |
| Custom-coded actions | Partner, unless you employ a developer | Code needs version control, tests and someone on call |
| Breeze agents and AI steps | Partner for setup, in-house for review | Output quality and credit use both need measuring before go-live |
For the build techniques themselves, see our older posts on advanced workflow automation for marketing teams and workflow automation in RevOps. This post is only about who should do the work.
Which HubSpot subscription and skills does each type need?
Workflows are available on Professional and Enterprise subscriptions across Marketing, Sales, Service, Data Hub, Smart CRM and Revenue Hub. Custom code, webhooks and the Format data action need Data Hub Professional or Enterprise. AI actions need HubSpot Credits on top. Check the tier before you scope the work, because it rules options in or out.
What HubSpot's documentation says, type by type:
- Notifications, tasks, nurture. Any Professional or Enterprise hub. Skill: a HubSpot admin. Source: Create workflows, last updated 25 September 2026.
- Lead routing. The Rotate record to owner action is limited to Sales Hub and Service Hub Professional and Enterprise. Skill: an admin plus a sales leader who will sign off the rules. Source: Choose your workflow actions, last updated 25 September 2026.
- Scoring. The lead scoring tool needs Marketing Hub or Sales Hub Professional or Enterprise; building scores with AI is Marketing Hub Enterprise only. Source: Overview of the lead scoring tool, last updated 2 September 2026.
- Syncs and custom code. Send a webhook and Custom code are Data Hub Professional and Enterprise only. Custom code runs JavaScript, with Python in beta, and each action must finish within 20 seconds and 128 MB of memory. Skill: a developer. Source: HubSpot's custom code actions reference.
- AI steps and agents. One AI action in a workflow uses 10 credits, and the Run Agent action is limited to 500 executions a day. Sources: the HubSpot product and services catalog and Run agents using workflows, last updated 10 September 2026.
Workflow limits, from the workflows FAQ, last updated 3 August 2026: 300 on Marketing, Sales or Service Hub Professional, 1,000 on Enterprise, 400 on Data Hub Professional and 1,100 on Data Hub Enterprise. The highest limit among your subscriptions applies. We could not confirm from that page whether any Starter plan includes the full workflows tool, so we have left Starter out.
What goes wrong when you build everything in-house?
The library grows faster than anyone documents it. We have inherited portals with more than 400 active workflows where nobody on the team could say what each one does. The failures are quiet: an action errors, the record moves on, and the log is never read.
The patterns we see most, from our HubSpot workflows page:
- Two workflows write the same property and overwrite each other.
- An integration action fails for two months before anyone notices.
- A property is renamed and the workflows that depend on it break.
- A workflow is switched off during a rebuild and never switched back on.
None of these need an agency to fix. They need a naming convention, a limit of two branch levels, and a weekly error-log review with a named owner. The second in-house failure is harder: one admin holds the whole design in their head, and it leaves when they do.
What goes wrong when you outsource everything?
You pay partner rates for work an admin could do in ten minutes, and every small change waits on a ticket. Worse, nobody inside understands the system, so the team cannot judge whether a proposed build is sensible, and the library drifts as soon as the engagement ends.
Three signs you have outsourced too much:
- A rep asks for a new task reminder and it takes a week.
- Nobody internal can open a workflow and explain why a lead went where it did.
- The partner is the only party with the documentation.
If your automation is deterministic, low volume and stable, you probably do not need a partner at all. HubSpot also sells its own technical consulting for programmable automation, listed in the same catalog, which is a fair route if you want one process built by HubSpot's team.
What does a partner engagement cost, and how long does it take?
At INSIDEA, an AI workflow build runs five weeks from mapping to handover and a workflow library clean-up takes two weeks, each a fixed fee, scoped at proposal, from $2,000. Activating a Breeze agent is $300 in 5 business days or $250 over 10.
We have no verified market-wide figures for partner fees, so these are ours only.
Where each figure comes from:
- AI workflow build. Week 1 map and plan, weeks 2 and 3 build, week 4 deploy, week 5 handover, with AI actions run in shadow mode for 1 to 2 weeks against a human baseline before rollout and a 30-day warranty after launch. Source: AI workflow automation.
- Library clean-up. Week 1 audit, naming and refactor; week 2 monitoring and owner training. Source: HubSpot workflows.
- Agent activation. One price for any agent, Fast Track or Standard. Source: HubSpot agent activation.
HubSpot's own charges are separate. Credits cost $0.010 each, or $10 per pack of 1,000, per HubSpot's catalog. HubSpot's credits article, last updated 16 September 2026, says usage-based features pause when included credits run out unless you have bought more.
Who maintains the workflows after go-live?
Your team should own the list, the naming convention and the weekly error review, whoever built the workflows. A partner should maintain what your team cannot safely change: code, integrations and AI steps that need tuning. Decide this at scoping, and write down who is on call for each workflow.
Two models work:
- Handover. The partner documents, trains a named owner and leaves. Right when the build is rules only and you have an admin with time.
- Managed. The partner stays on a retainer. INSIDEA's AI managed operations starts from $2,000 a month and covers quality monitoring, drift detection, cost tracking and minor prompt tuning. That page says plainly it is a poor fit if you need about five hours of work a month.
What does the split look like for one mid-sized team?
Take an illustrative 45-person B2B software company on Marketing Hub Professional and Sales Hub Professional, with one HubSpot admin and 1,500 new leads a month. The admin keeps the everyday workflows. A partner builds routing and scoring and hands them back, and builds and maintains the sync and the AI step.
- Kept in-house. Notifications, task creation, nurture, and day-to-day edits to routing rules. All available on their tier, inside a 300-workflow limit.
- Partner builds, team owns. Routing by region and a scoring model, signed off by sales. Our client Promptly routes every lead to the right sales director by region this way.
- Partner builds and maintains. An ERP sync. This needs webhooks or custom code, so the company must add Data Hub Professional first; check HubSpot's pricing page for the current price.
- AI step. Classifying every inbound lead with one AI action uses 1,500 x 10 = 15,000 credits a month. HubSpot's credits article gives 3,000 included credits for Marketing Hub Professional, leaving 12,000 to buy: 12 packs, or $120 a month.
Our guide to adding AI agents to HubSpot covers the agent side of the same decision.
INSIDEA
Ready to get more out of HubSpot?
We are an Elite HubSpot Partner rated 4.99 across 500+ verified reviews. Let's make your portal work harder.
How does INSIDEA build and hand over HubSpot automation?
INSIDEA is an Elite HubSpot Partner rated 4.99 across 500+ verified reviews, with 150+ in-house experts. We start by mapping which decisions rules can make and which need judgment, and we tell you which workflows to keep. Nothing with an AI step ships without a test set of 50 to 200 examples. Builds are a fixed fee, scoped at proposal, from $2,000, and the workflow, code and runbook end up in your hands. See AI workflow automation for the build, HubSpot agent activation for Breeze agents, and AI managed operations if you want us to keep running it.
How INSIDEA works
