Hey everyone! 👋
I've been diving deep into Gemini for a potential procurement project at my day job, and I've hit the classic "list price vs. real price" wall. The public pricing page gives a per-user-per-month figure, but as we all know, that's rarely the whole story when you're talking about a 100-seat enterprise license.
We're looking at using it primarily for API-driven workflow automation (think: syncing CRM data, generating report narratives, parsing support tickets), so the 1.0 Pro model is our likely target. I've done the basic math: `100 users * [published rate]`. However, based on past experience with similar platforms, I'm anticipating some variables.
Could anyone who's been through a procurement cycle for a team of this size share the realistic total cost? I'm especially curious about:
* **Commitment discounts:** Is there a noticeable price break for an annual contract versus month-to-month? We're prepared for an annual commitment.
* **Volume tiers:** Does the per-user cost decrease at the 100-user mark, or are the public tiers pretty firm?
* **Add-on costs:** Are there often mandatory add-ons for that scale? For example:
* **Enhanced data privacy** or dedicated processing terms.
* **API call packages** beyond what's included with the seat. Our use case is heavily automated, so we'll need to factor in potential API usage costs on top of the seat license.
* **Support SLA levels.** We'd likely need a business-level support agreement.
* **Implementation & onboarding:** Is professional services/onboarding a separate line item, or is it typically rolled into a larger package?
A rough ballpark or percentage over the "sticker price" would be incredibly helpful. I'm trying to build a realistic business case, and hidden costs are the number one thing that gets projects like this shelved six months in.
If it helps, here's a snippet of the kind of logic I'm budgeting for, which will drive our token usage:
```javascript
// Example of a daily automated workflow per user
for each user {
// 1. Analyze latest support emails (avg 2 emails of 500 chars)
let analysisPrompt = `Summarize key issues: ${emailText}`;
// 2. Generate a CRM update (avg 300 chars output)
let crmUpdatePrompt = `Create internal note from analysis: ${analysis}`;
// 3. Categorize for dashboard (avg 100 chars output)
let categorizationPrompt = `Assign category: ${analysis}`;
}
// This needs to be multiplied by 100 users, per day.
```
Any insights, gotchas, or even just your own negotiation experience would be a huge help. Thanks in advance for saving me from some future headaches!
-- Ian
Integration Ian
That's a great point about list price versus real price. I'm in a similar boat trying to budget for my team, though a bit smaller.
For your API-driven focus, have you checked if the per-user license covers the API call volume you'll need? I've seen a few platforms where the seat license is separate from API usage tiers, and that can add a big chunk if you're automating heavily. It's worth asking their sales about overage charges.
Also, don't forget to budget for any training or onboarding hours. It's not always included.
You're focusing on the right things. The public per-user rate is almost irrelevant for an enterprise deal.
For a 100-seat annual commitment, you should expect a discount off the list price, but the real negotiation starts with the API quotas. Your seat license will include a base API call volume, but at 100 users automating workflows, you will exceed it. You need the pricing schedule for overages, and you must define those quotas in the contract. Missing that is how you get a bill 3x your forecast.
On add-ons, data privacy features for handling CRM/support ticket data are often a separate SKU. So is any contractual commitment around data residency or encryption key management. Budget 15-20% on top of the negotiated seat+API cost for those.
Where is your SOC 2?
You're right to focus on the annual commitment and add-ons, as those are the primary cost drivers. However, I'd push back slightly on the idea of a "noticeable" discount for an annual contract. For a 100-seat deal, you're often trading a modest discount (maybe 10-15%) for a significant contractual lock-in on API quotas. The real leverage comes from negotiating those quotas upfront, not from the seat price itself.
On volume tiers, the public tiers are typically firm for the per-user license, but the associated API call packages are negotiable. The add-on list you're hinting at is accurate. Enhanced data privacy and residency will be separate line items. You should also explicitly ask about the cost of a dedicated support channel or SLA, which often becomes mandatory at your scale and isn't included in base enterprise pricing.
My advice is to build your internal cost model based on projected API call volume per user per month, then use that as the basis for negotiation. The seat license becomes almost a fixed admin fee; the variable API overages and required add-ons are where the total cost balloons. Without that call volume model, you cannot get a realistic figure.
—KM