ServicesCoding agent cost review
Coding agent cost optimisation, starting with one team
Cloudsail, an AI engineering company with engineers in Germany and Poland, finds out where one team's coding agent spend goes and cuts it without hurting code quality. The review ends with a written result that your team keeps.
The review in four steps
- 1
We read the usage and billing exports and set a baseline on changes the team has already merged.
- 2
We find the largest costs by tool, model and type of task.
- 3
We change defaults, routing and budgets together with the team.
- 4
We measure the same kind of work again and write down what changed, what it saved and what comes next.
What you receive
Everything is written down and stays with your team, whether or not you work with us afterwards.
- Spend by tool, model and type of task for the team in the review.
- The changes made with the team: default models, routing, context settings and budgets.
- Cost per merged change before and after, with review effort and rework checked on the same kind of work.
- A plan for the next teams: what to roll out, in which order, and what to measure.
How the review runs
First we read the usage and billing exports, talk to the engineers about how they work, and replay a sample of changes the team has already merged. That gives the baseline: what a merged change costs today, and how much review and rework it needs.
More detail
Next we change defaults together with the team, such as which model handles which kind of task, how much context an agent loads and where budgets sit.
Then we measure the same kind of work again. A change stays only if the cost falls and review effort and rework do not rise. The review ends with the written result and a rollout plan for the next teams.
What we need from you
- One team that already uses Claude Code, Cursor, GitHub Copilot or OpenAI Codex.
- Usage and billing exports from those tools, or read access to their admin consoles, and, to replay merged changes, access to the team's repository or a code snapshot your team provides. We need no production data.
- A named contact in the team, and an hour with the engineering lead at the start and at the end.
- A confidentiality agreement, if you want one before we start.
Would you like to talk this through for your own case? The first call is free and takes 30 minutes.
Book a 30-minute callMeasured by team, not by person
We report by team, tool, model and type of task, and we do not rank individual engineers. Finding the savings rarely needs it. In German companies, measuring individual people can also require the works council's agreement before anything starts.
After the review
The review stands on its own, and you decide what follows once you have the result. If you continue, the services below cover the rollout to more teams, ongoing cost controls and training on your own code.
Questions
What does the review cost?
A fixed price, agreed in writing before we start. It depends on the size of the team and the number of tools, and we quote it after a first 30-minute call.
Do you need access to our code or production systems?
For the code, yes. To replay changes the team has already merged, we need access to the team's repository or a code snapshot your team provides. Before work starts, we agree that access and the replay environment with you, and we work inside your environment and under your rules. We need no production data. If you prefer, your team runs the usage and billing exports and sends them to us.
Which tools does the review cover?
Claude Code, Cursor, GitHub Copilot and OpenAI Codex, including models you run through your own cloud account.
Will cutting the cost hurt code quality?
Each change is checked on the same kind of work before and after. If review effort or rework rises, the change does not stay.
Is there a free first assessment?
Yes. In a 30-minute call you can share an aggregated usage or billing export, or show us your admin dashboard on screen. We need no access to your systems, and you leave with a first view of where the money goes and whether a review is worth it.
Does the works council need to be involved?
Often, if you have one. Usage dashboards can show what individual engineers do, and in Germany tools that can monitor behaviour or performance fall under the works council's co-determination rights in section 87 of the Works Constitution Act. We report by team, leave individual data out and describe what we collect in a form you can take to the works council. This is not legal advice.
What happens to our data?
We work from usage and billing exports and from changes the team has already merged, inside your environment and under your rules. Where we process personal data on your behalf, we sign a data processing agreement (in Germany, an AVV) before we start.
In which languages do you work?
English, German or Polish, remotely or on site in Germany and Poland.
Related services
LLM cost optimisation
Agent spend broken down by team and task, then lowered through defaults, budgets and routing your platform team can run.
Coding agent adoption
Agents taken from a few pilot teams to the rest of engineering, with training and one shared setup.
Evaluations on your repositories
Tools, models or settings tested side by side on changes you have already merged, before you commit to one.
Claude Code training
Workshops where your engineers practise Claude Code on their own repositories and backlog tasks.
From the blog
Coding agent cost calculator
Seats, usage beyond the seat and review time for your own team at the vendors' list prices, with the cost per merged change worked out for you.
What a coding agent rollout costs
Seat prices for 50 engineers on Claude Code, Cursor, GitHub Copilot and Codex, why usage and review time often cost more, and how to budget per merged change.
Coding agents compared for teams
Claude Code, Cursor, GitHub Copilot and OpenAI Codex side by side: plans, usage billing, models, instruction files, data handling and when each one fits.
LLM cost allocation
How to explain an LLM bill by team, task and accepted outcome: tag requests at the gateway, price them as you are invoiced, allocate shared costs by a stated rule and reconcile with finance every month.
Talk to an engineer
Tell us which tools your team uses. In a 30-minute call, an engineer will tell you whether a review makes sense for you.
Booking runs on Google Calendar.

Mickey Graf
Founder and CEO of Cloudsail
Prefer to write first? Leave your email and a few lines. Mickey reads every message himself and replies by email with times for a call.
Look for the draft in your email program
Send it from there, and Mickey replies in person with times for a 30-minute call. If no draft has opened, write to us at miki@cloudsail.com.