REMVOO

REMVOO — TRANSFORMATIONS

Architecture becomes valuable
when it changes reality

Large technology transformations are never only technical changes. They move systems, teams, dependencies and the way an organisation operates.

01VODAFONEZIGGO↗02citizenM↗03ASSIGNCLOUD↗04SAINT-GOBAIN↗05VISMA eACCOUNTING↗
01THE COMPLEXITY

The hard part is not
drawing the architecture

The hard part is moving everything around it: teams, platforms, dependencies, risks, decisions, cutovers and a business that still has to operate.

02THE TRANSFORMATIONS

Five different problems. One constant: architecture eventually has to land in reality.

01 / 05VODAFONEZIGGO
Solution Architecture · Migration · Technical leadership

1.34M customers.
34 teams.
One transformation.

Replacing an end-of-life rating model with a new real-time rating platform.

ResultA coordinated path towards real-time rating for 1.34 million customers across 34 teams.

1.34Mcustomers
34teams
01transformation
View transformation→
TRANSFORMATION / ARCHITECTURE FLOW
CUSTOMERS
EXISTING RATING
34 TEAMS
MIGRATION
REAL-TIME RATING
01
A migration of 1.34 million customers cannot be solved by one team.
02 / 05citizenM
Solution Architecture · Migration Lead · Azure

34 hotels.
9 months.
One complete transformation.

A new hospitality platform, a new architecture and a complete migration — delivered while the platform itself was still being built.

Result34 hotels migrated to a modern, API-first hospitality platform in just nine months.

34hotels
7,837rooms
6.46Minvoices
View transformation→
TRANSFORMATION / ARCHITECTURE FLOW
AMADEUS
iRECKON
AZURE
APALEO
34 HOTELS
02
The new platform was being built while the migration was being prepared.
03 / 05ASSIGNCLOUD
Solution Architecture · Software Architecture · Engineering

No legacy architecture.
No constraints.

A greenfield SaaS platform designed around the business rather than around inherited technology decisions.

ResultA business challenge transformed into a modular, API-first SaaS platform built for independent evolution.

GREENFIELDstarting point
API-FIRSTarchitecture
03core services
View transformation→
TRANSFORMATION / ARCHITECTURE FLOW
BUSINESS
API
CUSTOMER
PRODUCT
SALESORDER
03
The architecture started with the business — not the technology.
04 / 05SAINT-GOBAIN
Architecture · Engineering · Azure · DevSecOps

One monolith.
Everything moved together.

Modernisation was about creating architectural freedom — not simply moving old software to Azure.

ResultA tightly coupled monolith transformed into independently deployable services on Azure.

01monolith
03services
AZUREnew platform
View transformation→
TRANSFORMATION / ARCHITECTURE FLOW
MONOLITH
DECOMPOSE
BASKET SERVICE
PRICE SERVICE
STOCK SERVICE
04
The goal was not cloud migration. The goal was architectural freedom.
05 / 05VISMA eACCOUNTING
Solution Architecture · Implementation

Connecting
business systems.

An API-first Azure integration layer connecting HC Software with Visma eAccounting.

ResultA working Azure integration connecting business processes with Visma eAccounting.

APIintegration
AZUREFunctions
01working flow
View transformation→
TRANSFORMATION / ARCHITECTURE FLOW
HC SOFTWARE
API
AZURE FUNCTIONS
INTEGRATION
VISMA eACCOUNTING
05
Architecture was not the deliverable. The working integration was.
03THE ROLE OF ARCHITECTURE

Not just deciding
what gets built

REMVOO works where architecture, execution and change meet. The solution has to be technically right — but also executable, aligned and ultimately operational.

ARCHITECTURE+EXECUTION+OWNERSHIP
04REMVOO

Architecture is only
valuable when it
changes reality

A complex transformation on the roadmap? Start with the problem.

Book an intro call→