Get in touch

Challenge 2026

Get your field service fit for the future with AI.

Talk about your Proof of ValueSee the journey
WHY IS NOW THE RIGHT MOMENT?

Business Value

AI is no longer an experiment. Every month of delay costs market share. The C-level demands measurable results. Those who do not automate, lose.

Delight customers

  • Response time to dispatch
  • Contract renewal rate
  • Churn rate

Increase efficiency

  • First-time fix rate
  • Mean time to repair
  • Jobs per day

Reduce cost

  • Fewer on-site visits
  • Spare-part cost through better forecasting
  • Customer care / support cost
WHAT DOES IT TAKE?

Building blocks of a successful implementation

Technology alone is not enough: only the interplay of all five building blocks creates real business value.

Data & infrastructure

IoT, cloud and Azure form the foundation: they capture, transmit and process all relevant data in real time.

AI & agents

AI agents analyse data and give the service technician exactly the information they need at the right moment.

Structure & organisation

Building a Digital AI Product Unit with clear end-to-end ownership, from the first feature to scaling across markets.

Mindset & change

Targeted training and active change management. Employees are enabled, brought along and sustainably enabled.

Product as a Service process

A continuous end-to-end process with continuous feedback loops that secures value not once, but for good.

HOW DO YOU GET THERE?

The way to the goal

Alignment on a Product as a Service (PaaS) process

Today

Everyone runs, but not in the same direction.

Business, IT and system integrators each own a part, but nobody owns the whole chain. Discovery, product definition and adoption fall through the cracks.

The gap

Some things get left behind.

Pilots done, go-live celebrated, and then? Real business value only comes from adoption, scaling and continuous iteration. Exactly this last mile gets left behind.

Future

All forces. One direction. One outcome.

ARISE closes the gaps, aligns teams, shapes the change and delivers outcomes.

Our approach

Deliver fast.
Enable for good.

ARISE works on two levels in parallel.

Field service technician with toolbox
OUR APPROACH

Stream 01 Deliver

Tech integrators usually own only the technical parts of the process. ARISE owns the entire process with a focus on user acceptance and scalability.

  1. Discovery

    Problems & opportunities

  2. Strategy

    Vision & goals

  3. Product definition

    Scope & features

  4. Delivery

    Development & shipping

  5. Adoption

    Enable users & secure acceptance

  6. Scaling

    Extend & scale

  7. Outcome

    Measurable results

OUR APPROACH

Stream 02 Enable

Companies have to deliver outcomes before they have built the necessary capabilities in-house. ARISE bridges exactly this gap and builds the target organisation at the same time.

Build-up

Digital AI Unit

Training

Internal talent is identified, developed and gradually integrated into the Digital & AI Product Unit.

Hiring

New roles and talent are actively supported by ARISE, from profile to onboarding.

Shadowing

Employees work together with ARISE first, then gradually take on responsibility themselves.

Documentation

Processes, decisions and handover guides secure the knowledge, so it stays in the company.

THE JOURNEY

The journey in pilot operation

The technician works as before. The agent prepares, answers and writes along.

  1. 01 Job

    before the drive

    Service technician

    Gets the job assigned as before

    In the background

    Read the job header, pull unit history by serial number, search the corpus for matching fault patterns

    Data sources

    Ticket system · read-only, live

    Ticket history · Export

    Knowledge corpus · Export

  2. 02 Briefing

    2 min before leaving

    Service technician

    Opens the app and reads the briefing

    Agent / app

    Briefing: likely causes, parts needed, last visits at this unit, with sources

    In the background

    Retrieval and summary

  3. 03 On site

    at the machine

    Service technician

    Works at the machine, asks by voice when needed

    Agent / app

    Questions on the fault pattern, troubleshooting steps, available offline

    In the background

    Retrieval on the local cache

    Data sources

    Knowledge corpus

  4. 04 Debriefing

    right after

    Service technician

    Dictates what was done

    Agent / app

    Transcript and structured report fields

    In the background

    Speech recognition and structuring

  5. 05 Report

    handover

    Service technician

    Checks the report and accepts it

    Agent / app

    Finished report to accept

    Data sources

    Write-back to the ticket system
    Proof of Value / MVP

    In the Proof of Value as an option, text-based, once the rights are in place. Direct write access from the MVP.

