Who is behind it
I build systems that take on real work.
My name is Paul Kahle, and Nori Works is my software and automation studio in Schongau. No agency, no layer of account managers: you talk directly to the person who also builds.
- Based in
- Schongau, Upper Bavaria
- Working
- Across Germany & online
- Form
- Sole proprietorship (Einzelunternehmen)
- Focus
- Software & automation
I like technology when it makes a specific task better. A request lands where it should. A status is visible at a glance. A recurring email does not need to be rewritten from scratch every time. These things sound small, but they are exactly where a lot of time disappears.
That perspective does not only come from software projects. I completed my master’s in Edinburgh and I am also the founder and managing director of a trades business in Munich. So I know the other side too: full days, unclear handovers, customer requests, and systems that need to work in real life.
AI plays a role in that, but it is not the centre of everything. Sometimes a model helps, sometimes a clean form, a solid interface, or a small dashboard is enough. What matters is that the workflow becomes easier to understand and easier to use.
Alongside client work I build my own products, including large ones. What drives me is the question of what a single person can build today, working with teams of AI agents and well-built workflows. What I learn there feeds straight back into client work.
I do not build systems that do whatever they want in the background. When something is sent, paid, deleted, or signed off on, an approval step stays in the workflow. The system prepares. You decide.
I will also tell you when something is not worth building. Not every process needs automation and not every idea needs its own tool. Often the best first step is smaller than you expect.
Nori Works is based in Schongau, Upper Bavaria. I work with businesses in the region just as well as online and across Germany. What matters is the workflow, not the postcode.
Good automation takes work off your plate without taking control out of your hands.
How I approach projects
- 01
Understand first, build second
Before any code, it needs to be clear which problem is actually being solved. That listening is what saves the most time later.
- 02
Small enough to ship
Version one does not need to do everything. It needs to solve the most important part reliably and be built so you can keep going from there.
- 03
Approvals stay visible
Automation can prepare, sort, and suggest. For critical steps, it stays clear who decides and who triggers the action.
- 04
Handover is part of it
A system is only finished when you know how it runs. Documentation, onboarding, and a clear state are part of the deal.
Why this site is this plain.
No frills here, on purpose. Could I add more effects? Sure. Elaborate websites are easy to build these days, and they prove very little. The question is whether they help you read.
This site loads fast, says clearly what I offer, and leaves you alone: no tracking, no cookie banner, nothing that blinks or pops up. I build systems the same way. First the part that carries the day-to-day, decoration later, if at all.
If you have a workflow that is costing too much time or keeps getting stuck, write to me. It usually does not take long to see whether a small system could help.
Paul Kahle
Founder of Nori Works
Working together
Got a process that should run better?
Describe it in a few sentences. You get an honest take on whether it can become a working system, and what that would look like.