Start with the workflow specification
These templates define the operating logic first. Adapt them to your actual systems and policies before building.
Lead follow-up
Trigger: New qualified lead enters CRM.
Steps: Validate contact → assign owner → send useful acknowledgment → create follow-up timer → escalate if unanswered.
Stop: Reply, opt-out, invalid contact, booked appointment, or human takeover.
Measure: Time to first useful response, reply rate, booked-call rate.
Client intake
Trigger: Signed/approved customer enters onboarding.
Steps: Create record → collect required fields → validate completeness → assign owner → schedule next step.
Stop: Missing consent, missing required data, duplicate account, or human exception.
Measure: Time to complete intake, missing-field rate, handoff failures.
Operational reporting
Trigger: Reporting window closes.
Steps: Pull authoritative metrics → validate freshness → reconcile conflicts → publish dashboard → alert on missing data.
Stop: Source unavailable or conflicting authoritative values.
Measure: Report freshness, missing-data rate, decision latency.
Automation handoff
Trigger: Automated step finishes or fails.
Steps: Persist outcome → assign exact next actor → include evidence → set deadline/checkpoint → verify receipt.
Stop: Ambiguous side effect or missing authoritative state.
Measure: Unacknowledged handoffs, retry rate, time blocked.
Use the result as a decision aid, not a promise
These tools are designed to help an operator define the business problem before choosing software or paying for implementation. The calculators use only the assumptions entered on the page. The scorecards measure whether a workflow has a clear trigger, reliable source data, ownership, exception handling, and a measurable outcome. A high score does not guarantee that automation will produce a financial return, and a calculated dollar amount is not a forecast of guaranteed recovered revenue.
The next useful step is to compare the estimate with real operating data. Check actual lead volume, current response time, close rate, labor cost, handoff failures, and the systems that currently hold the authoritative data. Start with one bounded workflow, define what success and failure look like, test it with representative data, and measure the result before expanding. That approach keeps the tool useful for planning while avoiding false precision or automation built on an unstable process.