T-NEX
Menu
DEEN
T-NEX for Regulated Markets · Consulting

Turn business requirements into a buildable software solution.

We combine experience in regulated markets with AI and software development. Together with your business team, we clarify processes, data and requirements. The resulting functional concept helps your team decide on implementation and steer development.

Business and IT working on the same processDocumented decisionsPrepare implementation
T-NEX · ConsultingApproach
Brief
Use case and current situation
Specification
Workflows and owners
Technical plan
Data, interfaces and permissions
Implementation decision
Work packages and acceptance
How business advice and technical planning fit together.
01
Agree on the problem to solve
02
Assign owners and approvals
03
Review data and interfaces
04
Define the next step
Starting point

Start with the actual workflow

We start with your specific project. We examine what information people need and which handovers hold up work. That establishes the brief for business and technical planning.

01Define the task

We establish which workflow should change and who uses it.

02Develop requirements

Business rules are connected to data sources and responsibilities.

03Review the solution

An existing module or prototype makes unresolved decisions visible.

04Prepare implementation

Work packages and acceptance criteria provide a basis for commissioning the next stage.

Advice and software

Translate business requirements into buildable solutions

A functional specification defines inputs, workflow steps, roles and results. For a control process, this means identifying which records the responsible person reviews, how exceptions are documented, who approves an action and what reporting needs. Together with your institution, we translate those decisions into data fields, permissions and test cases.

The result must describe what needs to be built or changed.
T-NEX working principle
Areas of work

Where we support your team

Our advisory work connects regulatory requirements with daily operations. We structure requirements, link controls and evidence, describe processing and approval routes, and establish the data needed for management and reporting. The following work areas can be addressed individually or as a connected programme.

01DORA implementation

Connect ICT-related requirements with risks, responsibilities, evidence and practical work packages. Structure technical information for registers and provider management.

02MaRisk and GRC processes

Describe control and processing workflows: what is checked, which evidence is produced, who handles a deviation and who approves the result?

03Third parties and outsourcing

Bring services, contracts, dependencies and responsibilities together. Prepare information for assessment, ongoing management and a future provider change.

04AI governance

Inventory AI use cases, data flows, models and responsible people. Define evaluation criteria, usage boundaries and the route from experimentation to approval.

05Business design and software

Translate business decisions into data objects, forms, permissions, interfaces and clear test cases. Assess existing modules against the need for extensions.

06Implementation and enablement

Support business and IT teams through configuration, testing and acceptance. Work through agreed processes with the future team and hand them over for operation.

Deliverables

What supports your next decision

Potential deliverables include current and target workflows, a role and permission model, a data and interface inventory, and prioritised work packages with acceptance criteria. Requirements from your GRC framework are mapped to the relevant steps. This provides a basis for the institution’s decisions and the subsequent technical implementation.

Possible consulting deliverables
Work areaDeliverableUse
Business processDocumented steps and exceptionsBusiness team review
Technical solutionData model and interface descriptionDevelopment planning
Testing and introductionTest cases and acceptance criteriaPrepare approval
Engagement boundaries

The brief determines the result

Consulting may conclude with a specification or support the introduction of a solution. Configuration and development are included only when explicitly defined in the engagement.

Task and suitable starting point
Starting pointNext step
The process is unclearBusiness process review and specification
Feasibility is uncertainPlan a limited prototype or AI proof of concept
Requirements are agreedCommission configuration or development
Business responsibility: Your institution retains decisions about internal rules.Institution
Implementation scope: Additional development requires a defined brief.Agreement
Service boundary

Our advice concerns business and technical implementation. It does not replace legal advice or an independent audit.

Preparation

Useful material for the first discussion

An existing process description is a useful starting point. Specific examples from daily work also help us define the task.

  1. 01Workflow: Which steps are currently handled manually or across several systems.
  2. 02People involved: Which teams provide information and make decisions.
  3. 03Systems: Which applications and data sources need to be connected.
  4. 04Expected result: What should exist at the end of the engagement.
People at T-NEX

Business and technical experience in one team

Christoph Gembruch brings experience in GRC process consulting and introducing GRC software. Andreas Unruh works on software architecture and GRC design. Both are managing directors of T-NEX GmbH.

Christoph Gembruch · Process consulting and introduction
Andreas Unruh · Software architecture and GRC design

Your project is considered from both business and technical perspectives.

Working with us

Frequently asked questions

Do we have to buy T-NEX software?

The consulting engagement is defined by your task. Whether to use an existing module or develop software is a separate decision.

What do we receive after consulting?

Depending on the engagement, a functional specification, technical plan or specific material for introduction and acceptance. Agreed deliverables are defined in the scope.

Does T-NEX work with our business team?

Yes. Future users and the responsible IT team are involved in agreeing workflows and requirements.

Can implementation follow?

Yes, once requirements and implementation scope are clear. We agree which configuration or development is needed.

Let's discuss the next step for your application

Describe the current workflow and what should change. We will discuss a suitable consulting scope with you.

Discuss your projectProcess documents and an overview of the systems involved are useful.

Sources & further reading

  1. AI PoC SpeedboatsT-NEX
  2. T-NEX for Regulated MarketsT-NEX

In-depth articles