Understand the problem
Business objectives, constraints, existing systems and stakeholders.
REMVOO designs the architecture, aligns the people and leads the technical execution needed to move complex technology forward.
Not just a diagram. The connection between business objectives, technology, teams and the decisions required to move from problem to a working solution.
Business objectives, constraints, existing systems and stakeholders.
A coherent target architecture across applications, data, integration and infrastructure.
Make trade-offs, dependencies and risks explicit — and make the architectural decisions.
Ensure teams, systems and technology work together as one solution.
REMVOO brings the right disciplines together around the problem — and keeps ownership of the whole.
Turning a business challenge into a coherent technology solution that can actually be built.
Designing cloud and platform foundations around the problem — not around a single vendor.
Turning architectural decisions into coordinated execution across teams, dependencies and delivery.
Creating alignment between business, product, engineering, operations, vendors and leadership.
Architecture only becomes valuable when the organisation can move with it.
Understand the challenge, landscape, stakeholders and constraints.
Define the target, decisions, trade-offs, dependencies and roadmap.
Move teams forward, coordinate dependencies, risks and technical delivery.
Make the architecture work in production and ready for handover.
Azure is a major part of our experience. It is not a boundary on how we architect.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Have a complex technology challenge? You do not need to know the solution yet.
Book an intro call→