How to Model SaaS Subscriptions, Licenses, and Active Users

One SaaS account can include several distinct records: the customer, the subscription, the licensed capacity, and the people actively using the product. A practical model for HubSpot custom objects for SaaS companies keeps these records separate and associates each with the relevant company, contact, or deal. Use standard objects for core customer and sales records, and custom objects when subscription, license, or usage data needs its own structure.

That separation makes it easier to see what a customer purchased, how access is provisioned, and whether product activity aligns with renewal or expansion conversations. It also prevents teams from treating a subscription, a license, and an active user as interchangeable measures.

This guide explains how to define each record, choose between standard and custom objects, connect related data, and plan integrations with external systems. You’ll also learn how to structure associations and properties so sales, marketing, and customer-facing teams can work from a coherent account view.

Custom objects for SaaS subscriptions, licenses, and active users

A practical model of HubSpot custom objects for SaaS companies separates subscription, license, and user activity into records that support distinct decisions. Custom-object properties can feed reports, including pie, bar, and area charts, while workflows can respond to record or property changes. Plan for setup requirements: custom objects require API access and appropriate permissions, and each HubSpot portal can have up to 10 custom objects.

1. Map Subscriptions, Licenses, and Active Users

   Create a separate record for each SaaS concept that needs its own properties and reporting. For example, associate a subscription with a company and track its plan and status. Represent licensed capacity separately from active users, associating those records with the relevant company or contacts. This structure helps sales and marketing distinguish purchased access from product activity instead of combining different measures in one record.

2. Track Subscriptions and Recurring Revenue

   Create a payment schedules object when billing activity needs its own timeline. Add properties for billing frequency, payment amount and method, payment status, next payment date, and failed payment attempts. These fields help teams organize recurring revenue activity and identify records that need attention. Keep subscription terms separate from payment events: one subscription may have multiple scheduled payments, each with its own status and date.

3. Use associations to link each custom record with standard CRM records, such as companies, contacts, deals, or tickets. When configuring HubSpot custom objects for SaaS companies, choose clear property names for plan, license status, and active-user count. Custom objects support properties, views, pipelines, automations, reports, and associations. Define each around a specific operational or reporting need.
4. Set workflow enrollment criteria around meaningful events, such as a payment status changing or a subscription record being created. Workflows can trigger when custom-object records are created, updated, or deleted, or when selected properties change. Actions can include sending an email or notifying CRM users. Plan custom-object setup carefully, including how records, associations, and properties will be managed if an object type is removed.

Custom-object use cases across business types

Choose a custom object when a business record needs its own properties, relationships, and reporting. The examples below show how to connect CRM records with the operational details teams need to act on.

1. Model a loan account when a fintech team needs to organize repayment details separately from a customer profile. Create properties for loan amount, interest rate, repayment schedule, outstanding balance, and payment history. Associate each loan record with the relevant contact or company so account teams can review financial activity alongside customer records.
2. Represent financial goals as individual records when progress should drive personalized communication. For example, a fintech workflow can trigger congratulatory emails when a client reaches 25%, 50%, or 100% of a goal. Store each goal’s target and progress on its record, then use the milestone as an enrollment criterion.
3. Organize physical products with an inventory, parts, or equipment object when those records need dedicated properties. For example, a manufacturer can represent each machine model as a custom object and associate it with deal records. This relationship supports segmentation and reporting on deals involving particular models, without embedding product details in every deal.
4. Track services delivered as projects or programs when an organization needs a delivery record beyond the original sale. Associate each program record with its related company and deal, then define properties for its status and delivery details. This structure helps operations teams connect service activity to the customer relationship and sales context.
5. Represent trade shows and other appearances as records when teams need to organize event information in HubSpot. Associate each appearance with related companies, contacts, or deals to preserve those relationships. Use these records to structure event follow-up and reporting rather than leaving event context in disconnected notes or emails.

HubSpot custom objects can also be used to organize services delivered similarly to a project or program. The object can represent that service-delivery activity in a project-like or program-like form, matching the record type to the kind of work being organized.

An individual machine model can likewise be represented by a HubSpot custom object and associated with deal records. This association helps teams identify, segment, and report on related deals, using the model as a reference for grouping those records.

Differences between custom and standard HubSpot objects

Use standard objects for core CRM records and custom objects for distinct business entities. Both support structured records and relationships, while custom objects provide flexibility for more complex processes.

1. Start by assigning each record type to the right platform structure. HubSpot’s standard CRM includes contacts, companies, deals, and tickets. Custom objects work like standard objects but represent separate entities, such as SaaS subscriptions or licenses, when those records need their own properties and workflows.

