We sell outcomes. Not hours.
Most CRMs treat the quote as an attachment to the deal: one amount, one stage, one close date. But the negotiation happened in the revisions. Rev 2 is where you gave away the freight. Rev 4 is where the alloy changed and nobody repriced the tooling. Rev 6 is what you sent. If the CRM only stores Rev 6, you have a record of the outcome and no record of the decision, which means you cannot tell a rep why the last deal like this one was won, and you cannot tell finance why the margin moved.
CPQ in HubSpot is the work of making the quote the centre of the model instead of a document hanging off the side of it: a product library that matches what you actually sell, discount logic and approval thresholds your finance team will sign off, revisions that survive, and an accepted quote that becomes an order somewhere real.
We agree all four before we build anything. Most CPQ projects that go wrong went wrong here, quietly, in week one.
The first question, and most projects answer it last. If you have an ERP, a configurator or a quoting platform, that system owns price and HubSpot agrees with it. The CRM never becomes a second pricing authority, because the moment it does you have two numbers and a monthly argument about which one is right. Where there is no upstream pricing system, HubSpot's product library becomes the source and we build it so your team can maintain it.
Every version of the quote is kept, with what changed and who changed it, so the quote history is a record of the negotiation rather than a record of the last keystroke. This is what turns quoting into a reporting asset: win rate by configuration, discount depth by rep, which concession actually closed the deal, and which customers keep asking for the option you have never priced properly. Overwritten quotes cannot answer any of that.
Discount thresholds, margin floors, non-standard terms, unusual payment schedules. Written down as rules with named approvers, so approval is a step in the flow rather than a message to whoever is awake. The rule set is the part finance signs off, and it is the part we insist on settling first.
An accepted quote has to become an order, an invoice or a project in whatever system runs delivery, with the same line items and the same numbers. If that handoff is a person re-keying what the quote already said, the CPQ build has moved the problem one desk to the left rather than solved it. We scope the handoff in the same conversation as the quote itself, because it is the step most projects leave until it is expensive.
Which one you need is decided by your product, not your budget.
Products, tiers, bundles, discount rules, approvals, templates, e-signature and payment, all inside HubSpot. The right shape when your pricing logic can be expressed as rules on a product library, which covers most software, services and distribution businesses.
Where the quote needs a real configurator — geometry, machine time, material, tolerance — the platform holds the quote and HubSpot holds the deal, the account and the forecast. The work is the integration between them, and the thing that matters is latency: a platform that batches overnight gives your reps yesterday's number.
Quoting comes up hardest in manufacturing, because the quote is the unit of work. More on the manufacturing page.
Uptive runs additive manufacturing, CNC machining, sheet metal fabrication and injection moulding for aerospace, automotive, medical and industrial customers. Their old CRM took a 2am batch push from Paperless Parts, so quote data landed a day or two late and often incomplete, which broke sales reporting and caused repeated territory conflicts. Changing anything meant external consultants and code.
We moved them to HubSpot and built a custom Paperless Parts integration syncing in near real time. Quote generation and logging are automated instead of manual, reporting reconciles to the quotes, and the team changes its own sales process and territories without calling anyone.
One figure, published here and on our pricing page, covering the product library, the pricing and discount rules, the approval flows, quote templates, e-signature and payment setup, the revision model, and the reporting built on top of it.
Fixed means fixed. If a real project lands outside the model, we fix the model, not the invoice.
Three answers we give before we quote anything.
Yes. Quotes, a product library, line items, custom quote templates, e-signature and payment collection are native, and approval logic is built with workflows and custom objects. What HubSpot does not ship is your pricing model, your discount rules or your approval thresholds. That is the build.
$25k, fixed, per portal. Connecting an ERP or a quoting platform is separate: $2.5k on a marketplace connector, $10k for a custom integration.
It handles configured products where the configuration can be expressed as rules on a product library: tiers, bundles, volume breaks and options with dependencies. Where configuration needs a real engineering configurator, the configurator keeps the quote and HubSpot keeps the deal and the forecast, connected in near real time.
No. The ERP stays the system of record. Where it owns price, HubSpot agrees with it rather than holding a second copy that drifts.
Written as rules with named approvers and built into the quote flow, so a quote outside policy cannot be sent without the approval having happened. Agreeing those rules is the first working session, before anything is built.
That is the test we build to. Product library, pricing rules and approval thresholds are all maintainable in the HubSpot UI by your ops person. If a routine change needs us, we have built it wrong.
The one with six revisions, the non-standard terms and the discount someone approved by text message. If HubSpot can hold it cleanly, we will show you how. If your pricing rules need settling first, we will say that instead.
+972-54-819-1655
info@penguinstrategies.com
4 Dolev Street, Ra'anana, Israel
