The Bill You Did Not Budget For
The conversation about custom software cost almost always centres on one number: what does it cost to build? Business owners compare quotes, negotiate scope, and sign contracts — all focused on the build phase. Then the software launches, and a new category of invoices begins arriving.
Hosting. Database fees. Security updates. Dependency upgrades. The API service that was free during development and now costs money at production volume. The small feature request that seemed simple but required a developer for a week. The emergency fix when a third-party service changed its interface without notice.
Industry research consistently finds that 60–80% of software's total lifetime cost occurs after the initial build. A $50,000 custom application may consume $30,000–$40,000 per year in post-launch costs once you account for everything. Most business owners are not told this before they sign. This post is meant to change that.
Infrastructure and Hosting: Your Monthly Baseline
Every custom application needs somewhere to run. Cloud infrastructure — servers, databases, storage, content delivery, backups — is an ongoing operating cost that begins the day you go live and does not stop.
For a small business application with modest traffic, expect a baseline of $100–$500 per month on AWS, Google Cloud, or Azure. Applications with meaningful user volume, real-time features, or data-intensive processing can run $1,000–$5,000 per month or more. If your agency deployed your application on their own infrastructure rather than yours, that monthly bill may be coming directly from them — with a markup.
The variables that drive this cost up fastest: file storage for user uploads, video processing, high-frequency database queries, and AI API calls made on behalf of your users. All of these are usage-based — they are cheap in testing and expensive when real customers start using your product.
Key Takeaways
- Cloud infrastructure costs begin at launch and do not stop — budget $100–$5,000/month depending on scale
- Usage-based services (storage, AI APIs, video) are cheap in development and expensive in production
- If your agency hosts your application on their infrastructure, clarify ownership and monthly costs before launch
- Ask your agency to model infrastructure costs at 10x and 100x current usage before you go live
Maintenance Is Not Optional — It Is the Product
Software does not sit still. The operating systems, programming language runtimes, frameworks, and third-party libraries your application depends on all update continuously — and when they do, your application may stop working correctly, become a security liability, or both.
Security patches alone require ongoing developer attention. In 2025, the average application used 528 open-source components, and 84% of codebases contained at least one known vulnerability. Keeping your dependencies current is not a nice-to-have; it is the price of keeping your product safe and functional.
Annual maintenance for a professionally built custom application typically runs 15–20% of the original build cost per year. On a $60,000 project, that is $9,000–$12,000 annually — $750–$1,000 per month — for a team that knows the codebase and is keeping it healthy. This is separate from new features. It is the cost of keeping what you already built working.
Agencies that do not discuss a post-launch retainer before you sign are leaving you to discover this cost after the relationship ends. Ask about it explicitly during the proposal phase.
Key Takeaways
- Annual software maintenance typically costs 15–20% of the original build price
- Security vulnerabilities in dependencies require ongoing patching — 84% of codebases have at least one known vulnerability
- Maintenance retainers ($1,500–$5,000/month for most business applications) cover upkeep, not new features
- Deferred maintenance is not cost savings — it is technical debt that compounds and eventually requires expensive remediation
The API Tax: What Third-Party Services Cost at Scale
Modern applications are built on third-party services: payment processing, email delivery, SMS, mapping, authentication, AI inference, document generation. Most of these services charge based on usage — and the pricing that looks reasonable at low volume can become a significant operating cost at scale.
A few examples of what this looks like in practice: an AI feature that calls a language model API for each user interaction may cost $0.002 per call in testing and $2,000 per month when real users are active. An email service that is free up to 100 sends per day costs meaningfully more when you are sending transactional emails to 10,000 users. Payment processing fees (typically 2.5–3% per transaction) are not a third-party API cost per se, but they are a usage-based cost that scales directly with your revenue.
The question to ask your agency before launch: for every third-party service in the application, what does it cost at our expected usage volume, and who is responsible for that invoice?
Feature Requests Will Come — They Always Do
Custom software is not a product you buy once and use forever unchanged. It is a living system that evolves with your business. New user feedback surfaces needs you did not anticipate. Competitors add capabilities you need to match. Regulations change. Your own processes improve and the software needs to keep up.
The cost of ongoing development is the category most consistently missing from business owners' post-launch budgets. Because the initial build consumed most of the budget conversation, the assumption becomes that the software is now done. It is not done. It is at version one.
Development work after the initial launch is typically billed at time-and-materials rates. If you are working with the agency that built the original software, expect to pay their standard rate — usually $80–$200 per hour depending on the team's location and seniority. Small feature additions take days. Meaningful new capabilities take weeks. Budget a minimum of $1,000–$3,000 per quarter for minor ongoing development, and significantly more if your product is evolving actively.
Key Takeaways
- Version one is the beginning of the product, not the end — ongoing development is a standard operating cost
- Post-launch development is billed at T&M rates ($80–$200/hour for most agencies)
- Budget $1,000–$3,000 per quarter minimum for minor changes; meaningful new features cost more
- Agencies that built your codebase have an advantage in extending it — factor transition costs into any decision to switch vendors
How to Build an Honest Total Cost of Ownership
Before you sign a software development contract, ask your agency to provide a total cost of ownership estimate — not just a build quote. A good agency should be able to give you projected infrastructure costs at your expected usage level, a recommended maintenance retainer with a scope of what it covers, a list of every third-party service the application will use with their pricing at scale, and a rough estimate of what a typical quarter of post-launch development looks like for a project of this type.
If an agency refuses to have this conversation, or cannot answer these questions credibly, that is information. It means either they have not thought carefully about your project, or they are structuring the relationship so that the ongoing costs are a surprise that keeps you engaged with them on reactive terms.
The business owners who get the most value from custom software are the ones who budget for the full lifecycle, not just the build. They treat the launch as the beginning of an operating cost, not the end of a capital expenditure. That framing changes what they budget, what they negotiate, and what they ask for in their initial contract.
Key Takeaways
- Ask for a total cost of ownership estimate — infrastructure, maintenance, third-party services, and ongoing development — before signing
- A credible agency can model post-launch costs at your expected usage volume
- The businesses that get the most from custom software budget for the full lifecycle from day one
- Ongoing costs are not a failure of the build — they are the normal economics of software as a living product
The Bottom Line
At StepTo, every project proposal includes a post-launch cost breakdown alongside the build estimate — because we think you should know what you are actually committing to before you sign anything. We cover infrastructure projections, maintenance retainer options, third-party service costs at scale, and what a realistic ongoing development budget looks like for your specific product. If you are evaluating custom software right now and want a clear picture of what it will actually cost to run — not just to build — we are happy to walk through that with you.
Building a team in Eastern Europe?
StepTo helps European and US companies build senior-led nearshore engineering teams in Serbia. Let's talk about what your next engagement could look like.
Start a conversation