Calculate the return before you automate the work.
A polished demo is not a business case. Put the current cost, believable improvement, risk and full operating cost on one page before you approve a build.
Two formulas are enough to make the first decision.
Use the same period for every number. Twelve months is useful for comparison; a monthly view makes payback easier to understand.
ROI % = (total benefit − total cost) ÷ total cost × 100“Benefit” should already be adjusted for the share you reasonably expect to realise.
Payback months = upfront cost ÷ monthly net benefitMonthly net benefit means benefit after subscriptions, review time and maintenance.
Capacity is not automatically cash
If an automation returns five founder hours, the business has gained capacity. It becomes financial value only when those hours reduce paid work, avoid a hire, increase throughput or are redeployed into valuable activity. Show that assumption instead of quietly calling every saved hour profit.
Count what changes in the operation.
Hands-on labour
Weekly hours removed × the true loaded hourly value of the people doing the work. Include wages or drawings, super, payroll costs and relevant overhead—not an inflated aspirational rate.
Error and rework
Measure corrections, refunds, duplicated effort or missed records. Use actual frequency and average cost, then count only the reduction the system can plausibly cause.
Response delay
Faster follow-up can matter, but do not convert it to revenue until you can connect response time to a measured conversion or retention change.
Work that falls through
Unsent follow-ups, unbilled work, expired quotes and missed renewals can be valuable. Use records, not memory, to establish how often they occur.
More work without more headcount
Value incremental gross profit, not revenue. If capacity is not likely to be sold, keep it as an operational benefit rather than a cash claim.
Unverified commercial assumptions
- Every minute the task currently takes
- Revenue with no demand or margin
- The same benefit twice
- “Strategic value” with no decision attached
Replace every orange placeholder before approving spend.
Observe a normal period. Ask the people doing the job, and sample the records. Estimates are allowed; invisible assumptions are not.
| Input | Your baseline | How to verify it |
|---|---|---|
| Runs per week | [XX] | System log, inbox or task history |
| Minutes per run | [XX minutes] | Time five to ten representative runs |
| Loaded hourly value | [$XX] | Payroll/owner cost plus relevant on-costs |
| Errors or exceptions | [XX per month] | Corrections, refunds and support records |
| Expected time removed | [XX%] | Pilot result, not vendor promise |
| Upfront build and training | [$X,XXX] | Written scope including handover |
| Monthly tools and usage | [$XXX] | Subscriptions, model/API and integrations |
| Monthly review and maintenance | [X hours / $XXX] | Named owner and expected cadence |
Use hypothetical numbers to test the model—then replace them.
These examples explain the calculation. They are not Aenta client results or promises.
Support reply preparation
Assumptions: 8 hours/week at $45 loaded; pilot removes 4.5 hours. Annual capacity = $10,530. Tools and review = $3,600/year; build = $5,000.
Year one: net benefit $1,930; ROI 22%; payback about 8.7 months on the $575 monthly operating benefit. This is capacity unless roster cost falls or the team uses it productively.
Weekly client reporting
Assumptions: 6 hours/week at $70 loaded; pilot removes 4 hours. Annual capacity = $14,560. Tools and review = $2,400/year; build = $6,500.
Year one: net benefit $5,660; ROI 64%; payback about 6.4 months. If reports still need two hours of correction, that review time remains in the model.
Lead follow-up
Assumptions: labour benefit $4,680/year plus $12,000 potential gross profit from recovered jobs. Only 40% of that commercial benefit is accepted: $4,800. Costs total $7,000 in year one.
Year one: probability-adjusted benefit $9,480; net benefit $2,480; ROI 35%. Track actual booked gross profit, not messages sent.
Adjust uncertain benefits by probability.
Use a confidence factor for every benefit that is not proven. If a workflow could recover $20,000 in annual gross profit but you believe there is only a 35% chance of achieving it, use $7,000 in the decision model. Keep the full upside visible as a scenario, not the base case.
A simple risk adjustment
Expected benefit = potential benefit × probability of realisation. Then subtract an expected failure cost where errors could create refunds, rework, lost customers or compliance issues.
Include ongoing operating and maintenance costs.
- Discovery, process mapping, design, implementation and testing.
- Subscriptions, API or model usage, hosting and integration fees.
- Training, documentation and the temporary productivity dip during adoption.
- Human review, exception handling and quality checks.
- Monitoring, supplier changes, broken integrations and improvement work.
- Security, privacy, backup and incident-response controls appropriate to the workflow.
Turn the forecast into evidence.
- Days 1–5: baseline. Measure volume, hands-on time, delays, errors and current commercial leakage.
- Days 6–10: define the pass mark. Choose one primary outcome, one quality measure and clear actions the system cannot take.
- Days 11–20: controlled pilot. Run on a small share of real work with human approval and record every correction and exception.
- Days 21–27: compare. Calculate time removed after review, quality, failure cost and the actual operating effort.
- Days 28–30: decide. Continue, simplify, redesign or stop. Update the model with observed numbers.
Use thresholds as judgment, not universal law.
A founder-led business might favour a short payback, positive first-year return and a clear path to adoption. A strategic capability may justify longer. Whatever you choose, write it down before seeing the result. A sensible go decision also needs acceptable quality, a named owner, manageable downside and evidence the team will use the system.
Say no—or narrow the scope—when most of the return depends on unproven revenue, review consumes the time supposedly saved, the process is still unstable, or the access and failure risk outweigh the value.
Questions behind the spreadsheet.
Use a defensible economic value: current drawings or replacement cost for the work, then show a separate upside case for high-value redeployment. Do not use an imagined consulting rate for routine admin.
Only where the causal link can be measured. Use incremental gross profit rather than revenue, discount it for uncertainty, and keep it separate from hard labour savings.
The business has not realised the forecast value. Fix the workflow or adoption plan, define how the capacity will be used, and avoid calling it a cash return.
Precise enough to expose the decision. Use ranges for uncertain inputs, show the assumptions and identify which number the pilot must prove.
Move from business case to the right build.
Useful references for finance and measurement.
- Australian Government — Key financial terms and ROI
- Australian Government — Artificial intelligence for business
- National AI Centre — Guidance for AI Adoption
- NIST — AI Risk Management Framework: Measure and Manage
The formulas are standard decision tools. The thresholds and examples in this article are Aenta guidance and hypothetical illustrations, not financial advice or guaranteed results.