01 — WHAT WE DO

Complex technology needs
direction

REMVOO designs the architecture, aligns the people and leads the technical execution needed to move complex technology forward.

ARCHITECTUREEXECUTIONOWNERSHIP
02THE ROLE OF A SOLUTION ARCHITECT

A Solution Architect turns a business challenge into a technology solution that can actually be built

Not just a diagram. The connection between business objectives, technology, teams and the decisions required to move from problem to a working solution.

01

Understand the problem

Business objectives, constraints, existing systems and stakeholders.

02

Shape the solution

A coherent target architecture across applications, data, integration and infrastructure.

03

Make the decisions

Make trade-offs, dependencies and risks explicit — and make the architectural decisions.

04

Connect the pieces

Ensure teams, systems and technology work together as one solution.

The architecture is not the deliverable. The outcome is.
03FOUR DISCIPLINES

One problem rarely needs
one discipline

REMVOO brings the right disciplines together around the problem — and keeps ownership of the whole.

01
DESIGN THE SOLUTION

Solution Architecture

Turning a business challenge into a coherent technology solution that can actually be built.

  • ↳Business objectives & constraints
  • ↳Target architecture & technical decisions
  • ↳Integration, APIs, data & security
  • ↳Trade-offs, dependencies & risks
02
DESIGN THE FOUNDATION

Cloud & Platform Architecture

Designing cloud and platform foundations around the problem — not around a single vendor.

  • ↳Azure as a core area of expertise
  • ↳AWS, Kubernetes & OpenShift
  • ↳Networking, platform & infrastructure
  • ↳IaC, CI/CD & operational readiness
03
MAKE THE ARCHITECTURE MOVE

Technical Leadership

Turning architectural decisions into coordinated execution across teams, dependencies and delivery.

  • ↳Technical direction & decision making
  • ↳Cross-team dependencies & sequencing
  • ↳Risk, escalation & delivery alignment
  • ↳Architecture connected to execution
04
MAKE PEOPLE MOVE TOGETHER

Technology Alignment

Creating alignment between business, product, engineering, operations, vendors and leadership.

  • ↳Business ↔ technology alignment
  • ↳Stakeholder communication
  • ↳Shared decisions & ownership
  • ↳A common direction across teams
04HOW WE WORK

From direction to production

Architecture only becomes valuable when the organisation can move with it.

01

Direction

Understand the challenge, landscape, stakeholders and constraints.

02

Architecture

Define the target, decisions, trade-offs, dependencies and roadmap.

03

Execution

Move teams forward, coordinate dependencies, risks and technical delivery.

04

Transition

Make the architecture work in production and ready for handover.

05TECHNOLOGY

Architecture is not tied to a single stack

Azure is a major part of our experience. It is not a boundary on how we architect.

CLOUDAzureAWSOpenShiftKubernetes
ARCHITECTURESolutionEnterpriseAPI-firstEvent-driven
ENGINEERINGC# .NETObservabilityCI/CDIaC
06TRANSFORMATION

Architecture becomes valuable when it changes reality

View transformations ↗
VODAFONEZIGGOCITIZENMASSIGNCLOUDSAINT-GOBAINVISMA
07FAQ

Answers to what you often ask

What does a solution architect do?

A solution architect translates a business challenge into a solution that can be built. It starts with goals, constraints and existing systems, and covers technical decisions with explicit trade-offs and dependencies. The architect then helps the teams actually carry those decisions out.

What is the difference between solution architecture and enterprise architecture?

Enterprise architecture looks at the whole: the landscape, principles and direction of the organisation. Solution architecture designs a concrete solution for a specific problem within that whole. REMVOO combines both, so technical decisions fit the business goals as well as the wider landscape.

When does a cloud or Azure migration make sense?

Simply moving old software to the cloud rarely solves anything. It makes sense when it creates architectural freedom: parts that can change independently, clear dependencies, and security and operations that grow with the platform. At Saint-Gobain a tightly coupled monolith was transformed into independently deployable services on Azure.

How do you approach moving from a monolith to services?

First you understand why everything moves together: the dependencies. Then you decompose the monolith step by step into independently deployable services, with DevSecOps as a standard part of the platform. This is how it was done at Saint-Gobain.

What does an API-first approach deliver?

Systems are connected without coupling them directly, and parts can evolve independently. At AssignCloud a business challenge became a modular, API-first SaaS platform, and at Visma eAccounting a working Azure integration connecting business processes.

What is event-driven architecture and when does it fit?

In an event-driven architecture, systems communicate through events: one component announces that something has happened and other components react to it independently. This keeps systems loosely coupled, lets them scale and change independently and enables near real-time processing. It fits when processes may run asynchronously or several parties react to the same occurrence. It does require clear agreements on event formats, ordering and error handling. On Azure this can be done with, for example, Event Grid, Service Bus or Event Hubs. REMVOO has applied event-driven architecture at citizenM and AssignCloud.

What does technical leadership mean in a transformation?

Architecture only has value when teams can execute it. Technical leadership therefore means connecting people, sequencing dependencies, making decisions and enabling delivery. At VodafoneZiggo this was a coordinated path towards real-time rating for 1.34 million customers across 34 teams.

Do you also work for organisations with strict security requirements?

Yes. At Robeco the public website moved to Nuxt 3, with network isolation through Virtual Networks and Key Vaults, Azure Front Door as the security layer and infrastructure that met the strict policy and security guidelines of the financial sector.

Do you work on a project basis or also on an interim basis, and internationally?

Mainly on a project basis, with a clear challenge and a concrete result. Interim assignments are open for discussion. We work in the Netherlands and internationally, in Dutch and English.

How does a first introduction work?

You book a 30-minute conversation and tell us about your challenge. No preparation is needed. Together we then decide whether and how REMVOO can help.

08NEXT STEP

Let's change
something

Have a complex technology challenge? You do not need to know the solution yet.

Book an intro call→