Frontier spoke

HubSpot App Marketplace — the SMB CRM marketplace Breeze agents read

HubSpot's App Marketplace is the SMB-CRM analogue of AppExchange — smaller scale, faster review, but the same agent-discovery dynamic as Breeze (HubSpot's agent runtime) absorbs more of the marketer-and-sales user's workflow. A standard App Marketplace listing earns human installs from HubSpot admins; a Breeze-aware listing exposes capabilities the Customer, Prospecting, Content, and Social Media agents can call inside their flows. The lighter touch on review timelines makes HubSpot the fastest of the four big-platform listings to ship — and the smallest cost of being absent.

By Chris Mühlnickel · 2026-05-18

What is HubSpot App Marketplace?

HubSpot's third-party app store, increasingly relevant as HubSpot adds AI-agent features to its CRM, marketing, sales, and service products. A listing here is the primary route to being discoverable by HubSpot's Breeze agents — Customer Agent, Prospecting Agent, Content Agent, Social Media Agent, Knowledge Base Agent — and to the human admins who configure the workflows those agents run on top of.

By the numbers

Why it matters

HubSpot is the SMB and mid-market version of the same listing-driven agent-discovery shift happening across enterprise marketplaces — smaller scale than Salesforce or Microsoft, but the same dynamic, faster review, and meaningful early performance data. Customer Agent resolves 65% of conversations across 8,000+ users today; Prospecting Agent grew activations 57% quarter-over-quarter through 2025; Breeze Marketplace exists as an explicit agent-and-assistant catalog alongside the broader App Marketplace. For vendors selling into HubSpot-using customers, the App Marketplace is the route to discoverability by both the human admins who install apps and the Breeze agents those admins are increasingly delegating to.

The App Marketplace and Breeze Marketplace are complementary surfaces, not redundant ones. The App Marketplace is the broader third-party-app catalog — CRM integrations, workflow extensions, custom dashboards — that HubSpot admins browse to extend their portals. The Breeze Marketplace, launched in 2025, is the agent-runtime-extension catalog where vendors list Breeze-specific agents and assistants. Most ISVs need both: the App Marketplace listing captures the broader funnel of admins, the Breeze Marketplace listing surfaces inside the Breeze runtime when admins are looking for additional agents. Skipping either narrows the visible surface.

HubSpot's pricing direction makes per-invocation capability billing inevitable. HubSpot moved Breeze agents to pay-per-result pricing (per-resolved-conversation, per-qualified-lead) in late 2025 — an explicit commitment to modeling agent invocations as billable events. The downstream implication for App Marketplace vendors: HubSpot is increasingly likely to bill third-party agent-callable capabilities per invocation as well, and vendors who can price per agent-call rather than per-seat align cleanly with that direction. Vendors locked into flat-rate subscriptions today will look out-of-step with the platform's pricing model through 2026-2027.

The faster review timeline is a feature, not a discount. AppExchange certification takes 8-12 weeks; AppSource takes 4-8; HubSpot App Marketplace takes 2-4. The faster cycle means listings ship and update fast, capability metadata stays current, and the cost of listing experiments is low. The trade-off — less platform-side security review — pushes more responsibility onto vendors for handling scoping, auth, and data governance themselves. For vendors with disciplined security posture, this is a positive trade; for vendors who relied on AppExchange's review to validate their security work, HubSpot's lighter touch is a different mental model.

The cost of being absent is smaller in absolute terms but proportionally similar. HubSpot's installed base is smaller than Salesforce's or Microsoft's, so the absolute opportunity loss from absence is correspondingly smaller. But the listing investment is also smaller, so the proportional impact is similar. For vendors selling into customers that overlap meaningfully with HubSpot's SMB and mid-market base — particularly in marketing, sales-enablement, customer-service, and content tooling — the App Marketplace listing is the highest-ROI single listing among the big four because the cost-to-presence ratio is the most favorable.

Where it's heading

