Projects & case studies
Anonymised projects. Concrete technical decisions.
Each example shows the starting point, the critical technical question, my role and the result — without client names and without sensitive system details.
- Connecting existing systems and data sources
- Integration
- Internal processes and reporting
- Business software
- Critical business logic and transactions
- Platforms
- Clarification · Architecture · Delivery · Operations
- End-to-end
Connecting existing systems and data sources
Internal processes and reporting
Critical business logic and transactions
Clarification · Architecture · Delivery · Operations
In practice
Not just building software. Making the right decision.
The projects differ considerably in technical terms — mobile image processing, escrow logic, data integration, ERP connectivity. What they share is the point at which things got critical: a technical question that had to be answered before development, because the wrong answer would have carried the entire project.
Technology is the tool. The dependable decision is the result.
Case studies
Every project had one critical technical question.
Some projects are subject to strict confidentiality and security requirements. The case studies are therefore anonymised and contain no client names, logos or identifying details.
The shared principle
Different projects. The same way of working.
- 01
The critical question first
Every project has one technical question that everything else depends on. It gets answered first, not last.
- 02
Decision before implementation
Requirements, architecture, interfaces and risks are understood before development budget is committed.
- 03
Custom development
The software is built to fit the requirement, rather than the requirement being bent to fit an existing product.
- 04
The whole system
Frontend, backend, data, integrations and infrastructure are treated as one connected system.
- 05
Production-oriented
The goal is not a prototype but software that actually holds up in operation.
End-to-end
One technically accountable person for the whole path.
The projects differ considerably in technical terms. The approach still follows the same order.
- 01
Frame
Understand the goal, the problem and the system landscape — operationally, not only technically.
- 02
Clarify
Make risks, architecture and effort dependable before development budget is committed.
- 03
Build
Implement with focus, with the technical questions decided rather than left open.
- 04
Hand over & evolve
Stabilise close to production, hand over documented, and extend along real requirements.
Your project
Are you facing a similar decision?
Describe the situation and the open technical question at a high level. After a short review you will get the next sensible step.