CRM

Jenny26
Top Contributor

Calculated Pricing Properties

SOLVE

Hello,
We have all hubs at the enterprise level.

I want to enable our sales staff to calculate in HubSpot (hopefully in a deal record) pricing for our products. HubSpot's line items/product library doesn't seem to allow enough options to do this for us.

 

Our Products

To make this question a little simpler, basically we have the following software products:

  • Base package
  • Complete package (includes base package + Add-on “A”and Add-on “B”
  • Add-on “A” (an upgrade for current clients to their base package)
  • Add-on “B” (an upgrade for current clients to their base package)

> I’ve create a pricing property for each of the products above with a numerical text field.

 

How Price is Calculated

The pricing for each product depends on the number of employees at the client company and the software item selected. Our pricing table goes all the way to 10,000 employees but for my question, I’ll just include  3 pricing options in a “Number of Employees Range” Property:

  • 1-50 employees
  • 51-100 employees
  • 101-150 employees

My questions:

  • Is there a way to create a pricing calculation property where the pricing is determined by the range of employees selected?

    For example, for the Base Package, if 1-50 employees is selected in the "Number of Employee Range" property, the price shows as $1000 in the "Base Package" property. If 51-100 is selected, the price shows as $1500 in the "Base Package" property. If 101-150 is selected, the price shows as $2000.
  • Is there a way to use HubSpot DB to create a property for calculating price? Perhaps with a custom object?
  • Should I just use a workflow to update the pricing properties based on the number of employees? I've started doing this but am not sure if it's the best option.

Thanks in advance for your help!

 

0 Upvotes
1 Accepted solution
trevordjones
Solution
Recognized Expert | Diamond Partner
Recognized Expert | Diamond Partner

Calculated Pricing Properties

SOLVE

Hi @Jenny26 ,

 

Assuming that you don't need to manipulate the Deal line items and you only need to put the value in a custom property, I would use a combination of two number properties, a calculated property and a workflow to do this.  I'd also add in a dropdownt to pick the add on package.

 

Property 1 = Your Base Package Price

Property 2 = Your Add On Price

Property 3 = Calculation: Property 1 + Property 2

Property 4 = A dropdown where the sales team chooses the add on, if appliccable.

 

Here's your workflow:

 

2024-02-05 - 20-20-58 - Unnamed workflow - 2024-02-06 01-02-03 GMT-0000 - HubSpot.png

 

 

- Trevor
If my post solves your problem, please accept it as a solution.

 

Trevor Jones

Consultant II

Process Pro Consulting
mobilePhone
(207) 939-7689
emailAddress
tjones@processproconsulting.com
website
processproconsulting.com
address
Remote from Maine
linkedin

View solution in original post

0 Upvotes
2 Replies 2
trevordjones
Solution
Recognized Expert | Diamond Partner
Recognized Expert | Diamond Partner

Calculated Pricing Properties

SOLVE

Hi @Jenny26 ,

 

Assuming that you don't need to manipulate the Deal line items and you only need to put the value in a custom property, I would use a combination of two number properties, a calculated property and a workflow to do this.  I'd also add in a dropdownt to pick the add on package.

 

Property 1 = Your Base Package Price

Property 2 = Your Add On Price

Property 3 = Calculation: Property 1 + Property 2

Property 4 = A dropdown where the sales team chooses the add on, if appliccable.

 

Here's your workflow:

 

2024-02-05 - 20-20-58 - Unnamed workflow - 2024-02-06 01-02-03 GMT-0000 - HubSpot.png

 

 

- Trevor
If my post solves your problem, please accept it as a solution.

 

Trevor Jones

Consultant II

Process Pro Consulting
mobilePhone
(207) 939-7689
emailAddress
tjones@processproconsulting.com
website
processproconsulting.com
address
Remote from Maine
linkedin
0 Upvotes
Jenny26
Top Contributor

Calculated Pricing Properties

SOLVE

Thank you, Trevor!