Leaders approve custom software based on build estimates. Then year two arrives: on-call pages, dependency upgrades, a feature that needs three services touched, and a contractor who left with the only mental model of the billing module.
The operating cost of custom software is not a surprise tax. It is the predictable price of owning a system. Budget for it - or the system budgets for you in outages and delay.
Cost line items that somehow never make the spreadsheet
- Keep-the-lights-on engineering - patches, certificate rotations, dependency CVEs.
- Observability - logs, metrics, traces, and someone who reads them.
- Environments - staging that matches production enough to catch real bugs.
- Access and compliance - audits, SSO, offboarding, vendor reviews.
- Product change - every new integration raises the floor of complexity.
Design choices that lower the bill
- Prefer boring architecture where you can - fewer moving parts, fewer 2am mysteries.
- Write runbooks while the builders are still in the room.
- Make tenancy, auth, and billing explicit early (multi-tenant SaaS architecture).
- Agree who owns cloud accounts and source control before kickoff.
How to talk about TCO with a partner
Ask for a 12-month operating sketch: expected engineering days per month, on-call model, upgrade cadence, and what happens if your internal team takes over. Vague answers mean the build quote is incomplete.
Orissian prices and designs work as systems you can operate - see software engineering, cloud and infrastructure, and our SaaS partner guide.
Talk through ownership · Insights
