Digitalisation

What Is IT Strategy Consulting and How Does It Support Your Digital Transformation?

IT strategy consulting defines how your technology landscape should evolve to enable digital transformation, improve operational performance, and support strategic goals. Dreher Consulting helps organisations in Germany, Austria and Switzerland align IT strategy with business outcomes for measurable value.
WHAT AN IT STRATEGY DECIDESDACH MITTELSTAND LIFE CYCLE01 2 of 5 Systems already past end of life Every application mapped with the life-cycleposition that sets its replacement date. SOURCING POSITION02 Per app Sourcing decided per application Cloud, hybrid and on-premise tested against yourrequirements — not chosen project by project. ROADMAP & BUDGET03 7 steps A roadmap with owners and a budget line Three phases, seven steps, each with the KPIit will be measured against.

Three decisions: the life cycle, the sourcing, the roadmap.

The answer, first

What does IT strategy consulting actually do?

A well-defined IT strategy highlights which applications you need, how they support your business processes and where each system currently stands in its life cycle. It also identifies when upgrades, replacements or new solutions are required — so you understand your digitalisation status and the challenges ahead.

As expectations around mobile usability, data analysis and automated processes continue to grow, companies need a clear framework to guide technology decisions. That framework starts with the goal of the IT strategy: why it is being developed, what information it should provide — and what is deliberately out of scope.

At Dreher Consulting the focus is practical implementation, not abstract marketing concepts. The IT strategy defines the landscape that carries your digital transformation, and it is written against the enterprise architecture it has to run on — the applications, processes and data the roadmap depends on.

Would you like to see what an IT strategy engagement looks like in your industry?

Discuss your IT strategy
Decision summary

Does this engagement fit your company?

A quick read before you spend a meeting on it. If most of this matches your situation, an IT strategy engagement is worth scoping — if it doesn't, we will say so.

When this engagement fits

No life-cycle view, pending sourcing decisions, rising IT spend

  • No current view of the application life cycle — nobody can say which systems are near end of life
  • Cloud or on-premise decisions are pending without a sourcing position
  • IT spend is rising without a roadmap to test it against
  • The structure of the IT organisation is unclear as the company grows
What we need from you

Access, honesty, and a decision-maker through to sign-off

  • Access to IT leadership and the process owners
  • Honesty about the current landscape — the status quo only works on the real state
  • A decision-maker through to roadmap sign-off
See what you get from the engagement
Why this approach is different

A target architecture diagram — or an implementable roadmap?

A typical IT strategy project
The Dreher approach
Starting point
Vendor architecture reference models
Your applications, processes and their life-cycle status
Output
A target architecture diagram
A 7-step roadmap with owners, sourcing decisions and KPIs
Sourcing
Cloud-first as a default position
Cloud, hybrid or on-premise decided per application against your requirements
After the strategy
Handed to IT to implement
Grounded in ERP and process implementation — we stay accountable into rollout
Vendor stance
Framework tied to partner ecosystems
Independent since 1992 — no reseller agreements, no kickbacks
Our take

We plan the landscape you actually have — not the one on the slide.

Reference models are useful for orientation and useless for decisions. An IT strategy has to start from your applications, your processes and their life-cycle status — because that is the landscape the roadmap has to change, and the one we stay accountable for into rollout. 

How we work

Our IT strategy process model

Three phases, seven steps. The status quo is established before anything is designed, and the rollout is planned before it is approved. 

Phase 01

Determine the status quo

Step 1 — Status quo: IT organisation, IT service, applications, projects and budgets. Step 2 — Requirements: corporate strategy analysis, state of digitalisation, IT security and IT vision.

Output · status-quo report
Phase 02

Strategy design

Step 3 — Application strategy: application portfolio and life cycle. Step 4 — Sourcing strategy: including the cloud, hybrid and on-premise position. Step 5 — IT organisation: demand and supply, staffing and skills, IT mobility, IT governance and IT security.

Output · target picture
Phase 03

Strategy rollout

Step 6 — Rollout: project portfolio management, IT roadmap and IT budget. Step 7 — Ensure success: define objectives and key results, define communication, apply change management.

Output · IT roadmap

The 7-step model

