A report has to be assembled manually every week or month
Data is copied between files, spreadsheets, or systems, and producing the final result takes more time than it should.
Reporting · Automation · Data · Analytics
I automate reporting and data work where manual processes start holding the business back.
From a single report or Excel-based process to a structured data flow, I choose the solution around the real need instead of starting with a specific technology.
When it's worth talking
Data and reports work — until someone has to keep them running by hand.
Most of the time, there is no need to rebuild everything. The best place to start is where the process consumes the most time, creates errors, or depends too heavily on manual work.
Excel has become a process that is hard to change safely
The file has grown over the years, contains many dependencies or manual steps, or only works reliably when one specific person handles it.
Data needs constant cleaning and combining before reporting
Sources are inconsistent, structures change, or data has to be prepared manually before every reporting cycle.
An existing report or Power BI setup is no longer reliable
Numbers do not reconcile, refreshes are unstable, the logic has become difficult to maintain, or the reporting setup needs to be brought back under control.
It is unclear where the real bottleneck is
Reporting spans several files, systems, and people, so the data flow and responsibilities need to be understood before anything is automated.
The same data gives different answers in different reports
KPI definitions, filters, or preparation logic differ between files and reports, making it difficult to know which version to trust.
How can I help
From a single report to a structured reporting process, I shape the scope around what you actually need.
Not every challenge needs a new system or a large project. Sometimes the right solution is to fix an existing report, automate a few manual steps, or get the data into better shape. I define the scope around the situation instead of forcing the situation into a specific technology.
How I work
I understand the problem first. Then I choose the solution.
The scope depends on the problem — sometimes one report needs fixing, while other situations require understanding the whole process first. In both cases, the way I work stays simple and transparent.
We talk about the problem
I start with what is not working today, takes too much time, or makes the report or process harder for its users.
I review the current way of working
I look at the data, files, reports, and manual steps only as far as needed to understand the source of the problem.
We define the scope
I propose the simplest scope that solves the right problem without adding technology or features that are not needed.
I build and verify the solution
I implement the agreed solution and verify it against real data and the scenarios the team will actually use.
I hand over the solution and stay available
I document the key elements and explain how the solution works. The collaboration does not have to end at delivery — I can continue supporting the solution, help when issues arise, and develop it further as new needs appear.
About
I combine business and technical perspectives to solve the right problem — not just build another tool.
I have spent the past eight years working with reporting, data, and automation in corporate environments, collaborating across business functions ranging from finance and controlling to logistics, purchasing, and operations. I combine that business perspective with hands-on technical experience, allowing me to move from understanding the problem to building a solution that works in the company's real environment without unnecessary complexity.
I understand the process, not just the tool
Before I start building a solution, I want to understand where the data comes from, who uses it, and what decision or work depends on the result.
I connect reporting, data, and automation
I do not treat Excel, Power BI, or data flows as separate worlds — I choose the elements that work together to solve the specific problem.
I understand the business from different perspectives
Years of working in corporate environments have taught me to look at reporting and data from the perspective of different functions — including finance, controlling, logistics, purchasing, and operations. That helps me understand not only the data itself, but also the decisions and processes it is meant to support.
I build solutions that can be maintained
Clear logic, documentation, and the simplest practical architecture matter more to me than a solution that looks impressive but becomes difficult to develop later.
Technology is a means, not the starting point
I do not start by assuming the answer is Power BI, Python, or a new system. I first look for the smallest solution that actually solves the problem.
You work directly with me
ETLens is my expert-led brand — from the first conversation through analysis, implementation, and handover, you work with the person who actually designs and builds the solution.
Work
Selected projects and case studies live in the Work section.
I publish only material that can be shared without exposing employer or client confidential information. I do not fill the portfolio with invented examples.
Let's talk about your project
Having trouble with reporting, data, or a manual process? Let's start with a conversation.
You don't need a finished brief or to know which technology you need. Tell me briefly what isn't working today, takes too much time, or needs to be brought under control — we'll work out the next sensible step.
Once scope and price are agreed, projects are currently contracted and settled through Useme. Useme acts as the settlement intermediary and issues the client invoice under its current platform rules; ETLens does not issue the invoice directly.