Software for trade businesses
Internal tools for technician planning, field-service control, proof documentation, and job records - built for real trade workflows instead of abstract office processes.
Learn moreI build internal web apps, automation, and data solutions that fit your actual workflow - instead of forcing your team into off-the-shelf software that does not match how you work.

Many companies start pragmatically with Excel, copy-paste, manual handovers, and isolated tools. That often works for a while. But as complexity grows, sources of error, media breaks, and unnecessary coordination overhead begin to appear.
Good custom software does not just replace a tool. It makes workflows more understandable, reduces operational friction, and ensures that data and processes end up where they are actually needed in daily work.
Before → After
The focus is on software solutions that simplify processes, replace Excel, and cleanly digitize operational work inside the company.
Internal tools for technician planning, field-service control, proof documentation, and job records - built for real trade workflows instead of abstract office processes.
Learn moreI replace error-prone Excel workflows and manual processes with stable software, clearer workflows, and less operational friction in day-to-day business.
Learn moreCustom internal applications for teams that want to work more cleanly, make information centrally available, and digitally support recurring tasks.
Learn moreIf data from web sources, APIs, or existing systems is missing, I build solutions to capture it reliably, prepare it properly, and integrate it into workflows.
Learn moreDashboarding
KPIs centralized and usable
Data integration
Information structured and available
Automation
Less Excel, fewer manual steps
If you want to better understand the background, the blog contains deeper content on Excel replacement, internal tools, data acquisition, and automation.
Both. It is especially valuable wherever Excel sheets, manual handovers, or grown one-off processes are already costing noticeable time, transparency, or reliability.
Yes. Depending on the project, APIs, databases, CSV/Excel imports, internal systems, or external data sources can be connected.
Both. Many projects start with a short analysis of the current workflow so that the result is not just software, but a solution that truly fits operational needs.
Yes. Especially with internal tools, automation, and data-driven processes, continued development often makes sense as requirements grow or workflows change.
Then the best next step is a short conversation about your specific use case.