Maastricht software studio
Automation, internal tools, and practical software built directly in Maastricht.
Practical by design
Automation
I turn the repetitive steps between inbox, spreadsheet, and next action into one dependable flow.
Workflow Fix: map one task and leave with a prototype or priced next step.
Tools + websites
A focused tool or site should remove uncertainty, not add another layer to maintain.
Evidence, not theatre
Small software still deserves proper engineering: clear scope, working code, and an owner you can reach.
A practical first response, not an automated sales sequence.
Say helloOne builder, many layers
Python, Java, TypeScript, containers, networks, and the useful bits between them.
Map the bottleneck and leave with a prototype or priced next step.
View sprintA housing monitor, transit router, and self-hosted stack you can inspect.
Open workScoping, building, and replies stay with Raman in Maastricht.
Local storyFirst beat
A screenshot or rough explanation is enough.
I’ll find the first useful move.
Second beat
Start where the payoff is visible.
A useful step beats a giant roadmap.
Third beat
Build directly with the person doing the work.
Small enough to start. Real enough to use.
