ROI model workspace
Instead of relying on uncertain project-mix assumptions, this version starts with the current weekly workload dedicated to the spreadsheet build. Adjust the inputs on the left and the economics update instantly.
The process map identifies a part-time contractor working roughly 10–20 hours per week and currently focused on building the budget tracker / item-list sheet so the styling team can stay focused on design. That directly anchors the workload being automated.
Current workload
Automation & value
Wise pricing
Modeling
The numbers
LiveCumulative value vs. cost
Shows when cumulative quantified capacity value moves ahead of cumulative Wise cost.
Net benefit by year
Year 1 includes implementation; later years carry only the recurring subscription.
Current workload disposition
The model keeps 30% of the current work for human review / correction at the default 70% automation rate.
Cost by year
Separates the one-time implementation from the recurring subscription.
Mapped workload range
The process discovery supports a 10–20 hour weekly range. This shows the economics at the lower bound, midpoint, and upper bound without changing any of the other assumptions.
Conservative
Midpoint
Upper range
Break-even view
This is the threshold the model needs to clear. Because the recurring annual subscription is $30,000 at the default price, the current workflow only needs to exceed that value after implementation is behind it.
Three-year breakdown
The full economics of the selected workload assumptions. Capacity value can optionally grow over time; Wise implementation and subscription follow the inputs above.
| Year | Capacity value | Subscription | One-time setup | Total cost | Net benefit | ROI |
|---|---|---|---|---|---|---|
| Year 1 | $49,140 | $30,000 | $15,000 | $45,000 | $4,140 | 9.2% |
| Year 2 | $49,140 | $30,000 | — | $30,000 | $19,140 | 63.8% |
| Year 3 | $49,140 | $30,000 | — | $30,000 | $19,140 | 63.8% |
How to read this table
- Capacity value
- Current weekly budget-tracker workload × working weeks × automation share × loaded hourly value.
- Subscription
- Monthly Wise subscription multiplied by 12 months.
- One-time setup
- The implementation fee, charged only in Year 1.
- Net benefit
- Quantified capacity value minus Wise cost for the year.
- ROI
- Net benefit divided by total Wise cost. This does not include unquantified operational upside.
How we got there
The model is intentionally narrow: it quantifies only the current spreadsheet-building capacity that Phase 1 gives back, while preserving the rest of the process-map findings as unquantified upside.
The process map identifies the Miro → Excel itemization step as the styling workflow's No. 1 pain point. Today, a part-time contractor is working approximately 10–20 hours per week and is currently focused on building the budget-tracker / item-list spreadsheet so Heather can spend more time designing.
Rather than infer annual savings from project count, duration, and project mix, this version anchors the ROI to that observed weekly workload. At the default midpoint of 15 hours per week, the workflow represents 780 annual hours of current activity.
The agent is modeled as removing 70% of the mechanical build while leaving review and correction with the styling team. At a loaded value of $90/hour, that creates the quantified capacity value below.
Wise cost is modeled as a $15,000 one-time implementation plus a $2,500/month subscription. The model calls the benefit “capacity value” because the returned time may be redeployed into design, higher project throughput, or avoided incremental support rather than taken as direct payroll reduction.
Not counted in the ROI
Additional upside- Fewer errors and less triple-checking when translating Miro into Excel.
- The roughly one-week delay that can occur when broken links or mismatched images bounce a sheet back from procurement.
- More Heather / Peyton capacity available for design and client-facing work.
- Ability to support a higher styling volume without proportionally adding support capacity.
- Reduced key-person dependency and a more consistent item-sheet format.
- Value from later opportunities such as Core → Excel transposition, replacement assistance, and delivery / receiving automation.