A CTO or founder building a budget for engineers or a project needs numbers that hold up under scrutiny. A single headline rate rarely survives that test. These software development cost guides exist for that moment: when a budget has to leave a spreadsheet and stand in front of a board, an investor, or a finance lead who wants to know where the figure came from.
The collection spans the whole budget, from the headline rate down to the layers most estimates skip. It breaks down what it costs to hire a senior developer in Europe by country, and the costs that sit on top of salary before a number becomes a real bill. Mobile developer rates get their own guide, because mobile hiring runs on a different market with different scarcity. MVP cost gets one too, for a founder scoping a first build. Staff augmentation pricing is compared across vendors for a CTO weighing external partners, estimation methods turn a rough scope into a number a team can commit to, and cloud migration cost includes the labour behind the cloud bill alongside the infrastructure line items.
Every one of those topics hides a layer the headline number skips. Salary is not payroll cost. A vendor's advertised rate is not what a client ends up paying once overhead and margin are added on top. An estimate built from a feature list behaves differently from one built with the team that will actually do the work. A cloud migration budget that counts only compute and storage has already missed the engineering hours spent moving, testing, and cleaning up after the move.
The guides here share one stance. Every figure states whether it is a bill rate or a pay rate, and where a margin sits on top of a number, that margin gets named instead of folded in. A rate with its margin disclosed lets a buyer compare it against another rate on equal terms. A rate without its margin disclosed is not a price; a buyer who accepts it is negotiating without knowing where the other side's floor sits. Knowing which side of that line a figure falls on, before it goes into a budget, keeps that budget accurate months later, when it actually gets tested against real invoices.
Every cost and rate guide
- Section 174A and a European engineer: the real US cost: Domestic R&E is deductible again under 174A; work done in Europe still amortizes over 15 years. What that does to a European engineer's after-tax cost.
- Cost of employing a developer in Switzerland (2026): What a CHF 130,000 developer costs a Swiss employer in 2026: AHV, ALV, the age-banded BVG pension, and the break-even against a nearshore contractor.
- Cost of employing a developer in the Netherlands (2026): What a €70,000 developer costs a Dutch employer in 2026: holiday pay, premiums, pension, sick pay, and the 30% ruling cut to 27% in 2027.
- Unexpected cloud bill: the first 48 hours: Find the source, stop it, rotate the key, then ask AWS or Google Cloud to review the charge. Budgets don't cap spend, so name an owner.
- LLM API costs higher than your AI feature earns: cut, reprice or cap?: The AI feature's LLM bill is above what it earns. Price the levers with real token math: routing, caching, batch, caps or a price change, and who does it.
- AWS credits running out? Your first real bill and what to cut first: AWS, Google and Azure credits end on a date, not a balance. Forecast the first paid bill, cut before it lands, and decide who does the work.
- A recruiter quoted a fee for your senior engineer: what the contract gives back, and when another route costs less: Recruiter fee for a senior engineer: what published agency contracts charge and refund, and what contract-to-hire costs on the same salary.
- Your AI coding bill blew the budget: cap it, cut seats, or fund a hire?: AI coding overage landed? Find where the spend goes, set Copilot, Cursor and Claude Code caps, decide seats, and judge when the money buys an engineer.
- Capitalized software development costs: IFRS vs US GAAP and outsourced engineers: How to capitalize software development costs under IAS 38 and ASC 350-40 after ASU 2025-06, and how to treat nearshore contractor invoices.
- Software development team cost in Europe: a 2026 guide: What a software development team costs in Europe: employer cost, contractor and vendor pricing, margin, hidden costs and AI tools, with sources.
- How to evaluate an MVP development quote: a line-by-line check: Read an agency's MVP quote line by line: hours by role, implied hourly rate, exclusions, change requests and IP terms, with European rate benchmarks.
- In-house vs nearshore developer cost: the employer-side math: In-house developer vs nearshore cost: employer contributions, recruiting and notice terms worked for Germany and Poland, set against a nearshore rate.
- Monthly vs hourly developer billing: what a real month costs: Monthly vs hourly developer billing: how holidays, overtime, partial months and notice change the bill, and the utilisation where each model costs less.
- AI coding tools cost per developer vs. hiring one: Copilot, Cursor, Claude Code and JetBrains AI list prices vs a senior engineer's real cost, plus what Jellyfish, METR and DORA actually found.
- Software development cost estimation: 5 methods (and how the number changes): Bottom-up, analogous, three-point, COCOMO and function points explained, with a worked example of how team model and rate change your total.
- Cloud migration cost in 2026: the cloud bill and the labor behind it: Cloud migration cost has two budgets: the cloud bill and the engineering labor to move it. Real 2026 ranges, sourcing options, and rate math.
- Cost to hire a senior developer in Europe in 2026 (by country)
- Cost to hire a mobile app developer in Europe: rates & hiring guide
- Cost of an MVP in Europe - full guide
- Staff augmentation pricing 2026: 6 vendors, real rates
FAQ
How should a CTO budget for engineering capacity when the scope isn't final yet?
Budget in ranges tied to confidence rather than a single number pulled from a rough scope. A range built from an early estimate should widen for anything not yet designed and narrow only once a team has broken the work into pieces it actually understands. Treat the first number as a planning input for stakeholders, not a commitment the team gets held to later.
What's the biggest mistake founders make when estimating software project costs?
Founders anchor on a headline rate or a vendor's quote and stop there, without asking what sits underneath it. A rate rarely includes everything: recruiting, management overhead, tooling, and the ramp time a new team needs before it ships at full speed. Building a budget around the headline number alone all but guarantees a mid-project surprise.
How do hidden layers like margin and overhead change a capacity budget?
Margin and overhead sit between what an engineer earns and what a buyer pays, and skipping them turns a budget into a guess dressed up as a plan. A buyer who knows the margin on a rate can judge whether it is fair and can negotiate from an informed position. A buyer who does not know it is trusting the vendor's math without a way to check it.
