Building a Scalable HubSpot Sales Hub Integration for a B2B SaaS Growth Platform without Enterprise Tier Dependencies
Most B2B SaaS integrations with HubSpot lean on Custom Objects, which only Enterprise portals have, and this referral platform's prospects were on Professional. For a referral platform, we bypassed that limitation with an AWS-hosted middleware layer. The solution maps complex referral data to standard objects and injects contextual iFrames via CRM custom cards. That expanded the total addressable market.
Executive Summary
Context
A B2B SaaS growth-enablement company already had a mature Salesforce integration. It needed to replicate that core product experience in HubSpot Sales Hub. That would close stalled enterprise deals.
What We Built
We engineered an AWS-hosted middleware integration. It maps referral data to standard objects and injects a context-aware UI via CRM custom cards and iFrames.
Tech Stack
- HubSpot Sales Hub (Professional)
- Amazon AWS (API Gateway & Hosting)
- the client's platform API
- HubSpot CRM Custom Cards
Not a fit if your target customers are already on HubSpot Enterprise, since native Custom Objects would handle the engagement states directly and the AWS middleware layer only adds a system to maintain. It also depends on your own product having a dashboard that can render inside an iframe from a record-specific URL; without one, there is no reporting view to embed.
The Challenge
Data sync was one problem, but market accessibility turned out to be the harder constraint. The client's original roadmap assumed HubSpot Custom Objects would handle the engagement states of their referral logic, but their primary target market turned out to use HubSpot Professional. Forcing an Enterprise upgrade for a single integration was a non-starter for their sales team. The technical challenge was replicating a client's proprietary "Engagement" object's functionality using only standard Contact and Deal properties. We also ran into a limitation in the HubSpot API: it allows querying reports but forbids the programmatic creation of new report assets, which meant we could not ship a plug-and-play dashboard using native reporting tools.
Our Approach
We pivoted from a native Custom Object architecture to a property-mapping strategy managed via AWS middleware. We also built a custom handshake through an AWS API Gateway that manages OAuth installations. On install, the gateway creates the integration's custom properties in the customer's portal, with no manual setup. To solve the UI problem, we moved away from the then-beta React UI Extensions and used standard right-hand sidebar custom cards that trigger context-aware iFrames instead. That let us render the client's native application UI directly inside HubSpot records, so sales reps could initiate referrals without leaving the CRM. For reporting, we bypassed the API constraint by embedding the client's own performance dashboards into HubSpot via "Other Content" modules, giving a unified view of deal velocity.
This engagement is part of our systems integration work for technology & software organisations.
Impact
Recovered Mid-Market Sales Velocity
The integration removed the sales blocker. The client could now convert high-value prospects who'd been stalled by the lack of a HubSpot-native workflow.
Professional Tier Compatibility
The solution works without Custom Objects. That lets the client sell into the HubSpot Professional segment, expanding their total addressable market.
Native CRM Adoption
Sales reps can work from the Contact and Deal sidebars. They initiate and track referral status there. They don't have to toggle between the CRM and the external client platform anymore.
We used an AWS API Gateway for multitenant OAuth installations. That layer manages the exchange of secret keys and creates custom properties across disparate HubSpot portals.
We skipped hierarchical objects. Instead, we engineered state-tracking logic that maps engagement IDs to standard HubSpot properties. That kept data sync clean on lower-tier HubSpot licenses.
Prospects on HubSpot Professional couldn't use Custom Objects, and an Enterprise upgrade for one integration wasn't an option. Now AWS middleware maps referral data onto standard Contact and Deal properties. An API Gateway handshake manages OAuth installs and creates the custom properties with no manual setup. Custom cards on the record sidebar open the client's own app in an iFrame, so reps start referrals inside the CRM.
FAQ
The AWS middleware manages the relationship logic externally. When a referral starts, it maps the unique external record ID to a custom property on the standard HubSpot Deal or Contact record. That lets the integration run on the Professional tier, and data integrity between the two platforms still holds.
The HubSpot API limits the programmatic creation of reports. So we embedded the platform's native dashboards into HubSpot via iFrames instead. Users get real-time deal velocity and win-rate data inside the HubSpot UI, with no manual configuration of custom reports for every new installation.
