I'm Michael. For the past five years I've worked with financial systems, large data platforms, and AI. I redesign workflows so teams spend less time copying information and more time doing the work they were hired for.
Problems I solve
I start by finding where time gets lost, build the right solution, and stay involved after it goes live.
I turn repeated tasks into clear workflows: an event starts the right checks, the data is cleaned up, and the result reaches the person responsible.
I connect CRMs, ERPs, email, messaging tools, databases, and external APIs so information moves between them without being entered twice.
I use OpenAI, Claude, and Gemini where they earn their place: reading documents, drafting replies, classifying requests, and searching internal knowledge.
I design ETL pipelines, data stores, and reports for high-volume workloads. In finance, these systems handled millions of events each day.
I help smaller companies choose tools, set up infrastructure, and establish sensible working practices without accumulating software they do not need.
I monitor live workflows, fix failures, document changes, and train the team. As the process grows, the system can grow with it.
Background
I began in financial software, then moved into large data platforms and machine-learning workloads processing millions of events a day. That experience taught me to pay equal attention to the code and to the way a business actually uses it.
My main focus now is practical automation. I connect services, add AI only where it helps, and take each solution far enough that it works reliably on an ordinary working day.
Most of my clients are small and mid-sized companies. We can start with one troublesome process, then expand the system as new needs appear.
How the work runs
At every stage, you know what is finished, what comes next, and which result we are checking.
In a free introductory call, we look at the current process, its bottlenecks, and its constraints. If automation is not the right answer, I will say so.
I outline the workflow, integration points, timing, and acceptance criteria, so the scope is clear before development begins.
I configure the integrations, test routine and edge cases, then introduce the solution using real data.
I show the team how the solution works, leave clear documentation, and agree on the support needed after launch.
Is one process slowing the team down?
Describe the problem briefly in the form or contact me directly. In the first call, we will work out what is worth automating.
Prefer not to use the form? Contact me directly: