Skip to main content
Your inputs · scenario, not an ROI promise

Workflow Opportunity Calculator

Before automating anything, it helps to know how much time a task really takes. This calculator multiplies your own numbers and shows a range for the share you think is repeatable. It does not assume an automation rate, a wage or an outcome.

Your inputs · scenario, not an ROI promise

Your task

Pick one repetitive task — re-typing enquiries, chasing confirmations, answering the same questions — and enter your best estimates.

For example, enquiries entered by hand.

Average, including switching between tools.

Change this to match your calendar.

The part that follows the same steps each time.

Leave empty to see hours only.

Your scenario

Calculated from your inputs only

Time spent today
307
hours / year
Potential time in scope
92 – 184
hours / year

How it's calculated

  • Time spent today: tasks × minutes × people × weeks ÷ 60
  • Potential time in scope: time today × repeatable share (low – high)
  • Cost of that time: time in scope × cost per hour

What this does not assume

  • No automation rate — the range is your own repeatable-share estimate
  • No wage or currency unless you enter one
  • Not all time in scope can or should be removed; exceptions often stay manual
What kind of work is it mostly?

Adds these numbers (not your name or task details) to the contact form. Nothing is sent until you submit it.

Purpose

What this demonstrates

  • Sizing a task from frequency, duration and people involved
  • A low–high range based on your own estimate, not a single promise
  • Choosing the next step by the type of problem, not defaulting to AI

Constraints · not production-ready

  • Everything is calculated in your browser; nothing is stored or sent
  • Results are only as good as the inputs you enter
  • Potential time in scope is not guaranteed savings or ROI

What a production version would need

  • Measuring the task as it happens today (time samples or system logs)
  • Mapping exceptions that would stay manual
  • Agreeing success measures before any build starts

Want to adapt this idea?

Share the context and we'll help define a sensible first step.