I am conducting a comparative analysis of CI/CD platform pricing models, with a specific focus on high-volume, enterprise-scale usage patterns. The standard, publicly available pricing tiers for platforms like CircleCI become increasingly problematic at scale, as costs scale linearly—and sometimes exponentially—with concurrent workloads and compute minutes.
My primary inquiry is whether any members of this community have successfully engaged CircleCI's sales team to negotiate a custom, enterprise-wide rate structure. The public "Scale" plan offers some volume discounts, but I suspect there is significant room for negotiation beyond that facade, particularly when committing to annual contracts or guaranteed monthly minimums.
I am particularly interested in the concrete contractual and pricing levers that were available. For instance:
* **Discount Structure:** Was the negotiation based on a straight percentage discount off the published compute-minute rate, or did it involve a complete restructuring of the pricing model (e.g., a flat fee per developer seat with unlimited or pooled compute minutes)?
* **Commitment Terms:** What was the minimum annual commitment (in USD or compute minutes) that unlocked these custom rates?
* **Concurrency Cap Handling:** How were overages on concurrent containers handled? Was a true "burst" pricing model agreed upon, or were additional "blocks" of concurrency purchased at a progressively discounted rate?
* **Contractual Safeguards:** Were any clauses related to annual price increases (e.g., a cap of 3-5%) successfully included?
From my own preliminary modeling, the cost divergence between list price and a hypothetical negotiated rate becomes stark at around 5 million compute minutes per month. Using the public `large` resource class (2 vCPUs, 8GB RAM) at $0.036/minute:
```
List Price Monthly Cost: 5,000,000 min * $0.036 = $180,000
Annual List Price: $180,000 * 12 = $2,160,000
```
A mere 20% discount would yield an annual savings of $432,000, which justifies significant procurement effort. I have heard anecdotal evidence of discounts ranging from 15% to 40% for large, multi-year commitments, but I lack verifiable data points.
Any detailed insights—especially regarding the initial ask, the negotiation process, and the final agreed-upon unit economics—would be invaluable for my ongoing total cost of ownership framework. Please share any non-confidential specifics you can.
Show me the bill.
CostCutter
I pushed them hard on the "Scale" plan discounts being mostly smoke and mirrors. Yes, you can negotiate, but forget about a flat fee per seat with unlimited compute. That's a non-starter.
The levers you have are:
* A straight percentage discount off the list price for compute minutes, based on a committed annual spend. We got 22% off after guaranteeing $350k/year.
* Slight concessions on the per-seat cost for the orchestration layer if you have a huge team.
The real fight is over minimums and true-ups. Their standard contract wants to bill you for any overage monthly. We insisted on a quarterly true-up, so you only pay for what you actually used beyond the commitment at the end of each quarter, not every month. That alone saved us from some nasty surprise bills.
Exactly the questions I'd ask. The other poster nailed the main levers. The commitment term is your biggest weapon.
> the concrete contractual and pricing levers
To add to that, you can also push on the "resource class" definition. Their standard pricing for the high-performance instances is brutal. We got a slightly better rate on those by arguing that most of our guaranteed spend would be on those machines, so they should discount the premium. It wasn't huge, but it moved the needle.
Also, get everything in the MSA. The "standard" terms about data processing and indemnification are... aggressive. Make sure your legal team has a red pen ready. We spent more time on the contract language than on the price.
It's not marketing, it's logic.
That's a really good point about the MSA. We're a much smaller shop, but when our legal team saw the standard data processing addendum, they flagged several clauses that were a hard no for us, especially around audit rights and data location. It added weeks to the process.
> slightly better rate on those by arguing that most of our guaranteed spend would be on those machines
We tried a similar angle, but for us, it was about standard Linux vs. Windows resource classes. The Windows premium is steep, and we managed to get that differential reduced a bit. It seems like they're more flexible on the *spread* between classes than on the absolute base price.
Did you find their sales team was familiar with the legal details, or did you constantly have to loop in their contracts people?
Oh, the annual GAM with quarterly reconciliations is the only sane way to do it. That's the real win. But don't let that SQL snippet fool you into thinking the discount is as clean as they're making it sound.
The devil is in how they define "committed spend" for the discount application. Is it against the full list price of every resource class, or just the base Linux VM minute? In our case, the negotiated discount only applied to the base rate, not the resource class multiplier. So your 25% off that 6 cents means nothing when you're actually running on the 4x "large" instances most of the time. You're still paying the full multiplier premium on the discounted base, which is where the real cost is.
Also, watch for the "effective rate" calculation if you dip below your commitment. Some of these agreements claw back the discount on the entire quarter's usage if you don't hit the pro-rated minimum, which can turn a mild underage into a massive bill surprise.
Your k8s cluster is 40% idle.