ESSEC · AI Process Architect

Financial discipline.
AI execution.

I help startups and teams of up to 100 people automate repetitive operations, build qualified lead systems, improve their visibility in AI answers and turn a credible web presence into useful operating leverage.

JUSTIN ESCOUROLLESPARIS · MADRID
Justin Escourolles at graduation
EDUCATIONESSEC Business School
FOCUSAutomation · lead systems · GEO
PUBLISHEDAI for Profit
EDUCATIONESSEC Business School · Strategy
EXECUTIONAI workflows, automation and integrations
PUBLISHED WORKAuthor of AI for Profit

“Useful AI should not make a business look more intelligent. It should make the work clearer, faster and easier to operate.

01

Finance made rigor non-negotiable.

Experience shaped first at the French Ministry of Economy, then across HSBC and BPCE, built a durable instinct: a useful answer must be explainable, defensible and connected to a real business decision.

French Ministry of EconomyHSBCBPCERisk · valuation · reporting
02

AI became a practical operating layer.

The opportunity is not another isolated chatbot. It is a well-designed flow that can read context, structure information, coordinate tools and leave the team with a usable result.

Workflow designAutomationMake · n8nAPIs
03

The intersection became the specialty.

Finance brings discipline. Automation brings speed and leverage. Combining both makes it possible to improve serious operational work without introducing unnecessary complexity.

Measured ROIClear ownershipOperational designTeam adoption
AI for Profit book cover by Justin Escourolles
The published thesis

AI for Profit

The book explores a simple business question: how can organisations turn artificial intelligence into useful operating leverage? It connects productivity, better decisions and practical adoption — the same lens applied to every botticceli.io system.

From potential to use caseFrom tool to workflowFrom output to business value
01 / VALUE

Business case before build.

Start from the repeated work, its cost and the result it should create.

Output: a measurable baseline
02 / EVIDENCE

Proof before scale.

Run representative cases and compare the result with the current process.

Output: a defensible go / no-go
03 / ADOPTION

Usability before complexity.

Design the workflow so the team can understand, operate and improve it.

Output: a system the team can use
One problem is enough to begin

Bring the bottleneck.
We'll map the next move.

Start a conversation →