Know what to automate — before you build.

Fit / problem

• 3+ manual workflows are eating team hours
• A decision-maker can commit to a 2-week discovery window
• Basic process documentation exists, or the people who know it are available

Not a fit if: You already have a validated automation backlog and just need build capacity · No one can spend time in discovery interviews

Outcomes / deliverables

• Prioritised opportunity backlog with effort/impact scoring
• Process and data-flow diagrams for the top 3 candidates
• Recommended tool and architecture per opportunity
• Phased roadmap with rough cost bands

Architecture

• Structured discovery interviews and system walkthroughs
• Process and data-flow mapping
• Feasibility and risk scoring against your stack
• Roadmap sequencing by effort and payback

Tools / systems / integrations

• Read-only access to core systems during discovery (CRM, inbox, spreadsheets)
• No production changes are made during the audit
• Findings translate directly into build scope for later phases

Controlled / controls

• No system write-access during the audit
• Findings reviewed with your team before roadmap sign-off
• Assumptions and data sources documented for later verification

Implementation / timeline & cost

• Number of processes in scope
• System count and access complexity
• Whether interviews span multiple departments
• Requested turnaround time