2. Define Properties and Associations

   Define the custom object through the API, with appropriate permissions and developer involvement. Set its properties around the information teams need to manage, such as license status or subscription tier. Configure associations with standard objects during setup, then map how each custom record relates to a company, contact, or deal. Custom objects can associate with standard objects, not with other custom objects.

3. Let the difference guide your choice. A deal tracks a sales opportunity, while a custom subscription object holds subscription-specific details. Standard objects keep core CRM processes recognizable; custom objects provide dedicated structure when adding properties to a standard record would blur distinct processes. Tie each object to a clear reporting or operational need.

4. Check Record and Association Limits

   Plan the object model around HubSpot’s limit of up to 10 custom objects per portal. Associations can connect custom-object records with standard CRM objects, including contacts and deals, and those relationships are bidirectional. This supports viewing related records from either side, but does not enable custom-to-custom associations.

5. Before implementing the model, map each proposed object to its properties, associations, and workflows. Creating custom objects requires API access and appropriate permissions, so include technical setup in the implementation plan. Avoid creating separate objects for details that fit naturally into an existing standard record. Reserve custom-object flexibility for entities with distinct lifecycles or reporting needs.

HubSpot’s 2025 standard-object renaming feature was described as applying initially to Contacts, Companies, Deals, and Tickets. Renaming standard objects in HubSpot does not alter the underlying data structure, but affects views, pipelines, dashboards, and automations. This separates changes to object names from changes to the underlying model.

API and external system integrations

Connect HubSpot custom objects to external tools through the HubSpot API. A deliberate field-mapping strategy helps SaaS teams keep records consistent across systems.

1. Identify which system owns each data point before defining an integration. For example, decide whether a billing platform or HubSpot maintains subscription status, payment details, and renewal dates. Assigning ownership for each field reduces conflicting updates and gives sales, marketing, and operations teams a consistent basis for action.
2. Map external fields to matching HubSpot properties before transferring records. Use a subscription identifier to connect the same subscription across systems, and align field formats for values such as status or next payment date. Clear mappings help the API create or update the intended record instead of generating disconnected duplicates.
3. Define the direction and timing of each data flow. For example, a product system might send active-user changes to HubSpot, while HubSpot workflows respond to relevant property updates. Specify which system updates each field, and avoid letting two systems overwrite the same value without a clear rule.
4. Test representative records before expanding an integration. Include a new subscription, a changed license status, and a record with missing optional fields. Confirm that HubSpot receives the intended properties and associations, then review how the records appear to users. Testing can reveal mapping errors before they affect broader CRM operations.
5. Use connected data to support reporting and coordinated follow-up. For instance, teams can organize subscription records alongside contacts and companies, then use HubSpot workflows to respond to defined property changes. Align reporting fields with the business question, such as tracking active subscriptions separately from licensed capacity.

For support aligning CRM structure and connected data, explore HubSpot CRM implementation.

Stratagon: HubSpot CRM Implementation

Stratagon helps SaaS teams shape HubSpot CRM around subscription, license, and user data. Turn to its HubSpot CRM Implementation when standard records do not reflect how commercial and customer-facing teams manage account relationships, or when custom objects need to connect with external systems.

The work aligns CRM structure with business processes by defining record relationships, organizing properties, and connecting workflows to practical reporting needs. This gives sales, marketing, and operations a shared framework for using customer data. For broader system change, digital transformation can help align technology and organizational processes.

If your SaaS data model needs clearer structure in HubSpot, contact Stratagon to discuss your implementation needs.

Build a data model that can evolve

Your SaaS data model should support decisions as products, customer segments, and internal processes change. A well-designed approach to HubSpot custom objects for SaaS companies connects CRM structure with how teams qualify accounts, support adoption, and plan growth. Treat the model as an operating framework: review whether its records still reflect the business, whether teams use data consistently, and whether new processes call for adjustments.

Stratagon’s HubSpot CRM Implementation can help align your structure with commercial workflows. Digital transformation can address broader process and technology alignment, while Account-Based Marketing (ABM) can connect account strategy with customer data. Take the next step with a focused conversation about your setup and where the model needs to support better decisions.

Contact Stratagon to discuss your HubSpot setup, and move forward with a CRM structure built around your business.

Frequently Asked Questions

How do custom objects differ from standard objects, custom properties, and associated objects in HubSpot?

A custom object creates a distinct record type, while a custom property adds a field to an existing record. Standard objects are HubSpot’s built-in record types, such as contacts, companies, deals, and tickets. An associated object is a separate record linked to another record, such as a subscription associated with a company. For example, store a renewal date as a property or create a subscription record to hold broader details.