How this works

Use this when sellers repeatedly compare contract lengths, quantities and packages before a buyer selects an offer. AI converts a conversational request into structured option inputs, while the existing calculator determines prices and applicable approvals.

Keep exploration separate from formal quote creation. Each preview should identify its price-book version, currency and assumptions. A plausible model calculation is not an approved price, and a requested discount is not permission to bypass a threshold.

Before you start

Prepare the inputs

buyer_request

Required

Email or structured option brief

Confirm product, quantity, term, currency and start date; preserve unknown fields.

pricing_rules

Required

Versioned calculator or spreadsheet

Check authority and effective period; test a known quote before use.

account_terms

Optional / conditional

Existing contract and eligibility facts

Required for amendments, grandfathered prices or customer-specific terms.

Implementation, step by step

1. 01

   Structure the options

   • Extract each requested variation into a separate row with product, units, term, billing frequency and discount request.
   • Resolve whether quantities are concurrent seats, annual units or usage commitments. Do not silently choose a unit basis when the buyer is ambiguous.

   Checkpoint: The buyer’s alternatives are represented without hidden assumptions.

2. 02

   Validate commercial inputs

   • Check product combinations and eligibility against the current rule set. Mark unsupported packages and missing renewal context before calculation.
   • Identify which requests require finance approval. Preserve the requested value and allowed value separately so the exception remains visible.

   Checkpoint: Every option is calculable or has an explicit blocking reason.

3. 03

   Run deterministic pricing

   • Submit normalized inputs to the approved calculator, or reproduce its documented formulas in a local spreadsheet when no connector exists.
   • Reconcile recurring amounts, one-time fees, discounts and proration. Keep taxes separate if the source system cannot establish them.

   Checkpoint: Prices can be reproduced from versioned rules and inputs.

4. 04

   Preview billing effects

   • Show total contract value alongside invoice cadence and the first invoice estimate. Distinguish a lower annual rate from a lower total commitment.
   • For changes to an active subscription, use effective dates and prior billed amounts; do not treat the amendment as an entirely new contract.

   Checkpoint: The comparison explains both commercial and billing consequences.

5. 05

   Prepare selection and handoff

   • Present the options with assumptions, validity dates and approval status. Record which option the buyer or authorized deal owner selected.
   • Create a formal quote only when that specific action is authorized. Recheck rules at creation time and record the resulting identifier instead of creating every preview.

   Checkpoint: One selected option can enter the quote process without duplicate records.

Decisions along the way

What you will produce

Check the result

• Validate a known quote against the calculator before producing alternatives.
• Check all units, currencies, effective dates and rounding conventions.
• Confirm previews did not create duplicate commercial commitments.

When something goes wrong

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Run a small pilot

Keep the scope clear

• The model interprets requests; authoritative arithmetic and approval rules determine prices.
• Customer-facing offers and formal quote creation follow existing task authorization.