ABOUT BERTRAND CAPARD

I’ve learned that the most important growth opportunities rarely sit in the headline numbers.

Performance tells you where you are. Behaviour shows you where to grow.

Traffic, conversion and AOV tell you how the business performed. They rarely tell you what the business can actually change.

I work with teams to break performance down across consumers, cohorts and behaviours, find the persistent gaps underneath it, and turn those gaps into focused opportunities to test, learn and grow.

Portrait of Bertrand Capard.

FROM PERFORMANCE TO ACTION

I turn performance signals into decisions the business can act on.

The value of analytics is rarely in producing more data. It is in knowing which view of the problem matters, finding the customer differences hidden inside the averages, and turning that evidence into a clearer decision about what to change, test or build.

Build the right view of the problem

I move between sales, customer, experience, CRM, product and merchandising data, but I do not start by combining everything. I start with the problem and connect the sources that help explain it. The job is to absorb the complexity, reconcile definitions and put the customer back into the performance view so teams can see what is happening, for whom, and where it is worth looking next.

Find the differences that actually matter

Aggregate performance can look healthy while very different customer behaviours sit underneath it. I use segmentation, cohorts and behavioural decomposition to understand who is creating the result, who is not, and where persistent gaps exist. The point is not to create more segments. It is to find differences meaningful enough to change how we understand the problem or what the business should do next.

Decide what is worth testing

A gap is only useful if it leads to a better decision. I look at how many customers are affected, the size of the difference, what the business can plausibly influence and whether the potential value justifies acting on it. The goal is not perfect certainty. It is enough consistent evidence to choose where to move next, then use experimentation to validate the direction.

Analysis gives direction. Experimentation provides validation.

Build the model, not just the recommendation

I like staying close enough to the work to make the idea usable. I have built measurement frameworks, segmentation and scoring models, experimentation structures and decision workflows, and I increasingly turn that logic into working prototypes, internal products, applications and automated workflows.

That means moving comfortably between the strategic question and the underlying system: how something should be measured, how the decision logic should work, what the user needs, and what has to exist for a team to use it in practice.

I increasingly use AI agents to delegate parts of the execution, accelerate development and automate repeatable build work, while tools such as Python, SQL and KNIME sit underneath the solution where they are useful.

I do not need to engineer every component at scale. I want to take an idea far enough to prove the approach, build a credible first version and work effectively with the specialists who take it further.

18+ years

Ecommerce, analytics and consumer growth

From hands-on analysis to senior leadership across global consumer businesses.

€30M+

Incremental commercial value

Across conversion, personalisation, engagement and digital journey improvement.

+500%

Revenue per 1,000 emails

Through predictive targeting and more relevant CRM journeys.

€300M+

Impact measured & governed

Across major global digital initiatives and investment portfolios.

The more technology gives us, the more judgment matters.

The range of things a team can now turn into something real has expanded dramatically. Ideas that once required long development cycles or several specialist teams can increasingly be explored through working models, prototypes, products and automated workflows much earlier in the decision process. That creates enormous opportunity. It also creates far more choices.

The harder question is increasingly not whether something can be built, but whether it is worth building. The value is in narrowing the problem, recognising which customer differences matter, deciding what deserves investment, and choosing where technology will genuinely improve the decision or the outcome.

More capability does not remove uncertainty. It changes how quickly we can investigate it. The advantage is being able to move from an idea to evidence faster, learn what is worth pursuing, and stop investing in what is not.

Why BC75 Labs

That change in how work can be done is a large part of why I created BC75 Labs. I wanted to combine the judgment built through senior leadership roles with a much closer relationship to solving and building.

I want to be able to frame the challenge with leadership, work through the choices that matter, and then stay close enough to turn the thinking into something usable — a model, prototype, product, application or workflow that can be tested in the real business.

Modern development tools and agent-based ways of working make that combination far more practical. I can delegate parts of the execution, automate repeatable build work and take a concept much further myself before specialist engineering or scale becomes necessary.

If a client trusts me with an important problem, I want them to get my full attention and experience. The goal is to leave with a clearer understanding of the problem, a better decision about what to do next, something useful that works, and a stronger way of tackling the next challenge.

HOW I WORK

The way I work comes down to four principles that keep analysis connected to decisions, action and learning.

01

Use evidence to improve the decision, not postpone it.

Data should reduce uncertainty, not create an endless search for certainty. I want to understand what the evidence tells us, what it cannot tell us, and when we know enough to move. Sometimes the next useful step is more analysis. Sometimes it is testing the assumption in practice.

02

Start with the decision, not the metric.

A metric can tell us something changed without telling us what to do about it. I start by understanding the decision we need to make, the consumer behaviour behind it and what the business can realistically influence. That determines what evidence is actually useful.

03

Challenge the thinking, then commit to the decision.

I expect assumptions to be challenged, including my own. Different perspectives and evidence should improve the choice while there is still time to change it. Once a direction is chosen, the focus shifts to execution, ownership and learning from what happens next.

04

Solve the problem in a way the team can use again.

The best outcome is not a team that needs me for the next answer. Where it makes sense, I want the work to leave behind something repeatable: a model, framework, workflow, tool, process or simply a stronger way of approaching the next problem.

JUDGMENT, TEAMS AND LEADERSHIP

I want people to develop judgment, not dependency.

My role as a leader is to set a clear direction, make the objective and standards understood, and then give people real ownership of how they get there. I do not want to prescribe every step. When someone is developing, I would rather ask questions that help them work through the problem themselves. That is how autonomy grows.

Bertrand Capard coaching a youth basketball team.

Clear direction and real ownership go together. Once someone owns a piece of work, I expect them to build the plan, find the information they need and make the decisions within their responsibility. I stay available to help, remove barriers and challenge the thinking, but not to manage every step.

Accountability starts before the final result. I expect people to show direction early, validate important choices, raise issues before they become delivery problems and ask when the standard is unclear. If the result misses the expected level, I believe in being clear about it, understanding why the gap happened and helping them improve the way they work next time.

Over time, the aim is greater independence. People should understand the quality bar, frame problems more confidently, know when to ask for help and increasingly make difficult decisions themselves.

The same principle shows up when I coach basketball. You cannot make every decision for a player from the sideline. You can understand the individual, develop their strengths, give them structure and help them see the game. Then they have to make the decision. Good coaching develops players who can read the game themselves. I think good leadership should do the same.

LET'S TALK

Enough about me.What are you working on?

If you are dealing with a customer or growth problem that has plenty of data around it but still feels harder to solve than it should, bring the problem. We can work out what it actually needs.

Talk to me about your challenge