Case studies
Salesforce projects delivered, told without jargon
Agentic AI, marketing, migration, integration, field service, legacy takeover: seven projects led by the Zebras, with the starting challenge, what we did and what changed.
Remake Asset Management
Remake automates its asset management with Agentforce
A Salesforce + Data 360 foundation to absorb AI agent automation without making teams’ daily work more complex.
Major cultural and leisure retail chain
Marketing Cloud and Service Cloud: a day-to-day partner for three business teams
Run, enhancements and major projects on Marketing Cloud and Service Cloud, all the way to the Data 360 integration.
Film and TV production group
Moving off an in-house CRM without putting production at risk
Salesforce deployed alongside the legacy tool and connected to the ERP, for a gradual switchover in two phases.
Subsidiary of an energy group
Field technicians move to Salesforce Field Service
The legacy field tool replaced by Field Service, plugged into the group’s Salesforce: scheduling, routes, customer SMS.
International group of media agencies
Sales logic put back on track, ticket by ticket
Scattered automations and incorrect cost calculations brought together in a single foundation, with no rebuild project.
National leader in home services
Franchisee recruitment: two tools finally connected in real time
From the web form to the recruitment tool, every application flows automatically and its progress comes back into Salesforce.
Building envelope manufacturer
Customer claims: from the quality software to Salesforce, with no re-entry
Claims logged in the quality software flow into Salesforce automatically, with their progress and full history.
Remake Asset Management · Real estate fund manager (SCPI)
Remake automates its asset management with Agentforce
The challenge
Manual processes spread across several teams, data scattered between tools: Remake needed a Salesforce + Data 360 foundation able to absorb AI agent automation without making teams’ daily work more complex.
Our approach
- Audit of existing processes and data mapping
- Data 360 architecture to make the data exposed to agents reliable
- Configuration of 5 Agentforce agents
- Phased rollout and team training
The result
Four processes automated, three teams working with the agents every day and a productivity gain measured at 25%. Remake talks about the project itself in a video.
Major cultural and leisure retail chain · Nationwide network, three business teams on Salesforce
Marketing Cloud and Service Cloud: a day-to-day partner for three business teams
The challenge
The retailer has used Marketing Cloud and Service Cloud for several years. Three business teams work in them every day: customer service, CRM marketing and B2B, with several IT teams involved in the projects. It needed a partner able to maintain the platforms, support the teams and drive new initiatives.
Our approach
- Day-to-day support and run: data extensions, SQL queries, email builds, dashboards and reporting
- Customer journeys set up and configured (Journey Builder)
- Audits and clean-up projects led on both platforms
- Partner solutions integrated: OwnBackup, Klark, Reelevant
- Data 360 integration project led
The result
Teams more autonomous on their tools thanks to training and shared documentation, new features adopted, reduced technical debt and storage under control. The same people support the retailer over the long term, from run to projects.
Film and TV production group · Full productions and technical services
Moving off an in-house CRM without putting production at risk
The challenge
The group ran its business on an in-house tool that had become hard to maintain and to connect to the rest of its IT. The goal: move to Salesforce Sales Cloud without weakening long productions, its core business and most sensitive activity.
Our approach
- Switchover in two phases: Salesforce first for short projects, the legacy tool kept for long productions
- Salesforce data model and data migration strategy
- Analysis of undocumented SQL Server and MySQL databases, mapping rules between the three systems
- Integration flows Salesforce ↔ ERP ↔ legacy tool, with controls and error handling
- Go-live of the integration infrastructure, documentation and support for the teams
The result
Salesforce entered the sales processes with controlled risk, thanks to the tools running side by side. The integration absorbed a major change late in the project: a sync planned every 24 hours, moved to every 5 minutes. Dependence on the legacy tool is shrinking, and phase 2 paves the way for a single Salesforce CRM across the group.
Subsidiary of an energy group · Operation and maintenance of solar power plants
Field technicians move to Salesforce Field Service
The challenge
Acquired through external growth, the subsidiary managed tickets, technician scheduling, corrective and preventive maintenance, inspections and cleaning campaigns in a business tool that was hard to evolve. The group chose Salesforce Field Service to optimise routes, keep customers better informed and build on the data already in its Salesforce: customers, sites, equipment, contracts.
Our approach
- Target solution designed with the business teams: data model, business rules, user journeys
- Field Service configuration: dispatch, territories, crews, variable shift patterns
- Beyond-standard adaptations: several technicians per job, overnight stays for remote sites
- Technical documentation available offline on mobile
- Manufacturer alerts turned into work orders, customer confirmation SMS
The result
Deployment ran in two phases, the first focused on getting operations started. Every team moved to the new solution within two weeks, and maintenance is now part of the group’s Salesforce ecosystem.
International group of media agencies · 6 brands, 13 territories
Sales logic put back on track, ticket by ticket
The challenge
The group sells its campaigns in Salesforce Sales Cloud. Over the years, the org had piled up scattered automations: cost and agency fee calculations that were sometimes wrong, performance limits reached, every change had become risky. The clean-up was done as part of managed services rather than as a rebuild.
Our approach
- Scattered automations brought together in a single Apex foundation
- Cost, margin and agency fee calculations made reliable
- Automatic sync of revenue schedules across product lines
- Territory-specific rules made configurable without development
- Legacy test classes that blocked deployments reworked
The result
All the sales logic now sits in a maintainable foundation that follows Salesforce best practice. Opening a territory or changing a cost rule no longer requires development, and future changes carry less risk.
National leader in home services · 130 franchised branches, targeting 200 by 2029
Franchisee recruitment: two tools finally connected in real time
The challenge
Leads lived in Salesforce Sales Cloud, franchisee applications in a specialist recruitment tool. With no link between the two, every candidate was entered twice, Salesforce had no visibility on progress, and a first integration attempt had been abandoned.
Our approach
- Automatic capture of website applications and creation in Salesforce
- Applications sent to the recruitment tool and progress returned to Salesforce, through the vendor’s API
- Traceable exchanges with personal data masking
- Go-live, documentation and operations guide handed over to the Salesforce administrator
The result
Delivered on time, where a first attempt had failed. Double entry is gone, every application reaches the recruitment tool in real time, and its progress is visible on the lead record. The client handles day-to-day maintenance itself.
Building envelope manufacturer · French manufacturer of metal profiles and panels
Customer claims: from the quality software to Salesforce, with no re-entry
The challenge
Customer claims were logged and tracked in the quality software, then re-keyed by hand into Salesforce Sales Cloud by customer service, with no up-to-date view of their progress. The goal: feed Salesforce directly from the quality tool, history included.
Our approach
- Custom integration, adapted to an API not designed for bulk processing
- Daily sync: new claims created and open ones tracked
- Claims isolated from other quality records, then the full history migrated
- Working directly with IT and business teams, from design to go-live
The result
Customer service no longer re-keys claims, and their progress is visible in Salesforce to every team that uses it. A tight team, direct access to IT and the business, and a solution adapted to the limits of the existing systems.
Does your project look like one of these?
Tell us about your context: a consultant who has led this kind of project will get back to you.