Free tool
Should you automate this?
Eight questions, two minutes, and the same classification we run in the consult. Plenty of workflows shouldn't be automated yet. This tool will tell you if yours is one of them.
How to think about the verdict
How do I know if a task is worth automating?
A task is usually worth automating when it recurs at least weekly, its rules can be written down as a checklist, its inputs are digital, and an occasional error would be cheap to catch. If it consumes hours of team time every week and meets those conditions, automation typically pays back within months.
When should a business NOT automate a process?
Three signals mean not yet: the process changes monthly (automation freezes process, and frozen chaos is still chaos), the task is rare and quick (minutes a week cannot repay a build), or the human touch is the actual product (automating it destroys what clients pay for).
What makes an automation build hard rather than easy?
Messy inputs (emails, PDFs, voice), many systems to integrate, judgment calls in the middle, and output that ships to customers. Hard does not mean no: it means the build needs validation layers, approval gates and monitoring, phased in starting with the repetitive core.
How does this assessment score my workflow?
Eight questions each add a signal toward easy build, hard build, or not yet. Two or more disqualifying signals return a 'don't automate yet' verdict; three or more complexity signals return 'hard build'; otherwise the workflow classifies as an easy build. Scoring runs entirely in your browser.
Whatever the verdict, check it against a human
The consult is free, 30 minutes, with the engineer who builds. The honesty rule applies: if nothing is worth building, you'll be told exactly that.