From 99 Pipelines to 6: How One Events Company Made HubSpot Work for a Multi-Sided Conference Business

A National Events company that produces conferences and trade shows, reached out to HarvestROI for help. They had hit the 99 pipeline maximum with HubSpot and did not know where to go from there. 

They run dozens of conferences a year. HubSpot was supposed to be the system holding it all together, however, it was not architected properly to do this.

HarvestROI helped tear down a bloated, fragmented HubSpot instance and rebuild it around a single organizing principle: the Conference. By re-architecting the data model, consolidating 99 pipelines, and building purpose-built systems for sponsors, speakers, and attendees, we delivered a platform that finally matched the complexity of the business it was supposed to support.

About The Client

This is an events organization that produces hundreds of conferences and trade shows across America. Each conference focuses on a specific theme, from emerging technologies like AI in gaming, to regulated industries like cannabis and hemp, to healthcare and community development. Their events bring together leaders, enterprises, and industry partners to share knowledge, explore new opportunities, and drive economic industry growth.

Across these events, the company operates a multi-sided model with three distinct audiences that constantly overlap and interweave:

• Attendees participate to learn, network, and explore solutions
• Sponsors fund and promote their products and services to a highly targeted audience
• Speakers deliver the content and insights that drive the value of each event

They run a portfolio of recurring conferences each year with variations in topics, locations, and audiences. That requires consistent coordination across sales, marketing, and event operations. Their current system setup was not providing it.

The Challenge: 99 Pipelines and No Visibility

Before engaging HarvestROI, the events company had a HubSpot portal that had grown organically without architecture. The team was creating new pipelines for every single conference to manage each key process. The result: 99 deal pipelines. That is the maximum limit HubSpot allows. They had literally run out of room to scale.

But the pipeline explosion was a symptom, not the root cause. The real dysfunction ran deeper.

1. Three Audiences, Zero Connected Processes

This National Events Company manages attendees, sponsors, and speakers, and those audiences overlap constantly. A sponsor might also be a speaker. A speaker gets a free attendee ticket. An attendee purchase might cover five people whose names are not yet known. 

Each of these audience journeys was handled through a different combination of spreadsheets, email chains, and manual data entry. The processes were disconnected, inconsistent, and rarely made it into HubSpot at all.

One of our issues is if I want the director of marketing for all the casinos and I want that title, some salespeople will put it in as, you know, 'Dir. of marketing', or they'll spell 'Director of Marketing', they'll do 'Marketing Director'

- CEO

2. E-Commerce Without Follow-Through

Attendee tickets were purchased online through WooCommerce, creating HubSpot e-commerce deals. But the process stopped there. Tickets were often bought without knowing the names of the actual attendees, requiring manual outreach to collect badge information. No automation. No tracking. Just revenue records with no operational value behind them.

3. A Conference Object That Did Nothing

A Conference custom object existed in HubSpot, but it was a vanity record. Minimal associations to deals, attendees, or speakers. Not used in workflows, automation, or reporting. No standardized naming or structure. Many conferences were missing or duplicated. The object that should have been the backbone of the system was decorative, leaving their team to manage all events manually.

When we are doing four shows at one time, which is about a thousand attendees. There's just too much that is left to one person.

- CEO 

4. Reporting Was Impossible

With no connected data model, reliable reporting across revenue, attendance, or speaker status simply did not exist. Leadership had no centralized view of how any given conference was performing.

The net effect: high effort, low visibility, and no scalable way to grow events or revenue.

The Solution: Build Around the Conference

Instead of trying to patch the existing setup, we re-architected the entire system around how the business actually operates.

The strategy had four pillars: anchor everything to a central Conference object, separate each audience into its own purpose-built process, standardize pipelines and automation, and integrate website data into structured workflows.

Every design decision started with one question: does this connect back to a Conference?

Technical Architecture: The Conference-Centered Model

1. The Conference Object: From Vanity Record to Operational Backbone

We rebuilt the Conference object from the ground up. Every conference now carries a standardized Conference Code (e.g., SEC 2023, NAED 2026) that functions as the system backbone for attribution, automation, and reporting.

Each Conference record stores operational data: dates, location, city, state, and year. It is fully associated to sponsor deals, attendee records, and speaker tickets. Custom views for sponsors, attendees, and speakers are built directly into the Conference object, so it serves as a true source of truth for show managers.

The Conference Code is referenced across workflows, reporting, and segmentation. It is the connective tissue for the entire system.

2. Pipeline Consolidation: From 99 to a Structured Model

We replaced the 99 pipeline sprawl with a clean, purpose-built structure:

