Excel's fine. Until it's the only thing that knows how you price.

The more pricing logic you add, the harder it is to leave. Here's how to tell where you are.

Book a demo
See pricing

When should a company stop quoting in spreadsheets?

When the file stops being a calculator and becomes the pricing engine. The tell is dependency: hidden tabs and cascading lookups only one person can explain. At that point the spreadsheet holds your business logic, and every month of new formulas raises the cost of moving it anywhere else.

Six signs you're past it

Diagnosis before solution. Read these and count.

  1. 1

    One person maintains it. When they're out, quoting slows down.

  2. 2

    Nobody edits the formulas. Changing a price risks breaking a dependency nobody can see.

  3. 3

    There are versions. pricing_v4_FINAL_use-this-one.xlsx lives on three desktops and two of them disagree.

  4. 4

    New estimators take months to get up to speed. Not to learn the products. To learn the spreadsheet.

  5. 5

    Errors surface at the customer. A line item that didn't make it across, or freight priced off last year's table.

  6. 6

    The CRM never sees the quote. Someone rebuilds it by hand in HubSpot afterward, which is why nobody can answer "what's our revenue by product line?"

Four or more and the spreadsheet is the constraint on your growth. You just haven't priced it yet.

Somebody built that file because the business needed a number

HubSpot didn’t do the calculation and a customer was waiting. So somebody opened Excel and built the thing that would. A pricing matrix in Visual Basic. A 42,000-row lookup. Both of them worked. They had been working for years.

None of that was a mistake, and this page isn’t going to pretend otherwise. The file did a job nothing else was doing, and the business grew around it.

Then it quietly became the system. Every rule about how you price is now in one file, on one machine, in one head. That’s the part worth fixing, and it has nothing to do with whether the spreadsheet is any good.

The thing most CPQ vendors get wrong

They promise to replicate your spreadsheet. They can't, and neither can we.

A quoting spreadsheet built over ten years holds real business logic. It also holds dead logic nobody removed, and workarounds for problems that stopped existing in 2019. Replicate all of it and you've imported the mess along with the value.

The work is translation. Which of those formulas still reflects how you sell, and what's in there because someone needed a number on a Tuesday? That's a harder conversation than a data import, and it ends with something better than what you started with.

Translate, don't replicate. It's the least popular sentence we say on a first call, and it's the one that decides whether this works.

Four systems, and the spreadsheet each one replaces

A quoting spreadsheet is doing four jobs at once. Below is which system takes each one, and the mistake it stops on the way out.

Configurable Products

What it replaces: the tab per product configuration, and the hidden validation rules underneath it.

The failure it prevents: the combination that can’t actually be built. Compatibility rules read product attributes, so a rule written once covers every SKU carrying that attribute, including the ones you add next spring. An invalid combination can’t be selected.

Who stops waiting: the rep, who stops opening the file to check.

Guided Selling

What it replaces: the discovery that lives in a senior estimator’s head, and the months a new one spends learning the file.

The failure it prevents: the skipped question. Discovery comes in a fixed order and it comes to everyone. A rep hired last month walks the same path as the one who has been quoting for nine years.

Who stops waiting: the new hire, and whoever used to sit beside them while they quoted.

Calculated Pricing and Price Books

What it replaces: the 42,000-row lookup, and last year’s freight table, which the formulas still point at.

The failure it prevents: the stale price. Formulas pull from live CRM data, and each segment gets its own price book, which assigns from the deal. A rate changes in one place, and every quote built after that uses the new number.

Who stops waiting: finance, who stops asking whether a number came off the current table.

Rules Engine and Approvals

What it replaces: the manual check somebody runs before the quote goes out, and the discount rule that only exists in an email thread.

The failure it prevents: the discount that never got asked about. Caps enforce while the quote is being built, and anything past the floor routes before it sends. An approval stays in force once you give it.

Who stops waiting: the manager who is currently the last set of eyes on every quote.

What moving actually looks like

Quotivity is a HubSpot-native CPQ app. You build price books in Quotivity Studio, along with the rules and approvals that govern them, and the quote lands on HubSpot's own records. Moving off a spreadsheet means working out what each part of that file was really doing, then rebuilding it where the CRM can see it.

Weeks one and two: the real rules. We go through the file with whoever built it and separate the logic from the archaeology.

The build runs alongside it. Price books, calculated pricing, compatibility rules, approvals.

Most customers are quoting within weeks of kickoff.

Where each piece ends up
In the spreadsheet In Quotivity
Lookup tables for customer pricing
Price books, assigned by company
Nested IF formulas for discounts
Price rules that fire on conditions you set
A tab per product configuration
A bundle with compatibility rules
A manual check before it goes out
Approvals that route when policy says they should
Tribal knowledge about what to ask
Guided selling questions every rep answers
Copy-paste into HubSpot afterward
The quote is the HubSpot record

Plenty in a real spreadsheet has no row on the right at all. That's what the first call is for.

Nobody has to remember anything

Here is the after. A rep opens the deal and answers the questions in front of them. The right price book assigns itself, because the customer record already says which one applies. A discount past the floor routes for approval before the quote sends. Nobody walks over to ask, and no quote sits waiting while whoever built the file is on vacation.

The person who built the spreadsheet gets their week back. Operations stops being the translation layer between how the business actually prices and what the CRM knows about it. And the question in sign 6 finally has an answer, because the quote was built in HubSpot in the first place.

Aptarro cut negotiation from 29 days to 6
Sales reps are incentivized to stick to price book because they can get their deal out the door much faster.
Renée Durrance, Senior Director of Business Systems, Aptarro Renée Durrance Senior Director of Business Systems, Aptarro
we can get rid of the spreadsheets for reps and take their mind off of it while eliminating errors at the same time
S. Hodgson HubSpot marketplace review

Aptarro's reps pulled prices from an Excel table saved to individual desktops. Every rep had a different version of the truth, and pricing drifted far enough that the board discussed a blanket increase just to normalize it. After rebuilding their price books, average negotiation time went from 29 days to 6.

Don't do this if nothing in the file can change

Open the spreadsheet and try to name three formulas you'd trade away for speed. Come up empty and you have your answer. If every tab is a hard requirement and none of the logic is negotiable, don't buy CPQ from anyone, us included. No CPQ reproduces a ten-year-old quoting spreadsheet, and an implementation that begins with "change nothing" ends with a worse version of what you already have, plus an invoice. Better you hear that now than in month two.

Questions we get on the first call

Send us the spreadsheet

Genuinely. Book a demo and bring the worst one you've got. Thirty minutes and we'll tell you what translates and what doesn't. If the answer is not much, we'll say that too.

Book a demo
See pricing