Process Automation Architect (Discovery & Redesign)

National sustainability company (~30 people) running 20+ AI agents across Sales, Finance, and Operations on n8n, Airtable, Make.com, and AWS (with some Zapier and Retool in the mix). The agents work, but no one has mapped what each person actually does and redesigned their workflows AI-first. That's this role: interview the team, map every task/tool/handoff by role, redesign using an eliminate/automate/HITL framework, and write build-ready specs for our dev team to execute. You architect — you don't build. Deliverables: Role-Based Process Maps (Wk 1–2): Interview all ~30 team members (45–60 min each). One process map per department + master task inventory by role. Flag multi-role people and duplicated tasks. Gap + Redesign Analysis (Wk 2–3): Compare current AI coverage vs. actual task inventory. Classify every task: eliminate / automate fully / automate with HITL / keep human. Deliver a prioritized report on what each person's job becomes post-automation. Build-Ready Specs (Wk 3–5): Spec every automation opportunity — trigger, inputs, AI action, output destination, confidence threshold, HITL routing logic. Implementation-ready, not conceptual. Audit Layer Spec (Wk 5–6): Design observability — failure modes, alerts (what/who/when), recovery paths. Implementable by our infrastructure engineer. Not a fit if you: primarily want to build rather than architect; have only mapped one department, not a whole company; need heavy direction to drive discovery; or hand back current-state maps without redesign thinking. To apply, answer all (incomplete applications won't be reviewed): A process mapping/discovery project you've led — company, # interviewed, what you delivered. One example of redesigning a manual process into automation — before/after, and what the person's job became. Tools you use for process mapping, with an example. Experience with n8n, Airtable, Make.com, Zapier, Retool, or monday.com — what you built or specced, and which is your strongest. How you'd interview a non-technical finance person to surface automation opportunities they don't know exist. An example of designing monitoring/alerting for automations that can fail silently.