What Cursor actually restructured on June 24 and why the FY27 AI-IDE spend policy has to catch up
Cursor shipped a Teams pricing overhaul on June 24, 2026 — new customer signups run against the new plan immediately, and every renewing team crosses over on the July 1 billing cycle. Three load-bearing changes ship together: every Standard seat is split into two usage pools (Composer/Auto for first-party Cursor models including Composer 2.5, and Third-Party API for the Claude / GPT / Gemini fleet); a Premium seat lands at 5× the included usage for 3× the cost, positioned against the agents-running-all-day workload class; and the how-do-I-explain-this-line-item-to-my-CFO problem the prior single-pool credit model created gets a per-pool-envelope answer the standing FY27 IDE contract can grade against.
The operationally important reads:
- The dual-pool split is the real news, not the Premium seat. The prior single-pool model let a team burn its entire month's included usage on a single week of heavy Opus-tier coding-agent runs — every FY27 IDE spend policy that grades against the per-seat monthly credit envelope was running against a spend variance the single-pool model amplified. The split pool gives the Composer/Auto workload class its own envelope and the Third-Party API workload class its own — the FY27 spend forecast the finance team drafted against the prior model grades against a variance envelope the new model closes.
- Composer 2.5 is the load-bearing substrate the Composer/Auto pool grades against. The Composer/Auto pool's generous headroom is Cursor's bet that the first-party substrate can carry the default-routing coding-agent workload class at a per-token cost the third-party frontier tier cannot match. The team whose per-prompt routing policy still defaults to Claude Sonnet 5 or GPT-5.6 Terra on every coding-agent turn is paying third-party-API-tier rates for a workload class the Composer 2.5 substrate covers inside the first-party pool.
- The Premium seat prices the agent runs all day workload class explicitly. The 5×-usage-for-3×-cost math is Cursor's read on which per-seat workload class carries the tail of the concurrency distribution. The engineering team whose top-10% of seats runs coding-agent loops eight hours a day grades against a per-seat cost envelope the Standard seat's included pool cannot underwrite; the Premium seat is the answer to that specific workload class, not a general upgrade path.
- The July 1 billing cycle is the FY27 IDE contract renegotiation clock. Every renewing team crosses over on the July 1 cycle — the standing contract on the AI-IDE line item gets its shape rewritten on the same day the frontier-model pricing (Sonnet 5's introductory rate through August 31) is still in the negotiation window. The FY27 spend policy update the team ships this quarter runs against the intersection of both surfaces, not against the IDE surface alone.
The structural read isn't Cursor changed its pricing again. It is that the AI-IDE spend line item now grades against per-workload-class-pool-envelope math, the Composer 2.5 substrate collapses the per-token cost of the default-routing coding-agent tier, the Premium seat prices the tail-of-the-concurrency-distribution workload class explicitly, and the FY27 IDE contract needs a per-pool-envelope clause the prior standing contract does not carry.
What the dual-pool split restructures for the FY27 AI-IDE plan
The per-seat spend forecast splits by workload-class-pool-envelope, not by aggregate credit envelope. The prior single-pool credit model gave the finance team a per-seat monthly credit envelope that grouped Composer, Auto, Claude, GPT, and Gemini spend into a single line item. Every internal spend chargeback the platform team was writing had to reconstruct the per-model attribution from the underlying usage logs. The dual-pool split gives the FY27 chargeback model two first-class envelopes to run against — Composer/Auto workload class and Third-Party API workload class — and lets the per-workload-class spend forecast grade against a per-pool envelope the invoice reports natively.
The per-prompt routing policy grades against the pool-envelope-arbitrage the new pricing opens. The routing-policy artifact the platform team owns needs the default-route-through-Composer-2.5 update on the coding-agent workload classes whose accuracy envelope Composer 2.5 closes. Every workload class whose FY27 routing decision was made at Composer 2.4 accuracy is a candidate for re-shootout against Composer 2.5 accuracy inside the July window; the workload classes whose accuracy envelope the first-party substrate does not close stay on the Third-Party API pool with the per-pool budget the FY27 plan grades against.
The Premium seat count is a tail-of-the-distribution decision, not a top-of-the-org-chart decision. The FY27 IDE plan the team writes against the new pricing needs to identify the seats whose per-week concurrency runs the coding-agent loop at eight hours a day — those seats are the Premium seat candidates. The senior-engineer count and the Premium-seat count are not the same axis; the concurrency-tail axis grades against the per-seat throughput the coding-agent loop produces, not the org-chart position the seat is assigned to.
The standing IDE contract needs a per-pool overage clause the prior contract does not carry. The single-pool overage clause the FY27 procurement plan was written against does not survive the dual-pool split. The per-pool overage rate the standing contract needs — Composer/Auto pool overage rate versus Third-Party API pool overage rate — is a first-class negotiation input the procurement function has to add inside the July 1 window, not a defer-to-Q4 line item.
Where the pricing update is signal and where it is noise
Signal: the significantly more headroom at the same price framing is directionally right for teams that route heavily to Composer/Auto. The Composer/Auto pool is generous by design — Cursor's bet is that the first-party substrate covers the default-routing coding-agent workload class at a per-seat cost the Standard seat can underwrite. Teams that ship the routing-policy update to default to Composer 2.5 on the coding-agent workload classes whose accuracy envelope Composer 2.5 closes read the same per-seat cost envelope as a spend improvement.
Signal: the deprecation of the prior Ultra plan and the reshaping of Business into the new Standard-and-Premium split is a hard renegotiation trigger. Every team on the prior Ultra / Business / Team plans crosses over on the July 1 billing cycle; the standing contract on the AI-IDE line item gets its shape rewritten on the same date. The renegotiation clock the standing contract runs against is the July 1 cycle, not the FY27 procurement-cycle nominal deadline.
Noise: the Premium seat replaces the Standard seat for real developers framing overshoots the shift. The Premium seat is the pricing for the tail of the concurrency distribution, not the shift from Standard to Premium as the new default. The FY27 seat mix stays majority-Standard for every team whose per-seat concurrency distribution has a fat middle, not a fat tail; the Premium-seat count is the top-decile line item, not the mid-team line item.
Noise: the third-party frontier tier stops mattering is the wrong read. The Third-Party API pool stays on the plan because the workload classes where Claude Sonnet 5, GPT-5.6, and Gemini 3.5 Flash close accuracy envelopes the Composer 2.5 substrate does not close still route through the pool. The dual-pool split does not deprecate the third-party frontier tier; it prices it as a separate workload class with its own per-pool budget the FY27 plan grades against.
What the engineering and finance functions should do inside the next two weeks
Run the per-workload-class shootout on Composer 2.5 against the Third-Party API frontier tier inside two weeks. For the team's top-three coding workload classes (multi-file refactor against explicit test contracts, dependency upgrade against explicit version pins, structured extraction against deterministic schema), measure per-class pass-rate, per-class time-to-completion, per-class per-token cost, and per-class per-pool-envelope consumption on both substrates. The output is the routing-policy update artifact the FY27 IDE spend plan grades against.
Rewrite the per-seat spend chargeback model against the dual-pool envelope. The platform team's internal spend chargeback needs the per-pool envelope split as a first-class attribute — Composer/Auto workload class chargeback and Third-Party API workload class chargeback — the aggregate credit envelope stops being the chargeback input. The FY27 chargeback model grades against the per-pool envelope the invoice reports natively; the reconstruction-from-usage-logs step the prior model forced becomes a delete-code refactor.
Identify the top-decile-concurrency seats and grade them against the Premium seat math. The seats whose per-week concurrency runs the coding-agent loop at eight hours a day are the Premium seat candidates. Pull the per-seat concurrency distribution from the last two months of usage logs, identify the top-decile of seats by concurrency, and grade the Premium seat's 5×-usage-for-3×-cost math against the identified seats' per-week overage rate on the prior single-pool model. The Premium seat is a positive-NPV upgrade for the seats whose per-week overage rate the math closes; for the seats whose overage rate the math does not close, the Standard seat with the new dual-pool envelope stays the shape.
Renegotiate the standing IDE contract with per-pool overage clauses inside the July 1 window. The procurement function's standing IDE contract needs the per-pool overage rate clause as a first-class attribute — Composer/Auto pool overage rate and Third-Party API pool overage rate are separate line items, not a single blended rate. The negotiation clock is the July 1 billing cycle; the standing contract that renews at the new pricing without the per-pool overage clause forces the FY27 spend forecast against a single-blended-rate variance envelope the new pricing does not carry.
What the Cursor Teams update cheapens but does not replace
The Cursor Teams update compresses the per-token cost of the default-routing coding-agent tier through the Composer/Auto pool and prices the tail-of-the-concurrency-distribution workload class through the Premium seat, not the senior judgment of deciding which coding workload classes route to Composer 2.5, which route to the Third-Party API frontier tier, which seats grade against the Premium seat math, and which per-pool overage clauses the standing IDE contract underwrites. The teams that confuse the cheapened per-seat cost for cheapened judgment ship the routing-policy update against a single-pool assumption the new pricing does not carry, read the per-cycle finance post-mortem on the per-pool overage variance the standing contract does not close, and eat the Premium-seat mis-assignment cost the concurrency-distribution shootout would have caught. The teams that keep the senior judgment at the center of the AI-IDE decision translate the pricing shift into per-quarter throughput improvements the prior single-pool model could not produce.
The AI-IDE question is no longer which IDE does the team pay for; it is which per-workload-class pool the coding-agent surface routes through, which per-seat concurrency-distribution class the seat mix grades against, and which per-pool overage clause the FY27 standing IDE contract underwrites against the July 1 renegotiation window.
At SONNET CODE we run the AI Development engagement against the per-prompt routing policy and per-seat concurrency-distribution artifact — per-workload-class shootouts on Composer 2.5 versus the Third-Party API frontier tier, per-pool spend chargeback models on the FY27 IDE line item, and per-cycle standing-contract renegotiations against the per-pool overage envelope. If your team's IDE spend policy is still written against the single-pool credit envelope, schedule a call — we'll walk you through the FY27 AI-IDE plan update we ship inside one sprint, ahead of the July 1 billing cycle crossover.
