Public price pages still get ‘what does it cost for us?’ from companies that will not self-serve. The form should ask for volume or seats, the company, and enough location context for tax and freight before a human sends a rate card.
Fast reply beats a prettier deck.
Keep the extra field visible.
Not on a buried contact page.
Log what you sent on the row so the AE is consistent.
A pricing inquiry is a sales question about money when the website’s public numbers do not fit: volume breaks, education discount, multi-site, or a UK public-sector framework. US buyers often want a PDF rate card; UK buyers may want a quote that includes VAT treatment. The form exists so you do not email the same spreadsheet to a student and a 400-seat rollout.
This is lighter than an RFQ. There may be no drawings—only a seat count and a ‘can we pay annually?’ in the message.
A rate card without volume is how your lowest public price becomes the only price they remember.
If you have a public calculator, link it above the form so qualified self-serve buyers never submit.
Chatbots quote the homepage. Humans still need a ticket for exceptions.
The ‘talk to sales’ path that actually captures volume.
Great for SMB. This form catches the rest.
Forward them a link to this form so volume is structured.
Feed this row into CPQ later; do not wait for CPQ to exist.
SaaS and agency sites often freeze pricing in HTML. Publish the form under the grid and send it to sales development.
Currency: ask USD versus GBP in the message if you list both. Do not assume the page language matches the buyer’s bill-to postcode.
If they exist, show them. The form is for exceptions and volume.
Use inquiry type or a line in the message. Verify.edu / charity numbers later.
Policy in copy. Do not let the form imply you will match anything.
Ask in the message. Capture it before legal drafts.