Show Clients the Hours You're Saving Them

Think about how long the task would take manually. A workflow that processes an invoice might save 5 minutes of data entry. A report generation workflow might save 30 minutes of manual compilation. Start with conservative estimates - you can adjust as you learn more.

Use an average. If a workflow sometimes saves 10 minutes and sometimes 20, estimate 15. The aggregate over hundreds of executions will be reasonably accurate even if individual estimates vary.

Yes. Each workflow has both 'minutes saved per success' and 'minutes saved per failure' settings. Most workflows save nothing on failure (the task still needs to be done manually), so the default failure value is 0.

For each workflow: (successful executions × minutes per success) + (failed executions × minutes per failure). Results are shown in hours. Per-client and dashboard totals sum across all applicable workflows.

Time saved is a proxy metric useful for demonstrating value, not a billing metric. For billing, most agencies use LLM costs (actual spend) or execution counts (activity-based billing). Time saved is better for showing ROI in proposals and reviews.

Show hours saved per month alongside execution counts. 'Your automations ran 1,200 times this month, saving approximately 40 hours of manual work.' It makes the abstract value of automation concrete.