Consolidating 60+ Fragmented Tools into an Event-Driven CRM for a $500M+ Telecom Provider
A $500M+ telecom provider was losing data across 60+ fragmented tools during their fiber network transition. A standalone data lake would have cost $35,000. We skipped it. We architected an event-driven HubSpot CRM instead. Using custom "FiberHood" objects and eLation ERP account numbers as unique keys, we unified ISP and MSP data with no manual double-entry.
Executive Summary
Context
A regional ISP and MSP ran 60+ non-integrated tools. During their transition from legacy copper to fiber networks, they faced massive data loss and manual entry errors.
What We Built
We engineered a hub-and-spoke CRM architecture using custom "Address" and "Account" objects to bridge ISP and MSP workflows.
Tech Stack
- Salesforce, Trello, eLation, ConnectWise, HubSpot Sales/Service Enterprise, Operations Hub.
Not a fit for companies without a centralized ERP with stable API endpoints. Same if geographical serviceability isn't a sales driver.
The Challenge
Reps and billing staff were drowning in "swivel-chair" operations. A rep would close a deal in Salesforce, track the task in Trello, and then hope the billing team manually entered the correct data into eLation. Because these systems didn't talk to each other, the marketing team had no way to know which neighborhoods were actually fiber-ready. Early on, the obvious solution, a standalone data lake, was priced at $35,000 just for the infrastructure. We needed a 95% data match across systems without that overhead.
Our Approach
We pivoted to an event-driven architecture that used HubSpot as the engagement layer and eLation as the system of record. We identified that eLation account numbers had to be the "source of truth" to prevent record duplication. We built a custom "FiberHood" object, which meant we stopped treating addresses as static text fields. Instead, they became targetable entities. When eLation flagged a new address as serviceable, it automatically triggered the marketing automation. The plan wasn't perfect from day one. We had to iterate on the entity map several times so the many-to-many relationship between accounts and serviceable locations wouldn't break standard CRM reporting.
Impact
Operational Tool Consolidation
We moved the entire sales and service operation off Salesforce and Trello. That saved on seat costs. It also cut fragmentation. Before, 10% of deals stalled due to missing task updates.
$35,000 Data Lake Cost Avoided
Automated Proximity Marketing
The "FiberHood" custom object let the marketing team launch geo-targeted campaigns the moment a network build-out finished. They stopped waiting on manual address lists. Instead, they started triggering ads from live serviceability data.
Unified Identity Management
We used eLation account numbers as the unique key across HubSpot and ConnectWise. That removed the "Account ID" mismatch errors. Sales reps now see a single, accurate view of what a customer pays for, across both ISP and MSP services.
We built a custom "Address" object specifically for serviceable locations. It supports a many-to-one association, so multiple accounts or deals can link to a single geographic service point. That enables spatial reporting.
eLation Account Number is the architecture's unique identifier. We used Operations Hub to format these keys consistently. That prevented the common "dash vs. no-dash" duplication issues found in legacy telecom data.
Highly fragmented tech stacks cause massive data loss and require expensive manual double-entry. Bypassing a heavy data lake requirement, this event-driven HubSpot CRM architecture unifies inputs from over 60 tools. Using custom entity mapping, the system cleanly associates complex account structures without risking data overwrites or requiring constant developer maintenance.
FAQ
A standard text field can't hold a many-to-many relationship. In a fiber buildout, one serviceable location ties to multiple accounts and deals. We built a custom "FiberHood" address object instead, so locations became targetable entities rather than static text. When the ERP flags an address as serviceable, that object can trigger marketing automation and support spatial reporting, something a property field could never carry.
