Workflow Mapping
-
What It Is
A structured discovery workshop that identifies and prioritises the workflows most worth automating.
-
Who It Is For
Organisations that have dozens of potential workflows and no structured way to decide which to tackle first.
-
How Does It Work?
A structured, in-person workshop held at your office. Full day or two half-days, with around ten participants. The group maps five to ten workflows at a high level, covering triggers, stages, data, and people involved, then applies an ROI framework to produce a prioritised shortlist. Typical scoring criteria include time saved per month, quality and risk impact, number of people affected, and ease of build. The exact criteria are agreed per engagement.
-
What Is the Output?
A ranked shortlist, a shared understanding of how each workflow functions, clarity on data readiness, and agreement on what to build first.
Workflow Specification
-
What It Is
An in-depth discovery process that produces a build-ready Project Requirements Document (PRD) for a specific workflow.
-
Who It Is For
Organisations that know which workflow they want to automate and need a proper specification before building.
-
How Does It Work?
Recorded remote stakeholder interviews, followed by iterative refinement. WAA produces a first-attempt PRD covering role, inputs, outputs, data sources, integrations, guardrails, and success criteria. Each workflow is broken into steps identifying triggers, edge cases, roles (AI-only, AI-augmented, or human-only), and the dataset required. Your team reviews and stress-tests the document, and further rounds of edits refine it until it is build-ready. Turnaround is approximately three weeks.
-
What Is the Output?
A build-ready specification that belongs to you. You can take it to any provider, build internally, or engage WAA for the build.
"We Are Agentic helped us to map out an entire agentic workflow consisting of multiple agents working together. It took a few weeks of interviews and back and forth. They skillfully managed to navigate the varying opinions and conflicts internally with the team to produce a highly detailed specification document ready for us to build."
Ian Syer | CEO | MyArtBroker
Frequently Asked Questions
-
Yes. Workflow Specification can be taken independently.
-
Workflow Mapping: subject matter experts, AI champions, and relevant stakeholders from across the business. Workflow Specification: the people currently doing the workflow manually, plus IT, data owners, and anyone involved in the process.
-
A Project Requirements Document. It covers role, inputs, outputs, data sources, integrations, guardrails, and success criteria, and is refined through internal review until it is build-ready.
-
Yes. The document belongs to you.
-
Workflow Mapping is a single-day workshop. Workflow Specification takes approximately three weeks, with pace determined by your internal review cycle.
Start a Conversation
If your team is ready to move from individual AI use into operational workflows, a conversation is the right next step. We will help you understand what the process looks like for your business.
Ready to understand what comes after specification? Read about Phase 4: Build →
Read Our Philosophy →