How RedWeek Replaced a Generic Deal Pipeline With 2 Custom HubSpot Objects to Run Its Timeshare Marketplace

A Generic CRM Model Was Working Against RedWeek's Own Business:

1. No Model for Listings or Bookings.

HubSpot's standard Deal pipeline could not represent RedWeek's actual marketplace transactions, and some transaction records had no corresponding booking record at all. This made deal-based reporting structurally unreliable for the business the system was supposed to track.

2. No Owner/Renter Segmentation.

Contacts were not separated by their role as timeshare owners versus renters. This closed off owner-specific campaigns such as notifying owners of underpriced "twin" listings or re-engaging past owners in high-demand locations.

3. Revenue Reporting Mixed With Non-Revenue Figures.

A standard Deal-amount field could not exclude owner payouts, refunds, and broker discounts from reported revenue. This left RedWeek without a reliable figure for actual company revenue versus pass-through payments.

4. Legacy Tooling Sized for a Different Company.

RedWeek inherited Marketo and Tealium licenses sized for its former parent company after the spinoff, including cross-domain tracking capability it no longer needed. This left the business paying for martech capacity that didn't match its own, smaller scale.

5. Service Data Disconnected From Sales and Marketing.

Customer service ran in Zendesk with no connection to HubSpot. This left RedWeek's team without a unified view of a customer across support, sales, and marketing touchpoints.

How Campaign Creators Built a Custom Object Model for RedWeek's Marketplace

Campaign Creators sequenced the engagement from discovery through a dedicated system design review before building anything, since RedWeek's two-sided marketplace model didn't match a standard HubSpot implementation.

Listings and Bookings as Two Custom Objects

RedWeek's actual transactions, timeshare listings and bookings, had no object built to represent them, and forcing them into the standard Deal pipeline had already produced transaction records with no corresponding booking record. Campaign Creators built two custom objects, Listings and Bookings, with properties specific to each: resort, unit type, pricing, and status flags including a "twin"/lowest-price indicator for Listings; check-in/out, guest, fees, and owner payout for Bookings, associated to Contacts in owner or renter roles and to Companies in broker or affiliate roles. RedWeek's sales, marketing, and service teams can now report on and automate around its actual marketplace activity, in place of a generic deal pipeline that never matched the business.

Zendesk Data Into HubSpot Without a Data Hub Subscription

RedWeek needed Zendesk ticket and contact data inside HubSpot without adding an Operations/Data Hub subscription at an estimated $800 a month. Campaign Creators built a one-way, API-based Zendesk-to-HubSpot sync for contacts and tickets in place of native field mapping, documented for RedWeek to activate once its team defines which custom ticket fields to map. RedWeek gains a path to unified service data without an added recurring hub cost, activated on its own timeline.
 

Marketo Lists Loaded Ahead of RedWeek’s Own Sync

RedWeek's existing owner and suppression data lived in Marketo, in lists sized for its former parent company, not its own marketplace. Campaign Creators migrated RedWeek's Marketo-sourced owner and suppression lists into HubSpot by CSV ahead of RedWeek's own larger, independently built contact sync. RedWeek's owner data was available inside the new Listings and Bookings model from go-live, without waiting on a longer-running sync project.

A Provisional Flag for Records With No Owner

A generic contact and deal property set did not capture what RedWeek's listings and bookings actually needed to track, including when a record had no assigned owner. Campaign Creators defined a property set specific to the Listings and Bookings objects, including an is_provisional flag identifying orphaned records without an assigned owner. RedWeek can now queue and report on orphaned listings and bookings separately from fully owned ones, so those records no longer disappear into an undifferentiated list.

Owner, Renter, Broker, and Affiliate Roles on Every Record

A single generic Contact record view gave every RedWeek team member the same information, no matter if that contact was an owner, renter, or broker. Campaign Creators configured conditional record cards, including an owner-specific card that only surfaces when a Contact's type is set to Owner, alongside association labels distinguishing owner, renter, broker, and affiliate relationships. RedWeek's team sees role-relevant information on each record without manually filtering for it.

Segmentation Built In for the Campaigns RedWeek Wants to Run

RedWeek's owner and renter campaigns, including notifying owners of underpriced "twin" listings and re-engaging past owners in high-demand locations, depended on segmentation the platform didn't have before this engagement. Campaign Creators built the owner/renter/broker segmentation these campaigns require directly into the Listings and Bookings model, so RedWeek's marketing team can build and launch them without a further data restructuring project. This groundwork, not a pre-built workflow library, was the deliverable at this stage of the engagement.

Training Across Campaigns, Workflows, HubDB, and Attribution

A new object model and three-hub deployment meant RedWeek's team needed to learn both the new structure and day-to-day platform mechanics. Campaign Creators delivered HubSpot training sessions, including one covering campaigns, email building, workflows, dynamic content, HubDB, and UTM/attribution mechanics, supplemented by an outside trainer brought in to extend training capacity. RedWeek's admin team can configure and extend the new system on its own, without depending on Campaign Creators for routine changes.

The Impact: A Data Model That Matches RedWeek's Own Marketplace

RedWeek's Listings and Bookings objects now give the business a structural record of its own marketplace, independent of any future reporting or campaign work built on top of it. Because the property set and associations were defined around RedWeek's actual roles, owner, renter, broker, and affiliate, the model can support new campaigns or reports without a structural rebuild. The standard-object pipeline RedWeek used before this engagement could not make that claim.

Solve Marketplace Data Modeling and Multi-Hub Onboarding With Campaign Creators

Businesses with a two-sided marketplace, a service-based transaction model, or data inherited from a parent company often find that HubSpot's standard Deal and Contact structure doesn't match what they actually sell. Closing that gap requires custom object design built around the real transaction, not a generic template, along with the integration and reporting work to make that model usable day to day.

Campaign Creators builds HubSpot implementations around a business's actual operating model, from custom object architecture to multi-hub Enterprise onboarding and the integrations that connect them.

Talk to a HubSpot expert to see how Campaign Creators can build a custom data model around your existing HubSpot tools.