TIMELINE

A clearly bounded Proof of Value in 12 weeks

Start focused, deliver measurably. Two stages, each can be commissioned on its own: first the Scoping Sprint, then build and pilot in the field.

  1. Stage 01 · Scoping SprintPhase 01, 2 weeks. Recommended entry, can be commissioned on its own.

    01

    Discovery & impact

    2 weeks

    • Map the technician journey
    • Review cases and tickets
    • Measure the KPI baseline
    • Use case and unit type
    • Inventory of source systems

  2. Stage 02 · Build and pilot in the fieldPhases 02 to 05, 10 weeks.

    02

    Design

    2 weeks

    • Define target process and screens
    • Agent cut and prompt architecture
    • Set integration scope
    • Success criteria and pilot plan
  3. 03

    Build & integrate

    4 weeks

    • Build agent and RAG pipeline
    • Read-only link to one source system
    • App for field use
    • Check security and GDPR
  4. 04

    Pilot in the field

    3 weeks

    • 20 to 30 technicians on real jobs
    • Support and rapid improvements
    • Feedback loops from the field
    • Measure impact on the KPIs
  5. 05

    Impact review

    1 week

    • Assess business impact
    • Gap analysis against the MVP
    • MVP roadmap with effort
    • Decision paper

Our goala solid business case before the big budget flows.

Solution & scope

  • Briefing before the drive, debriefing after
  • One product line, all documented fault patterns
  • Mobile app, in German

User scope

  • 6 to 8 technicians in interviews
  • 20 to 30 in the field test
  • One field service group

Data & integration

  • One system live, read-only
  • Documents and ticket history as export
  • No live telemetry

Team & effort

  • Proof of Value core team
  • Business, product, service design and agentic engineering
  • 12 weeks

in 12 weeks

SCOPE

What is included in the Proof of Value?

What is not included has a clear phase or responsibility assigned.

Included in the Proof of Value

9 items
  • Technician briefing before the drive and debriefing after
  • One product line, all documented fault patterns
  • RAG over the knowledge base provided by the customer
  • One source system, read-only
  • (Web) app with offline handling and voice input
  • Distribution to the pilot devices via a signed build
  • Field test over 3 weeks with 20 to 30 technicians
  • KPI measurement against the baseline from phase 1
  • Gap analysis and MVP roadmap with effort estimate

Not in the Proof of Value

11 items
  • Live diagnosis at the machine during the jobMVP
  • Live IoT telemetry, digital twins, edge AIMVP
  • Write access to systemsMVP
  • Building the production cloud and data platformMVP
  • Data cleansing, PII removal, taggingCustomer
  • Second language, second market, second product lineRollout
  • iOS build, app store distribution, MDM rolloutMVP
  • Operation, SLA, monitoring, second-level supportRollout
  • Penetration test and formal security sign-offMVP
  • Cloud, token, speech and licence costsCustomer
  • Change programme beyond the pilot groupRollout
PREREQUISITES

What the customer contributes

If prerequisites drop away, the effort of the Proof of Value shifts.

  1. 01

    Knowledge base

    selected, available as documents or PDF

    before phase 2

  2. 02

    Ticket export

    cleaned, PII removed

    before phase 2

  3. 03

    System and cloud access

    Azure and rights in the source system, a test environment and a solution architect for the system questions

    week 1

  4. 04

    Subject-matter reviewer

    named for validation, plus design support for the service journey

    from phase 2

  5. 05

    Access to technicians

    6–8 for interviews, 20–30 for the pilot

    phases 1 and 4

ARISE can supply building blocks. Backing from the C-level it cannot: time, focus, budget, capacity.

LETS GET STARTED

Complexity made simple: Crawl, Walk, Run

We know the pitfalls and lead your project to success with a proven, staged roadmap.

  1. Step 01:
    Walk

    Focus on feasibility: validate the core idea and build a working MVP.

  2. Step 02:
    Run

    Learn and optimise: implement the model, gather feedback, build structures and automation.

  3. Step 03:
    Sprint

    Scale and optimise: use the latest tools, automate deeply, secure lasting growth.

