HubSpot just opened up custom coded modules for quotes inside Commerce Hub, and your quotes are no longer stuck being static pricing PDFs. They can now be interactive, data-rich, buyer-accessible web pages that pull live CRM data, capture buyer information, and render server-side with your brand. If you're a HubSpot admin or RevOps human, this is the update that turns a quote into an experience.
In this live episode of HubHeroes, George, Chad, and Max dig into what HubSpot actually shipped, why it matters for RevOps and sales, how Chad built a real ROI calculator module for Rad AI using Claude and Claude Code, and how everyday admins (not just developers) can ship custom quote experiences without a dev team. It's a control, creativity, and barrier-to-entry conversation, and it's a fun one.
What HubSpot Actually Shipped (And Who Can Use It)
Here's the short version: inside the new Commerce Hub quote experience, you can now build custom coded modules and drop them into a quote just like you'd drop custom modules into a HubSpot CMS page. Stack them vertically. Place them side by side. Theme them to match your brand. Pull live CRM data. Capture buyer input. All of it.
This is not the legacy quote tool. Legacy quotes are still legacy quotes, and as Chad put it, they're "more or less extremely difficult to work on." The new custom modules live in the new Commerce Hub quote builder, and they're built on the HubSpot project framework, the same scaffolding that powers UI extensions across the platform.
Access requirements: Commerce Hub Professional or Enterprise. To actually create, manage, and use these for buying, you need both a sales seat and a commerce seat. If you haven't enabled the new Commerce Hub yet, that's step one.
Why a Quote Should Be More Than a Document
HubSpot's own language on the update is telling: quotes should be more than a document, they should be buyer-accessible web pages. Max called this out fast. When you buy almost anything online today, you don't get a static PDF emailed back and forth. You get a page where you can flip optional line items on and off, see totals update in real time, and self-serve through the parts of the decision a salesperson doesn't need to babysit.
Speed kills deals. Every minute a buyer spends waiting on a sales rep to rebuild a quote in some clunky system is a minute the competition is using. When the buyer can change the configuration themselves, see the new ROI, and move forward, the whole motion gets faster, smarter, and more human.
Real Use Cases That Got Us Excited
Chad walked through where his brain goes once you have custom modules in a quote. A few that hit hard:
- Multi-location and subsidiary breakdowns. If you sell B2B and use association labels for locations, you can render every location and address you'll be servicing directly inside the quote, pulled live from clean CRM data. Nobody types it in. Nobody mistypes it.
- Interactive ROI calculators. Sales drops in assumptions (units, average reports per day, error rate reduction), the module recalculates server-side, and the buyer can move sliders to model their own scenarios. Chad built exactly this for Rad AI.
- Optional line items. Let the buyer toggle add-ons on and off, with rules so they can't build a configuration you can't honor.
- Sales-to-service handoff data capture. Use the quote to collect the information the delivery team needs before the deal closes, so onboarding starts on day one instead of day fourteen.
- Brand-matched theming. Match your website fonts and colors so the quote feels like the rest of your buying experience, not a HubSpot template a buyer can spot from a mile away.
Everything renders server-side, which is the security headline. Your CRM data shows up inside the quote without exposing endpoints or tokens. GraphQL executor calls can pull associated records in a single request. It's the kind of thing that used to need a real dev sprint, and now lives inside a HubSpot project folder.
The Human-Powered, AI-Assisted Build Pattern
Here's the part that should activate every HubSpot admin and RevOps human who's been told for years that "custom" means "call a developer." Chad isn't a full-time developer. He knows enough to be dangerous, but he didn't write this module by hand. He used Claude as a coding assistant, and the pattern he ran is repeatable.
- Feed the assistant the context. Chad gave it the HubSpot documentation link, the alpha-stage email and Google Docs from the HubSpot Commerce team, a meeting transcript with his internal team, and a Loom transcript of a HubSpot developer walking through the framework.
- Have it plan before it builds. Ask it to read everything, identify the gotchas, and produce a project plan. Don't let it start coding until it has the full picture.
- Point it at your brand. Send it to your website so it can pull the color palette, fonts, and feel. Otherwise you'll get a module that looks like a generic template.
- Hand the plan to Claude Code (or similar). Once the planning is done in a desktop chat tool that can write files, drop the folder into Claude Code and let it execute the build, push the project, and deploy.
George's hard rule: don't try to do this with a browser ChatGPT context-window-paste workflow. That's how you get "context rot." Use a desktop AI assistant that can read your local files, write to disk, and leave itself notes between sessions. That's the unlock.
And start small. Don't make a custom coded quote module your first project if you've never built one. One bite-sized module. One quote. One product line. Get the win, learn the rhythm, then go bigger.
The Gotchas Worth Knowing Before You Build
- The in-editor preview is not interactive. Sliders don't slide. Numbers don't recalculate. You have to publish a live quote to see the real behavior. Don't panic and assume you built something broken.
- Your AI assistant needs solid HubSpot project framework context. Not every model knows it cold. Point it at the official docs and the example GitHub project, every time.
- Mobile responsiveness needs an explicit check. Chad's first pass looked bad on mobile until he asked his assistant to fix it. Build the prompt: "check mobile, this should look great on mobile."
- Side-by-side modules are possible, but double-check the responsive behavior before you ship.
- Rename the template project folder. Chad's still says the default template name because he forgot to rename it. Small thing, but you'll catch it on the second build.
What This Signals About Where HubSpot Is Going
Max made the bigger observation worth sitting with. Custom coded quote modules are step one. The likely next step is declarative, Breeze-driven custom quote modules where you describe what you want in natural language and HubSpot builds it for you, the way Content Hub is already moving on the CMS side.
Either way, the direction is clear: HubSpot is collapsing the gap between "what an admin can build" and "what a developer can build," and the buying experience is the next surface getting rebuilt. If you've been waiting for the moment when quotes become a real part of the buyer experience inside HubSpot, this is it.
The One Thing: What Each Host Wants You to Know
Max: "We're officially in the age where you don't always need to default to hiring a developer. There's still plenty of times you will, but maybe it shouldn't be your first thought. And watch for declarative, Breeze-driven custom quote modules next, because that's where this is going."
Chad: "The world's your oyster. If you've got any inclination for exploring, learning, and building, get in and give it a whirl. And stop living with your AI assistant in the browser. Get into the desktop interfaces, Claude Code, Codex, Claude desktop, anything that can work on your local files. That's the big unlock."
George: "This update isn't just about custom coded modules. It's about control, creativity, and giving HubSpot admins, RevOps humans, and builders the ability to turn a quote into something more than a final document with a number on it. Be a happy, helpful, humble human while you build."
The Bottom Line
HubSpot Commerce Hub just turned the quote from a static document into a build surface. You can render live CRM data inside a quote, theme it to your brand, let buyers self-serve through configuration, and capture the information your service team needs before the ink dries. And thanks to AI-assisted coding tools, the barrier to entry is now low enough that the same HubSpot admin who used to email a developer can ship the first version themselves.
Go enable Commerce Hub. Go enroll in the beta. Go read the docs and feed them to your AI assistant. Build one small module. See how it feels. Then come back and build the second one, because the buying experience you've always wanted to give your humans just got a whole lot closer to reality.
