Skip to content

How we built a custom service catalogue in HubSpot using UI extensions and automation

By Kiara Robinson on Mar 17, 2026
Narrate this article
How we built a custom service catalogue in HubSpot using UI extensions and automation
5:11

Professional services organisations rarely sell a single, simple product. They sell bundled services, advisory engagements, and structured fee arrangements that span multiple business units and timelines.

For our client, one of Australia’s largest financial advisory and accounting firms, this complexity created a structural challenge inside HubSpot:

  • Hundreds of service SKUs
  • Multiple service lines and families
  • Different billing models (upfront vs ongoing fees)
  • Operational tasks that needed to trigger automatically when services were sold

Standard CRM product libraries can struggle when organisations need to represent hierarchical service structures rather than simple products.

To solve this, Engaging.io designed and implemented a custom Service Catalog architecture using HubSpot UI Extensions and automation workflows. The result was a system that allowed our client to manage complex service offerings while maintaining accurate forecasting, operational task creation, and revenue reporting.

 

Building the custom service catalogue using HubSpot UI extensions

Using HubSpot UI Extensions, Engaging.io created a custom interface embedded directly within HubSpot records. This extension allowed our clients teams to select services through a structured service hierarchy rather than a flat product list.

The catalogue structure included:

  • Service line
  • Service family
  • Individual service SKU

This hierarchy allowed services to be organised in a way that mirrored how our client actually delivers its advisory offerings. From a user perspective, the experience looked like a structured catalogue rather than a generic CRM product selector.

The interface enabled teams to:

  • Browse services by advisory category
  • Select services aligned with the firm's organisational structure
  • Maintain consistency across offices and teams
  • Reduce errors in service selection

The system effectively became a custom service configuration interface inside HubSpot.

Automating operational workflows from service selection

The catalogue was only one part of the solution, the second component was automation tied to each service selection. When a service is added to a deal, the system automatically generates the operational activities required to deliver it.

These activities are created using the HubSpot Ticket object, which acts as a structured operational workflow. This automation creates:

  • Delivery tasks
  • Operational milestones
  • Service tracking records
  • Forecast dates tied to service completion

This approach ensures that selling a service automatically initiates the operational workflow required to deliver it. One of the biggest benefits of this architecture is the connection between service delivery and financial forecasting.

Each service in the catalogue is linked to revenue structures, so when a service is selected the automation populates key revenue tracking properties, allowing leadership to track the full lifecycle of a service engagement.

A CRM architecture designed for advisory firms

By combining UI extensions, automation workflows, and structured revenue tracking, our client’s HubSpot implementation introduced a scalable model for professional services CRM management. The system achieved several key outcomes:

  • Structured service catalogue aligned with the firm’s advisory model
  • Automated operational task creation for every service sold
  • Accurate revenue forecasting tied to delivery milestones
  • Improved reporting across fee structures and service completion

This architecture transforms HubSpot from a simple CRM into a service operations platform for advisory organisations.

 

Engineering CRM systems for real-world business models

Many professional services organisations struggle with a structural gap between sales systems and operational delivery systems. Deals are tracked in the CRM, but the work itself often lives in separate project tools, spreadsheets, or internal processes. This disconnect limits forecasting accuracy and creates manual coordination between teams.

For our client, the custom Service Catalogue architecture solved this by embedding service selection, operational workflows, and revenue tracking directly inside HubSpot. When a service is added, automation creates the associated delivery activities using the Ticket object, while key forecasting and billing milestones are populated automatically.

This creates a unified system where sales triggers delivery, delivery updates forecasting, and forecasting drives reporting. The result is improved operational visibility, reduced manual handoffs, and clearer insight into the full lifecycle of each service engagement.

More broadly, this implementation demonstrates how CRM architecture can be adapted to reflect the realities of complex advisory businesses. By combining UI extensions, automation, and structured service hierarchies, the system gives our client a scalable way to manage hundreds of advisory services while maintaining operational clarity and accurate revenue reporting.

 

Get in touch, We love to talk