Inside Pinkcube's enterprise onboarding and integration

Pinkcube sells promotional products in bulk across the Netherlands, at a volume and order complexity that a standard CRM object model does not describe. HubXpert onboarded all five hubs, integrated Stella Connect, and built a custom Sub Deal object to handle how orders actually work.
image 104 (3)

30%+

Sales and marketing team efficiency increase

7

Reporting dashboards built

5

HubSpot Hubs onboarded

1

Custom object built

BULK PROMOTIONAL PRODUCTS, SOLD AT VOLUME

About the client

Pinkcube is a Netherlands wholesale platform selling promotional items in bulk alongside clothing, accessories, electronics and home goods. The proposition is to make ordering promotional products as simple as possible, which in a bulk B2B context means handling order complexity on the seller's side rather than passing it to the buyer.

That complexity is the reason a standard CRM model does not fit. A promotional order is rarely one product at one price. It is a parent order with components that get specified, amended and approved separately, often through a system the buyer is already using.

Pinkcube came to the engagement with HubSpot in place but not structured. There was no centralized database, contacts and deals and tickets were difficult to manage, Stella Connect sat outside the portal holding customer feedback, and there was no reporting to measure team performance or company growth.

What You Will Learn

  • 1 When a custom object is the right answer rather than more properties
  • 2 How to bring a feedback platform into the CRM ticketing system
  • 3 What onboarding all five hubs changes about how a team works
ENTERPRISE LICENSING, NO STRUCTURE UNDERNEATH IT

The Challenges

Pinkcube had bought capability and not yet built anything with it. The gaps were structural rather than cosmetic, which is why the answer was onboarding rather than optimization.

  1. 1

    No centralized database.

    Customer data and feedback lived in different systems, with Stella Connect holding quality and feedback information that never reached the ticketing system.

  2. 2

    The portal was unstructured.

    Without a designed CRM structure, managing contacts, deals and tickets was difficult, and the difficulty grew with the order volume.

  3. 3

    Order complexity had nowhere to live.

    A bulk promotional order with separately managed components does not fit a standard deal record, and forcing it in produces data nobody can report on.

  4. 4

    No performance reporting.

    There was no way to track team performance or measure company growth, so management decisions were made without the numbers.

  5. 5

    No segmentation or lead management.

    Contacts and companies were not segmented, scored or routed, so lead handling depended on individual judgment rather than on a system.

"Before HubSpot, we were living kind of in chaos with Post-it notes. Every lead, every patient type, and every renewal had to be tracked manually, and our front desk was spending more time managing spreadsheets than focusing on patients."

Dr. Jean-Paul Leva
Dr. Jean-Paul Leva Board-Certified Cosmetic & General Surgeon, FACS
A STRUCTURE SHAPED TO HOW PINKCUBE SELLS

What We Built

Full onboarding across five hubs, a custom integration bringing feedback into the ticketing system, and a custom object built specifically for how promotional orders behave.

  1. 1

    Stella Connect integrated with HubSpot

    Customer feedback and quality management data flows into the portal with custom mapping, unifying the ticketing system rather than leaving feedback in a separate tool.

  2. 2

    A fully customized portal onboarding

    Record customization, custom property mapping and advanced workflows were built rather than configured from defaults, across all five hubs.

  3. 3

    Automated deal and ticket management

    Ticketing and deal stages run on custom workflows, which improved how both the sales and service teams work through volume.

  4. 4

    A custom Sub Deal object

    Built specifically to handle order processing, so the components of a bulk order are tracked as their own records rather than crammed into the parent deal.

  5. 5

    The Sub Deal object connected externally

    Clients can update specific properties from an external platform, so order changes reach the CRM from where the customer already is.

  6. 6

    Contact and company segmentation

    Custom lead scoring, lifecycle stages and lead allocation automation replaced manual handling.

  7. 7

    Optimized contact management

    Contact records were structured so leads and customers are managed consistently rather than according to whoever touched the record last.

  8. 8

    Seven reporting dashboards

    Campaign performance, sales metrics, team performance, lifecycle stage analysis, marketing insights, contact sources and conversion rates.

Our front desk team used to spend hours each week manually logging leads and chasing renewal calls. With HubSpot handling confirmations, reminders, and renewal nudges automatically, that time now goes straight into patient care. The dashboards also mean we stop guessing which campaigns are actually working.

