Skip to main content

The Margin-Driven Engine: Why Post-Sales AI Enablement is an Operational Design Problem

A conversation with Pierrick Joliveau — Fractional CCO and former VP of Customer Success — on bridging the gap between systems engineering, high-stakes operations, and the strategic frontier of AI-assisted enablement.

By Louise Servoin · 2026-10-16 · 10 min read

## Pierrick Joliveau – Fractional CCO & Founder at The Openside Flanker LLC

Expert in post-sales operations, international scaling, and AI-driven workflow design. Leader in scalable digital and post-sales workflows, bridging the gap between technical architecture, software, and international business strategy. Based in Brooklyn, NY, United States.

Some professionals understand the code. Others understand the relationship. Rarely do you find someone who can navigate both while operating in the high-stakes environment of international scale-ups and SaaS operations.

Pierrick Joliveau's trajectory — from the rigorous engineering halls of ENSIL-ENSCI to managing complex operations portfolios for global ad-tech and SaaS leaders like Criteo and Kevel, all while founding his own ventures (CAMAREL, IMALEO) and now running The Openside Flanker LLC, his fractional CCO practice — places him at a unique intersection of technology and operational leadership.

We sat down with Pierrick to discuss why most "AI integrations" in customer success fail to move the financial needle, how being an engineering-minded operator makes him a better builder, and why the future of SaaS efficiency relies on AI-assisted human enablement.

## The Hybrid Architect

Pierrick, you have a dual identity as both a fractional advisor and an operational leader. How does the "builder" mindset of an entrepreneur influence how you advise massive SaaS organizations?

I'm not a storyteller, I'm a fixer. If I use a reference to my other passion, rugby, I describe myself as the openside flanker of commercial teams — often the on-field captain. I'm the one calling the shots on structure and process while I'm still the one making the tackle. I don't step off the pitch to draw up the playbook; I build it between plays, with the team, while the game is live.

That's the same instinct whether I'm founding a venture or advising one. In the startup world, you learn very quickly that technology is not valuable if it doesn't solve a friction point. Building new technology is resource-consuming, so you have to be solution-oriented, lean, fast, and obsessed with building for the user.

When I step into my role to advise a SaaS firm through The Openside Flanker LLC, I bring that same builder pragmatism. Large organizations sometimes get enamored with the idea of AI; they want "innovation" as a concept. My job is to act as a reality check. My starting point with every client is always: post-sales teams should be treated as a crucial part of the revenue engine, not as an expendable cost center. So before we talk about any tool, we ask: what structure, process, or metric is actually stopping CS from protecting NRR and margin today? Only once that's clear do we start talking about the tech.

Whether you're a seed-stage startup or an enterprise leader, the goal is the same: building post-sales workflows that protect operating margins, convert usage data into expansion opportunities, and make operations run smoothly.

## The Foundations of Technical Leadership

Your background at ENSIL-ENSCI suggests a deep technical foundation. In an era where AI is often treated as "magic," how important is it for operations managers to actually understand the underlying engineering?

It's critical. The opportunities that recent AI tools have opened are amazing. But if you don't understand the limitations of the models underneath — the bias, the hallucinations, or the infrastructure required to scale a solution, it is very hard to lead a project effectively.

My academic journey provided the bedrock for this perspective: ENSIL-ENSCI instilled a rigorous engineering discipline, a structural integrity in problem-solving that is often dismissed when companies feel the pressure to "ship fast." While that speed might win a sprint, that underlying technical rigor is what proves critical in the long run, especially when dealing with high-stakes environments where failures are not an option.

In SaaS operations, the stakes are too high for black boxes. When I manage operations and customer success projects, this technical background allows me to be a translator. I operate at the interface between engineers, talking about API integrations and data flows, and business stakeholders who want to understand why a specific workflow will protect Net Revenue Retention (NRR). That's why I favor clear, automated metrics over complex, unexplainable systems — operational transparency is what lets a team trust the numbers instead of fearing them.

"I believe post-sales teams should be treated as a crucial part of the revenue engine, not as an expendable cost center." — Pierrick Joliveau

## The Implementation Gap

You've seen the operations landscape from both the European and American perspectives. Where is the "bridge" breaking down between having great technology and actually seeing NRR expansion?