LETS GET STARTED

Getting Ready: these are the things we need to start

Not everything has to be in place — ARISE takes on missing building blocks.

Business
  • 01Business Use case
  • 02Executive Sponsor
  • 03Product Owner
  • 04Pilot group users
  • 05Budget
Data
  • 06Service Documentation
  • 07Service History
  • 08Access Core Systems
  • 09Live Data Source
  • 10Technical Documentation
Systems
  • 11Azure AI Foundation
  • 12Azure AI Foundry
  • 13Open AI
  • 14Agent Runtime
  • 15Access ERP, CRM & FSM
Product
  • 16Roadmap & Strategy
  • 17Customer Experience
  • 18Research
  • 19Rollout
  • 20MVP & Proof of Value
WHY ARISE?

What ARISE really does differently.

Four principles that set ARISE apart from classic system integrators.

Product

instead of project

We own the product across all phases and departments.

System integrators own the project and deliver technology.

Integration

instead of handover

We integrate into your company, steer departments and align everything on the outcome.

System integrators deliver project results and leave.

Outcome

instead of deliverable

We drive and own real outcomes.

System integrators deliver technology.

User focus

instead of tech focus

We work user-centred, so the product is accepted and scales.

System integrators implement technology without looking at acceptance and scaling.

Why ARISE?

Real impact only happens at the intersection.

ARISE

We deliver outcomes.
Without user acceptance, every product fails, no matter how good the technology is. Without user acceptance, no business performs.

Product as a Service

System integrator

They deliver technology.
Without user acceptance, every product fails, no matter how good the technology is. Without user acceptance, no business performs.

FROM PRACTICE

TK Elevator

20k+
Supported technicians
+20%
Elevator uptime
-50%
Elevator outages
+40%
Issue reduction
Challenge & Solution

Challenge

Elevator service technicians drove to faults unprepared — no context, no briefing. The full product (digitally native elevator, IoT, data platform, AI agents and a service technician app) was presented as an MVP prototype on the way to market entry at the end of 2026, on the Microsoft stand at Hannover Messe Industrie 2026.

Solution

By staffing programme management and leading a cross-functional team, ARISE secured product focus from the start: technology follows the user and the intended outcome, not the other way round. Forming one team and aligning it continuously on a shared north star were the decisive success factors.

“Most relevant for this transformation: A humble team, a strong team with passion and the right culture of listening, getting things done and the will to collaborate across silos and company boundaries.”

Matthias Gohl, CDO TK Elevator
FROM PRACTICE

Canyon

56%
of customers say the app speeds up their decision to purchase
+1.562 €
higher revenue from multichannel customers compared to web-only customers
+6.56
average NPS uplift of app users
Challenge & Solution

Challenge

Customers spent hours on the hotline looking for the right spare parts, without success. Frustration and churn followed.

Solution

IoT retrofit integration in the bikes, an Azure cloud platform and an app that shows customers only the parts that fit. ARISE built an agile speedboat team, took over end-to-end orchestration and put the user experience at the centre from the start — the basis for the scaled rollout.

“ARISE has been an exceptional partner in the Connected Bike project and a key contributor to the Canyon success. The dedication to delivering targets and driving the team towards success is truly commendable.”

Nico De Wallace, CEO Canyon Bicycles
Key Performance Indicators7 figures

01

Faster purchase

The app helps customers decide and buy faster, and so unlocks revenue from mobile visitors.

56%
of customers say the app speeds up their purchase decision
21%
of customers would probably not have bought without the app
5x
higher conversion in the app than on the mobile web

02

Higher customer lifetime value

Multichannel customers have a 70% higher lifetime value than customers who only order on the web.

2.5x
more orders from multichannel customers compared to web-only customers
+1.562 €
higher revenue from multichannel customers compared to web only

03

Positive response in the NPS

App customers rate their brand experience 10% higher.

+10%
from an NPS of 60 for Canyon to 66.6 among Canyon app users
+6.56
average NPS uplift among app users

Let’s do it.
We build the capabilities you need for good.

ARISE
Talk to ARISE