Why are infrastructure, third-party, and operations costs separate from software development?
Development pays for a defined delivery. Infrastructure and third-party charges pay for resources that continue to be consumed. Operations fees pay for continuing response and reliability work. None disappears when the code is accepted, and none should be estimated as one fixed percentage of development. Wavesteam separates them so the client can forecast, own, renew, optimize, or stop each item knowingly.
Software depends on compute, storage, networks, domains, certificates, external APIs, and operational attention. Cloud instances keep billing, SMS and model calls follow use, dependencies develop vulnerabilities, and suppliers change interfaces after development ends. An “all-inclusive build” hides what must renew in year two, who controls the account, and what breaks if it stops.
| Cost | What it purchases | Driver | Immediate effect if stopped | Original bill |
|---|---|---|---|---|
| Development delivery | Discovery, design, code, testing, migration, release, documents | Work packages, roles, scope, risk | Agreed construction stops | Development provider |
| Infrastructure | Compute, database, storage, CDN, backup, logs, network | Runtime, size, requests, egress, region | Degradation, outage, or unavailable data | Cloud/host in client account |
| Business APIs | SMS, maps, payment, logistics, identity, AI, messaging | Messages, calls, tokens, transaction value, seats, plan | Related capability is limited or unavailable | Third party in client account |
| Operations and reliability | Monitoring, release, patching, recovery, on-call, incident review | Coverage, SLO, systems, changes, tickets | No promised detection or recovery response | Operations provider |
| New iteration | New processes, changing rules, UX and performance improvement | Work package or team capacity | Product retains current capability | Development provider |
Warranty is separate again: it corrects a failure to meet the signed acceptance baseline for an agreed scope and period. It is not free operations and does not include new requirements. Even without features, certificates renew, backups need restore testing, security patches arrive, and provider APIs change.
When defining budget, scope, and cost assumptions, also compare Is pre-contract discovery free, and does accepting a proposal lock us in? and How should software maintenance and operations be priced?; the linked guidance adds context that should be considered in the same decision.
Forecast from business volume
A monthly model is fixed resources + Σ(usage × current rate) + operations service + peak/risk allowance. Show baseline, growth, and peak scenarios with currency, region, taxes, discount expiry, and retrieval date.
Active users, requests, and concurrency drive compute and data services; images, video, and audience region drive storage, CDN, and egress; successful verification, delivery, or AI tasks drive APIs; retention and recovery targets drive backup and replication; and coverage plus incident requirements drive monitoring and staffing. Report business units such as cost per successful order or AI task, not only technical request totals.
Google Cloud Pricing Calculator and AWS Pricing Calculator can model list-price resources, but only under the entered assumptions. They do not replace architecture tests, actual bills, or a negotiated agreement. The FinOps Framework adds allocation, forecasting, and unit economics so technical consumption can be connected to product value.
Separate first-year and renewal views
The first year combines one-time delivery, migration, release, production resources, third-party volume, and post-launch operations. A renewal view retains resources, APIs, domains and certificates, operations, and planned iteration. Show what happens when free tiers or introductory discounts expire. Separate production and test spending and automatically stop or remove unused environments where safe.
Wavesteam quotes its engineering service separately from supplier charges, while production cloud and API accounts normally belong to the client. We can forecast demand, configure alerts, and reduce unit cost, but we do not hide marked-up external bills inside a maintenance fee. The handover register identifies owner, renewal date, data location, alternative, and shutdown effect for every continuing service.