How to Calculate the Total Cost of Custom Software
What is custom software total cost of ownership?
Custom software total cost of ownership is the cost of building, running, maintaining and eventually replacing your software over a defined period. Calculate it by adding the initial investment, recurring operating costs, internal staff time and any replacement costs within that period. The build quote is one line in that calculation.
Start with a planning window and a clear description of what the software must do. Then use the worksheet below to make each assumption visible. The result should help you compare options and decide what you can afford to operate after launch.
What should your calculation include?
Use this working formula:
Total ownership cost = initial costs + operating costs over the planning window + internal staff cost + replacement costs within the window.
Keep an uncertainty allowance separate from the base estimate. This makes it clear which spending you expect and which money you are holding for unresolved risks.
Choose one currency and a consistent treatment of taxes. Use the same planning window, scope and service expectations when comparing proposals.
| Cost category | What to include | How to estimate it |
|---|---|---|
| Initial build | Discovery, design, development, testing and launch | Agreed scope plus separately priced exclusions |
| Initial setup | Data migration, training and connections to other systems | One-time tasks and named owners |
| Hosting | Application hosting, storage, backups and monitoring | Expected usage multiplied by the relevant charges |
| Licenses | Paid tools, subscriptions and outside services | Seats, usage units and renewal terms |
| Support | Help requests, fault investigation and agreed response coverage | Contract fee plus work outside the agreement |
| Security | Access reviews, security testing and corrective work | Defined activities, frequency and responsibility |
| Upgrades | Dependency updates, compatibility work and planned maintenance | A specific work allowance with clear exclusions |
| Internal staff | Product decisions, acceptance checks, administration and training | Hours multiplied by an agreed internal hourly cost |
| Replacement | Successor software, data transfer, transition and closure | A separate exit and replacement estimate |
These are worksheet categories, not a requirement to buy every service separately. If a support agreement includes security updates, record that coverage and avoid charging for the same work twice.
Which assumptions should you write down first?
Create a short assumptions sheet before entering prices:
- Planning window: how long the comparison covers.
- Scope: the workflows, users and connections included.
- Usage: expected users, storage and billable activity.
- Service expectations: support hours, response commitments and recovery needs.
- Responsibilities: what the supplier handles and what your staff handles.
- Price basis: currency, tax treatment and any assumed price changes.
- Exit timing: whether replacement happens within or after the window.
Use a quote, contract or documented usage estimate where available; how to estimate a software project explains how to read a build estimate's range. Mark missing figures as assumptions with an owner responsible for checking them.
Ask for precise coverage rather than accepting a label such as “maintenance included”. Our guide to choosing a software development agency offers related questions for assessing a build partner.
What does a worked ownership worksheet look like?
The following example is entirely illustrative. Every amount, hourly cost and workload is a chosen assumption, not a market average or a suggested budget. All figures use the same unspecified currency.
Assume a three-year planning window, with the original application operating throughout those three years. A successor launches at the end of the window. Recurring costs stay flat, and replacement includes the transition work shown below.
| Item | Illustrative assumption | Three-year total |
|---|---|---|
| Initial build | 60,000 once | 60,000 |
| Setup and training | 6,000 once | 6,000 |
| Hosting | 300 per month × 36 months | 10,800 |
| Licenses | 200 per month × 36 months | 7,200 |
| Support | 600 per month × 36 months | 21,600 |
| Security work | 3,000 per year × 3 years | 9,000 |
| Upgrades | 4,800 per year × 3 years | 14,400 |
| Internal staff time | 12 hours per month × 50 per hour × 36 months | 21,600 |
| Exit and transition | 12,000 once | 12,000 |
| Successor software | 40,000 once | 40,000 |
| **Base ownership cost** | **Sum of the rows above** | **202,600** |
The assumed exit allowance covers data export, transition checks, a short period of running both systems and closing the old service. The successor allowance covers its build and setup. Its operating costs after the planning window are excluded.
Under these assumptions, external spending totals 181,000. Adding 21,600 of internal staff time produces the 202,600 ownership estimate.
If you also choose an illustrative uncertainty allowance of 15,000, the planning budget becomes 217,600. Keep that allowance visible as a separate line.
How should you count internal staff time?
List the work your organisation must supply even when a development partner writes the code.
Include time spent answering product questions, preparing data, checking releases, managing access, helping users and coordinating suppliers. Assign each activity to a role and estimate its hours.
For a simple worksheet, multiply those hours by a consistent internal hourly cost. State whether that figure includes salary alone or other employment costs.
Keep two views:
- Cash budget: external payments and any additional staffing payments.
- Ownership estimate: the cash budget plus the value of existing staff time committed to the software.
Existing staff time may already sit in your payroll budget. Count its value in the ownership comparison without presenting it as a new supplier invoice or counting it again elsewhere.
How do you estimate support, security and upgrades?
Ask your proposed partner to describe deliverables for each category.
For support, define coverage hours, how requests are raised, response commitments and what happens when included work runs out. Separate correcting a fault from adding a feature.
For security, specify the activities you want priced, who performs them and whether fixing issues found during testing is included. Use data security in modern applications to frame that discussion.
For upgrades, distinguish keeping the existing application working from expanding its capabilities. Ask what happens when a component needs a larger change than the maintenance allowance covers.
Keep optional product development in a separate roadmap budget. If the ownership estimate assumes particular future features, name and price them explicitly.
How should you budget for eventual replacement?
Write an exit outline while comparing proposals. Ask how you would obtain your data, transfer operational knowledge and move to a successor.
Estimate data transfer, replacement connections, staff training, any overlap between systems and closure work. Keep those costs distinct from buying or building the successor.
Include replacement in the total when it falls inside your planning window, as in the example. If it falls outside, show a separate future estimate and its timing. Do not add an entire successor build to a shorter operating comparison without explaining the difference.
Avoid treating a replacement allowance as a prediction that the software will become unusable on a particular date. It is a planning assumption you can revise.
Which common mistakes make the estimate misleading?
Comparing different scopes. A lower quote with fewer workflows or less support is a different offer. Align the comparison first.
Counting bundled work twice. Map each responsibility to one cost line and note what the agreement includes.
Assuming usage stays flat without checking. Build a second scenario with higher billable usage and recalculate the affected rows.
Treating every future feature as maintenance. Separate the cost of preserving current behaviour from the cost of expanding the product.
Hiding uncertainty in one large number. Name the unresolved risk, the assumed amount and what would make you revise it.
Comparing ownership cost without considering value. Cost alone does not tell you whether the software is worth building. Assess the expected business benefit separately.
What should you confirm before approving the budget?
- Every cost has a calculation, quote or clearly labelled assumption.
- Each responsibility has an owner.
- Bundled services appear only once.
- Internal time and external payments remain distinguishable.
- Usage changes have been tested in a separate scenario.
- Replacement timing and exclusions are explicit.
- Someone owns reviewing actual spending against the worksheet.
Frequently asked questions
How many years should the estimate cover?
Choose a period that matches your decision and expected use. Apply the same period to every option. If the useful lifetime is uncertain, compare more than one planning window.
Is there a standard maintenance percentage to use?
This worksheet does not assume one. Price the work you expect: support coverage, security activities, upgrades and responsibilities. A percentage without defined coverage does not explain what your budget buys.
Should sunk costs affect a replacement decision?
For a decision made today, compare future costs from today onward. Keep historical spending visible separately, so it does not obscure the costs of keeping or replacing the software.
Hosting is one of the recurring lines here; see how to estimate hosting costs before launch.
*Need help turning a build proposal into an ownership budget? Start a conversation →*