Does consulting require a later development project?
No. The assessment can remain independent and be used by your team or another supplier.
SERVICE
Technical consulting and software architecture
I support teams and product owners when understanding must come before building: reviewing a codebase, selecting an architecture, reducing technical risk or defining the right sequence of interventions. The goal is not more theory, but a decision that is clear and actionable.
Let’s talk about your projectALREADY RUNNING SOFTWARE OR PROCESSES?
Software & Automation Assessment
We start with a workflow that slows people down or a part of your software that causes problems. I assess where custom development, integrations or AI can help.
Manual hand-offs · Legacy · Missing APIs · Technical debt · Repetitive tasks
The outcome of the review
A map of bottlenecks and an action plan: priorities, risks, effort and automation opportunities to validate.
A focused scope agreed around the problem. It can stand alone or become the starting point for development.
Let’s talk about your project- 01
Observe
We map a workflow with its users and review the relevant code or integrations.
- 02
Assess
We separate bottlenecks from their effects and compare options, with and without AI.
- 03
Decide
You receive priorities, risks and an effort estimate to choose the first intervention.
When a technical review helps
- You need to choose between several solutions and make costs, risks and consequences explicit.
- A codebase is slowing the team down, but the first useful intervention is unclear.
- You are preparing a new product, migration or critical integration.
Consulting outcomes
- A technical assessment of the context, constraints and main dependencies.
- A comparison of options with explicit trade-offs, risks and decision criteria.
- A reference architecture or prioritised intervention plan.
- Support for the team during the first decisions or implementation stages.
PROCESS
From diagnosis to action
- 01
Collect evidence
I start from code, workflows, available metrics and conversations with the people using or maintaining the system.
- 02
Separate symptoms from causes
We identify which problems are structural and which can be resolved with smaller interventions.
- 03
Make trade-offs visible
Each option is considered against time, skills, operational cost and ability to evolve.
- 04
Define the next step
The engagement ends with owners, priorities and a first verifiable action, not an isolated document.
FAQ
Common questions
Can you run a focused codebase review?
Yes. We first define the decision or risk to investigate, so the review produces concrete guidance rather than a generic list.