Automation delivery & team collaboration
Build the workflow. Make it work for the people using it.
I help teams turn repeated manual work into connected software. We can deliver one workflow from source to result or work together on your existing systems. The workflow assessment is an optional starting point when the right approach still needs investigation.
01 / Ways to work together
A clear goal. The right involvement.
Deliver a project
Take one recurring workflow through implementation and validation. We choose rules, APIs or AI around the task, with clear handling for exceptions and human decisions.
- A workflow with agreed inputs and expected results
- Connected sources, transformations and destinations
- Checks using representative examples and exceptions
- Run visibility, operating notes and an agreed handover
Join your team
Add practical engineering capacity for integrations, data processing and browser workflows. I work with the people who do the task and the developers responsible for the connected systems.
- An agreed workflow or integration to own
- Implementation within your existing stack
- Inspectable results and review points
- Shared documentation and operational responsibilities
02 / The first milestone
Something concrete to review together.
Connect the critical path for one workflow, run representative examples and review both successful results and exceptions before expanding the scope.
What we need from you
- A person who performs the workflow and can explain its exceptions.
- Representative inputs and expected outputs, shared through an agreed channel.
- Contacts for source-system access, API permissions and the destination of the results.
03 / Relevant experience
Work in its actual context.
Test Flow – Automated AI based E2E Testing Framework ↗
Personal project · solo delivery · occasional internal use
Product screenshot
A browser flow defined in natural language
Automatically generated image description
This is a screenshot of a dark-themed web application interface named 'FlowTest' for AI testing agent workflows. The left sidebar contains navigation options including Dashboard, Suites, Flows, History, Healthchecks, and Settings, with a prominent green '+ New Test' button. The main panel shows a form for creating or editing a test flow, with fields for 'Flow type' set to 'Reusable / independent' and a description text box. Below are detailed flow steps with numbered instructions and verification checkmarks, each step having options to add verifications or delete the step.
NuMobility – E-Mobility Database, Configurator & Blog ↗
Startup project · pipeline contribution within a team · historical implementation
Product screenshot
Published vehicle rankings · historical interface
Automatically generated image description
This is a screenshot of a web application interface titled 'nu_mobility' focused on electric car rankings. The page is in German and features a clean, minimalistic design with a white background and black text. The main heading reads 'Elektroauto Ranglisten' with a subtitle encouraging users to find the best rankings. There are multiple rectangular buttons in turquoise labeled 'Komplette Liste ansehen' for viewing complete lists of various electric car metrics such as acceleration, trunk volume, charging time, top speed, NCAP rating, and range. A search bar with a turquoise button labeled 'Rangliste suchen' is present. On the left, there is a list of other ranking categories in green text. A cookie consent banner is visible at the bottom right with options in orange and gray buttons.
04 / Practical questions
Before we work together.
Do we need to start with a review or assessment?
No. If the goal and starting point are clear, we can agree a delivery milestone or team involvement directly. A review or assessment helps when you first need an independent basis for the decision.
How much involvement do you need from us?
We need a contact who can make product decisions and access to the relevant technical knowledge. We plan the walkthrough, access, feedback and acceptance together, agreeing a review rhythm that fits your scope.
What determines effort, fee and start date?
Effort depends on source access, data quality, API limits, exception handling and operating requirements. Model and service costs are considered where relevant; fee and schedule are agreed for the chosen scope.
What does the handover include?
We agree the handover before implementation: relevant designs and code, setup and operating notes, open issues and a walkthrough with the people continuing the work. Your existing tools and process shape the format.
Who handles operation and maintenance afterward?
We establish responsibility for operation, monitoring, changes and fixes before handover. Your team can take over, or we can agree further involvement. Ongoing maintenance scope and availability are explicitly agreed.
What needs to work next?
A short introduction to your product, task and team is enough to start. We establish responsibilities, scope and fee together.