Choose a result the business cares about
For an internal workflow, the goal might be less time preparing a reviewed record or fewer incomplete handoffs. For a website, it might be more relevant inquiries or fewer unanswered service questions. Decide which outcome matters before selecting an impressive-looking dashboard measure. Activity can be useful diagnostic information, but more generated text or more conversations does not automatically mean more value.
Use an illustrative calculation carefully
Suppose a task takes ten minutes and happens sixty times a month. That is ten hours of current effort. If a pilot reduces the net time to six minutes, including review, it releases four hours of capacity. These numbers are an example, not a prediction or client result. The next question is what the business can actually do with those hours. Freed capacity is not automatically a reduction in payroll or an increase in revenue.
What would useful capacity look like?
Change the inputs. Include review time and operating costs before deciding whether a pilot is worth exploring.
Illustrative capacity value: $160/month. Less $100 operating costs: $60/month.
Setup recovery equivalent: 16.7 months, if capacity can be fully realized at your hourly assumption.
Calculation: tasks × (current minutes − new minutes) ÷ 60. Capacity is not guaranteed cash savings or revenue. Maintenance and review must be included in your inputs. This tool runs locally and sends no inputs.
Include the complete cost
Consider setup, tool usage, integrations, review, maintenance and the effort of training the team. Include exception handling: a workflow that saves time on routine cases may still create work on difficult ones. Compare alternatives, including a simpler non-AI process change. A useful estimate makes its assumptions visible so the business can replace them with observed numbers during the pilot.
Evaluate website changes in context
If inquiries rise after a website update, ask what else changed. Advertising, demand, seasonality and a new offer may all affect the result. Compare relevant periods and look at inquiry quality, not only volume. Where practical, isolate one change at a time. Record which pages and actions were involved. Avoid turning a short positive trend into a claim that the website caused every additional sale.
Agree on a decision rule
Before a trial begins, decide what would justify continuing, revising or stopping. Identify who reviews the evidence and when. A result can be mixed: faster preparation but more corrections, or fewer inquiries but better fit. My preference is to discuss those tradeoffs directly. A project should earn the next stage through a useful result, not simply because time has already been invested.
Common questions
Should I use revenue as the only measure?
No. Quality, reliability, staff effort and customer experience may be important intermediate measures. Revenue attribution can be difficult.
Can you guarantee a return before building?
A proposal can define scope, assumptions and evaluation criteria. Actual business results depend on the implementation and operating context.
What would this look like in your business?
Bring the workflow, website or unanswered question. We can define the useful next step.
Discuss your project Explore Aethra websites

Work with Josh 