Windsurf Teams isn't
"$40 per user."
Glance at the price sheet and Windsurf's Teams plan looks like a flat per-head rate. The real structure is two layers: an $80/month base plus $40/month per seat. As headcount grows, the "sticker price" and the actual bill drift apart. Worth running the real numbers before it goes into a budget request.
It only looked like
"$40 per user"
Open the pricing page for the AI coding tool Windsurf and the first thing you see is a list of plan numbers. windsurf.com shows the Teams plan alongside the individual Pro plan in a way that reads as "about $40 per person," and at a glance it's easy to assume a simple flat rate multiplied by headcount. When a team lead first sketches a budget, the back-of-envelope math is almost always "$40 × number of people."
The actual billing structure isn't that simple. Windsurf Teams is built as an $80/month base plus $40/month per seat, not a flat "$40/user" rate. Whether one person uses it or five, the $80 base applies first, and per-seat charges stack on top. Laid side by side, the assumption and the actual bill diverge like this:
| What it looks like | What you're actually billed |
|---|---|
| Determined by $40 × headcount alone | Determined by $80 base + $40 × headcount |
| Same $40 rate whether 1 or 5 seats | Fewer seats means a higher effective rate above $40 |
| Budget = $40 × seats is a valid estimate | That estimate always undershoots by the base fee |
Reading it as "$40 per user" gets
further from the truth the smaller your team is.
Plug in a headcount,
see the real bill
The $80/month base is a fixed cost sitting on top of everything. The fewer seats, the further the effective per-seat rate drifts from $40.
The formula is simple: monthly cost = $80 + $40 × seats. Windsurf's pricing page does spell this out, but it's the kind of detail that's easy to miss if you only skim the plan headline. At 5 seats that's $280/month (+40% versus a headcount-only estimate), at 10 seats $480/month (+20%), at 25 seats $1,080/month (+8%). Annualized, a 10-seat team that took "$40 × headcount" into a budget request would be off by $960 a year from the actual bill.
The base fee's weight fades as headcount grows, but it never disappears. Even at 50 seats the effective rate is still $41.60 — never quite $40. In other words, the structure rewards scale and penalizes small teams by design.
Who feels this,
and how
The impact differs by role — here's what to watch for in budgeting, rollout, and vendor comparisons.
Finance and management building the budget
Take a "$40 × headcount" figure into a budget request and the real bill will always come in higher. The gap is proportionally larger for small teams, so any company piloting with 5-10 seats should confirm the real number before it's approved.
PMs and IT running the rollout
The $80 base keeps applying no matter how many seats come and go. Because cutting headcount doesn't dramatically cut cost, it's worth estimating the eventual steady-state team size during the trial, so you avoid mid-contract churn later.
Anyone comparing tools side by side
Competitors like GitHub Copilot and Amazon Q Developer tend to read closer to a flat per-seat number, so a Windsurf-only base fee can make it look "more expensive" in a naive side-by-side. Always normalize comparisons to the same headcount before drawing conclusions.
Before it goes into
a budget request
Simulate at your real headcount
Run "$80 + $40 × n" for candidate seat counts (say, 5, 10, and 25) and put it next to the "$40 × n" estimate. That gap is exactly the error that would otherwise land in the budget document.
Model growth and shrink scenarios too
Apply the same formula assuming headcount rises or falls in six months. Because the base fee applies regardless of seat count, it also matters for any downsizing or cancellation decision.
Ask about custom pricing at scale
The base fee's impact shrinks as contract size grows. For anything beyond a few dozen seats, it's worth asking the vendor for a volume-based quote rather than relying on the public plan table alone.
Pricing is getting more
complex industry-wide
AI coding tool pricing has gotten noticeably more complex in the past few months. GitHub Copilot's terms shift with every model addition, and tools like Amazon Q Developer/Kiro lean toward usage-based billing. Claude Code has also revised its usage limits — a sign that "price per person" is no longer a single number you can compare across vendors at a glance. Windsurf Teams' "base plus seats" structure is one example of that broader shift.
To be fair, the $80/month base fee is a design that becomes relatively lighter at scale. For a company deploying hundreds of seats, it will fall within rounding error, and Windsurf may well offer custom quotes or volume terms that aren't visible here. This analysis applies the published price sheet's numbers mechanically; it doesn't account for promotional pricing or a negotiated contract rate. Always confirm the current published price before signing.