MCP-server registration becomes a first-class submission primitive for both Marketplaces. Today, App Marketplace listings reference REST integrations and HubSpot OAuth flows; the 2026-2027 trajectory pulls toward MCP server endpoint + scoped capability declarations as the durable shape of an agent-callable HubSpot listing. The pattern parallels what AppExchange did with AgentExchange and what AppSource is doing with Copilot Studio MCP general availability. Vendors who ship MCP-modeled capabilities from the start position cleanly; vendors with HubSpot-specific REST shims will retrofit.

Breeze agents become a discovery surface for App Marketplace apps inside HubSpot's product UI. HubSpot's direction is for Breeze Customer Agent, Prospecting Agent, and Content Agent to surface contextual App Marketplace recommendations ('to handle this kind of return, install [X]'). For App Marketplace vendors, the implication is that Breeze becomes a primary distribution channel — vendors who ship capabilities Breeze actively recommends will see install velocity uncorrelated with their direct marketing spend.

Per-invocation billing becomes a first-class App Marketplace primitive. HubSpot's Breeze pricing shift to pay-per-result is a strong signal for how third-party agent-callable capabilities will be metered on the App Marketplace. Expect HubSpot's billing tooling to expose per-invocation metering through 2026, and expect vendors who can price per agent-call to compound advantage versus flat-rate subscriptions.

Cross-platform capability federation reaches HubSpot. The Linux Foundation Agentic AI Foundation work that's federating capability declarations across enterprise marketplaces will reach HubSpot's surface in 2027. The expectation: an MCP server registered through the HubSpot App Marketplace gains incidental federated visibility in AppExchange, AppSource, and the public MCP directory — provided the vendor modeled their capability as MCP rather than as HubSpot-specific glue code.

HubSpot's CRM-to-commerce surface expands, pulling commerce-side apps into the Marketplace. Breeze's expansion into commerce-relevant workflows (cart abandonment, post-purchase service, churn-risk identification) pulls the App Marketplace's category coverage into the same surface area that Shopify and Adobe Commerce occupy. Expect 2026-2027 to surface HubSpot-Shopify bidirectional capability listings as a common pattern — apps that mediate the CRM-to-commerce flow inside a single Breeze invocation.

Smaller marketplace, faster iteration loop. HubSpot's review cycle and platform velocity mean the marketplace evolves faster than its enterprise peers. Vendors using HubSpot as a testbed for agent-callable capability designs before shipping to AppExchange or AppSource get a faster iteration loop with real customer data. Several vendors are already operating this pattern explicitly — HubSpot first to validate capability design, enterprise marketplaces second once the design has stabilized.

Common mistakes

  • Listing on the App Marketplace but not the Breeze Marketplace when you ship a Breeze-runtime extension. The two surfaces are complementary; agent-runtime extensions live in the Breeze Marketplace. Vendors who only ship to the App Marketplace miss the Breeze runtime's native discovery surface.
  • Shipping a HubSpot-specific REST integration instead of an [MCP server](/learn/agent-protocols/model-context-protocol). REST integrations work for human-admin-mediated flows but don't surface natively to Breeze agents. The 2026-2027 trajectory pulls toward MCP-callable capabilities; new integrations should ship MCP first.
  • Pricing the App Marketplace listing on a flat per-seat subscription. HubSpot's pricing direction is per-result for Breeze agents and increasingly per-invocation for third-party agent-callable capabilities. Vendors locked into flat-rate subscriptions look out-of-step with the platform's pricing model.
  • Assuming the faster review means lower listing standards. HubSpot's 2-4 week review is faster than AppExchange or AppSource, but expectations for capability declarations, scoped permissions, and security posture are still material. The faster timeline reflects narrower platform-side review, not lower vendor responsibility.
  • Letting capability metadata go stale. App Marketplace listings rot as the underlying product ships features. A listing claiming capabilities your integration no longer offers leads to failed invocations from Breeze agents and to install-then-uninstall churn from human admins.
  • Treating HubSpot as too small to matter. The absolute opportunity loss is smaller than Salesforce or Microsoft, but the listing-cost-to-presence ratio is the most favorable of the big four. For vendors selling into the SMB and mid-market segment, skipping HubSpot is leaving the cheapest agent-routable listing on the table.
  • Skipping App Marketplace because 'we sell direct to HubSpot-using customers anyway.' Direct enterprise contracts still flow through customers' HubSpot portals, and the Breeze agent layer still reads the App Marketplace as the discovery surface. Direct-sales vendors who skip the App Marketplace listing end up invisible to their own customers' Breeze flows.

