They were getting ready to buy AI. It was already paid for.

I am an operator, not a vendor, and I have no product to sell you. I spend three days inside your finance and operations team, find the work worth automating, and build it on the systems you already run.

30 yrs
running and fixing operations, most of it before anyone sold AI
10
industries, five of them for years at a time
$200M+
in programs built from scratch, then run, not advised on
3 days
to a written verdict, and it can be "do not build yet"
01The problem

A year of AI, and your close still takes exactly as long as it did.

People have built things ("skills"), plenty of them. Here is what I walk into almost everywhere.

Every one sits in somebody's personal account, where nobody else can reach it.

Each one was built a different way, so the same question asked twice gets two different answers.

Nothing gets properly tracked, and nothing handles its own errors.

The models are good enough. What is missing is one owner, one baseline, and one written rule for what the machine may do without asking.

02What the end game could look like

Your rules, written down once, and every agent reads them.

How your team actually closes the month, held in one place instead of in three people's heads. I call that a second brain.

  • A new hire reads the same rules the agents do.
  • When something goes wrong, there is a log of what the machine did and which rule it followed.
  • The second build costs less than the first.

The longest-serving member of your team retires. The reason that entry is booked the way it is does not retire with them.

A second brain drawn as a graph: about 500 pages and 3,000 links between them
Mine, September 2026. Every dot is a verified page the agents read; every line is a cross-reference.

Mine runs my companies.

~40
agents, in tiers, each with a job it answers for
80+
skills, written once and used by all of them
500+
verified pages in the wiki the agents read from
1 loop
that turns every correction into a rule the next session obeys

Everything I build for a client, I have run on myself first.

See the builds
03What I found on a recent engagement

A finance team was about to buy an AI tool. They were already paying for one.

The plan

Thousands of card transactions a month, each read by a person before approval. The team was about to shop for a tool to help with the pile.

What I found

The expense platform had shipped a policy checker months earlier, on the tier they already pay for. It tests every transaction against the written policy.

The answer

No new tool. Turn on the feature, and build it into a tracked workflow with proper constraints. Coding judgment still stays with people.

It is not the unusual one. Three things I find over and over, before anybody needs new software:

You are already paying for it

The capability ships inside a product you subscribe to, switched off.

The weekly export nobody questions

Two systems that could talk on licences you hold, and a person filling the gap every week.

The laptop tool everything depends on

Macros, a script, an AI assistant on one person's account. It breaks quietly, and the output still looks right.

04What gets built

Agents are not a workflow. A workflow is not a second brain.

Three nested layers. An agent sits inside a workflow, which sits inside a second brain. The agent answers a question and stops. The workflow adds a named owner, a baseline and a written rule. The second brain holds the rules, exceptions and decisions that every agent reads from.
Agents

Most companies have them. An agent answers a question and stops there.

A workflow

Few have one: a named owner, a baseline, and a written rule for what the machine may touch.

A second brain

Almost none have one: your rules and decisions in one place, read by every agent.

99%
of private equity leaders are exploring, piloting, scaling or embedding autonomous AI
9%
are very confident they could pass an independent AI governance audit within 90 days

Grant Thornton, 2026 AI Impact Survey. 100 private equity fund leaders, February to March 2026.

05How an engagement runs

Three steps. The first one can end with "do not build yet."

Step two

Build, with your owner

One or two days a week, with the person who will run it after I go.

  • The rules this work runs on, written down
  • Six acceptance tests, written before anything is built
  • Shadow mode until the output earns promotion
Step three

Run, measured

Priced per agent in production, not per hour of me.

  • A weekly ledger of hours returned against your baseline
  • Each build adds to the second brain
06What it looks like when it works

Inside what you already own, with an owner's name on each line.

Instead ofYou get
Three days of copy and pasteA monthly package pulled from the ERP and the bank feed, commentary drafted before the controller opens the file
The spring audit scrambleEvidence matched to the request list as transactions happen
The accountant everyone waits forReconciliations, accruals and intercompany matched in shadow mode until the machine agrees with your people
Asking the one person who knowsHow the company runs, written where a machine and a new hire can both read it
A pilot described as promising, for a second yearA weekly ledger of hours returned against your baseline

If your ERP already does one of these, I will tell you to switch it on, and I will go home.

07Fit

Who this is for, and who it is not.

For you if

  • You own a finance or operations workflow and answer for its number.
  • You want someone to look at what the data contains before anyone builds.
  • You are ready for the hard questions: security, legal, what the machine may see, and what happens the day it is wrong.

Not for you if

  • You just want a platform or model recommendation.
  • You do not care about the workflow. You just want a batch of quick skills, before anyone has checked you are ready to build.
  • Your private equity owner has already chosen an AI partner for every company it owns.

Things you may hear from me that most vendors will not say:

"Do not build yet."

Your data will not carry an agent yet. Building on it automates the mess.

"Your ERP already does that."

A feature you pay for every month, switched off. Turn it on and keep the money.

"This workflow needs an owner."

Put a name on it first, or there is nothing for a build to move.

"You don't need me anymore."

The agent runs, your owner runs it, and there is no reason to keep paying me to watch.

08Why an operator

Most people selling you AI have never even run an operation. I have built and run several.

I have owned the process, run the team, and answered to a CFO for the result. The same pattern every time: understand before you buy, or build.

Energy, 2011 to 2013TXU Energy, retention strategy

Attrition from 25% to 12% while raising price.

Mobile, 2014 to 2019Samsung, co-founder and GM

Built, then ran, the world's first certified pre-owned phone program and the first trade-in program run by a phone maker. $100M+ each.

Retail finance, 2020Samsung US retail operations

Head of finance, planning, procurement and logistics: $150M+ budget, over 30,000 doors, 700 FTEs.

Insurance, 2021 to 2025SquareTrade / Allstate, VP and GM

Built, then ran, a global trade-in business inside an insurer that had never had one. Three countries, two continents.

Advisory, 2021A wireless handset wholesaler

A product line losing money on every unit. Nothing was built: they widened what they traded, and revenue and gross profit both went up.

AI implementation, 2026A PE-backed multi-site operator

Five weeks, five deliverables. The biggest item on their automation list was a capability they already paid for, switched off.

Guennael Delorme
09About

Guennael Delorme, G to most people.

CELX Advisory started in 2021 after Samsung, advising in reverse logistics and trade-in. In 2026 it became the home for AI implementation, because that is what operators were asking for.

CSC (now DXC Technology), TXU Energy, BCG, Samsung, SquareTrade. I have spent my career at the front edge of the tools, and I take the part that is useful and leave the rest. I can hold the argument in the boardroom and stand on the floor where the work is done.

Not ready for a call

Read Execution Gaps first.

My newsletter on Substack, free. It started with operations: why good plans stall between the deck and the floor. It is moving, issue by issue, toward AI.

Thirty minutes. You get my read before you decide anything.

Bring the workflow that annoys you most. You leave with a different set of questions for your team, whether or not you ever hire me. If the answer is no, I will say so.

Rather write? guennael@celxadvisory.com

The link appears as soon as you submit.