Custom software
When the spreadsheet that grew for years hits its limit and the off-the-shelf product doesn't know the one step that matters: an application that follows the route your business actually takes.
More on custom softwareApplication Development
Software that adapts to how you work. Not the other way round.
I'm Jeff. Since 2024 I've been a qualified IT specialist for application development — and ever since, my job has been to make custom software solutions happen for our clients. From the first fuzzy idea to the day nobody thinks about the tool any more, because it simply works.
// Client request: "Can't this just happen by itself?"
public async Task<Ergebnis> VerarbeiteAsync(Auftrag auftrag)
{
var geprueft = await _regeln.PruefeAsync(auftrag);
if (!geprueft.IstGueltig)
return Ergebnis.Abbruch(geprueft.Hinweise);
await _erp.UebertrageAsync(geprueft.Daten);
await _archiv.LegeAbAsync(geprueft.Belege);
return Ergebnis.Erfolg($"{auftrag.Nummer} verarbeitet");
}Yes, that is real code and not a stock photo of a screen. The identifiers are German — entirely normal in a German codebase, and usually the right call: the domain language belongs in the code.
2021
first line of code — out of sheer curiosity
2024
qualified in application development
35+
course certificates collected on the way
2
cats on the quality assurance team
Services
Three questions I answer most often
It usually starts with a sentence like “we've always done it this way, but really we should …”. That's exactly where I come in.
Interfaces & integration
ERP, document management, inventory systems, databases, third-party software: programs that previously knew nothing about each other exchange data reliably afterwards — without the “just retype it once” step in between.
More on integrationAutomation
Describe the repetitive manual work properly once, verify it, pin it down — and then never do it by hand again. Reports, documents, transfers, routine checks.
More on automationApproach
Not off the shelf
Good software rarely comes together at a desk alone. It comes together where somebody explains why this one intermediate step has been necessary for years — and where you listen long enough to notice that it isn't necessary any more.
So understanding comes before building. What happens today, who is involved, where does time disappear, and what must absolutely not break? Only then comes the decision whether new software is needed at all — or whether a small bridge between two existing systems will do.
And because I spent fifteen years working with customers before moving into IT, I know this much: the best solution is the one nobody notices two weeks later.
01
Listen, and write it down
The process as it really is. Including the exceptions that “basically never happen”.
02
Start small, show early
Something you can click on beats a perfect concept document nobody has read.
03
Hand over, don't walk away
Documentation, training, staying reachable. Software doesn't end at delivery.
Read on
Three ways through this site
Profile & background
How a phone app in the autumn of 2021 turned into a vocational qualification. And what came before.
To the profileStack & qualification
What I work with, what I've learned, and where I'm currently digging deeper.
To the stackProjects & lab
Personal projects, GitHub — and two small tools that run right here in your browser.
To the projectsGot a process that annoys you?
Tell me about it. A first conversation costs nothing but half an hour — and afterwards you'll know whether software is worth it at all.