Service portal
Requests, assets, contracts and responsibilities in one place.
02 / Digital Solutions & Automation
Web apps, assets, tickets and automated workflows. We turn your idea into a solution that helps with everyday work.
Personally led by Matthias Totzauer · For SMEs, industry and business teams
What we deliver
A small application or a connected service process: your needs define the solution. Scope, integrations and operations are agreed before engagement.
Identify repetitive work, clarify ownership and prioritise a roadmap by value and feasibility.
Deliverable: process map, prioritised use cases and a pilot scope.
Plan my project →Responsive business applications, customer and employee portals, forms and protected workspaces. Reusable components adapted to your process.
Deliverable: usable application with agreed roles, functions and interfaces.
Plan my project →Connect equipment, software, owners, locations, licences and contract dates. Include imports, QR identification and lifecycle workflows where useful.
Deliverable: structured inventory with responsibilities and reliable data flows.
Plan my project →Centralise requests, routing, service catalogues, knowledge and escalations across IT and other departments. Configure established systems where they fit.
Deliverable: agreed service processes, queues, roles and reporting.
Plan my project →Connect systems through APIs and controlled workflows: onboarding, approvals, reminders, document generation and scheduled reporting.
Deliverable: documented workflows with error handling, logs and accountable owners.
Plan my project →Combine sources into useful operational views, management reports, project tracking and capacity or budget overviews.
Deliverable: agreed metrics, traceable sources and usable exports.
Plan my project →Explore internal knowledge search, document extraction, classification, draft replies and summaries. Define data boundaries and human review before a pilot.
Deliverable: evaluated AI use case with access rules and quality criteria.
Plan my project →Prepare migration, testing, training and handover. Agree monitoring, backup, update and support arrangements for continued operation.
Deliverable: acceptance record, operating documentation and agreed maintenance scope.
Plan my project →Possible use cases
Requests, assets, contracts and responsibilities in one place.
Client-specific time tracking, approvals and service records with PDF/Excel exports.
Project progress, costs, risks and tasks with scheduled reports.
Coordinate requests, approvals, equipment handover and access reviews.
Find approved knowledge and create AI-assisted drafts with human review.
Structure policies, measures, owners and evidence for internal steering.
Examples of individually scoped projects; not off-the-shelf products or client reference claims.
How we work
Use existing software where it fits, adapt reusable components and build custom functionality where your process requires it. AI supports delivery; review and accountability remain with people.
Define the problem, users, data, value and acceptance criteria. Choose a pilot with a clear boundary.
Make the workflow tangible, test with representative users and resolve technical assumptions.
Implement roles, integrations and tests. Agree migration, training and acceptance.
Hand over source code and documentation as agreed. Define updates, backups, monitoring and support.
Permissions and tenant separation, secure authentication, data minimisation, traceable changes and backup and recovery inform the design. Agreed controls are checked before production launch.
Bringing a digital product to market? We also support scoping and implementation under the Cyber Resilience Act. Explore CRA services →
Not necessarily. We assess suitable existing systems, configuration and integrations first. Custom development is an option when the process and expected value justify it.
Available APIs, permissions, licences, data quality and vendor constraints are checked during scoping. An integration is only committed once these dependencies are understood.
The effort depends on scope, users, integrations and operating requirements. After scoping, you receive a proposal with deliverables, assumptions, milestones and costs. Hosting, licences and maintenance are listed separately.
We agree hosting, ownership, maintenance windows, support and handover before launch. Existing infrastructure or a dedicated environment can be considered. Response times and availability require a specific service agreement.
No. Both navigators use transparent rules and your selections in the browser. Their results are initial orientation, not a technical assessment, binding offer or promised return.
Your next step
Describe the workflow that costs you time or visibility. Together, we define the smallest useful starting point.