Home
When IT complexity blocks sound decision-making
Not through new tools or target architectures,
but through structured analysis of existing systems, costs, and
dependencies.
Typical situation
- historically grown IT landscapes
- rising infrastructure and operating costs
- unclear responsibilities and dependencies
- high-risk decisions without a solid factual basis
My role
I work independently, vendor-neutral, and without a sales agenda. My contribution is clarity — enabling you to make informed decisions about what makes sense and what does not.
What comes next
The engagement typically starts with a time-boxed infrastructure assessment (4–6 weeks).
Infrastructure Assessment
Clarity on costs, dependencies, and risks
Many mid-sized companies know that their infrastructure is too expensive and too complex — but not why, where exactly, or what can be changed safely.
The infrastructure assessment provides exactly this clarity.
When this assessment makes sense
This assessment is right for you if:
- your IT infrastructure has grown organically over time
- infrastructure costs are continuously increasing
- dependencies between systems are no longer transparent
- simplification is desired, but without operational or regulatory risk
- decisions are discussed internally, but no solid factual basis exists
It is not intended to sell a new tool, platform, or cloud migration.
What the infrastructure assessment is
A time-boxed, independent assessment of your existing infrastructure.
- Duration: 4–6 weeks
- Delivery: remote
- Role: independent, with no vendor or tool agenda
- Goal: enable informed decision-making
No project, no transformation, no obligation to proceed.
What I analyze
The focus is deliberately on structure, not on technology details.
-
Costs & cost drivers
- Where do ongoing infrastructure costs arise?
- Which costs are structural — and which are historically grown?
- Where are you paying for complexity instead of value?
-
Dependencies
- Which systems depend on each other technically or organizationally?
- Where do dependencies prevent simplification?
- What can be analyzed in isolation — and what cannot?
-
Risks
- Operational risks (operations, stability, recovery)
- Regulatory risks (dependencies, traceability, control)
- Risks from implicit assumptions or missing documentation
-
Simplification potential
- What is redundant, oversized, or historically grown?
- What can be shut down, consolidated, or decoupled?
- What must not be touched?
What is deliberately not part of the assessment
- no tool or vendor recommendations
- no cloud or platform agenda
- no migration projects
- no theoretical models
The assessment first answers the question:
“What makes sense — and what does not?”
Typical next step
After the assessment, you decide how to proceed:
- implementation of clearly defined individual measures
- targeted sparring on architecture or cost decisions
- fractional engagement over a defined period
- or no further collaboration at all
There is no implicit obligation.
Who this assessment is not for
- startups or greenfield projects
- organizations looking for tools or vendors
- “we want to rebuild everything anyway” initiatives
Non-binding introductory call
If you want clarity about your infrastructure —
without a sales agenda and without new risks:
Duration approx. 30 minutes · no preparation required.
Way of Working
Decision readiness before actionism
I work with the goal of enabling clear, well-founded decisions — before money, time, or risk are committed to action.
My approach
-
Independent and vendor-neutral
No tool, cloud, or vendor agenda. -
Focus on costs, risks, and dependencies
What consumes budget? What creates complexity? What must not be touched? -
Business-oriented communication
Results are equally understandable for executive management, IT, and audit. -
Realistic rather than visionary
No target states that are operationally or regulatorily unsustainable.
What you get
- Transparent decision foundations
- Clear options with consequences
- Priorities based on impact and risk
- No implicit obligation to implement
Collaboration
Time-boxed, remote, and focused.
No project pressure. No dependency.
Next step
Schedule a non-binding introductory call
Duration approx. 30 minutes · no preparation required.
Introductory Call for the Infrastructure Assessment
Clarity on the current situation, key questions, and the next sensible step.
→ Simply select a date, see available time slots, and book directly!
- Duration: approx. 30 minutes
- Format: Remote (video or phone)
- Preparation: not required
Let’s talk!
Address
E-mail address
Phone number
© 2026 by spotlight core²code