Quotingsoftware
you own outright.
JetCPQ replaces spreadsheet quoting with one live price book, guided builds, a customer portal and an assistant that drafts a quote from a sentence. Built around your catalogue, delivered as a one-time engagement, handed over with the source code.
- One-time
- not per seat
- Your code
- handed over
- Your brand
- end to end
priced on Q3-26v1
NEWCTQ · Conversation to Quote
The call writes the first draft.
Every deal already gets transcribed by something. Forward that transcript to your JetCPQ address and a priced draft is waiting when you next open the tab — customer, line items, quantities, and the sentence each one came from.
As far as we can tell, nobody else does this.
We have not been able to find another CPQ platform that accepts a conversation as an input. The products costed in the comparison below all begin the same way — a rep, a screen and a catalogue. Checked August 2026. If you know of one that does this, tell us and this paragraph changes.
Your notetaker sends the transcript
Zoom, Teams, Meet, Gong, Fireflies, Otter — whatever already sits in your calls. If it can produce a transcript and send an email, it works. There is nothing to integrate and nothing to install.
You forward it to your JetCPQ address
One forward, from your own mailbox. You're recognised by the address you send from, so the draft lands in your queue and nobody else's.
The draft is waiting
Customer, line items, quantities and discounts, matched against your live price book and priced. You get an email back with a link straight to it.
…so that’s two of the 2600 session border controllers, one for each site.
…and put twenty-four seven on both of them, annual.
…plus the advance replacement cover, same term.
“a spare fan tray for the Chicago rack” — listed for the rep to resolve, not guessed at.
One habit doubles the accuracy: have reps read the agreed list back before they hang up. That recap is the passage the extractor trusts above everything else said on the call — it is where “about thirty” becomes thirty, and where the legal name and the billing address get said properly. It is also just good sales practice.
The pattern
Quoting runs on spreadsheets
until it can't.
Every company that sells configured products hits the same wall, whether quoting runs on a spreadsheet or on a platform you're already paying six figures for. It is never one dramatic failure, it is a slow tax on every deal.
One person owns pricing
Someone hand-edits the sheet and releases a new version, sometimes more than once a week. When they're away, quoting stalls.
Everyone quotes from a copy
Reps work from whichever file reached them. Quotes go out on last quarter's numbers and nobody notices until the margin is gone.
No defensible history
Six months after a deal closes, nobody can prove which prices it was based on. The evidence lives in someone's downloads folder.
Or you already pay for this
A platform went in, the implementation cost more than the licence, and it still doesn't price the way you sell. Now it renews every year, per seat, with an uplift.
Three ways to build one
Every rep quotes differently. That's fine.
A new hire and a fifteen-year veteran should not be forced through the same screen. JetCPQ gives you three routes to the same correct quote — four, counting the one where you don't build it at all.
A sentence becomes a draft
“Quote Northwind for two session border controllers with 15% off.” The assistant parses it, assembles the bill of materials, applies the discount to the lines that allow it, and opens a real draft.
Guided builds
For reps who'd rather be walked through it: how many sites, how many concurrent sessions, which service level. The right products, quantities and support items come out the other end.
The full catalogue
Thousands of SKUs, searchable by part number or description, ranked so the platform you meant comes before its spare fan tray. For the people who already know exactly what they want.
The platform
Pricing lives in one place, and quoting stops waiting on it.
One live price book
Versioned and authoritative. Admins update it in place, with no release to wait for and no all-hands email.
Prices freeze on send
The moment a quote reaches a customer its pricing locks. What you sent is what you agreed to, permanently, with a record of it.
Drafts stay current
If pricing moves under an open draft, the rep sees a flag and updates with one click. Nothing changes silently under a customer.
Structured discounting
Per line, per category, and per price target. Visible and controlled, rather than a formula buried in a cell.
Roles that mean something
Admins own the price book, managers see their team, reps see their pipeline. Everyone can quote.
A complete audit trail
Every change attributed and timestamped, from the first line item to the customer's signature.
After you hit send
Your customer gets a link, not a 12-page attachment.
They read the quote in the browser, download a PDF if they want one, and approve or reject it on the spot. A rejection comes with a reason, and it reaches the rep immediately.
- Secure link, no account for them to create
- Product documentation attached to every line item
- An assistant that answers questions from those documents
- Approve or reject, with the decision logged against the quote
“What does the 24×7 support cover?” Answered from the support terms attached to this quote, with the source cited.
The AI module
Used where it removes work. Never where it invents a number.
Pricing always comes from your price book. The AI assembles, explains and drafts, it does not decide what anything costs. It has three jobs here: it reads the call in CTQ, it turns a rep's sentence into a draft, and it answers your customers out of your own documents.
A quote in one sentence
Describe the deal in plain language and the assistant builds the draft: the right bundle, correct quantities, support items included, discount applied only where your rules allow it.
15% was asked for. Your rules cap hardware at 10% and software at 5%, so that is what the draft came back with — the assistant assembled it, the price book priced it.
A quote that answers questions
The customer portal ships with an assistant grounded in the product documentation for the items on that quote. What's included, what the support terms cover, what a line item does. Every answer cites the document it came from, and it will not answer outside them.
It renews annually. If it lapses, the controllers keep running on their last applied configuration — you lose central management and firmware updates until it's reinstated.
Your brand
It shouldn't look like our software. It should look like yours.
Colours, typography, logo, favicon, the customer portal, the PDFs and the emails. One setting swaps the entire identity, so the quote your customer opens looks like it came from you, because it did.
Connects to what you run
Your CRM stays exactly where it is.
JetCPQ is the quoting layer, not a replacement for your system of record. A quote pushes to the opportunity your reps already work, and edits after the fact flag the record as out of date rather than overwriting it quietly.
Salesforce
Push to an opportunity, drift detection, one-click re-sync.
API access is standard on Enterprise and above; Professional Edition needs the Web Services API add-on.
HubSpot
Deals and line items, on every HubSpot tier including Free.
HubSpot's own quoting sits behind Revenue Hub Professional. Writing deals and line items does not.
Dynamics 365 Sales
OData v4 with native quote, quote detail and opportunity tables.
Microsoft Entra ID OAuth, and a documented ceiling of 6,000 requests per five minutes.
Oracle Fusion Sales
Full CRUD on opportunities, with a describe endpoint for the schema.
The CRM, not Oracle CPQ. OAuth 2.0 or JWT assertion, and a per-pod host.
Not on this list? That's usually not a problem.
These four are the ones we get asked about, not the limit. If your CRM exposes a usable API, JetCPQ can push to it — and usable means something specific that we check in discovery rather than assume: read and write on the objects a quote has to land in, authentication we can automate instead of a login someone clicks through every morning, and rate limits that survive a real sync rather than a demo. Most modern CRMs clear that bar, including plenty smaller than these four.
What goes on top is the same either way: a quote pushes to the record when it's sent, later edits flag that record as out of date instead of overwriting it quietly, and the field mapping follows your names for things rather than ours. Salesforce is the one running today; the rest is integration work, scoped like any other. And if a system genuinely has no API worth using — some older on-premise installs don't — we'll tell you that rather than quote around it.
Product names are the trademarks of their respective owners and are used here to describe interoperability, not partnership.
Fits what you run
It joins your stack. It doesn't replace it.
Email that actually sends
Quotes go out from your domain, with your branding, and the link back to the customer portal.
PDF and CSV
A clean document for the customer's file, and an export for whatever your finance team already runs on.
Reporting
Value and win rate by rep, product group, customer and team, built from the data your reps are already entering.
ERP and billing
Systems integration is one of the four things JetBrackets does, so it isn't an edge case here. The size of the work depends on what your system exposes, which is a discovery question rather than a guess.
The arithmetic
Year one is the shock.
Years two and three are the bill.
Almost every CPQ vendor shows you a per-seat figure and stops there. Implementation lands once, the licence renews forever, and the renewal escalates. Set the assumptions to your own numbers and see what three years actually costs.
Hatched because the fee isn't published — the width is indicative, not a number. Years two and three are the comparison.
Implementation lands once. The licence never stops.
On the enterprise tier, services are frequently more than half of year one. Then year two arrives with no implementation and the invoice is still six figures, because the licence was always the recurring part.
The escalator is contractual.
Salesforce's standard renewal uplift is 7% a year, compounding, commonly negotiated down but rarely to zero. Three years of that is pure increase against no added function. JetCPQ has no renewal to escalate.
Seat minimums punish being mid-sized.
At 30 seats you are currently paying for 50 on SAP CPQ. Floors and multi-year commitments are written for enterprises, and a 30-person sales team pays the difference.
What you're buying
One engagement. One invoice.
You've just costed three years of the alternative. JetCPQ is built for the companies who wanted that outcome without that model: paid once, shaped to how you sell, and yours at the end of it.
Then it's yours.
The number depends on your catalogue, your pricing rules and how far the customisation goes. Discovery settles it, and it is fixed before anyone writes code.
We sit with the people who quote every day and map how it actually works before anyone writes code.
The process, the data model and the system, written down and handed over.
The platform shaped to your catalogue, pricing models and sales process.
Guided builds, the natural-language assistant, and the document-grounded customer assistant.
Included. Not a recurring per-seat fee.
Yours when the first phase ships. Modify and extend it however you like.
Your request isn't in a queue
A change goes to the people who built the system, not into a product backlog behind ten thousand other customers with their own priorities. Nobody has to be convinced it's worth doing for the whole market first.
Fit is the default, not an escape hatch
Off-the-shelf platforms make your pricing fit their model, and the gap gets filled with configuration nobody can maintain. Here the model is built around how you already sell, because there's no other customer's version to preserve.
Customising doesn't reprice the licence
There isn't one. Extending the system costs the work it takes and nothing else — no tier to move up, no seats to re-count, no renewal that quietly reflects how much you now depend on it.
The one limit: you can't resell it as a product. Everything else is open. Keep us on for future work if you want us, or take it from here with your own team. Both are fine outcomes.
Questions
The things people ask first
+What does it cost?
Materially less than the enterprise platforms it replaces, and once rather than every year. We don't publish a figure, because the honest one depends on your catalogue, your pricing rules, and how far the customisation and the integrations go. Discovery settles it, it's fixed before anyone writes code, and there's nothing recurring behind it. Ask us and you'll get a real number, not a range designed to start a negotiation.
+Why not just buy an off-the-shelf CPQ platform?
You could, and for some companies that's the right answer. Two differences. Those products make your pricing fit their model, and bending them is rarely less work than building what you actually need. And at the end of this you own the code and pay no per-seat licence, so cost doesn't scale with headcount. If your quoting is simple, buy something. If your quoting is part of what makes you competitive, own it.
+Where do the numbers in your cost comparison come from?
Third-party sources, every one of them linked on the page next to the figure it supports. None of those vendors publishes a rate card, so everything there is an estimate from analysts, procurement data and consultancy write-ups, compiled July 2026 and re-checked quarterly. That's also why the seat count, complexity and CRM assumptions are yours to set rather than ours to fix: what we're publishing is a model you can argue with, not a verdict. If you think a number is wrong, tell us and we'll correct it.
+How long does it take?
That's what discovery answers. We won't put a date on it before seeing your catalogue and your pricing rules, because a number invented before that isn't worth anything to either of us. We deliver in stages, so you see working software early rather than waiting for one reveal at the end.
+What happens if JetBrackets goes away?
You own the source code and the documentation, which is precisely why we hand them over. It's a standard stack, not a proprietary framework, so any competent development team can pick it up. It's a fair question to ask a small company, and our answer is to remove the dependency rather than argue about it.
+Who owns the data, and where does it live?
You own it, and it lives in infrastructure you control. This is your pricing, some of the most commercially sensitive data you have. It doesn't belong in a vendor's multi-tenant database.
+Can the AI invent a price or make something up?
No. Pricing comes from your price book, always. The customer-facing assistant answers only from the documentation attached to that specific quote and cites what it used. The guided build assembles from rules defined with you. Anything a customer sees is something a person could have written.
+What if CTQ mis-reads a call?
Then a rep catches it in about five seconds, because every extracted line shows the sentence it came from and nothing becomes a quote until someone opens the draft and confirms it. Items it can't match to your catalogue are listed as unmatched rather than guessed at. Treat it as a very fast first draft written by someone who was on the call, not as an automation you leave unattended. One habit makes it markedly better: have reps read the agreed list back before hanging up.
+Does CTQ need us to change our meeting tools?
No. It takes an email with a transcript attached or pasted in, so anything that can transcribe a call and send mail already works — Zoom, Teams, Meet, Gong, Fireflies, Otter. There is nothing to install and no integration to buy, which is deliberate: the moment it needs a connector per tool, it stops being something you can start using this afternoon.
+What about support after handover?
Two options, both legitimate. Your team maintains it, since you have the code and the documentation. Or you keep us on. We'd rather you chose deliberately than defaulted into it.
+Does it integrate with our ERP or billing system?
Systems integration is one of the four things JetBrackets does, so it isn't an edge case for us. The honest answer is that the size of the work depends on what those systems expose, which is a discovery question. What we won't do is quote an integration before seeing the API.
Next step
Bring us your catalogue. We'll show you your own quotes in it.
A short working session with the people who quote every day is enough to scope phase one properly. No slide deck required.