Bring a recurring workflow, the tools involved and a rough sense of the time it takes. Together, we look at the friction, the available data and whether automation is worth pursuing.
A workflow owner on your side
A clear trigger and desired result
An initial baseline to measure against
02
Agree what we’re building.
Before implementation, a written proposal defines the deliverables, cost, milestones and responsibilities. If more investigation is needed before we can quote, we make that next step explicit.
Integrations and access requirements
Acceptance criteria, approvals and exceptions
Ownership, operating costs and exclusions
03
Make the handover part of the build.
We test the agreed workflow and prepare it for the people who will operate it. Deployment, documentation and any support arrangement are defined in scope, with an agreed way to assess the outcome.
Testing against agreed scenarios
Operating guidance and failure handling
Measured outcomes and a clear next step
A good first project has boundaries.
Think a sourced account brief, a support investigation draft or a release-readiness summary. Start with work that repeats, uses accessible systems and has an accountable owner. Open-ended autonomy or an undefined “AI transformation” needs more discovery before it becomes a build.