From strategy to implementation — professional consulting from Hamburg.
01
AS-IS Analysis
Structured capture of the current state: processes, systems, weaknesses and untapped potential — fully documented.
Process & system analysis
Interviews & workshops
Gap analysis & optimisation potential
02
TO-BE Concept & Blueprint
From the current state to a clear target picture: the blueprint defines the target process, architecture and the path to get there.
Target process definition
Blueprint creation
Roadmap & implementation plan
03
Functional & Technical Specs
Complete requirements documentation — from high-level functional spec to detailed technical specification.
Functional specification
Technical specification
Review & quality assurance
04
Stakeholder Management
All stakeholders on board — we identify, analyse and communicate with business, IT and management.
Stakeholder analysis
Communication planning
Conflict resolution & facilitation
05
Agile Requirements
Epics, user stories, acceptance criteria — requirements in the right format for agile teams, ready to implement.
Epic & story mapping
Definition of Ready / Done
Backlog refinement
06
BAU & Hypercare Support
After go-live comes operations: we support the handover to business-as-usual (BAU) and remain available during the hypercare phase.
Go-live support
Hypercare support
Post-deployment stabilisation
FAQ
Frequently Asked Questions
Answers to the most common questions about requirements management and how we work.
The functional specification describes what needs to be achieved from the client's perspective — the business requirements, goals and constraints. The technical specification is the provider's response: it defines in detail how those requirements will be implemented technically and organisationally. We create both documents in close coordination with business and IT stakeholders so no gap opens up between expectation and delivery. The result is requirements documentation that serves as a binding basis for development, acceptance testing and contracts.
The AS-IS analysis captures the current state — existing processes, systems, weaknesses and untapped potential, fully documented and structured. The TO-BE concept builds on this to describe the target picture: the desired target process and architecture, and the path to get there. The blueprint connects both stages into a concrete implementation roadmap. Only once you truly understand the current state can you develop a realistic and achievable target picture.
This depends heavily on project scope — a focused AS-IS analysis for a single process can be completed in 1–2 weeks, while a complete blueprint for a larger IT initiative usually takes several weeks. We work with clear milestones and deliver early interim results so you can see and steer progress. In the free initial consultation we give a realistic time estimate for your specific project.
Work doesn't automatically end at go-live — the new process or system needs to be stably transitioned into business-as-usual (BAU) operations. During the hypercare phase we remain directly available right after go-live to quickly resolve issues and support users. Only once processes run reliably do we hand over fully into regular operations. This reduces the risk of disruption and adoption problems during the critical early phase.
IREB (International Requirements Engineering Board) is the international standard for professional requirements engineering. IREB certification ensures requirements are elicited, documented and managed using proven, traceable methods rather than ad hoc approaches. This creates comparability, traceability and reduces misunderstandings between business, IT and external providers. As an IREB-certified team, we apply these standards consistently in every project.
Contact
Request Requirements Management
Free 30-minute initial consultation — we analyse your requirements needs and provide a concrete proposal.