Work

Four projects delivered in a company, from the need to the result.

Labellemontagne · Since 2025

A data platform built from scratch

  • Microsoft Fabric
  • PySpark
  • Azure
  • CI/CD
  • Power BI

Bringing the data of a multi-business group together on Microsoft Fabric, from ingestion to reports.

4
families of sources connected
3
layers: bronze, silver, gold
6
ski resorts covered
  1. Sources

    • Ticketing and ski passes
    • Hotels and restaurants
    • CRM and customer service
    • Shops and indoor leisure
  2. Bronze

    • Raw data, as received
  3. Silver

    • Cleaned and checked data
  4. Gold

    • Data ready for analysis
  5. Power BI reports

    • Sales for the six resorts
    • Customer service
From sources to analysis: the path of a piece of data through the platform.

The context. A multi-business group: six ski resorts, hotels, restaurants, indoor leisure venues and shops. Each business runs its own tools. When I joined, in a newly created role, there was no data platform.

The need. Bring this data into one place, so that every team works from the same figures and the group can run its data and BI analyses.

The approach. I started from a blank page, in six steps:

  • Choose the stack. Assessing the options, then choosing Microsoft Fabric.
  • Map the data. Understanding and documenting the data of each business before writing the first pipeline.
  • Connect the sources. Four families: ticketing and ski passes, hotels and restaurants, CRM and customer service, shops and indoor leisure. Many are hosted on legacy servers with no modern connector, and some come from partners.
  • Build the pipelines. PySpark notebooks following a medallion architecture: raw data in bronze, cleaned in silver, ready for analysis in gold.
  • Make it reliable. Data-quality checks, and a CI/CD process to industrialise deployments.
  • Control costs. Automating and managing Azure cloud resources, to make the best use of the platform.

The result. A single platform feeds the group’s reports: sales for the six resorts and customer-service monitoring.

Labellemontagne · Since 2025

Migrating the group CRM

  • Dynamics 365
  • Power Apps
  • Power Automate
  • Docusign

Project lead for the Dynamics 365 CRM migration, delivered in three months from scoping to go-live, then the business tools built on top of it.

3 months
from scoping to go-live
4
phases: scoping, planning, testing, go-live
2
business tools built afterwards
  1. Scoping

    • Scope and goals
  2. Planning

    • Schedule, contractors
  3. Testing

    • Checking the migrated CRM
  4. Go-live

    • Teams move over
  5. Next

    • Ticketing tool
    • B2B sales management with Docusign signature
A three-month project, then two tools built on the new CRM.

The context. The group’s CRM, on Dynamics 365, had to be migrated from one Microsoft environment to another (a tenant-to-tenant migration).

The need. See the migration through, then build on the new CRM to structure customer service and sales management.

The approach. I acted as project lead for the three months of the project, coordinating the external contractors:

  • Scoping. Defining the scope and goals of the migration.
  • Planning. Setting the schedule and sharing out the work with the contractors.
  • Acceptance testing. Checking the migrated CRM before handing it to the teams.
  • Go-live. Moving the teams onto the new CRM.

Once the CRM was in place, I built two business tools on top of it:

  • A ticketing tool, to structure how customer-service requests are handled.
  • A B2B sales-management tool, with electronic signature through Docusign.

The result. The migrated CRM is in production. Customer service handles requests in a ticketing tool, and the B2B sales team follows each deal through to signature.

Labellemontagne · Since 2025

Sales and the customer journey as dashboards

  • Power BI
  • Power Query
  • Microsoft Fabric

Power BI reports for the sales of six ski resorts, and a BI view tracing a customer’s journey across every channel.

4
channels brought into one journey
6
resorts in the sales reports
1
single view per customer
  1. Channels

    • Website live chat
    • E-mail
    • Phone
    • Forms and tickets
  2. Data platform

    • Exchanges gathered per customer and put back in order
  3. Customer-service BI

    • A customer’s complete journey with the teams
Four channels, one journey per customer.

The context. Sales are tracked resort by resort. Conversations with customers run through four channels: the website’s live chat, e-mail, phone, and forms and tickets.

The need. Give sales teams a shared reading of sales, and give customer service a full view of what a customer has experienced with the teams.

The approach. Two sets of reports, built on the data prepared in the data platform:

  • The sales reports. The sales BI reports for the group’s six ski resorts.
  • The customer-service BI. It gathers all the exchanges of one customer, whatever the channel, and puts them back in order to trace their complete journey with the teams.

The result. The six resorts share the same sales reports, and customer service has a single view of each customer’s journey.

Labellemontagne · Since 2025

AI rolled out to the teams

  • Claude Code
  • AI agents
  • Training

Rolling out AI tools, including Claude Code, and training five people in marketing and customer service to work with AI agents.

5
people trained
5
different roles
2
teams: marketing and customer service
  1. Roll out

    • AI tools, including Claude Code
  2. Train

    • Content manager
    • Traffic manager
    • Operational marketing
    • Customer service
    • Marketing director
  3. Share

    • Good practices for working with AI agents
From rolling out the tool to shared practices.

The context. AI tools are arriving in the company, and teams do not yet share a method for using them.

The need. Teams that know how to work with AI agents, not just teams that have access to them.

The approach. Three stages:

  • Roll out. Making AI tools available, Claude Code in particular.
  • Train. Five people in five roles: content manager, traffic manager, operational marketing, customer service and marketing director.
  • Share. Spreading good practices for working with AI agents across the company.

The result. Five people trained, in five roles, and shared practices for working with AI agents.