Services
Consulting, architecture and implementation from one pair of hands
Depending on what you need, these services come as consulting, architecture work, hands-on technical implementation or coaching – on their own or combined. All of them can be measured against quality, cost and delivery.
Architecture Assessment
A structured review of architecture, code quality and the delivery process, with clear priorities for where to act.
Typical starting point
There are doubts about whether the existing architecture will hold up, or a major investment decision is pending and needs a solid technical basis.
What I actually do
I analyse architecture, code quality, technical debt and the delivery process, rank the findings by risk and impact, and set out concrete first steps.
Possible outcomes
- a clear, well-founded picture of where things stand
- a prioritised list of technical risks and bottlenecks
- concrete next steps you can act on
A sensible way to start
A focused assessment over one to two weeks, with a written evaluation.
Modernising software systems that have grown over years
Moving legacy and monolithic structures step by step into modular, maintainable architectures.
Typical starting point
A business-critical system that has grown over years now takes a great deal of effort to extend. Changes are slow and risky.
What I actually do
I work out a solid target architecture and a low-risk path for rebuilding, modularise step by step, and take full responsibility for implementing selected architecture and modernisation work.
Possible outcomes
- modules with clear boundaries that are easier to maintain
- technical debt reduced and kept under control
- changes become more predictable and less risky
A sensible way to start
A modernisation roadmap with a target architecture and the rebuilding steps in priority order.
Clean Architecture and technical quality
Introducing Clean Code, Clean Architecture and measurable quality and architecture standards.
Typical starting point
Code quality and architecture are inconsistent, decisions are undocumented, and new requirements keep adding complexity.
What I actually do
I introduce Clean Code, Clean Architecture and Architecture Decision Records, establish review and testing standards, and support the team in applying them.
Possible outcomes
- consistent architecture decisions that others can follow
- greater testability and maintainability
- a shared understanding of quality within the team
A sensible way to start
Establishing where code quality stands today, and agreeing standards together.
Cloud-native and platform architecture
Target architectures and container platforms with Kubernetes and OpenShift, plus support for cloud migrations.
Typical starting point
A cloud migration or platform modernisation is coming up, and there is no solid target architecture yet, or no in-house platform expertise.
What I actually do
I design cloud-native target architectures, build container-based platforms with Kubernetes, OpenShift, Docker and Helm, and support the migration of existing applications.
Possible outcomes
- a solid, documented target architecture
- a reproducible container-based platform
- a clear, low-risk migration path
A sensible way to start
A workshop on the target architecture and platform strategy.
CI/CD and DevOps architecture
Setting up and evolving automation for builds, tests, quality checks and deployment, with Infrastructure as Code.
Typical starting point
Releases take a long time, involve many manual steps and are easy to get wrong. Shipping is a risk rather than a routine.
What I actually do
I examine the whole path from commit to production and build automated CI/CD pipelines with GitLab CI/CD or Jenkins, backed by Infrastructure as Code and GitOps.
Possible outcomes
- fewer manual steps and sources of error
- shorter, more predictable lead times
- traceable, repeatable deployments
A sensible way to start
A delivery check of the existing release process, with a list of concrete measures.
Secure software supply chain
Automated checking of code and third-party components in the pipeline: SAST, software composition analysis and SBOM.
Typical starting point
There is no reliable record of which third-party components sit inside your own applications. Customers or internal policies ask for evidence, and security updates happen without coordination.
What I actually do
I build static code analysis, software composition analysis and the automatic generation of a software bill of materials permanently into the CI/CD pipeline, and put a proper process around dependency updates.
Possible outcomes
- a reliable overview of the third-party components in use
- vulnerabilities become visible early and automatically
- dependency updates become routine instead of a special project
A sensible way to start
A stocktake of the supply chain with a first SBOM and vulnerability overview.
Guiding technical transformation
Target architectures, roadmaps and hands-on support for technical change across several teams.
Typical starting point
A larger technical change has been agreed, but risks getting lost between day-to-day business, several teams and unclear priorities.
What I actually do
Together with the people involved I develop a technical target architecture and a realistic roadmap, and stay alongside the implementation – including checking its effect against suitable metrics.
Possible outcomes
- a shared target architecture and a prioritised roadmap
- measurable progress instead of scattered parallel initiatives
- changes take hold in everyday work
A sensible way to start
A workshop on target architecture and roadmap with the key people involved.
Technical coaching and enablement
Enabling developers, architects and teams through pair and ensemble programming, reviews and workshops.
Typical starting point
New practices or technologies need to be introduced, or the team should take on more responsibility for architecture and quality itself.
What I actually do
I work directly with the teams: pair and ensemble programming, reviews, katas and workshops, so that new knowledge takes root in practice and lasts.
Possible outcomes
- teams become more technically self-reliant
- new practices are actually applied
- knowledge stays in the company after the project ends
A sensible way to start
A focused coaching phase built around a concrete technical task.
AI-ready system modernisation
Preparing architecture, interfaces and data so that AI capabilities can later be integrated in a controlled way.
Typical starting point
The company wants to use AI capabilities, but the existing systems, data and interfaces are not yet ready for it.
What I actually do
I modernise the technical foundations: clear interfaces, well-ordered data flows, a modular architecture and a dependable supply chain – the prerequisites for safe and traceable AI integration. On request, this also covers running models on your own infrastructure and connecting them to existing applications. The focus is on architecture and operations, not on training your own models.
Possible outcomes
- clean interfaces and data flows
- a modular architecture as the basis for AI capabilities
- the groundwork for a controlled, maintainable integration
A sensible way to start
A baseline review: how AI-ready are your architecture, data and delivery today?
Embedding AI-assisted development in the team
Introducing agentic tools and human-in-the-loop workflows in a way that preserves quality and traceability.
Typical starting point
AI tools are already part of everyday development, but with no structure around them. There are no binding guard rails for how results are reviewed, documented and owned.
What I actually do
I establish traceable human-in-the-loop workflows: clear review responsibility, project-specific agent rules, connection to existing systems via MCP, and automated consistency and quality checks as a safety net.
Possible outcomes
- binding guard rails instead of everyone doing it their own way
- reviewed, traceable results with clear responsibility
- noticeable relief from routine work without any loss of quality
A sensible way to start
Taking stock together, working through a concrete task from everyday development.
Not sure where to start?
A short architecture assessment is often the easiest first step. In a conversation we can work out the starting point that makes most sense for your situation.
Get in touch