Dr. Jean-Paul Leva Board-Certified Cosmetic & General Surgeon, FACS
Dr. Jean-Paul Leva
STRUCTURE FIRST, THEN THE OBJECT THAT DOES NOT FIT

How We Got There

The portal had to be structured before a custom object could be designed against it, and the object had to exist before the reporting could describe an order accurately.

Phase 1

Discovery

Mapped the existing portal, the order process and where Stella Connect data was sitting outside it.

Phase 2

Portal onboarding

Built the customized HubSpot setup across all five hubs with record customization and property mapping.

Phase 3

Stella Connect integration

Integrated Stella Connect with custom data mapping to unify the ticketing system.

Phase 4

Custom object

Designed and built the Sub Deal object for order processing, and connected it to the external platform.

Phase 5

Automation and segmentation

Built deal and ticket workflows, lead scoring, lifecycle stages and lead allocation automation.

Phase 6

Reporting

Built seven dashboards across campaign, sales, team, lifecycle, marketing, source and conversion metrics.

A PORTAL THAT MATCHES THE ORDER MODEL

The Outcomes

Pinkcube now runs on a structured portal where an order is represented the way it actually works, feedback reaches the ticketing system, and leadership has reporting across seven views. The engagement is ongoing.

30%+

Sales and marketing team efficiency increase

7

Reporting dashboards built

5

HubSpot Hubs onboarded

1

Custom object built

Sales and marketing efficiency increased by over 30%. Automation and CRM structure removed the manual handling that grows with order volume.

Order complexity is modeled properly. The custom Sub Deal object holds order components as their own records, which makes both processing and reporting accurate.

Customers update orders from where they already are. The Sub Deal object connects to an external platform, so property changes reach HubSpot without a manual step.

Feedback reaches the ticketing system. Stella Connect data flows into the portal, so quality management informs support rather than sitting beside it.

Leads are scored, staged and routed automatically. Segmentation replaced individual judgment with a consistent system.

Seven dashboards support the decisions. Campaign, sales, team, lifecycle, marketing, source and conversion reporting give leadership a full read.

Before

Manual
  • Stella Connect feedback outside the ticketing system
  • An unstructured portal across five licensed hubs
  • Bulk order complexity forced into a standard deal
  • No segmentation, scoring or lead routing
  • No team performance or growth reporting
  • Order changes entered manually

After

Automatic
  • Feedback integrated into a unified ticketing system
  • A customized portal with mapped properties and workflows
  • A custom Sub Deal object built for order processing
  • Lead scoring, lifecycle stages and allocation automation
  • Seven dashboards across the business
  • Customers updating order properties from an external platform

"We enjoy working with HubSpot because they have an allround team. They are communicative and helpful. Their strength lies in execution, creating content, APIs, workflows, they can do it all. Give them an assignment and they start flying. Sometimes this eagerness makes them start working when they don't exactly understand what they need to do yet. Most likely due to cultural differences."

L. Leijten-Deppenbroek via HubSpot Review
HubSpot Logo-2 5.0 (26 reviews)
1766518370646
WHAT E-COMMERCE TEAMS ASK ABOUT CUSTOM OBJECTS

Frequently asked questions

  • When the thing you are tracking has its own lifecycle and its own properties and there can be several of them per deal. Pinkcube's order components met all three, which is why Sub Deal exists rather than another twenty properties.

  • Yes. Pinkcube's Sub Deal object is connected to an external platform so clients update specific properties from the system they already use, and the change reaches the portal.

  • Because quality management data is only useful next to the ticket it relates to. Keeping Stella Connect separate meant support handled the case without the feedback that explained it.

  • Pinkcube runs Marketing Hub Enterprise with Sales, Service, Operations and CMS Hub Professional. The custom object and cross-team reporting depend on that breadth.

  • Ongoing. Order models and reporting requirements change as volume grows, so the engagement continues rather than closing at handover.

bOOK CONSULTATION

Want a Custom

Quote?

If Meditech is managing your clinical operations but your teams lack visibility, automation, or connected reporting, it may be time to integrate! A structured Meditech and HubSpot integration can help align patient data, engagement, and revenue tracking in one connected ecosystem. ?

Icon-Apr-08-2026-10-02-31-8097-AM Takes 30 minutes
Icon-Apr-08-2026-10-02-31-8097-AM Takes 30 minutes
Ratul-Rahman