How much to charge for a HubSpot automation
How much to charge for a HubSpot automation comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is the yearly value of the manual work the automation removes, plus any tools it replaces. Your quote sits between the two. The typical job is a sales or marketing team that already lives in HubSpot: leads that sit unassigned, deal stages nobody updates, form fills that should create tasks, or a weekly pipeline report someone builds by hand.
I am not going to give you a market dollar figure. A workflow that assigns new contacts round-robin and a build that syncs deals to an outside billing system, retries on rate limits and alerts on failures are different jobs. One number would be noise. Your rate and the client's numbers will give you a real one.
What makes HubSpot different from most automation jobs is that the plan decides the route. The same request can be a few hours inside HubSpot's own workflows on one plan, and a hosted integration with its own error handling on another. Claude Code earns its place on the custom side: it writes and tests the API calls, the webhook handlers, the custom code actions and the retry logic.
Calculate your floor and ceiling
Run this before you name a price. Every input is yours or the client's, so you can show the working in the proposal.
The HubSpot automation calculation
| Number | How to get it | Who supplies it |
|---|---|---|
| Floor | Your estimated hours for each line in the quote, plus a buffer you choose for edge cases and revisions, times your hourly rate | You |
| Time value per year | Hours per week spent assigning leads, updating deal stages, copying data between systems and building reports, times 52, times what an hour of that person's time costs | Client |
| Spend replaced | What they pay per year for connector tools, add-ons or contractors the automation takes over, if any | Client |
| Cost of a miss | Only if they can point to real examples: a lead nobody followed up, a deal that sat in the wrong stage, a renewal nobody was reminded about | Client's own history, your judgment |
| Ceiling | Time value plus spend replaced, plus the miss line only if it is documented | Calculated |
If the floor is above the ceiling, the automation will not pay for itself in a year. Say so and offer a smaller version, such as automating only lead assignment and leaving reporting for phase two.
Check the HubSpot plan before you quote
Ask which hubs and tiers the client pays for in the first call. It changes what you can build and therefore what you charge.
What the plan unlocks
| Feature | Plans that include it | What it means for the quote |
|---|---|---|
| Workflows | Professional or Enterprise of Marketing Hub, Sales Hub, Service Hub, Data Hub, Smart CRM or Revenue Hub | On Free or Starter there are no workflows to build in. The job moves to the API and something you host |
| Webhook actions in workflows | Data Hub Professional or Enterprise | Lets a workflow send or fetch data from an outside system without you hosting a poller |
| Custom code actions in workflows | Data Hub Professional or Enterprise | JavaScript or Python that runs inside the workflow, limited to 20 seconds and 128 MB of memory per run |
The number of workflows an account can create also depends on its subscriptions, and some features need HubSpot Credits or seats. Check the client's account before you promise a design that needs ten workflows.
My rule: if native workflows do the job on the plan they already have, quote that route and price it lower, because there is nothing to host. If the job needs custom code or webhooks and they do not have Data Hub Professional, put the two options side by side in the proposal: their plan upgrade, or your hosted integration and its maintenance. Let them pick with both costs in front of them.
Check the API limits for a custom build
If any part of the build calls the HubSpot API, the client's tier sets your limits. These apply to privately distributed apps, which is what a client build should be.
HubSpot API limits for privately distributed apps
| Tier | Burst limit per app | Daily limit per account |
|---|---|---|
| Free and Starter | 100 requests every 10 seconds | 250,000 |
| Professional | 190 requests every 10 seconds | 625,000 |
| Enterprise | 190 requests every 10 seconds | 1,000,000 |
| With the API limit increase add-on | 250 requests every 10 seconds | 1,000,000 extra per increase, up to two |
The daily limit is the one that bites. It is shared by every privately distributed app in the account, so your integration can run out because another tool the client installed is busy. It resets at midnight in the account's time zone. The CRM Search API and the associations API have their own stricter limits, and a request over any limit gets a 429 response.
Quote the protection as its own line: batch endpoints where they exist, caching for settings and properties you read repeatedly, throttling under the burst limit, and retries on 429. Where the client has Data Hub Professional, webhook calls made from workflows do not count toward the API rate limit, which is a real reason to push data out of HubSpot with a workflow instead of polling for it.
The CCC HubSpot Quote
Six parts of a HubSpot automation quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Process map | Every pipeline, stage, owner and handoff, written up and signed off before the build | Walk me through one lead from form fill to closed deal |
| Property and data cleanup | Fixing property types, picklist values, duplicates and lifecycle stages so automations have clean fields to trigger on | Which property is filled in least consistently? |
| Workflows and code | Native workflows, webhook and custom code actions, and any API integration you host | When does this need to happen, and who should be told? |
| Error handling | Throttling, retries on 429, alerts when a run fails, and who gets told | If this stops for a day, who notices first? |
| Ownership and access | The app installed in the client's account, its scopes, and where its token is stored | Who is the super admin, and which hubs and tiers do you pay for? |
| Handover and tuning window | A walkthrough, notes on each workflow, and adjustments after the first month of real use | Who will own this once it is live? |
Data cleanup is the line people skip and regret. Workflows enroll on property values, so a lifecycle stage set three different ways or a lead source that is half free text breaks the build before you start. Price cleanup as its own line and get it signed off.
Build it in the client's account
HubSpot changed the rules on this recently, and older tutorials have not caught up. As of October 26, 2026, legacy private apps can no longer be created. A client build is now an app on the current developer platform with its distribution set to private, and to restrict it to one account you set its authentication to static. If you quote from an old guide that says to create a private app in settings, the step will not exist.
- Install the app in the client's own HubSpot account and request only the scopes the build needs.
- Store the access token as a secret in the environment, never in code or a repo.
- If the client still runs an existing legacy private app, only super admins can access it, and its token should be rotated at least every six months. Put the rotation in the handover notes.
- Write into the proposal which app owns each integration, which workflows call it, and the date your access ends.
Running the build on your own account or token is the handover mistake that costs you a weekend later. The day your access is removed, it stops, and the client remembers who built it.
How to present the HubSpot automation quote
- Lead with the outcome in the client's words, such as every inbound lead assigned and given a follow-up task within five minutes, then the price.
- Offer three options. A starter on native workflows only, a standard that adds webhook or custom code actions and error alerts, and a full version with a hosted integration and a longer tuning window. Make the middle one the clear best value.
- Show your calculation and the plan check side by side, so they see the design fits their subscription.
- Itemize it: process map, data cleanup, workflows and code, error handling, ownership and access, then handover.
- Take a deposit and tie the rest to milestones. How much deposit to charge covers the schedule.
Put a fixed tuning window in the first proposal, because someone will rename a pipeline stage or a property a workflow depends on in the first month. For ongoing changes, offer a retainer. How to price a maintenance retainer covers the structure, and client discovery questions before you quote has the questions to ask first.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a HubSpot automation?
Work out a floor from your estimated hours times your rate, and a ceiling from the manual hours it removes per year plus any tools it replaces. Quote between the two and itemize each part, including data cleanup, error handling and a tuning window.
Which HubSpot plans include workflows?
Workflows are available on Professional and Enterprise subscriptions of Marketing Hub, Sales Hub, Service Hub, Data Hub, Smart CRM and Revenue Hub. Free and Starter accounts need an API integration instead.
Do HubSpot workflows support custom code and webhooks?
Yes, with Data Hub Professional or Enterprise. Custom code actions run JavaScript or Python and must finish within 20 seconds using up to 128 MB of memory. Webhook actions can send or fetch data from outside systems.
What is the HubSpot API rate limit?
For privately distributed apps, Free and Starter accounts get 100 requests every 10 seconds per app and 250,000 per day per account. Professional gets 190 per 10 seconds and 625,000 per day, and Enterprise gets 190 per 10 seconds and 1,000,000 per day.
Can I still create a HubSpot private app?
Not a legacy one. As of October 26, 2026, legacy private apps can no longer be created. Build an app on the current developer platform with distribution set to private and static authentication to install it in a single account.
Can Claude Code help build a HubSpot automation?
Claude Code can write and test the API calls, webhook handlers, custom code actions and retry logic. You still own the process map, the data cleanup decisions, the plan check and the client conversations.
Last reviewed by Duncan Rogoff on November 21, 2026


