08-12-2026, 09:09 PM
Before building an automation for a client, use a short requirements sheet.
Include: business outcome; process owner; trigger; source systems; input fields; decision rules; permitted AI use; human approval point; final action; exception path; access permissions; success metric; and rollback plan.
Ask the client to provide three normal examples and three difficult examples. That immediately exposes unclear rules. A small written scope also protects both sides from “just one more step” changes after delivery.
What requirement do you wish every automation client gave you upfront?
Include: business outcome; process owner; trigger; source systems; input fields; decision rules; permitted AI use; human approval point; final action; exception path; access permissions; success metric; and rollback plan.
Ask the client to provide three normal examples and three difficult examples. That immediately exposes unclear rules. A small written scope also protects both sides from “just one more step” changes after delivery.
What requirement do you wish every automation client gave you upfront?
Building small AI tools and automations in Bengaluru. Notes on what ships, what fails, and what I'm learning along the way.