Ask the community

In certain pricing or contract scenarios, it's necessary to restrict selected start or end dates so they always align with the first day of a calendar month. This approach ensures consistency across billing cycles and simplifies downstream logic tied to monthly intervals. The following method explains how to configure this behavior using calculated date logic. How to Set Up the Base Date and User Input Begin by creating two date questions:One date question that acts as the base date. This should always be a fixed value—such as January 1, 2025—and represents the anchor point for all date calculations.

Some customers work with Distributors who require different SKU codes depending on specific product configurations. These variations typically relate to factors such as package type or environment. For example, in Keepit, the original SKU may change based on the selected package type. In AvePoint, it may depend on the environment.To handle these scenarios effectively, you can dynamically modify or extend the SKU using proposal attributes that concatenate additional data to the base SKU. How to Configure SKU Extensions First, create playbook questions that return the relevant extension values based on user selections. For instance:A question for package type that outputs a specific string (e.g., -ADV or -STD).

In certain business scenarios, clients may need to extract a value only from the last system opened in a Multi-System configuration. Since the number of systems opened is not known in advance, hard-coding logic for each instance is not feasible.This method allows you to dynamically identify and fetch the value from the last opened system. How to Create a Counter for System TrackingAdd a numeric question inside the Multi-System group. Set its default value to 1. This question will act as a system counter and will be used in an aggregate function (SUM) to determine the total number of systems opened at runtime.How to Use a Proposal Attribute to Identify the Last System To isolate the value from the last system, use conditional logic with the FLOOR() function. Example scenario:Assume the following values from each system:System 1: 100 System 2: 20

Exclude filters are a powerful feature used to dynamically remove or restrict options based on previous user input or existing customer data. Below are three common use cases that show how to implement exclude filters effectively in subscription flows, inclusion logic, and product selection. How to Remove Items from a Text List Based on Existing SubscriptionsUse Case 1: Subscriptions This scenario involves preventing users from selecting a product they already own in a new subscription quote. For example, if a client already has Product A from a previous subscription, it should not appear in the current selection list. InstructionsCreate a dedicated question group for exclude logic.

By default, subscription data in HubSpot is often filtered based solely on status. However, certain business use cases require fetching not only active subscriptions but also those that have expired within the past three months. This article outlines how to achieve that using a custom field and a structured query. How to Calculate Time Since Subscription End Date in HubSpot To begin, create a custom calculated property in HubSpot that determines the time difference between the current date and the subscription’s end date. This property will allow you to filter subscriptions based on how long ago they expired.

In some configurations, it's necessary to identify the latest date entered across multiple entries in a repeatable question group. This is useful in workflows where you need to calculate end dates, trigger validations, or control the visibility of sections based on the most recent event or timeline.The method below outlines how to calculate the maximum date using standard functions and formula questions. How to Configure the Max Date Logic In a regular question group, create a base date question. This date will serve as the reference point for all calculations. 

One common use case when working with multiple repeatable question groups is when you want a SKU in one group to pull a value, such as quantity, from a specific matching row in another repeatable group. This configuration allows you to tie product selections directly to user-defined attributes or inputs. How to Reference a Specific Row from Another Group To pull a value (e.g., quantity) from a matching row in another repeatable group, the assignment rule must include a comparison that matches a field in both groups. This ensures the value is only pulled when the context aligns—such as matching sites or environments. Example Scenario Let’s assume the following:In Question Group 1, the user defines a list of sites with quantities for each.Question_group_1Site_List Quantity  Site 1

In some use cases, clients want to sync the start date of a selected period from a Multi-System question group directly to an opportunity field in the CRM. For this scenario, we’ll assume there can be a maximum of three periods, and the user selects which period to sync.  How to Capture the Selected Period’s Start Date To implement this logic:Set up a global question outside the Multi-System group. This will determine which period (e.g., Period 1, Period 2, or Period 3) should be used for syncing. Inside the Multi-System group, ensure you have a Start Date question for each row (period).    

Scenario AtlasIQ, a SaaS company offering AI infrastructure tools, often builds proposals with multiple pricing packages—such as “Starter,” “Growth,” and “Enterprise”—using DealHub’s Multi-System functionality. While this gives customers flexibility, it created operational friction. Buyers would verbally choose one offer, but sales reps then had to manually remove the unselected systems and products from Salesforce, risking errors and slowing down approvals.To streamline this, AtlasIQ configured a dropdown menu in the DealRoom that lets buyers select the offer they want. Behind the scenes, DealHub converts that selection into a numeric value, which is used to flag which quote system to keep. All other sys

ScenarioOptiCloud, a mid-size SaaS company offering customizable cloud analytics, handles complex proposals with multiple SKUs, implementation services, and region-specific legal clauses. Their Sales Ops team was struggling with:Inconsistent formatting in output documents Manual insertion of legal clauses and billing tables Lack of dynamic fields (e.g., product-specific T&Cs, pricing tables, renewal dates) Inability to quickly preview or adjust order forms on a per-client basisTo address this, they standardized on DealHub’s Document and Sub-Document Templates functionality to automate and professionalize

Scenario DeployLogic, a SaaS provider offering modular implementation and onboarding services, often sells tailored solution packages to enterprise clients. These packages include multiple components like:Integration Setup Data Migration Training Programs Custom Feature DevelopmentEach of these services has its own start and end date, depending on resource availability, client readiness, and deployment sequencing. The Requirements

Scenario TechNest, a mid-market SaaS provider of enterprise collaboration tools, operates a multi-tier sales model:Sales Reps can offer limited discounts. Managers and VPs can approve deeper discounts for strategic accounts.However, rather than approving based on a discount percentage, TechNest sets absolute floor prices per SKU.

Scenario InsightFlow, a SaaS company, provides a flexible analytics platform with modular features. Customers can choose from a list of add-ons such as:Data Enrichment Predictive Modeling Custom DashboardsEach module adds value, but InsightFlow wants to incentivize volume purchasing through tiered pricing:The first module purchased is priced

Scenario A cloud communications provider sells products such as API calls, voice minutes, and message transactions. Buyers can either:Commit to purchasing a minimum volume upfront, or Lock in future rates through a rate card, without immediate purchase.Sales needs a way to configure deals that reflect both committed usage (which is billable now) and rate card agreements (which are

Scenario GlobaTech, a fast-growing SaaS provider for supply chain automation, operates globally with sales teams and customers across North America, Europe, and APAC. Pricing is maintained in USD, but clients often request quotes in their local currencies (EUR, GBP, AUD, etc.).Previously, reps manually adjusted currency conversions or referenced internal spreadsheets. This created:Inconsistent exchange rates across quotes Manual errors in pricing Discrepancies between DealHub proposals and Salesforce CRM recordsTo solve this, GlobaTech leverages Salesforce’s Manage