Founder building document-automation tools for tax firms here — the hardest part is definitely the verification step. For us it's not whether the agent can navigate a UI, but whether the output it produced (a reconciliation report, a tax form) is actually correct when every screen says "success."
We ended up building a secondary rule-based checker that runs independently over the agent's output — it catches things like missing schedules, transposed account numbers, and date mismatches with prior-year filings. The agents handle the execution path, the rules handle the truth.
Curious how you're thinking about this for workflows where a wrong but "successful" action has real downstream cost — do you rely on human review, or do you have a layered verification approach built-in?
We ended up building a secondary rule-based checker that runs independently over the agent's output — it catches things like missing schedules, transposed account numbers, and date mismatches with prior-year filings. The agents handle the execution path, the rules handle the truth.
Curious how you're thinking about this for workflows where a wrong but "successful" action has real downstream cost — do you rely on human review, or do you have a layered verification approach built-in?