Seven steps inside three phases.

Phase Step · what it covers
Phase 01
Determine the status quo
1Status quo IT organisation, IT service, applications, projects and budgets.
2Requirements Corporate strategy analysis, state of digitalisation, IT security and IT vision.
Phase 02
Strategy design
3Application strategy Application portfolio and life cycle — continue use, modernise or replace, per application.
4Sourcing strategy The cloud, hybrid and on-premise position, make-or-buy scenarios and service level agreements.
5IT organisation Demand and supply, staffing and skills, IT mobility, IT governance and IT security.
Phase 03
Strategy rollout
6Rollout Project portfolio management, IT roadmap and IT budget for the next 3–5 years.
7Ensure success Define objectives and key results (OKR), define communication, apply change management.

The seven steps sit inside the three phases above.

From our project work

From an undocumented landscape to a roadmap with a budget line.

Environmental-technology manufacturer

85% fewer Excel-based work processes — an IT and process landscape rebuilt from a documented status quo.

ProblemA manufacturer in environmental technology with grown structures: work processes running on Excel, media breaks between departments, and no documented view of the application landscape the growth depended on.

EngagementStatus quo and requirements first, then the strategy: application portfolio, sourcing position and a sequenced roadmap with a budget line — delivered along into the processes and systems.

85%

fewer Excel-based work processes · measured

15%

faster order processing · measured

12%

lower material stocks · measured

Read the environmental-technology IT and process reference
Setting Environmental technology · grown structures
“For 15 years we have been working with Dreher Consulting on various tasks in the context of process optimisation.”
Bernd Kullmann · Managing Director, Deuter

What managing directors ask before starting an IT strategy.

The questions managing directors ask us before they engage. Honest answers about our services, our approach, and how we support mid-market businesses across Germany, Austria, and Switzerland.

Answers by:

Dr. Harald Dreher

Founder · Dreher Consulting

Since 1992 he has guided Mittelstand companies through replacing in-house-built ERP systems. He advises vendor-neutrally, taking no commission from any software vendor.

1. What is IT strategy consulting?

IT strategy consulting assesses your application landscape, IT organisation and sourcing position, and defines how the technology landscape should evolve to support the corporate strategy. The result is a roadmap with owners, sourcing decisions and the key results the strategy is measured against — not a target architecture diagram.

2. How is IT strategy different from digital strategy?

A digital strategy covers the business model, processes and technology together: what the company wants to achieve and how digitalisation carries it. An IT strategy defines the technology landscape underneath — applications, sourcing, IT organisation and infrastructure. In our projects the digital strategy comes first and the IT strategy follows from it, not the other way round.

3. Do we need an IT strategy before replacing our ERP system?

Yes — in that order. The IT strategy places the ERP system in its application life cycle and defines the sourcing position the successor has to fit; the selection then tests systems against it. Whoever replaces first lets the new system define the IT strategy.

4. How long does an IT strategy engagement take?

That depends on the number of applications and locations and how well the current landscape is documented. The status quo phase is the largest variable — an undocumented landscape takes longer to establish than to design against. The honest range for your case is set in the first conversation, after we have seen the landscape.

5. Should our IT strategy be cloud-first?
No — it should be requirements-first. Cloud, hybrid and on-premise are decided per application, against your requirements for cost, integration, data and operations. A cloud-first default is a vendor position, not a strategy; some applications belong in the cloud, others do not. 
6. What does an IT strategy cost?
That depends on the scope: the number of applications and locations assessed and the depth of the roadmap. We fix the scope and the budget before the engagement starts — you decide on a defined offer, not an open-ended day rate. 
Start the conversation

Three ways to start. No wrong door.

An independent read of where your IT landscape stands — from a firm with no software revenue behind the advice. See how we helped companies in your industry: 

Recommended

45-minute independent strategy cal

The full first conversation, including an initial review of your application landscape and where each system sits in its life cycle.

Book the call
Quick start

15-minute orientation call

Not ready for the full conversation? A short call to clarify whether we're the right advisors for you.

Book a short call
No appointment

Prefer to email?

Send us a short note about where you are — we'll reply with a clear next step, not a sales pitch.

Email us