APPLIED INTELLIGENCE / WORK WITH ME
AI workflow automation
I design and build workflows that connect the repetitive steps between your tools. For businesses, teams and independent founders, the starting point is a concrete task: what comes in, what needs to happen, and what a useful result looks like.
Discuss your projectWhere automation could help
A possible project might turn incoming enquiries into organised records and draft replies for review. Another might collect research material, prepare a summary, and pass it to the person making the decision. These are examples to explore together; the right workflow depends on your actual tools and information.
We separate predictable steps from tasks that need language interpretation. Moving a file or applying a clear rule may need ordinary automation. Reading an unstructured request may benefit from AI. Each part should earn its place in the process.
Start with one complete task
Show me how the work happens today, including the awkward exceptions. Useful inputs include a few representative examples, the systems involved, who owns each step, and where mistakes cause extra work. A technical specification is not needed for the first conversation.
We agree on a useful first scope, deliverables and budget before building. That could be advice on the process, a prototype to test an uncertain step, or a defined workflow connecting the pieces. Access requirements and ongoing tool costs belong in that discussion.
Test the handoffs, too
Testing covers the path through the workflow and the points where information is missing or a tool fails. We decide when the system should ask for help, and which actions need a person to approve them before anything is sent or changed.
For implementation projects, the handover explains how to use and manage the result. The aim is a workflow you can understand: where it starts, what it does, and who takes over when an exception needs attention.
BEFORE WE BEGIN
A few practical questions.
Can you improve an existing automation?
Yes. We can start with the unreliable step or the manual work around it. Share the intended behaviour and a few examples of what goes wrong so we can define the repair before expanding the system.
Do we need to replace our current tools?
The starting point is the tools you already use. We check the access and connection options before deciding what can be linked, what needs a different approach, and whether a change is justified.
A USEFUL FIRST STEP
Tell me what you’re working on.
A few sentences about your idea or bottleneck is enough to start. We can work out the scope together.
Opens an email to me@aronbijl.com.