Frequently asked

What's the relationship between the App Marketplace and the Breeze Marketplace?

The App Marketplace is the long-running third-party app catalog — CRM integrations, workflow extensions, custom dashboards, the marketing/sales/service ecosystem. The Breeze Marketplace launched in 2025 as the agent-and-assistant catalog specifically for Breeze runtime extensions. Both are visible inside HubSpot; the App Marketplace is the broader surface, the Breeze Marketplace is the agent-extension layer. Most ISVs ship on the App Marketplace; ISVs building Breeze-specific agents or assistants list on the Breeze Marketplace alongside their App Marketplace presence.

Is HubSpot really comparable to Salesforce or Microsoft for agent-platform purposes?

Different scale, same dynamic. HubSpot's installed base is smaller than Salesforce's or Microsoft's, but the SMB and mid-market customers are the segment most likely to deploy a Breeze agent inside their entire workflow rather than as a focused experiment. Customer Agent resolves 65% of conversations across 8,000+ users; Prospecting Agent grew activations 57% quarter-over-quarter through 2025. For vendors selling into HubSpot-using customers, the App Marketplace is the discoverability surface for both human admins and Breeze agents — the same logic that makes AppExchange load-bearing for Salesforce-using customers applies here at SMB scale.

How long does HubSpot App Marketplace certification take?

Faster than its enterprise peers. App Marketplace certification typically ships inside 2-4 weeks depending on integration depth; Breeze Marketplace submission for agent-runtime extensions takes a similar window. The faster review timeline is one of HubSpot's distinguishing features versus AppExchange's 8-12 weeks or AppSource's 4-8 weeks. The trade-off: less depth in the platform-side security review, more responsibility on the vendor for handling their own auth, scoping, and data governance.

Are Breeze agents callable via [MCP](/learn/agent-protocols/model-context-protocol)?

HubSpot's published direction is yes, and the early 2026 Breeze Marketplace expansion explicitly cites MCP-server registration as a future first-class submission field. The current pattern is: App Marketplace listing + HubSpot OAuth flow + REST integration; the 2026 trajectory pulls toward App Marketplace listing + MCP server + scoped tool schemas that Breeze agents invoke directly. Vendors who model their capabilities as MCP servers from the start position cleanly for the shift; vendors who hand-roll HubSpot-specific REST integrations are building maintenance liability.

What does the 'Pay-per-Result' Breeze pricing shift mean for App Marketplace apps?

HubSpot moved Breeze agents to a pay-per-result pricing model in late 2025 (per-resolved-conversation for Customer Agent, per-qualified-lead for Prospecting Agent, etc.). For App Marketplace apps that surface capabilities Breeze agents invoke, the implication is downstream: HubSpot is increasingly modeling agent invocations as billable events, and the natural extension is for third-party MCP-callable capabilities to bill the same way. Vendors who can price their capability per agent-invocation rather than per-seat align cleanly with HubSpot's pricing direction; flat-rate-subscription vendors will look out-of-step over time.

Should I list on the App Marketplace or the Breeze Marketplace first?

App Marketplace first, almost always. The App Marketplace is the discovery surface for human HubSpot admins — and human admins are the audience that installs apps, configures workflows, and ultimately enables their Breeze agents to invoke your capability. The Breeze Marketplace is the agent-runtime-extension surface, which assumes the human admin has already adopted Breeze and is looking for additional agents or assistants to layer in. Most vendors ship App Marketplace first to capture the broader funnel, then layer Breeze Marketplace presence as their Breeze-specific value emerges.

Does the smaller marketplace size mean less competitive pressure?

Less than at AppSource or AppExchange, but the dynamic is similar — listing presence still beats absence. The opportunity cost of skipping HubSpot is smaller in absolute terms than skipping Salesforce or Microsoft, but it's also a faster, cheaper listing to ship. Vendors who sell into SMB and mid-market segments overlapping with HubSpot's customer base get disproportionate return relative to the listing investment because the App Marketplace review and integration work is light compared to its enterprise peers.