Evolve without ever stopping.
Legacy platform, non-negotiable service continuity, business and tech teams to align. You need someone who makes run and transformation coexist. No need to land the plane to change the engine.
The context
Does this sound familiar?
Three contexts where I make a difference, and what I put in place in each.
Open your systems to partners.
APIs to expose, interface contracts to structure, key-account partners to onboard. You need someone who speaks both tech and business, and makes the flows reliable end to end.
Decide what to build, and why.
A full backlog, but what's actually worth building? You need someone who starts from the problem and real usage, makes the call by value, and owns what you don't build. Not a PM who works a backlog, but someone who holds the product direction.
Value proposition
What you can count on
Structure, align and deliver in demanding technical and business contexts.
03engagements
- Scope before buildingGet the scope right from day one: functional definition, value versus complexity trade-offs, stakeholder alignment.
- Hold a roadmap on a critical productPrioritise what matters, make the call between business and tech, and set milestones that hold.
- Orchestrate systems & API integrationsCoordinate multi-system interfaces and partners: scoping, contracts, testing, delivery.
03engagements
- Modernise without disruptionRebuild journeys and back-office without stopping operations. Security, IAM, cloud migration.
- Operate in international contextsWorkshops in English, offshore coordination, agile practices adapted to context (Scrum, Kanban, SAFe).
- Bridge business and techFacilitate cross-functional workshops, manage dependencies across systems, communicate clearly at every level.
One profile, four hats
Product, delivery, tech, data: I hold all four.
Most profiles hold one or two. On a critical product, it is the links between the four that keep everything standing.
Product Manager
I decide what to build and why, by value, and I own what we leave out.
- Discovery
- Roadmap
- Value / complexity trade-offs
Product Owner
I turn the trajectory into sprints that deliver: backlog, specs, acceptance, release.
- Scrum · Kanban · SAFe
- User stories
- Acceptance & release
Tech & API
I challenge an architecture with the devs, frame interface contracts and secure flows end to end.
- OAS · Postman
- Okta
- GCP
Data & monitoring
BigQuery flows and SQL views for apps and business teams. Usage measured, customer feedback qualified.
- BigQuery · SQL
- Amplitude
- Intercom
Flagship project
Autossimo, Autodistribution's B2B e-commerce platform.
Client: Autodistribution · Product: Autossimo · Senior Product Owner · since January 2021
Autossimo is Autodistribution's B2B e-commerce platform, at the core of the group's information system: a national platform, 23,000 automotive professionals, 3 million SKUs, several interconnected ERPs (including SAP) and an API ecosystem open to European partners. English-speaking context, run and build in parallel.
- Multi-ERP · SAP
- English-speaking context
- RUN + BUILD in parallel
- Agile squads
Under the hood
What I run at Autodistribution.
At the top, the API: the flows opened to key accounts. In the middle, the Autossimo projects: the production core, the back-office redesign, V4, then migration and decommissioning. At the bottom, the loop that measures usage and feeds the backlog.
- Key accountsEuropean partners
- Their technical providersworkshops in English
- Open APIsREST · OAS · Postman · Moesif
- Autossimothe platform
- The key-account APIopening flows, in English
- Autossimo V3RUN · the production core
- Back-office redesignBUILD · no disruption
- Autossimo V4BUILD · GCP · BigQuery · Okta
- Migration planfeature by feature
- Decommissioninguntil the old one is off
- Amplitudeusage measured
- Intercomfeedback collected
- Backlogevolutions & TMA
- The feedback loopon the back office and on Autossimo
Migration & decommissioning
Build the target, then switch off the old, breaking nothing.
Two redesigns, one method: the back office, then classic Autossimo (V3 → V4). Keep the existing tool running, build the new one alongside, then decommission the old one feature after feature, until it is fully switched off.
Keep the existing running
The old tool stays in production and keeps being maintained throughout the redesign: users work without disruption.
- RUN
- Legacy in production
Build alongside
The new version is built next to the old one. RUN and BUILD are driven at the same time, on a single trajectory.
- BUILD
- Coexistence
Decommission step by step
Each feature moves from the old version to the new one, one at a time, at national scale, until the old tool is fully decommissioned.
- No big bang
- Old tool switched off
Result The back office and classic Autossimo rebuilt with the same method, with no disruption to production use.
- €700Min annual transaction volume on the platform
- ×2the platform's volume doubled over the period
- 0major service interruption
Four workstreams, run in parallel
API01
Partner integration
APIs opened to major European partners, with contractual, security and multi-system interfacing constraints.
- REST APIs + OAS
- Postman
- Moesif
- Workshops in English
- Act as the main point of contact for API interfacing.
- Run technical workshops 100% in English.
- Coordinate European vendors (DE / Eastern Europe).
- Drive partner onboarding.
- Settle technical choices and make the flows reliable end to end.
Result Millions of euros in annual revenue per connected partner · faster, more reliable integrations.
RUN02
Autossimo V3
The production core: B2B e-commerce for 23,000 professionals, a 3M SKU catalogue, €50-60M/month in transactions, on a legacy PHP/Symfony stack across several interconnected systems.
- Multi-consumer APIs
- Postman
- OAS contracts
- Jira
- Prod monitoring
- E-commerce journey & returns
- Drive the roadmap (epics → user stories) and prioritise by value.
- Scope and prioritise the e-commerce returns journey redesign from the reality of 23,000 users: order, return, refund, through to integration with logistics platforms.
- Write functional specs and user stories.
- Run refinement, planning, reviews and retrospectives.
- Coordinate QA, support, business, IT and vendors.
- Track post-release KPIs and keep production stable.
- Keep V3 running in production while V4 is built, then decommission it feature after feature.
Result €700M+/yr maintained, zero major outage · 3M SKUs served without degradation.
BUILD03
Back-office redesign
The national back-office for configuring products, offers and content. A legacy tool to modernise without disruption, and every configuration error turns into lost sales.
- PHP/Symfony → React/Node
- API-first
- Data modelling (conceptual & logical)
- Design system (Figma)
- Amplitude
- Intercom
- Okta
- Define the vision, scope, backlog and roadmap.
- Design the data model: database choice, data schema, conceptual and logical models (CDM / LDM).
- Rethink business journeys and workflows.
- Co-build the design system with the designers.
- Set up Intercom on the back office and on Autossimo: collect customer feedback, qualify it and feed the evolution and TMA backlog.
- Drive agile delivery (3-week sprints).
- Testing, releases, national rollout and change management.
- Define the back-office migration plan: no single cut-over for all users, but a migration feature after feature, at national scale.
- Keep the old back office running in production while the new one is built, then decommission it feature after feature, until the tool is fully switched off.
Result Faster, more reliable configuration means fewer lost sales, and the foundation for V4. A smooth national transition, through to the full decommissioning of the old tool, with no disruption to production use.
BUILD04
Autossimo V4 (target)
The new full-API, cloud and IAM version, coexisting with V3 and everything it depends on. A cross-functional effort carrying real responsibility.
- GCP
- BigQuery
- SQL
- Okta
- OAS contracts + Postman
- Amplitude
- V4 product scoping (vision, breakdown, backlog).
- Drive the V4 Jira board (3-week sprints).
- Run API design workshops (contracts, endpoints, flows).
- Drive BigQuery data flows: SQL queries, views exposed to apps and business teams.
- Measure usage via Amplitude.
- Define the target of a single back-office V3 → V4.
- Build and drive the V3 → V4 migration with the same method as the back office: V3 kept in production, V4 built alongside, V3 decommissioned feature after feature.
Result Target architecture scoped on GCP · V3/V4 driven in parallel, end to end.
API
Opening API flows to key accounts.
I am the main point of contact for the integration: I open API flows to key-account partners and work directly with their technical providers, in a fully English-speaking context.
- Key accountsEuropean partners
- Their technical providersworkshops in English
- Open APIsREST · OAS · Postman · Moesif
- Autossimothe platform
Main point of contact
I carry the integration end to end: from the first discussions with partners to their onboarding.
- Key accounts
- Onboarding
Workshops 100% in English
I work directly with the partners' technical providers, in an English-speaking context.
- OAS contracts
- Postman
Decide and secure
Technical choices, contractual constraints and security: flows made reliable end to end.
- Moesif
- Security
Result Millions of euros in annual revenue per connected partner · faster, more reliable integrations.
Previous engagement · key account
SNCF and RATP: replacing the fax with APIs.
In the Paris rail network, one part belongs to RATP and the other to SNCF. Before this project, the two companies exchanged important information (train timetables, rosters, passages) by fax or by e-mail: an archaic and entirely time-consuming exchange.
Product Owner · SNCF, Saint-Denis · one year
Before
Fax and e-mail: archaic and time-consuming
After
APIs: data flows at once
From fax to API, in six steps
Business workshops
Understanding the types of data that must be consumed on both sides.
- Timetables
- Rosters
- Passages
Building the APIs
Replacing these archaic exchanges with APIs that expose and share the data of both networks.
- API
- Two networks
Constant exchange with RATP
At RATP's headquarters, at Gare de Lyon, in their premises, throughout the project.
- Gare de Lyon
- On site
Interface constraints
Putting the associated interface constraints in place, for reliable and secure exchanges.
- Interface
- Secure flow
Testing with Postman
Acceptance testing of the APIs with Postman before deployment.
- Postman
Going to production
The APIs are deployed to production.
- Production
After one year, the project stops with Covid.
Recommendations
In their words.
01
He knows how to bridge client needs, technical constraints and product vision, while keeping every exchange constructive, clear and thoughtful.
Yassine JanahEngineering Leader · Autodistribution
Read the full recommendation
I had the pleasure of working with Nassim on several strategic projects in the B2B automotive sector, where he was my main product-side counterpart.
His deep knowledge of the business, his command of market challenges and his ability to quickly grasp complex technical topics make him a genuine partner for engineering teams. He knows how to bridge client needs, technical constraints and product vision, while keeping every exchange constructive, clear and thoughtful.
I also valued his openness to innovation, particularly around AI, as well as his ability to challenge ideas pragmatically.
I recommend Nassim without hesitation to any company looking for a Product Manager who combines domain expertise, product vision and excellent collaboration with engineering teams.
02
How would I define Nassim's work? Commitment, tenacity, rigour. The result? A collaborative and operational success.
Yoann BeliotKey Account Manager · Autodistribution
Read the full recommendation
I worked with Nassim on a large-scale, structuring project for the relationship between Autodistribution and a strategic client with 250 stores across France. A cross-functional project (sales, accounting, finance, IT). Three years of work. Thousands of emails, hundreds of hours of meetings, internally, with the client and a great many between ourselves. How would I define Nassim's work? Commitment, tenacity, rigour. The result? A collaborative and operational success. Thanks again!
03
I recommend him without hesitation to any organisation or team looking for someone capable, reliable and invested.
Massinissa KacimiIoT Project Manager · Datanumia
Read the full recommendation
I had the pleasure of knowing Nassim, and I can attest to his great professionalism. He is a highly capable person, with excellent know-how and a strong ability to adapt. He approaches every assignment with seriousness, rigour and a real sense of responsibility. Beyond his technical skills, he stands out for his human qualities and excellent communication. He listens, explains with clarity and builds a relationship of trust with colleagues and partners. His commitment, team spirit and constant drive to deliver quality work make him a professional you can count on. I recommend him without hesitation to any organisation or team looking for someone capable, reliable and invested.
04
A profile as pleasant as it is reliable.
Lucas Elslander CampionIndependent insurance broker
Read the full recommendation
I had the pleasure of supporting Nassim for several months, and what struck me most was his human quality. Always attentive, available and professional, we immediately built a relationship of trust. A profile as pleasant as it is reliable.
Track record
Before Autodistribution.
Product Owner and IT Engineer roles in demanding environments.
Renault Digital · Product Owner
Optimised the APIs that refresh the navigation system of new vehicles leaving the factory, cutting the time needed to update GPS data so maps are current on the day the car is delivered.
SNCF · Product Owner
Modernised data exchange between SNCF and RATP: APIs to expose and share both networks' data over a secure flow, replacing manual file transfers.
EDF · IT Engineer
IT transformation projects spanning Agile, Data, Business Intelligence, DevOps and innovation.
Engineering degree, EFREI ParisParis, France
Computer Science degree (DUT), IUT Paris Rive de SeineParis, France
Study abroad semester, Staffordshire UniversityStoke-on-Trent, England
The detail of each role is in my CV.Download CV
- Step 01
I speak both languages, tech and business.
I challenge an architecture with the devs in the morning, decide a roadmap with the business in the afternoon. Nothing gets lost in translation.
- Step 02
I focus effort where it counts.
Not everything is a priority. I protect what creates the most value and own the trade-offs, without turning the team into a feature factory.
- Step 03
I make run and transformation coexist.
On a critical product, you don't shut down the service to modernise. I structure RUN and BUILD in parallel.
- Step 04
I deliver, and it lasts.
The rituals I put in place still run after I leave. Migrating 23,000 users with zero interruption doesn't happen by chance.
- Step 05
AI is part of my toolkit.
I use it to automate workflows, speed up discovery and design features, in my process and in the product.
- Step 06
I hold the relationship as much as the product.
A critical project always goes through tension. My job is to keep business, engineering and leadership talking when things get tight, and moving in the same direction.
Skills & stack
What I bring.
Strategy & Governance
- Product vision & roadmap
- value/complexity trade-offs
- multi-stakeholder governance
- discovery & prioritisation
- product scoping & specs
- IT / business / leadership alignment
Delivery & Execution
- Scrum / Kanban / SAFe
- backlog & agile squads
- Run & Build in parallel
- testing, releases, incidents
- change management
- workflow automation (AI)
Technical environments
- REST / OAS APIs
- complex systems integration
- IAM Okta
- Cloud GCP / Azure
- BigQuery, SQL & data flows
- BI & observability
- AI / LLM integration in products
Product & delivery
- Jira
- Confluence
- Productboard
- ClickUp
- Notion (AI)
- Amplitude
- Intercom
API & security
- Postman
- OpenAPI / OAS
- Moesif
- Okta
Cloud & data
- GCP
- BigQuery
- Azure
- New Relic
- SQL
- Power BI
- Tableau
Build & design
- React
- Node.js
- Figma
AI Vision
AI isn't a product. It's a lever.
Automation, monitoring, intelligent features: I know where AI belongs in an enterprise product, and where it doesn't.
- In the productAssistants & copilots · Semantic search & knowledge · Document intelligence · Decision support & recommendations · Natural language & smart forms
- In delivery & operationsWorkflow automation · Monitoring & anomaly detection · Documentation & specs · Faster discovery
FAQ
Frequently asked questions
What kind of engagements?
Short scoping, reinforcement, or long-term product leadership. I adapt to the scope, from a few weeks of scoping to engagements spanning several months or years. Open to a permanent role or a contract engagement.
Remote?
Yes, seasoned in remote (tools, rituals, async), and I come on-site when the context calls for it.
What if scope shifts mid-way?
That's the norm in complex environments. I structure rituals to absorb scope changes without losing direction: continuous prioritisation, transparent trade-offs, regular alignment.
How do we get started?
A 30-minute first call to understand your context. If it is a fit, we get started.
Let's work together
Have a product challenge? Let's talk.
Product, applied AI, transformation. Tell me where you stand.
