What This Update Actually Is
Serverless functions have existed in other HubSpot Enterprise tiers for a while. They let you run custom backend logic inside your HubSpot tools without standing up a server. You write the function; HubSpot runs it.
What's new here is where they're available. Revenue Hub Enterprise users can now use serverless functions inside Custom Coded Modules on quotes. That means you can connect a quote directly to external data sources, run on-the-fly calculations, and, most critically, write buyer-entered data straight back into the associated CRM record the moment they interact with the quote.
Previously, Revenue Hub didn't have access to serverless functions at all. You'd need a separate hub subscription to get there. That barrier is now gone for Revenue Hub Enterprise and Professional accounts.
Why HubSpot Shipped This
Here's the problem this solves. A buyer opens a quote. They select a configuration option, fill in a product detail, or answer a question your team built into the quote. That input matters. It's real purchase intent, real specification data, real context your sales team needs.
Before this update, that data had two bad options: get lost entirely, or get manually re-entered by a rep who wasn't watching the quote in real time. Neither is acceptable in a modern CPQ setup.
The internal frustration is real. Sales ops teams tell us they spend hours each week chasing down what a buyer actually said during the quoting process. Reps guess. Managers audit. Deals slow down. Serverless functions fix the root cause: the quote and the CRM weren't talking to each other in the moment that mattered.
How to Use It Step by Step
- Confirm you're on Revenue Hub Enterprise or Professional. Serverless functions in quotes are only available on these tiers.
- Open your quote template editor and add or edit a Custom Coded Module. This is where the serverless function lives.
- Write your serverless function logic. Define what buyer input you want to capture, what external system (if any) you're pulling from, and what CRM property you want to update.
- Map the output to the right CRM record. Typically that's the deal or contact associated with the quote. Use the HubSpot API inside your function to write the value back.
- Test with a draft quote. Send it to yourself, fill in the custom fields, and confirm the CRM properties update in real time on the associated deal.
- Deploy and train your reps. Let them know the quote now captures input automatically. They don't need to re-enter anything. The deal record will reflect what the buyer told them.
What It Touches in Your HubSpot Strategy
This update ripples outward quickly. Let's map it.
Your deal properties get richer. When buyer input lands on the deal record automatically, your pipeline data reflects what buyers actually said. Forecasting, deal reviews, and handoffs to customer success all improve because the data is there without anyone chasing it down.
Key Takeaway
Serverless functions in quotes turn passive buyer interaction into active CRM data. The quote is no longer just a document; it's a data capture layer for your deals.
Your workflows gain a smarter trigger. Once buyer input is in the CRM, you can trigger workflows off those property values. A buyer selects a certain product configuration? Trigger a task for a solutions engineer. A buyer enters a volume above a threshold? Notify the account executive in real time. The logic possibilities are significant.
Your CPQ process tightens. For companies using Revenue Hub as their configure-price-quote engine, this closes a major gap. Buyers can now interact with a quote in a meaningful, specific way, and that interaction becomes structured data inside HubSpot.
This pairs naturally with other recent quote improvements. If you're already using Breeze inside the quote template editor to build smarter quote copy and product layouts, serverless functions give you the backend logic to match the front-end experience you're building.
External system integration also opens up here. Serverless functions can call external APIs, so you can pull real-time pricing from an ERP, check inventory from a warehouse system, or validate a buyer entry against a product catalog, all inside the quote experience.
Key Takeaway
If your sales process involves custom configurations, complex pricing, or buyer-specific product options, this update moves Revenue Hub closer to a true enterprise CPQ without requiring a separate tool.
If you're still getting your arms around what Revenue Hub includes and how it fits your stack, our complete Revenue Hub guide is the right place to start. It covers what's in the hub, how it's priced, and how teams are actually rolling it out.
Who Should Care Most
Not every HubSpot account needs to act on this today. But the humans listed below should pay close attention.
- Revenue Hub Enterprise admins who are already using Custom Coded Modules: you can add serverless logic to what you've built without changing your architecture.
- RevOps leaders who've been frustrated by manual data entry after quote interactions: this closes the loop without a middleware tool or a Zap.
- Sales engineers and solution architects at companies with complex, configurable products: serverless functions let the quote itself handle configuration logic, keeping buyers in one experience.
- Growing companies currently running CPQ through a separate tool: this may be your signal to consolidate. If Revenue Hub can now capture and sync buyer configuration data, one less tool in the stack becomes realistic.
If you're on Revenue Hub Professional, you get access too, though the most complex use cases will likely emerge at the Enterprise tier where developer resources and custom modules are more common.
George's Take
Here's what strikes me most about this update. We've seen it inside dozens of portals: the quote gets sent, the buyer engages, and then the information the buyer shared just... evaporates. Someone has to remember to update the deal. Someone has to track down what configuration the buyer selected. That's not a data problem; it's a trust problem. When your CRM doesn't reflect what actually happened, humans stop trusting it. They build spreadsheets on the side. They rely on memory. The whole system degrades. Serverless functions in Revenue Hub fix the data at the source, which means the trust comes back too.
“The quote isn't just a document you send. It's a conversation your buyer is having with your business. Now HubSpot can actually listen to that conversation and write down what it hears.”
If your team is also working on tightening revenue visibility, pair this with a look at Revenue Forecast Reporting in HubSpot. Better deal data from buyer-entered quote fields feeds cleaner forecasts. These two updates belong in the same RevOps conversation.
If you want help scoping what serverless functions could do inside your specific quoting process, or if you're not sure whether your Revenue Hub setup is ready to take advantage of this, let's talk. Book a strategy call with the Sidekick team and we'll map it out with you.
Frequently Asked Questions
What are serverless functions in HubSpot Revenue Hub Enterprise?
Serverless functions in Revenue Hub Enterprise let you run custom backend logic inside custom-coded modules on HubSpot quotes. You can connect to external data sources, run calculations, and automatically write buyer-entered information from a quote back into the associated CRM deal or contact record, with no server setup required.
Which HubSpot tiers get serverless functions in Revenue Hub?
Serverless functions in Revenue Hub are available to Revenue Hub Enterprise and Revenue Hub Professional subscribers. They were previously unavailable in Revenue Hub entirely and required a separate hub subscription to access.
How do serverless functions help with CPQ in HubSpot?
In a configure-price-quote workflow, buyers often fill out custom fields on a quote. Serverless functions capture that input and write it straight into your CRM record in real time. That eliminates manual re-entry, keeps deal data accurate, and lets you trigger workflows based on what buyers actually selected or entered.
Can serverless functions in Revenue Hub connect to external systems?
Yes. Serverless functions can call external APIs, so you can pull real-time pricing from an ERP, check product inventory, or validate buyer input against an external catalog, all within the HubSpot quote experience. The data returned can then be displayed to the buyer or written back to the CRM.
Do I need coding experience to use serverless functions in Revenue Hub?
Yes, serverless functions require writing code, typically JavaScript. They live inside Custom Coded Modules in the quote template editor. If your team doesn't have a developer, this is a case where a HubSpot partner or RevOps consultant can help you build and test the function before it goes live.
What's the difference between using serverless functions in Revenue Hub versus a workflow?
Workflows in HubSpot are triggered after an event and run on HubSpot's logic engine. Serverless functions run in real time during a quote interaction and can reach external systems mid-session. For capturing buyer input the moment it happens on a quote, serverless functions are faster and more precise than a post-submission workflow.
