How do I know which service fits my problem?

You don't need to know up front. Describe the workflow that costs you time, and I'll place it and propose the simplest solution that reliably covers the process. The service areas on this page are for orientation, not a menu you have to order from.

Can you work with our existing Excel files, macros or tools?

Yes. Many projects start with a file that has grown over the years. It gets stabilized and documented first, then extended. A rebuild only makes sense when the structure itself is the problem.

Who owns the code at the end?

You do. You receive all source files, the documentation and a walkthrough so your team or another provider can keep developing the solution. That goes for Excel macros as much as for web applications.

Do you use AI on sensitive data as well?

Only with a clear data concept: what does the model see, where does it run, what gets logged? Where necessary, locally hosted models or anonymized data are used. I don't make blanket promises about what's permissible; that's settled for your specific case.

Services

Automating manual processes: from Excel macros to web applications

Each service area is named after the problem it solves. This page gives you the overview and helps you place your own situation; the details live on the individual service pages.

Excel automation

Reports, calculations and reconciliations done by hand in Excel, again and again.

Data automation and web scraping

Information gathered from websites, portals, PDFs or files on a regular basis.

More on data automation and web scraping

The problem: The data exists, but it's scattered and somebody collects it by hand.
Typical situation: Staff open the same sources week after week, copy values into a spreadsheet and check what has changed.
Possible solution: A program pulls the sources on a schedule – websites, APIs, PDFs, files – validates the data and delivers it in a structured format. Usually built in Python.
A good fit when: … the research is recurring, the sources are accessible, and collecting is the bottleneck.

Reporting and dashboards

Reports and analyses assembled from several files every single time.

Custom web applications

Processes that have outgrown Excel.

AI automation

Recurring work with texts and documents that fixed rules can't capture.

Which tool fits which problem?

The technology follows from the process. As a rough guide:

Excel/VBA: A clearly bounded, table-based process handled by one person or a small team, with data from a few known sources.
Python: Data processing and automation in the background: fetching, validating, transforming and passing data along, without anyone pressing a button.
Report or dashboard: Recurring analysis and visualization. An auto-generated report when it's read at fixed intervals; a dashboard when numbers are needed continuously.
Web application: Multiple users, permissions, central data, change history, or a process that has simply become too complex for Excel.
AI (language models): Unstructured information: texts, documents, free text. Always embedded in a controlled process, never as an end in itself.

These are guidelines, not hard rules. The best solution is often a combination – say, a Python pipeline that collects the data and an Excel file where the team keeps working with it.

You don't need to know which tool fits your process. We'll figure that out together, based on how the work actually gets done.

Talk it through

Frequently asked about services

Answers before you have to ask.

How do I know which service fits my problem?: You don't need to know up front. Describe the workflow that costs you time, and I'll place it and propose the simplest solution that reliably covers the process. The service areas on this page are for orientation, not a menu you have to order from.
Can you work with our existing Excel files, macros or tools?: Yes. Many projects start with a file that has grown over the years. It gets stabilized and documented first, then extended. A rebuild only makes sense when the structure itself is the problem.
Who owns the code at the end?: You do. You receive all source files, the documentation and a walkthrough so your team or another provider can keep developing the solution. That goes for Excel macros as much as for web applications.
Do you use AI on sensitive data as well?: Only with a clear data concept: what does the model see, where does it run, what gets logged? Where necessary, locally hosted models or anonymized data are used. I don't make blanket promises about what's permissible; that's settled for your specific case.

Next step

Which task eats your team's time every week?

Whether and how a process can be automated is usually settled in one short conversation, not a requirements document. You describe how the work is done today. I tell you which approach is worth considering and whether it will pay off.

Let's talk automation Book a quick call