The everyday problem
Your workflow shapes the software.
When information is spread across spreadsheets, chats and separate tools, even a simple question takes work. I build applications where your team can find what it needs and act on it. We start with the part that is slowing you down most.
Data models, access, interfaces and operations are planned together. The first version solves a concrete need. Further modules can be added without forcing every extension to reshape the entire application.
What we will work on together.
The scope follows your project.- 01
A clear foundation
A data model and clearly structured architecture
- 02
Built for your team
A responsive interface, server-side validation and appropriate access control
- 03
Ready to operate
A verified build, a traceable release process and a technical handover
From my work
See what this looks like in practice.
Sales CRM
A CRM that moves with the way the team works.
Boards, inboxes and appointments work together. The team can adapt its sales processes directly.
- Boards shaped around the process
- Emails linked to the right card
- Calendar and team controls
- Next.js 16
- React 19
- TypeScript
- +3
Modular business platform
From a crowded inbox to a connected business workspace.
Seven business areas under one login, from email and payment checks to projects and daily briefings.
- Seven connected business areas
- AI-assisted inbox workflows
- Daily briefings for the team
- Next.js 15
- React 19
- TypeScript
- +4
AI dictation app and voice product
Speak your thoughts. Get straight to work.
Speak instead of typing. Dictation, AI editing and translation put your thoughts straight into the active text field.
- A hotkey instead of switching apps
- Turn speech into usable writing
- Think in one language, write in another
- Tauri
- Rust
- JavaScript
- +2
Our first conversation
Let us walk through a real piece of work.
You do not need a finished technical specification. Your idea, an example or a look at the current workflow is enough to start.
Let us talk it through- 01
Who uses the system, and which tasks need separate permissions?
- 02
Which data and existing tools need to be connected?
- 03
What must the first version do, and what can be added as a module later?
You might also be wondering:
Felix SchumannAI automation engineerName it, I build it.
If something here looks like the problem you have, write to me. A short description of what is not working is enough to start.