Despite different operational ecosystems, I believe American and European companies actually share the same challenge in the end. The bridge usually breaks at the "last mile": adoption and continuous enablement. Most companies have plenty of data, and many have built impressive automated pilots. But moving from a successful pilot to a standardized tool that a Customer Success Manager (CSM) or an operations analyst uses every day? That's where the friction is.

In high-pressure scale-up environments, teams don't have time to learn a complex new interface or navigate fragmented tools. The gap isn't technical; it's strategic. We need to stop building "tools" and start building "solutions." At Kevel, we solved this by reviewing the entire client database and building our first customer tiering — 25 accounts in Tier 1, 70 in Tier 2, the rest in Tier 3 — and reallocating the team's energy accordingly: 80% of the team on Tier 1, 20% on Tier 2, and automated, AI-assisted touchpoints for Tier 3. We paired that structure with AI-powered tooling to automate the manual, repetitive parts of the customer journey, so the team could focus on the accounts that actually moved the needle. The result wasn't just cooler tech — it shifted our Net Revenue Retention from 94% to 103%.

## Entrepreneurship and AI

As a founder of CAMAREL and IMALEO, and an advisor to many startups, how do you think AI is changing the barrier to entry for scaling operations?

It's democratizing it for sure. Ten years ago, if you wanted to scale a global customer success team, you had to scale your headcount linearly with your revenue growth. Today, AI-powered tools allow a small, agile team to do the work of twenty people.

But it's not a magic wand. Just because you can automate something faster doesn't mean you should. For the ventures I advise, I always emphasize that AI should be the engine, not the driver. The driver must be a deep understanding of domain knowledge, customer journeys, and commercial metrics.

At Potloc, we specialized roles, clarified processes, and introduced generative AI tools like MidJourney and ChatGPT to accelerate our creative and delivery pipelines — going from 100 to 300 visuals produced per day, with approval rates jumping accordingly. That structure-plus-AI combination increased team productivity by about 40%, helped drive a 400% increase in US revenue over two years, and protected our gross margins in the process. If you structure the workflow correctly, your technology directly improves your operational metrics. The true measure of success isn't a complex formula — it's whether your expansion revenue outpaces contraction and churn from your existing client base. Get that right, and your existing customer base shifts from a cost center to an active revenue engine.

## The Question of the Future

As AI begins to commoditize "average" knowledge, what is the one human skill or nuance in your field that you believe an algorithm will never be able to replicate?

Empathy-driven strategy and hands-on operational leadership. Navigating complex, fast-evolving startup ecosystems and disruptive international expansions requires more than just processing power. An AI can find a pattern in a CRM or scour databases to find useful information, but it cannot sit in a room with a founder and understand the cultural resistance to a new technology or the nuance in a high-stakes customer escalation.

It can't feel the "weight" of a strategic market entry. In executive advisory and international scaling, the most valuable skill is judgment. It's the ability to look at scarce data, listen to human intuition, and decide which strategic risk is worth taking. AI gives us the map, but the human still has to choose the destination.

## The Golden Thread

We often see a gap between what technology can do and what professionals actually adopt. How do we ensure AI becomes a 'co-pilot' that elevates human judgment rather than a tool that encourages intellectual passivity?

A co-pilot doesn't replace judgment — it clears the runway for it. My job has never been to make teams move faster for the sake of speed; it's to build simple structures that let trust, accountability, and meaningful work keep happening even when AI absorbs the repetitive part of the job. At Potloc, AI freed up creative bandwidth. At Kevel, it freed up time to focus on the accounts that mattered. In both cases, the team didn't get replaced — it got room to do the work only humans can do: reading a customer's hesitation, catching the account that's quietly at risk, deciding which relationship deserves an extra hour this week.

The moment AI stops freeing up judgment and starts being used to avoid exercising it — that's the moment you've lost the thread. My rule of thumb for founders is simple: if a tool is helping your team make better calls, it's a co-pilot. If it's letting them stop making calls altogether, it's a liability wearing a co-pilot's badge.

Tags: AI in Operations, Customer Success, SaaS Integration, TNT Growth Capital, Enablement