Test the cost. See the capacity.

A low-commitment way to test a software change with your own numbers. Start with one workflow that holds your advice up, such as preparing SoA requests, compare recurring and transition costs, then estimate the time it could release. Cash and team capacity stay separate.

AUD excluding GST. Scenario planning, not a Bunya quote, a prediction or a promised saving. Inputs start at zero; enter your figures or load the fictional example.

Your scenarioRuns in your browser
01Recurring costs

Use monthly totals for equivalent scope. Include retained tools in both sides where they remain necessary.

Include licences, usage and support for the scope being compared.
Include new services, retained tools, Microsoft licences, usage and support.
02Transition
Include build, migration, training and any period of overlapping subscriptions.
Recurring costs are held constant across the period.
03Potential team capacity

Optional. Model one repeatable workflow across the whole team, such as preparing SoA requests. Include checking and correction time in your estimate.

Total across the team, not hours per person.
Your scenario assumption. Test it in a pilot before relying on it.
Weeks when this workflow is performed.
Optional: salary and on-costs per hour. This values capacity, not cash savings.

Calculations run in your browser. This calculator does not submit or save your entries. Reloading clears them.

How to read the results

Transparent inputs. Separate outcomes.

ACash comparison

Annual recurring difference = (current monthly cost − proposed monthly cost) × 12.

Period difference = annual recurring difference × years − one-off transition costs. Positive means a lower proposed cash cost; negative means a higher proposed cash cost.

Simple payback = transition cost ÷ positive monthly difference. This assumes immediate savings and excludes time value of money, price changes and unentered costs.

BCapacity estimate

Annual hours released = weekly workflow hours × reduction percentage × working weeks.

Illustrative capacity value = hours released × loaded hourly cost. This is a way to value team time, not an additional cash return.

Test the whole workflow before accepting a time-saving assumption. Keep unknown costs visible rather than treating them as zero in a buying decision.

These results are scenarios built from your own assumptions. They are not promised savings, a Bunya quote or financial advice. Actual costs and any capacity released depend on your firm’s scope, data, licences and the way your team works.

Questions

Calculator questions. Straight answers.

01Is this a Bunya quote?
No. It is scenario planning with your own numbers. Your proposal sets out the price for your firm, and nothing is built until you have agreed it.
02Is anything I enter saved or sent?
No. The calculator runs in your browser. It does not submit or save your entries, reloading clears them, and calculator entries are not sent with a demo booking.
03Why are cash and capacity kept separate?
Time released does not automatically reduce payroll, avoid a hire or generate revenue, so it is not added to the cash difference. Keeping them apart lets you judge each on its own.
04What time reduction should we assume?
Use your own assumption, and include checking and correction time in the current hours. Test the whole workflow in a pilot before relying on a time-saving figure.

Read all FAQs ↗

Recurring costs Transition Capacity Your scenario Comparison period Hours / week Cash difference Payback Your figures Requirements

See what it could mean for your firm.

One meeting covers the demo and discovery, including the requirements behind your scenario. Calculator entries are not sent with your booking.

NextFAQs →