How calculated pricing works in HubSpot, and where it stops
Nine pricing models a formula handles well, and the point where one formula per product stops.
Aptarro’s negotiation cycle went from 29 days to 6.
What is calculated pricing?
Calculated pricing means the price on a line item is produced by a formula rather than entered by hand. The formula runs on data your CRM already holds, and it re-runs whenever that data moves, so a quote revised three weeks later reflects what was true three weeks later.
A formula is a pricing policy someone finally wrote down
Most teams don’t have a pricing math problem. They have a pricing policy that only exists in a spreadsheet and in one person’s head. A calculated price is that policy written down where the quote can read it, which is why the hard part of building one is agreeing on what the policy actually is.
The spreadsheet works. That’s what makes it hard to leave. It works because one person maintains it, and that same person remembers the reseller column has been stale since the last cost update. Writing the same logic as a formula on the product forces answers to questions the spreadsheet let you postpone. Which cost field is the authoritative one? What’s the floor, and who’s allowed to go under it?
The work is mostly not technical. Teams who already have their pricing written down get through setup quickly. Teams who haven’t will spend the first sessions discovering that two of them disagree about how a price is built.
What a formula can read
A calculated price is an expression over values that already sit on your records. Quantity and line-item properties. Deal properties like contract term or ship-to region. Company properties like headcount or customer type. A custom cost field your ops team keeps current.
Two consequences are worth sitting with.
The price recalculates when the data changes, so a corrected headcount corrects the quote without anyone rebuilding it. And anything the formula needs has to exist as a property first. If your cost rates live in a workbook on somebody’s desktop, moving them onto the record is the first piece of work, and it’s usually the longest.
Nine pricing models that run on a formula
These nine shapes cover most of what quoting teams price on. Each one is a formula reading values your business already tracks, even if today they’re tracked in a workbook nobody backs up. Read them as patterns. Most catalogs carry two or three at once.
1. Priced by dimension
Sheet goods, cut stock, fabricated parts, coatings. The price is a size times a rate: width by height by a per-square-foot number, or board feet by a cost with margin applied. Reps get this wrong in predictable ways. They round the dimension, or they use last quarter’s rate because that’s the version in the file they copied.
2. Weight and distance
Freight and field-service quoting runs on a rate per pound, adjusted for distance and for the fuel surcharge in force that week. The math is straightforward. The fuel number is what goes stale: it moves on its own schedule, and it lives in however many quote templates somebody duplicated last year. A surcharge that changed last week is still sitting in those templates, and every quote built from one of them prices last month’s fuel.
3. Per employee, per month
A benefits administrator prices one employer at a time: headcount from the company record, multiplied by a per-employee-per-month rate and by the number of contract months. Headcount is the number that moves. Because the formula reads the company property directly, a quote built in March and revised in June prices off June’s headcount, and nobody has to remember to go back and check.
4. Cost plus a markup, with a floor under it
Cost times markup is the easy half. The useful half is the floor. A formula can hold a gross-margin minimum so the calculated price never lands below the number finance set. A rep who needs to go under it is asking for an exception, and an exception is something you can see.
5. Volume breaks
The rate changes at quantity thresholds. First tranche at one rate, everything past the break at another. Built as a formula, a rep who edits quantity watches the price land in the correct tier without going back to a matrix to check which one applies.
6. A percentage of another line
Onboarding at 15% of the software subtotal. A first-year support fee that tracks the license total. These are the lines that quietly go missing, because they depend on a rep remembering to add them after the rest of the quote is built.
7. Hours at a role rate
A services firm estimating an implementation still needs a human to say how many hours of a solution architect and how many of a junior consultant the job will take, but once those numbers exist the formula carries the rate card and rolls them into a project number nobody retypes.
8. A different formula per segment
Sell the same product direct and through resellers and the calculation itself changes. Direct might price off internal cost and a dimension. Resellers price off a markup over that same cost. Both are legitimate, and neither one is a special case of the other. This is the model that breaks a single product-level formula, and it’s covered in the next section.
9. Renewal uplift
New business prices off seats and tier. A renewal prices off what the customer already pays, plus an uplift. Those two draw on different data, which makes them two formulas, and the renewal one belongs to a renewal price book. Left to memory, uplift gets skipped in a busy quarter. Sitting on the renewal book, it shows up in the price the moment the rep opens the quote.
One formula per product runs out here
Where the formula lives decides how many versions of it you can have. Quotivity is a HubSpot-native CPQ app, and its Calculated Pricing puts that formula on the product, so there’s one, and that one governs every quote in every book. Models 8 and 9 need two: a direct calculation and a reseller calculation, a new-business calculation and a renewal calculation.
Quotivity lets the same product carry a second calculation. Put the reseller formula on that product’s entry in the reseller book. Every quote assigned to that book then prices off it, while direct quotes still read the product’s own default, so the reseller math stays where it belongs. You never have to create a duplicate product to hold the second number.
| Pricing model | One formula per product | A formula per price book, per product |
|---|---|---|
|
1. Priced by dimension
|
Yes. Size times rate is the same math for every buyer.
|
Yes, and unnecessary unless the rate itself differs by book.
|
|
2. Weight and distance
|
Yes. One band table serves every quote.
|
Yes. Build one when a carrier program covers a single segment.
|
|
3. Per employee, per month
|
Yes. Headcount times rate times term.
|
Yes. Partner tiers that price at their own PEPM need their own book.
|
|
4. Cost plus a markup, with a floor under it
|
Yes. Markup and floor both sit on the product.
|
Yes, once the floor moves by segment.
|
|
5. Volume breaks
|
Yes. The thresholds are the same everywhere.
|
Yes, if a book carries its own break points.
|
|
6. A percentage of another line
|
Yes. The percentage travels with the product.
|
Yes. Resellers on a different percentage need the second formula.
|
|
7. Hours at a role rate
|
Yes. One rate card on the product.
|
Yes, where a segment has negotiated its own rate card.
|
|
8. A different formula per segment
|
No. The product record holds one formula and this model needs two.
|
Yes. The direct math stays the product default; the reseller formula sits on the reseller book.
|
|
9. Renewal uplift
|
No. New-business math and uplift math read different data.
|
Yes. The uplift formula sits on a renewal price book and resolves when a rep picks it.
|
The feature-page detail is on calculated pricing, and how the right book gets onto the quote without a rep choosing it is on price books.
Four gaps, and what closes each one
You now know what a formula reads and where one formula per product runs out. Here’s the part that matters on a quote: what each gap costs you, and what closes it. All four capabilities below are Quotivity’s, and each one closes a gap this page has already named.
One thing to know before you read them: calculated pricing is on the Enterprise plan. Price books are on both plans. If you're on Professional, the first two below are the ones a plan upgrade would open up, and the numbers are on the pricing page.
The formula Quotivity puts on the product
What it replaces: the pricing workbook, and the copy of it a rep saved to their own desktop.
The failure it prevents: last quarter’s number. The rounded dimension in model 1 and the stale fuel surcharge in model 2 both reach a customer as a price that was right once. A formula reads the field as it stands on the day the quote is built.
Who stops waiting: the rep. There’s no current version of the file to go and find.
A second formula, on the price book
What it replaces: the duplicate product you created so the reseller price had somewhere to live.
The failure it prevents: direct math on a reseller quote. Models 8 and 9 are the two that break a single product-level formula, and both of them fail quietly. The number looks reasonable and it’s the wrong number.
Who stops waiting: operations. Nobody has to remember which of the two products this customer buys from.
Price books that assign themselves
What it replaces: the rep picking the right book off a list, and the manager who checks that they picked right.
The failure it prevents: the renewal quoted at new-business rates. Model 9’s uplift only lands if the renewal book is on the quote, and deal context is what puts it there.
Who stops waiting: the sales leader, who stops auditing which book a quote came off.
A floor under the number
What it replaces: the discount policy in a document, and the sales manager who remembers what’s in it.
The failure it prevents: the price that goes out under the margin finance set. Model 4’s floor is only worth something if it holds while the rep is building, and approval routing is what makes it hold.
Who stops waiting: finance, who sees the exception on the day a rep asks for it.
Edges worth knowing before you build
A calculated price set on a price-book entry governs standalone products. Option products that take their price from inside a bundle run through a different part of the system, and neither one covers for the other. If your catalog leans hard on bundles, get that boundary drawn before you design around it.
Ramp pricing is a different tool again, for a price that steps up on a schedule across a term. It doesn’t cover bundles. Model a ramped subscription on standalone subscription lines and keep the bundle out of that structure.
Which plan includes which capability is a pricing question, and the answer is on pricing.
When a formula is the wrong tool
Look up how you price one product for two different customers. If the number is the same both times, and it would be the same next quarter, you don’t need a formula. A single price on a product in HubSpot’s native library already gets that quote right, and a calculated price is maintenance you’d carry for a result you already have.
The other case is harder to admit. If the price depends on judgment, a relationship, a competitor in the room, a favor you’re calling in, then no formula reaches it. You can put a floor under that number so a deal can’t go below it. You can’t compute it. Teams who buy calculated pricing hoping it will settle their negotiated pricing end up with a formula and the same argument they were having before.
Reps take the fast path
Sales reps are incentivized to stick to price book because they can get their deal out the door much faster.
That’s the mechanism worth copying. When the calculated price is already correct on the quote in front of a rep, following pricing policy is the shortest route to sent. Nobody has to police it.
Questions people ask before they build one
Build the shape that changes most often and let the other one live inside it. A fabricated part priced by dimension that also earns volume breaks is a single formula with a tiered rate in it. The case that genuinely needs two formulas is the one where the buyer changes the calculation, which is what a formula per price book is for.
That’s a data question before it’s a formula question. A formula computes from what is on the record, so the property it reads has to be populated on every record that will carry a quote. Deciding who owns keeping that field current is part of setup, and on most projects it takes longer than building the formula did.
Not formally, but every disagreement about how a price is built has to get settled before a formula can encode it. Agreed cost fields and margin floors make setup fast. Where they aren’t agreed, the first sessions turn into a pricing workshop, and that’s work worth doing whether or not you end up building the formula.
An admin builds and edits it. Reps supply inputs and never type the price. The question worth settling early is who signs off on a change, because editing a formula re-prices every future quote that uses it. Most teams give that to whoever owns the margin floor and route everyone else’s changes through them as requests.
Not the same way. A bundle prices its own options, and that path is distinct from the calculated price you set on a standalone product or on a price-book entry. Scope the two separately against your own catalog; don’t assume one reaches the other.
No. A formula produces a number. A rule watches a condition and does something about it, like capping a discount or routing a quote for approval. Most teams run both, and price rules are also what assign the price book a formula depends on.
Most customers are quoting within weeks of kickoff. The variable isn’t the formulas. It’s whether the data the formulas need is already clean and on the record.
Name the product you price two different ways
Most catalogs have one. Bring it, along with both numbers it comes out as, and we’ll build the two formulas in front of you so you can check them against a quote you’ve already sent.