Skip to content
RAFITTECH

About

An electrical engineer who ended up automating office work.

RAFIT TECH is a one-person studio. You talk directly to the person who designs and writes the solution — no account managers, no handovers between teams.

How I got here

I started in electrical engineering and industrial automation, not in IT. That way of thinking — diagram, signal, state, failure case — turned out to be an excellent starting point for automating office processes, because it forces the question "what happens when this fails?" long before anything reaches production.

For several years now I have been doing process automation and workflow design professionally. Earlier, at Szczecińska Energetyka Cieplna, I built tools supporting the daily work of internal teams. Today my largest client is Hemmersbach, where as a consultant and Principal IT Solutions Engineer my days are spent on:

  • designing and delivering new integrations and processes,
  • standardising existing implementations — reviewing what is already in place and building modules ready for every case,
  • designing and delivering AI-driven automations for the IT department, taking care of the simple tasks and surfacing the information that matters, so engineers can focus on what really needs them.

All of it in an environment used by hundreds of people.

Practice taught me one thing above all: the most expensive projects are the ones where nobody sat down with the person doing the work and asked how they actually do it. So that is always my first step.

How I work

  • 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.

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.