• Sponsor Deal Pipeline for contracted sponsorships
• Attendee Deal Pipeline for individual attendee tracking
• E-Commerce Deal Pipeline for WooCommerce purchases
• Archive Deal Pipeline to preserve historical data from sunset pipelines

On the lead side, we built dedicated Lead Pipelines for Sponsors, Speakers, and Attendees. These function as cold-call lists, feeding confirmed interest directly into the appropriate deal or ticket pipeline through automation.

3. The Sponsor Sales Engine

Sponsorship sales previously lived in PDFs, email threads, and internal knowledge. No standardized pipeline. No required data collection. No connection between the sale and the deliverables it included.

We built a full end-to-end process. The Sponsor Lead Pipeline creates a structured call list. When a lead hits "Confirmed Interest," a deal is automatically created in the Sponsor Deal Pipeline.

At close, required fields capture the Conference Code, sponsorship level, number of included attendees, and speaking slots. Then automation takes over:

• For each included attendee, a placeholder deal is created in the Attendee Deal Pipeline. Sixty days before the show, automation kicks in to collect registration information and confirm badges.
• For each included speaking opportunity, a placeholder ticket is created in the Speaker Pipeline, triggering the speaker management workflow.

The sale and every deliverable it includes are now connected, tracked, and automated.

4. The Speaker Management System

Speaker data previously lived nowhere near HubSpot. Spreadsheets. Email chains. Internal knowledge. That made it impossible to automate and impossible to report on.

We built the speaker process on HubSpot's Ticket pipeline (Service Hub). Each ticket represents one speaking engagement and tracks the speaker from initial interest through asset collection, panel confirmation, and performance feedback.

Speakers enter the system through two paths: invited speakers flow through the Lead Pipeline, while purchased speaking roles are automatically created when a sponsor deal closes. Either way, the same structured process applies.

The system automatically contacts speakers to collect bios, headshots, and presentation assets. It prompts the speaker management team to review and approve those assets. It tracks status by conference. And it catalogs speaker performance feedback so the team knows who to invite back.

No more fake $0 deals to track speakers. No more missing assets discovered the week before a conference.

5. Attendee and E-Commerce Automation

The WooCommerce integration previously stopped at creating an e-commerce deal. A revenue record existed, but no operational process followed.

We rebuilt the attendee process to handle the core complexity of event ticketing: one purchase often covers multiple attendees, and the buyer rarely knows who all those attendees will be at the time of purchase.

Now, each e-commerce deal triggers the creation of individual attendee deals, one per ticket purchased. Each attendee gets a unique Attendee ID. Post-purchase, the system automatically sends registration forms to collect names, emails, and badge details. Badge confirmation emails reduce reprints. The entire manual data entry process is eliminated.

This structure also enables post-event tracking. Attendee records can be updated after the show to distinguish confirmed attendees from no-shows, building a historical attendance database that did not previously exist.

The Impact

Operationally, the transformation eliminated massive amounts of manual work. Standardized processes now run consistently across all events. Every persona, sponsor, speaker, and attendee, lives in one centralized system. Outdated and incorrectly configured custom objects were removed.

Established New HubSpot Operations to Manage 1000+ Attendees at a Time

For data and reporting, revenue tracking by conference is now reliable. Pipeline, attendee, and speaker visibility exists where it previously did not. The Lead Pipeline structure provides a net-new prospecting engine for sponsors, speakers, and attendees. The foundation for forecasting and growth planning is in place.

Instant Insights with Reporting Now Based Around 1 Unique Conference ID

For scalability, the former setup had hit HubSpot's 99-pipeline ceiling. The system now supports multiple events, multiple personas, and repeatable workflows with room to grow. They are no longer boxed in by constraints of a portal that was never architected for them.

From 99 Pipelines to 6 Pipelines

Other Needs Supported

The rebuild established the foundation. After setting the foundation, we move to optimization. We helped with:  

• Post-event surveys for attendees, sponsors, and speakers
• Pre-event engagement automation tailored by persona
• Deeper WooCommerce integration improvements
• Advanced segmentation and personalization using the data now stored on Conference records
• Ongoing RevOps iteration as the event portfolio scales

The portal that once maxed out at 99 pipelines with no visibility is now a structured, scalable system built around how the company actually runs its business. The data connects. The processes automate. The reporting works. And the team can focus on growing the events instead of fighting the CRM.

When times are tough for your HubSpot portal, whether it be 99 pipelines or an exorbitant amount of bad data, were happy to help. Contact us to build a foundation that actually matches the complexity of your business.