An Enterprise Architect who speaks business, not just tech
I work with senior business and technology leaders on high-stakes technology decisions — where the consequences are financial, operational, and strategic, not just technical.
Starting from business priorities, I align IT strategy, project portfolio, and spend so that technology serves the business — and bring order when the path forward is unclear.
Or ask my assistant
It knows my track record, how I structure engagements, and the problems I typically work on — and can tailor a résumé or forward a vacancy.
What an Enterprise Architect actually does — in my practice
Say “Enterprise Architect” to most leaders and two images come up: TOGAF diagrams, or a Solution Architect with a bigger title.
My role is different. I sit at the business–technology interface: helping leadership see the organization as a system, connect strategic intent to structural choices, and decide where to invest, consolidate, or change direction.
I use enterprise architecture as a decision discipline, not as documentation.
When leaders typically bring me in
BUILD — launching new capabilities
- Standing up a new business unit, product, or platform from zero.
- Designing operating models and architecture that can scale with the business.
- Moving transformation programmes from slides to shipping.
FIX — restoring order after disruption
- Post-M&A integration: realigning overlapping systems, data, and ownership.
- Reorganization: connecting structure, processes, and IT to a new strategy.
- Cost and risk: reducing run-costs and legacy exposure without damaging critical capabilities.
I am most useful when an organization is about to change direction. Less useful for steady-state administration.
How I work
- Frame the decision. Most initiatives stall because the real decision is never clearly stated. My first contribution is usually to name it — which takes a grounded read of how the enterprise actually works.
- Surface the trade-offs. Cost, risk, speed, reversibility, strategic fit — made explicit so leadership can choose deliberately rather than default.
- Design the target state. A structured view of where the organization is going, and the minimum changes that get it there.
- Stay close to execution. I work directly with data, teams, and prototypes to make sure the decision holds up in reality.
Selected outcomes
- National top-2 aviation hub. Product portfolio reduced from 4,600 to 1,200 items and time-to-market cut threefold — by rebuilding classification, lifecycle rules, and governance across 19 legal entities.
- Major European retail group. A post-merger core-retail-platform roadmap that made retain / rationalize / replace trade-offs explicit — optimizing IT investment by removing functional duplication across banners and regions.
- European industrial equipment manufacturer. A subscription-management blueprint that moved the business from one-time equipment sales to recurring service revenue — bridging CRM, subscription, and ERP into a single order-to-quote flow.
(See the Cases section for the full project list.)
How we can work together
For a bounded decision, we work in a fixed-scope project of roughly 6 to 16 weeks — an assessment, a target operating model, a portfolio rationalization, an architecture audit, or a specific transformation call.
When the decisions keep coming, a fractional or embedded arrangement makes more sense: a regular rhythm with the CTO, CIO, or CEO over a series of related choices, typically a few days per week or per month.
And when a board, investor, or PE firm needs an independent read on a portfolio company or a single technology decision, I take on expert due diligence or a second opinion — a matter of days to weeks.
Architecture-as-code — an open methodology I build
My practice treats enterprise architecture as a decision discipline, not documentation. Transitrix is where I take that conviction further, in the open: an architecture-as-code methodology that describes an enterprise as text — its goals, capabilities, processes, and roles. Because the model is text, it can be versioned in Git, reviewed like code, and read by both people and machines. It builds on open standards (ArchiMate, BPMN) and is MIT-licensed.
Alongside the methodology I build Transitrix Studio, an editor extension and CLI that authors and previews these models directly in VS Code and other IDEs. It is a research initiative, not a product I am selling here — but it reflects how I think architecture should work: legible, current, and owned by the organisation rather than locked in a tool.
More at transitrix.com.
Let’s talk
If you are facing a complex technology decision — M&A integration, a scaling programme, cost restructuring, an AI adoption question, or a stalled transformation — a short conversation is usually the best way to see whether an architectural perspective would help.
Email: vkgeorgia@icloud.com · LinkedIn: Valerii Korobeinikov
No sales pitch. Just a structured discussion about your situation.