Freelance Semarchy xDI consultant: when and why to bring one in

"We've got Semarchy xDI in production, but nobody in-house really knows how to evolve it anymore." I hear that line almost word for word on every first call. It captures perfectly the moment a company starts looking for a freelance Semarchy xDI consultant: rarely to kick off a project from scratch, almost always because a business-critical integration tool is running with no one left to steer it. Before posting a job ad or signing with a consultancy, it's worth understanding what a freelancer actually brings to this kind of work.

Consultant or developer: where's the difference?

On paper, both write mappings. In practice, the word "consultant" changes the scope. A developer delivers a requirement that's already been scoped; a consultant also steps in when the requirement is unclear, when an existing platform needs auditing, when several technical options have to be weighed, or when an IT department needs to be told why a given architectural choice will prove costly two years down the line. With Semarchy xDI — formerly Stambia, acquired in 2020 — that hat matters, because the tool often sits at the heart of the information system without anyone having the full picture.

In practice, a consulting engagement on xDI almost never boils down to "ship me ten flows." It starts with a broader question: is the platform healthy? Can it still grow, or are we piling up debt with every addition? It's that diagnosis that justifies bringing in someone experienced rather than a junior who'll simply stack up more mappings.

The assignments where a freelancer truly makes the difference

Taking over an orphaned platform

The most common case. A project was delivered by a contractor who has long since moved on, and all that's left is a directory of flows nobody understands anymore. A freelance consultant used to this kind of situation doesn't dive straight for the keyboard: they first map out the sources, the chains of execution and the breaking points, then secure what exists before touching anything. It's the opposite of the rushed rewrite that breaks an integration pipeline the night before a peak in activity.

Migrating from Stambia to Semarchy xDI

Many companies still run on old Stambia versions whose support is winding down. Migration is a textbook consulting assignment: you have to audit the components in use, identify what changes on the runtime and metadata side, and plan a phased cutover with proper testing. I walk through how this plays out on the ground in my article on the role of a Stambia / Semarchy xDI flow developer in Lille.

Connecting xDI to the rest of the ecosystem

An integration engine never lives in isolation. It talks to SQL Server or Oracle databases, REST APIs, sometimes an ESB, and increasingly to marketplaces through Mirakl. A consultant who understands that entire chain — from the source system all the way to the catalog exposed to the customer — is worth far more than a specialist boxed into a single tool. That's especially true in retail and e-commerce, where data is only valuable if it arrives correct, in the right place, at the right time.

Freelancer or consultancy: how to decide?

With a niche technology like Semarchy xDI, the question comes up every time. Both models have their merits, and the right choice depends mainly on the nature of the need:

• The freelancer gives you direct access to the expert. No middleman, no project manager relaying things to a junior developer. You pay for the time of the person who actually does the work, and your teams level up by working alongside someone who knows the terrain. Ideal for deep expertise, a handover, a migration or a well-scoped reinforcement.
• The consultancy offers reassurance on service continuity and volume: several people who can be mobilized, a broad contractual framework. The downside is often a hefty margin, turnover among the people assigned, and a level of expertise that varies depending on who lands on your project.

My conviction, after fifteen years in the field: for a focused data integration problem, a senior freelance consultant offers the best balance of cost, genuine expertise and responsiveness. To run a program spanning dozens of people over several years, the consultancy still makes sense. Plenty of companies, in fact, combine the two.

Remote work, proximity and rates

A large part of an xDI engagement works perfectly well remotely: flow design, taking over mappings, architecture reviews. Remote work widens the talent pool beyond the local area, which is good news given how rare the profile is. That said, for the sensitive moments — a scoping workshop, a production cutover, a meeting where the real need differs from what the ticket says — proximity remains an asset. Based in Valenciennes, an hour from Lille, I work both remotely across France and on-site in the Hauts-de-France region.

On budget, a freelance Semarchy xDI consultant logically sits above a generalist .NET profile: the technology is niche, the expertise scarce, and a mistake on a product master costs far more than the daily rate. The right instinct isn't to compare raw rates, but to look at what the engagement prevents in terms of risk and what it gains you in autonomy once it's done.

How to spot the right profile

Beyond the years spent on the tool, three signals never lie. First, the ability to talk just as easily to IT leadership as to the people who run the flows day to day — data integration is as much an organizational topic as a technical one. Next, the instinct to document and hand over: a good consultant leaves behind readable flows and a team able to carry on without them, not a black box that only runs on their machine. Finally, a view of the whole chain, from the source system through to the marketplace, rather than an expertise folded in on the xDI engine alone.

That's exactly how I approach my integration work. My .NET / C# grounding often helps: when a flow needs a custom connector or a small tool to replay rejected records, I build it myself rather than having to subcontract.

In summary

Bringing in a freelance Semarchy xDI consultant makes sense as soon as data integration becomes a weak point: a legacy platform nobody masters anymore, a migration from Stambia, or a need for deep expertise without the overhead of a consultancy. The right profile isn't judged by the number of mappings produced, but by the peace of mind they leave behind. If you're looking for this kind of reinforcement, remotely or in the Hauts-de-France, let's talk.