Automation for everyday work
I map the steps that repeat from one week to the next, and build the automation or tool the need calls for. The scope follows whatever would make everyday work easier.
Where we start
The work starts from your current workflow. I go through the steps it contains, the data and tools each step uses, and the points where a person makes the decision.
The assessment shows what is worth automating first and what is worth leaving to a person. The scope of the build is drawn from that, and it is written down before anything is built.
- Workflow
- Data
- Tools
- Decision points
- Scope
What we can build
A build is usually one clear thing that handles one repeating step. Three examples give the size of the work.
Incoming enquiries can be routed straight to the right person. A recurring report can be assembled in the form it is read in. Message drafts can be prepared for a person to check, so the sender decides the final wording.
These are possible uses, and the one that fits your business comes out of the assessment.
- Routing
- Reporting
- Message drafts
- Human review
From assessment to implementation
The scope is agreed case by case, based on what the assessment showed. We also agree the examples that will show the build works.
The build is tried against those examples before it goes into use. How to run it and what is needed to carry it forward are documented, so the whole thing is yours once the work is done.
- Scope
- Trial run
- Rollout
- Documentation
Tools I have built
I built my own tools myself and use them daily. They are open to try, so you can see the standard of the work before anything starts.
Explore my applications- My own apps
Tell me which task keeps repeating
One repeating step is enough to start from.
Let's start with a conversation