Process automation
Repetitive manual work turned into a process that runs itself — from pulling the data, through validation, to the report in your inbox.
Process automation · Web applications
Automation that pays for itself in weeks, not quarters
I design and ship solutions that take repetitive work off your team — from mapping the process, through the integrations, to a finished tool. Fixed scope, fixed price, and a first working delivery measured in weeks.
- Your savings before my scope of work
- Fixed scope, fixed price
- Weeks, not months
Today ≈ 2 days of work every month
- Attachments from three systems
- A spreadsheet assembled by hand
- Checking, fixing, sending
After a few minutes, with nobody involved
- Data pulled automatically
- Validation and calculations in the background
- Finished report in the inbox
A typical reporting automation.
What I do
From a single script that saves a day a month, to an application that runs the whole process.
Web applications
Internal tools, dashboards and calculators built around your process — instead of bending the process to fit an off-the-shelf box.
Integrations & APIs
Systems that don't talk to each other start exchanging data — over an API, files, a database or e-mail, whatever is actually available.
Process modelling & gap analysis
Before anything gets coded — a map of the process, its bottlenecks and the places where work quietly disappears. Sometimes the best fix needs no code.
Reporting & data processing
Data from many sources, one consistent truth, and a report that builds itself in the format you actually use.
How I work
Four rules I hold to on every project — including when they are inconvenient for me.
Your savings before my scope of work
If the problem can be solved with a setting in a system you already own, I will say so plainly — even when it means a smaller project for me.
Fixed scope, fixed price
Scope and price are agreed before we start and do not move afterwards. The risk of it taking longer sits with me, not with you.
Weeks, not months
A first stage is typically two to six weeks from the first conversation to a tool your team actually uses.
Every requirement matters
Exceptions, odd cases and "well, sometimes it also happens that…" — that is exactly where the value hides. I write them down and solve them instead of simplifying them away.
From first contact to delivery
No surprises, and no invoice you didn't see coming.
- 01
Conversation and process map
I talk to the people who actually run the process and draw it out step by step. This is usually where the gaps and the unnecessary steps surface.
- 02
Scope and quote
You get a short document in plain language: what will be built, what is out of scope, what it costs and when it will be ready. One number, no hourly billing.
- 03
Build, with progress in the open
I work in short cycles and show working pieces as they land. Feedback goes in during the build, not after handover.
- 04
Handover and support
Documentation, code and access are yours. I stay available for as long as you need — without making you dependent on me.
Products
Tools I build and run under my own brand.
From the blog
On automation, the technologies I use, and how I run projects.
1 min read
Why Python and React, and not something trendier
A stack is a decision for years, not for one project. I pick boring, proven tools — so the thing is still maintainable three years from now.
- Python
- Stack
1 min read
Fixed price, fixed scope: how I run automation projects
Hourly billing rewards slow work. So I price the outcome, not the hours — and both scope and price are known before we start, and don't move afterwards.
- Automation
- How I work
Got a process that eats your team's time?
Describe in two sentences what happens today. I'll tell you whether it can be automated, roughly what it costs and how long it takes — before either of us signs anything.