Start with the commercial facts
Ask: “Exactly how will I be billed — per seat, tier, consumption, or a flat fee?” Demand the current list price and the price you will pay on renewal, in writing on the order form.
Why: seat‑based and flat‑rate plans behave very differently at scale. If you are quoted a low entry price, confirm whether that is an introductory or promotional rate and whether the vendor publishes a renewal price. Our catalogue lists examples of each pricing model — Slack (seat‑based) and Canva (flat‑rate with a published renewal value).
What a bad answer sounds like
“We’ll just charge your account whatever the invoice says at renewal.” That answer means there is no cap, no preset renewal schedule and probably no contractual limit on increases; vendors use this to push uplifts at renewal. Industry analysis shows renewal uplift is now a regular line‑item in procurement budgets and many vendors reserve broad rights to change prices at renewal. vendorbenchmark.com
Ask about renewal caps and automatic escalators
Ask: “Is there a contractual cap on price increases at renewal? If so, is it expressed as a percentage, CPI‑linked formula, or ‘vendor’s then‑current rates’?”
Why: some contracts permit fixed annual escalators, others tie changes to CPI, and many say nothing — leaving you exposed. Procurement reporting in 2025–26 shows uncapped or vaguely worded escalators are a common source of surprise increases. ironmarten.com
Bad answer
“We don’t negotiate those terms; you’ll renew at our standard commercial rates.” Translation: you’re expected to accept whatever the vendor decides to charge, and the vendor may have a history of quiet price moves. That’s a serious negotiation weakness.
Billing mechanics and overages
Ask: “How are overages measured and billed? Will you notify and obtain approval before charging overage fees?”
Why: vendors differ on whether overages are auto‑charged, prorated, or require approval. Put the notification, measurement method and dispute window in the contract. Practical buyer guidance recommends requiring written prior approval for any unexpected charge. tropicapp.io
Bad answer
“We bill any overages on the next invoice; it’s in the T&Cs.” If overages are automatic and backed only by T&Cs, you have limited recourse and will struggle to budget predictably.
Service levels and remedies
Ask: “What SLA do you offer (SLOs, availability percentage, measurement window) and what credits or remedies apply if you miss it? How is uptime calculated and who verifies it?”
Why: a quoted 99.95% uptime has a concrete meaning — roughly four hours of downtime a year — and SLAs should state how credits are calculated. Don’t accept vague promises; require the SLA and remedy schedule in the master agreement. technologysource.com
Bad answer
“We don’t give credits; we’ll fix the issue as fast as possible.” Fixes without contractual remedies leave you with operational risk and no monetary recompense for outages. For critical services, insist on clear, verifiable remedies.
Data: location, export and portability
Ask: “Where will our data be hosted (region/country)? Who are your sub‑processors? Provide your DPA and describe the data export process (format, timeline, tooling, costs).”
Why: data residency affects compliance; the sub‑processor list identifies third parties with access; the DPA clarifies processing rights. Good procurement checklists put these questions front and centre and recommend getting the DPA and sub‑processor list before commercial sign‑off. kennisbank.vectel.nl
Bad answer
“We’ll export anything you need at contract end.” If the vendor can’t specify formats, timeframes, or costs, you risk paying expensive migration fees or being locked in because your data is stored in proprietary structures. Insist on a concrete export plan and a test export if possible.
Data use, AI training and IP
Ask: “Do you use customer data to train models or improve services? If so, what controls and opt‑outs exist? Who owns derivative outputs?”
Why: AI features broaden the ways vendors can process your data; industry guidance recommends separating storage and model‑training questions and demanding clear, auditable consent if data will be used for training. reddit.com
Bad answer
“We anonymise everything and might use it internally.” That non‑committal reply leaves ambiguity about whether your proprietary or customer data will feed vendor models — a non‑starter if you handle regulated or sensitive information.
Termination and exit support
Ask: “What are the termination rights for both parties? What assistance do you provide on exit (export, runbook, cutover support) and for how long after termination?”
Why: many disputes arise at exit. A useful contract itemises exit support (export formats, timing, support hours and fees) and gives the buyer a sensible notice and dispute window. Clause audits and checklists stress the cost of poor exit planning. clauseaudit.com
Bad answer
“You can export via the UI.” If export is manual, slow or partial, your migration will be expensive. Avoid contracts that leave exit logistics undefined or charge high fees for reasonable data exports.
Security, compliance and audit rights
Ask: “Provide evidence of security certifications (SOC 2 Type II, ISO 27001), the last audit date, and your breach notification process. What audit or inspection rights will you grant our security team?”
Why: certification papers alone don’t tell the whole story. Procurement guidance recommends getting the latest reports and a clear, contractual commitment to timely breach notification and remediation. kohler-law.com
Bad answer
“We’re compliant; we’ll email the report.” Delays or refusal to provide recent audit reports, or evasive answers about breach notification, are red flags.
Support, onboarding and SLAs for implementation
Ask: “What onboarding and training are included? What SLAs apply during onboarding and who bears responsibility for integrations?”
Why: implementation costs are often forgotten. Contracts should be explicit about responsibilities, deliverables and timelines so you can budget professional services or internal resources correctly. Procurement guides recommend confirming implementation SLAs before signing. sitic.org
How to use these questions in a negotiation
- Get the DPA and master agreement before signing the order form — don’t accept being handed only an order form. clauseaudit.com
- Request explicit renewal language: cap, formula, notice period and the corridor in which you can negotiate. Benchmarks suggest many buyers do not secure caps and face material uplifts at renewal. vendorbenchmark.com
- Make exit terms commercial: add a defined export timeline and one or two test exports during the contract term to verify the process.
- Document promises in the order form and incorporate the support and SLA schedules into the contract; verbal assurances don’t survive renewal or dispute.
“If they sweat or stall when asked for the master agreement, the DPA or a sub‑processor list, consider that a negotiation advantage.”
These questions are the minimum for mid‑market and enterprise purchases in 2026. If the vendor balks, the answers you hear indicate where risk sits: opaque billing equals budget risk; vague export answers equal lock‑in; absent SLAs equal operational risk. Use the concrete, contractual language above — with the DPA and master agreement in hand — and you will reduce the common surprises at renewal and exit.
Related reading in our catalogue: compare pricing models and entry prices for common tools such as Slack, Figma, Notion and Canva to understand how a seat‑based vs flat‑rate model will affect your cost as you scale.