Job Title:Senior Enterprise Architect specialized in Build vs Buy and CRM strategy

Location:1030 Brussels, Belgium

Duration: 02/11/2026 - 11/12/2026 with extension

Mode of work: Hybrid (2 - 3 days onsite per week)

Languages: French

Job Description:

In this context, several studies have already been carried out.

CRM Feasibility Study

- An initial study concluded that the implementation of the Salesforce-based regional CRM was relevant in order to gradually replace several existing applications and centralize business processes.
- This study included a needs analysis, an implementation roadmap, a budget estimate and a business case.

Salesforce study on business compatibility, especially for approval management

A second mission, carried out in 2026, made it possible to:

- to analyse the business complexity of the CLIENT;
- to carry out workshops with the business teams;
- produce detailed mock-ups;
- model processes;
- Define a target architecture.
- Develop a transformation roadmap.
- Establish a functional backlog structured in the form of epics and needs.
- Confirm the feasibility of implementing Salesforce.
- provide a budget estimate, both in terms of investment and operation.

Preliminary Benchmarking

- A comparative analysis was then carried out between Salesforce, Microsoft Dynamics 365 / Power Platform, Odoo and custom development, in order to identify possible alternatives to the Salesforce solution.
- This study has provided initial elements of comparison, but does not allow a final decision to be made at this stage.
- CLIENT therefore already has a set of elements constituting an important basis for the work of this mission.

Defined functional scope

The following processes have already been studied:

- management of approvals;
- management of inspections;
- beneficiary management;
- management of management standards;
- management of FTE sheets;
- management of receipts;
- payment management;
- document management;
- management of contacts and associations;
- communication with non-profit organisations;
- Reporting and management.

Defined business backlog

The needs have already been formalized in different forms:

- epics;
- user stories;
- user journeys;
- models;
- Target BPMNs.

Documented Salesforce Solution

The following already exists:

- target architecture;
- functional models;
- data model;
- BPMN;
- roadmap;
- business case;
- ROI analysis;
- Change Management Analysis.

The studies previously carried out constitute the starting point for this mission and must be considered as the baseline.

The service provider is therefore not expected to restart the analyses already carried out or to redefine the business needs. The work will focus on consolidating existing elements and making an in-depth comparison of the different solutions envisaged.

As such, the purpose of the mission is not to:

- the completion of a new feasibility study;
- the complete reopening of the business workshops;
- the redefinition of the functional scope;
- Rebuilding the existing backlog.
- the questioning of needs already documented.





The objective is to provide CLIENT management with a final file allowing the following three scenarios to be compared:

Scenario 1

- Regional CRM based on Salesforce Public Sector Solutions.

Scenario 2

- Microsoft Dynamics 365 et Power Platform.

Scenario 3

- Tailor-made development carried out by the CLIENT.

The bidder will use the existing documents provided by CLIENT as a basis for work.

Expected work

Comparative functional analysis

The service provider will carry out a detailed analysis of the functional coverage of the needs already identified by the CLIENT.

This analysis will take the form of a Fit-Gap matrix to compare the three scenarios studied:

- Salesforce Public Sector Solutions;
- Microsoft Dynamics 365 / Power Platform;
- a solution developed specifically to meet the needs of the CLIENT.

For each requirement included in the reference documents, the service provider will specify in particular whether it is:

- natively covered;
- covered by configuration;
- covered by a specific development;
- covered by means of integration;
- not covered.

The objective is to allow CLIENT to concretely assess the adequacy of each solution with the business needs already identified.

Analysis and comparison of architectures

For each of the scenarios, the provider will produce an analysis of the target architecture.

This analysis will address:

- the components used;
- accommodation;
- Identity management and authentication
- security;
- integrations with the existing ecosystem;
- governance;
- exploitation;
- the support;
- maintenance and future developments.

Particular attention will be paid to the technical and organizational dependencies specific to each solution.

Economic analysis

The provider will carry out a homogeneous economic comparison of the three scenarios on the basis of clearly documented assumptions.

Investment costs

The analysis will include:

- analysis and design;
- configuration or development;
- integration;
- migration;
- testing;
- training;
- change management.

Recurring costs

The analysis will include:

- licenses;
- accommodation;
- corrective maintenance;
- evolutionary maintenance;
- the support;
- the administration of the platform.

TCO

The total cost of ownership (TCO) will be presented over two horizons:

- 5 years;
- 10 years.

The assumptions used to establish these estimates will have to be clearly explained in order to allow CLIENT to understand the different cost items and to compare them.

Implementation analysis

The provider will draw up a comparable roadmap for each of the scenarios.

For each solution, it will specify in particular:

- the different phases;
- the estimated durations;
- expenses;
- the outbuildings;
- the resources required;
- Prerequisites;
- the criteria for moving between the different phases.





The objective is to have a realistic vision of the efforts, constraints and deadlines associated with each implementation trajectory.

Risk analysis

The provider will identify the main risks associated with each of the scenarios and propose, where relevant, measures to reduce them.

The analysis will cover:

- Implementation risks
- the availability of skills;
- long-term maintenance;
- licensing costs and dependencies;
- integrations;
- security;
- GDPR;
- NIS2;
- reversibility;
- dependence on a publisher or service provider.

The organisational impacts will also have to be highlighted in order to enable the CLIENT to anticipate any necessary adaptations.

Analysis of regional pooling

Particular attention will be paid to the value of regional pooling.

The service provider will analyse the advantages and constraints related to the use of the regional CRM or, conversely, to the choice of a solution specific to the CLIENT.

This analysis will focus in particular on:

- the potential benefits of pooling;
- constraints;
- financial impacts;
- organizational impacts;
- the consequences on the autonomy of the CLIENT;
- the medium- and long-term operational consequences.

Expected deliverables

All the work will be grouped together in a decision-making support file for the Management and the Management Committee of the CLIENT.

The file must make it possible to compare the three scenarios on the basis of objective and documented elements, in particular:

- functional coverage;
- architecture;
- investment and operating costs;
- TCO at 5 and 10 years;
- deadlines and conditions for implementation;
- resources needed;
- risks;
- outbuildings;
- scalability;
- reversibility;
- organizational impacts;
- value of regional pooling.

The final report should provide CLIENT with the necessary information to assess the various options and make a decision on the direction to be taken.

The report will also include an executive summary intended to facilitate decision-making by the governance bodies of the CLIENT.

The service provider will present the conclusions of the mission to the Management Committee.

Desired profile: Senior Enterprise Architect

Mandatory skills

Enterprise Architecture

- Enterprise Architecture;
- Solution Architecture;
- urbanization of information systems;
- IT governance.

Strategic analysis

- Business Case;
- TCO (Total Cost of Ownership);
- KING;
- Fit-Gap Analysis;
- risk analysis.

CRM and business platforms

- Salesforce;
- Microsoft Dynamics 365;
- Microsoft Power Platform.

Build vs Buy Strategy

- analysis of tailor-made solutions;
- Estimated development costs;
- comparaison Build vs Buy;
- maintainability analysis;
- reversibility analysis.

Project Management

- roadmap de transformation;
- project governance;
- change management;
- preparation of decision-making support files.

Skills

- Architect
- Artificial intelligence (AI)
- Dynamics 365
- GDPR
- Information Security Management
- Microsoft Power Platform
- Public Procurement Expertise
- Public Sector Experience
- Salesforce
- Strategic Management

📌 Senior enterprise architect specialized in build vs buy and crm strategy (España)
🏢 Onesource Consulting
📍 España