Case Study:
How a Mortgage Lender Fixed a Broken HubSpot CRM Integration and Finally Got Reliable Pipeline Data
| Client | Mortgage lender operating two brands, a retail lending team and a sister wholesale brand, in one HubSpot portal |
|---|---|
| HubSpot | Sales Hub Professional, Marketing Hub Enterprise, Additional Brand |
| My scope | LOS integration stabilization, data model, lead routing, ownership governance, multi-brand setup |
| Built | Custom Loan object, Loan–Campaign attribution associations, LOS deal routing, duplicate suppression, routing workflows, governance framework, wholesale brand configuration |
| Integration | Loan origination system syncs deals into HubSpot; upstream duplicate issue escalated to the integration vendor |
“I trust her judgment completely and rely on her to guide foundational decisions, knowing that her approach prevents costly rework down the road.”
The Situation
When this mortgage lender came to me, they had a HubSpot subscription with plenty of horsepower: Sales Hub Pro for a team of loan officers, Marketing Hub Enterprise, and an integration that was supposed to connect their loan origination system to their CRM. In theory, everything was in place. In practice, loan officers were losing visibility into their own pipelines, duplicate records were piling up, and leadership had no reliable way to connect marketing spend to closed loans.
This is a common pattern I see with HubSpot portals that have grown faster than their underlying architecture. The tools are there. The data isn’t.
The Challenge
The LOS integration was the root of most of the pain. It was pushing deal records into HubSpot with no pipeline or stage assigned, which meant those deals were invisible to every pipeline-based filter, every workflow trigger, and every report. They weren’t lost, exactly. They just weren’t where anyone could find them.
On top of that, the integration was firing sync triggers multiple times per loan. With no deduplication logic, every loan could generate multiple deal records. Contact, Deal, and LOS ownership were routinely out of sync, so any automation built on owner logic was effectively broken before it ran. There was no custom Loan object, which left no structural way to tie closed loans back to the campaigns that originated them. Lead routing existed in name only, with manual ownership changes overwriting the automated assignment rules. And two entities, the lender and its sister wholesale brand, were operating in the same portal without clear data separation.
Here’s how each of those was addressed.
LOS Integration Stabilization
The first order of business was getting LOS-created deals routed correctly. Because those deals had no pipeline assigned at record creation, there was nothing for pipeline-based workflow logic to grab onto. The fix was to identify LOS-created records by their record source field (“Integration”) instead, then rebuild the workflow logic around that identifier so every LOS-originated deal landed in the right pipeline and stage automatically.
The duplicate problem was escalated to the integration vendor with full documentation of the deduplication gap. While that was being addressed upstream, triage logic was built inside HubSpot to catch and suppress duplicates as they came in.
Custom Loan Object & Marketing Attribution Architecture
This was the structural piece the portal was missing. A custom Loan object was built to represent actual loan records, separate from deal pipeline stages. That separation created the foundation for real marketing attribution: loans associated with the campaigns that influenced them, traceable all the way back to originating marketing activity.
Association workflows connected Loans to Companies (using Contact as an intermediary hop), Deals to Companies, and Campaigns to Loans. A contact backfill workflow handled existing records that were missing the associations needed for the logic to fire going forward.
Lead Routing & Ownership Governance
Lead routing had been quietly breaking down. Manual record reassignments had started overwriting the automated assignment rules, which meant the automation everything else depended on was no longer reliable.
The routing workflows were documented, reinforced, and protected. More importantly, the ownership issue was raised with leadership as a pipeline integrity concern, not just an operational one. A governance framework now defines what loan officers can do within HubSpot (update and advance their own records) and what requires a different process (reassigning records across the system).
Pipeline Architecture. A single-pipeline model was established for the current rollout phase, with a deliberate plan to revisit segmentation as the team’s operational maturity grows. The Leads workflow architecture (Leads 1 / Leads 2) was built with a third track in scope to move LOS loan object matching into its own deal progression workflow.
Multi-Brand Configuration for the Wholesale Brand. The lender and its wholesale brand share a HubSpot portal but operate as distinct entities, with different branding, team structures, and reporting needs. The build included a separate brand configuration for the wholesale brand under the Additional Brand seat, keeping the shared CRM infrastructure intact without collapsing the two businesses into indistinguishable data.
Results
| Area | Outcome |
|---|---|
| LOS Integration | LOS-created deals route automatically to the correct pipeline and stage; duplicate suppression logic in place |
| Data Model | Custom Loan object with association workflows connecting Loans, Deals, Companies, and Campaigns |
| Marketing Attribution | Loan-to-campaign associations established, so closed loans can be traced to originating marketing activity |
| Lead Routing | Automated routing reinforced; ownership alignment restored across Contact, Deal, and LOS records |
| Governance | Permission structure and escalation path documented; manual override risks surfaced to leadership |
| Reporting Integrity | Ownership discipline restored, so LO performance and pipeline reports can be trusted |
| Multi-Brand | Wholesale brand configured as a distinct operational entity within the shared portal |
What Made This Engagement Different
Integration work is only as clean as the upstream data. The most technically interesting part of this engagement wasn’t the HubSpot build. It was diagnosing where HubSpot ended and the LOS began. When workflow logic is proven sound but results are still messy, the gap is almost always upstream. Knowing when to stop chasing a problem inside HubSpot and escalate it to the integration vendor is a judgment call that protects both the client’s time and the integrity of the build.
Ownership isn’t just an org chart question. When records started being reassigned manually, the effects rippled into automation logic, LOS sync, and loan officer visibility all at once. Raising it as a systems concern rather than a personnel issue is what got it addressed at the right level.
“Teajai has deep strategic expertise in HubSpot and a clear understanding of how the platform should be structured to support real, day-to-day business workflows. I trust her judgment completely and rely on her to guide foundational decisions, knowing that her approach prevents costly rework down the road.
What sets Teajai apart is her ability to combine strong technical HubSpot knowledge with genuine business acumen. She understands sales, marketing, and operational realities — not just the software itself — which makes her recommendations practical, scalable, and grounded in how teams actually operate.
She remains calm, methodical, and highly disciplined even when working through complex or high-stakes scenarios. Teajai consistently thinks several steps ahead, identifying potential issues early and helping avoid problems before they surface.
Teajai has been an exceptional HubSpot partner. She brings deep platform expertise, sound business judgment, and a clear, structured approach to implementation. She’s direct, thoughtful, and focused on building systems that work long-term — not just quick setups. I would absolutely recommend her to any team that wants HubSpot implemented correctly, strategically, and with the future in mind.”
Technologies & HubSpot Features
HubSpot Sales Hub Pro, HubSpot Marketing Hub Enterprise, HubSpot Custom Objects, Workflows & Branching Logic, Association Workflows, Lead Routing & Assignment Rules, Campaigns, Additional Brand, loan origination system (LOS) integration
WHAT WAS BUILT
- LOS integration routing based on record source, with automatic pipeline and stage assignment
- Duplicate triage and suppression logic, plus documented vendor escalation
- Custom Loan object, separate from deal pipeline stages
- Association workflows connecting Loans, Deals, Companies, and Campaigns
- Contact backfill workflow for existing records
- Reinforced lead routing workflows and an ownership governance framework
- Single-pipeline model with Leads 1 / Leads 2 workflow architecture
- Additional Brand configuration for the wholesale brand
KEY SKILLS
- HubSpot Custom Objects
- Workflow Automation & Branching Logic
- Third-Party Integration Diagnosis
- Data Model Architecture
- Multi-Brand Portal Configuration
- Lead Routing & Assignment Rules
- Marketing Attribution Framework
- CRM Governance & Permission Design
WHAT WAS BUILT
- LOS integration routing based on record source, with automatic pipeline and stage assignment
- Duplicate triage and suppression logic, plus documented vendor escalation
- Custom Loan object, separate from deal pipeline stages
- Association workflows connecting Loans, Deals, Companies, and Campaigns
- Contact backfill workflow for existing records
- Reinforced lead routing workflows and an ownership governance framework
- Single-pipeline model with Leads 1 / Leads 2 workflow architecture
- Additional Brand configuration for the wholesale brand
KEY SKILLS
- HubSpot Custom Objects
- Workflow Automation & Branching Logic
- Third-Party Integration Diagnosis
- Data Model Architecture
- Multi-Brand Portal Configuration
- Lead Routing & Assignment Rules
- Marketing Attribution Framework
- CRM Governance & Permission Design
Questions about this case
These are the questions I hear most often from mortgage and financial services companies exploring HubSpot.
Can HubSpot integrate with a loan origination system (LOS)?
Yes. HubSpot can integrate with most loan origination systems through API connections or middleware. The integration needs clear logic for how records are created, assigned, and synced. The most common failure point is records arriving in HubSpot without pipeline or stage data, which makes them invisible to workflow logic. Getting the integration architecture right from the start, or stabilizing an existing one, is the difference between a CRM that helps and one that creates noise.
What are HubSpot custom objects, and do mortgage companies need them?
Custom objects let you represent data in HubSpot that doesn’t fit neatly into Contacts, Companies, Deals, or Tickets. For a mortgage lender, that typically means Loan records, which are distinct from deal pipeline stages and need their own properties, associations, and reporting logic. Without a custom Loan object, you can’t reliably connect a closed loan back to the marketing activity that originated it. That gap turns attribution into guesswork.
Why does lead routing in HubSpot break down over time?
Usually because manual processes are overwriting automated ones. Automated routing depends on ownership fields staying in sync. Contact Owner, Deal Owner, and any third-party ownership fields all need to agree for downstream automation to work. When team members manually reassign records outside the defined process, that chain breaks and the automation misfires silently. The fix is part technical (reinforcing the routing logic) and part governance (documenting what can and can’t be done manually, and why it matters).
How do you set up HubSpot for two brands in the same portal?
HubSpot’s Additional Brand option lets you configure a second brand with its own email domain, branding assets, and team association within a shared portal. The CRM infrastructure stays unified, but the two brands operate distinctly for marketing and reporting. The key is making sure the data model clearly separates the two entities so reporting doesn’t collapse them into the same view.
Do I need a HubSpot Solutions Partner for a complex integration project?
For a project that involves third-party integrations, custom objects, multi-entity configuration, and governance, yes. The technical complexity is one part of it. The bigger part is having someone who can diagnose where a problem lives (inside HubSpot or upstream in the integration) and make judgment calls that protect the integrity of the build. A HubSpot Solutions Partner brings the credentials and the pattern recognition from real client engagements to do that work.