How the Engagement Starts: Structured Organisational Intake
Every engagement begins with a structured intake of the customer’s organisation. This means systematically capturing the departments involved, the processes they own, the existing systems those processes touch, and the decision paths that govern how work moves between people and tools. The goal is to arrive at a clear, shared picture of the organisation before any agent design begins. We do not ask you to map this yourself. A structured method guides the conversation — covering the right areas in the right order, surfacing the details that matter for agent design, and flagging the constraints that could affect scope. The detailed discovery methodology — the specific questions, the sequencing of topics, and the analytical framework used to interpret what we learn — is part of the consulting engagement and not published here. What you can expect is that the process is thorough, repeatable, and focused on giving the design phase everything it needs to proceed without guesswork.What Happens During Discovery
Discovery centers on a 60-minute workshop held remotely or in-person. During this session, we walk through your current operations, map out the tasks that consume the most manual effort, and identify where an AI agent could realistically make a difference. After the workshop, you have the option to continue the conversation asynchronously. If follow-up questions come up on either side — clarifications, missing details, or new ideas — we handle them via a shared Q&A document so nothing falls through the cracks.Discovery is not a sales call. It’s a working session. The more openly you share about your current frustrations and workflows, the more useful your Discovery Summary will be.
What We Need From You
To make the workshop as productive as possible, come prepared with answers to these four areas:Your Top 3 Repetitive Tasks
Identify the manual, high-frequency tasks your team performs most often — the ones that feel like they could (and should) be automated.
Your Current Tool Stack
List the software your team uses day-to-day: CRMs, email platforms, helpdesk tools, spreadsheets, databases, and anything else in the mix.
Who Is Affected
Tell us how many people perform these tasks and how much time they spend on them each week. Even rough estimates are valuable.
What Success Looks Like
Define what a win means to you — fewer support tickets, faster response times, hours saved per week, reduced errors. Be as specific as you can.
What to Bring to Discovery
Use this checklist to prepare before your workshop:1
List your top 3 manual or repetitive tasks
Write down the tasks your team does repeatedly that feel like they could be handled automatically.
2
Document the tools you currently use
Gather the names of every software platform involved in the workflows you want to automate.
3
Estimate time and headcount
Note how many team members are involved and roughly how many hours per week are spent on each task.
4
Define your success metrics
Come with at least one measurable outcome that would tell you the project was worth it.
5
Identify any known constraints
Flag anything that might complicate automation — compliance requirements, data sensitivity, approval chains, or tools with limited API access.
6
Bring examples
If you have screenshots, process docs, or even just a rough written description of how a task works, bring them. Real examples speed up everything.
What You Get After Discovery
Within a few business days of your workshop, we deliver a Discovery Summary document. This document becomes the input for the Design phase.Discovery Summary Document
Your Discovery Summary includes a prioritised list of agent opportunities, each ranked by estimated ROI and implementation feasibility. It captures your workflows, pain points, tool stack, and success criteria in one reference document that your whole team can review.
Timeline
Discovery typically completes within 1 week of signing the initial agreement. The workshop is scheduled as soon as your team is available, and the summary document follows shortly after.