Limiting what a team may spend in a year did not simply reduce budgets. It changed the fundamental question engineering departments answer, from what is possible to what is worth doing.
Development became a zero-sum choice
Under unlimited spending, a promising idea could be pursued alongside everything else, and the only cost was time.
With a cap, every upgrade consumes budget that another upgrade cannot use, so each project must be justified against alternatives rather than on its own merit.
Teams therefore run internal comparisons in performance per unit of cost, which is a metric that barely existed when spending was open-ended.
Damage now carries a development cost
Repairing or replacing crashed components draws on the same limited budget as new parts.
A season with several heavy accidents can consume the money that would have funded an upgrade, so a driver's incidents affect the car's performance months later.
This has changed how teams discuss risk with drivers, and it is why aggressive moves in low-value situations are discouraged more explicitly than they used to be.
Simulation replaced physical iteration
Building and testing a part physically is expensive, so teams push further into computational analysis before committing to manufacture.
Wind tunnel and simulation time are separately restricted and allocated inversely to championship position, which gives trailing teams more of the resource.
The combined effect is that development throughput is now limited by allocated hours rather than by how much a team can afford to build.
Abandoning a season became rational
If a car is fundamentally uncompetitive, spending the cap on improving it delivers little, while spending it on the following year's design may deliver a great deal.
Teams therefore stop developing mid-season more openly than before, accepting poor results in exchange for a stronger starting point.
This is visible in the second half of most seasons, when the order among midfield teams shifts according to who stopped first.
Why enforcement is complicated
Teams sit inside larger businesses, and separating what counts as team expenditure from group activity requires detailed accounting rules.
Marketing, driver salaries and certain staff are excluded, and the boundaries around those exclusions are where disputes arise.
Penalties can include reduced testing allocation as well as fines, which makes a financial breach a sporting disadvantage rather than merely a cost.