Armand Charbonnier A. Charbonnier

AI & automation consultant

Thirty minutes

AI & automation consultant · Lyon, remote

The work nobody chose to do.

Re-typing, chasing, reformatting, searching. Those hours don’t show up on any line of your accounts, which is exactly why nobody counts them. I automate them. But the first thing I do is tell you what they are already costing you.

14 years of software engineering · 40+ applications shipped

02 Where the time goes

Nobody decided it. Everybody does it.

No company ever wrote “re-type this data” into a job description. These tasks moved in on their own, in the gap between two tools that don’t talk to each other, and they stayed there. It isn’t that people can’t be bothered, and it isn’t that they don’t know how. It’s plumbing.

  1. 01

    Double entry

    The same information typed into the CRM, then into the spreadsheet, then onto the invoice. One piece of data, three chances to get it wrong.

  2. 02

    Chasing

    Quotes with no reply, unpaid invoices, candidates left waiting. Somebody writes out the same message again, by hand, when they have better things to do.

  3. 03

    The Monday report

    A dashboard rebuilt by hand out of six exports, and already out of date by the time the meeting starts.

  4. 04

    Hunting for information

    “Who has the latest version of the contract?” Asked several times a day, to people who don’t have the answer.

One at a time they're trivial. Nobody is going to make a fuss about ten minutes. Added up over a year and across a whole team, they're not — and the number is yours to work out.

03 What it costs you

What’s it costing you?

Four sliders. You put your own numbers in, the page does the multiplication — the arithmetic is yours, I'm only putting it on screen.

12 people

Count only the people who actually do these tasks.

6 h / week

A rough estimate is plenty. You know better than I do how long it takes.

45 € / h

Gross salary, employer contributions and overhead included.

30 %

The default is deliberately cautious. The real figure gets measured during the audit.

994 hours

Hours you could get back per year

€44,712 per year

What that comes to

0.6 FTE

In full-time equivalent

21.6 h / week

Or, every week

What this calculation assumes

  • A basis of 46 working weeks a year, once holidays and bank holidays are out.
  • One full-time equivalent at 1,607 hours a year — the French statutory year.
  • The automatable share is the one you set yourself, so treat it as a working assumption.
  • The figure is gross. It deducts neither what the automation costs to build nor what it costs to run. And hours only turn into euros if you actually put them somewhere else.

An order of magnitude, not a quote. Your real figures come out of the audit, task by task — and some lines come back marked “do not automate”.

Send this calculation and talk it over

The result travels with your message, so there is nothing for you to copy out.

04 How I work

I’ll tell you when not to bother.

I start with your processes. The technology comes after, and sometimes it doesn’t come at all. We cost each task, automate the ones that pay back enough to be worth the work, and then look at what actually changed. The rest we leave alone.

  1. Map

    Duration
    2 weeks

    I interview the people who do the work, not only the ones who describe it in a meeting. Every repetitive task gets costed in hours per month, then ranked by gain and by difficulty.

    Deliverable
    A ranked list of opportunities with a verdict on every line. AI agent, automated flow, an off-the-shelf tool that already exists, or nothing at all.
  2. Automate

    Duration
    4 to 8 weeks

    Short sprints, wired into the tools you already have. Every automation is tested with the people who will actually use it, then put into production and documented. And fenced in. Limits, logs, alerts, a human sign-off everywhere a mistake would cost you.

    Deliverable
    Something running in production, with the documentation and the training that go with it.
  3. Measure

    Duration
    Ongoing

    A plain dashboard: hours saved, volumes handled, errors avoided, cost per run. What doesn’t pay gets switched off. What pays gets rolled out further.

    Deliverable
    Traceable numbers, with the method written out next to them, enough to defend them in front of your finance director.

05 14 years on the ground

14 years spent inside the teams losing that time.

Large corporates, fintech, start-ups, work abroad, products built alone in a back room. The track record isn't here to impress anyone. It explains why I move fast, why I am rarely wrong when I tell you a thing can't be done, and why I know when to stop.

  • 14 years of software engineering
  • 40+ applications shipped
  • 7 companies, in France and New Zealand
  • 2 working languages (French and English)
  • Fintech · AI · Mobile — Garance group

    Klemo

    klemo.com (opens in a new window)
    My role
    Mobile application development
    An AI-powered wealth advisor. Conversational onboarding, a free financial check-up, personalised recommendations. React Native, from the first screen to the store.
    What that tells you
    I put an AI-driven financial product into the hands of real users, not into a demo.
  • Fintech — 2022 › 2023

    Finary

    finary.com (opens in a new window)
    My role
    Developer embedded in the product team
    Key features across the mobile app and the web app, at a French consumer wealth-management platform.
    What that tells you
    I fit into a demanding product team and hold the pace on an app that’s already in production.
  • Insurance · Large account — 2016 › 2018

    MATMUT group

    My role
    Lead .NET developer, via Attineos
    Analysis, design, development of C# MVC web applications for the group. Alongside that I ran the internal training on Domain-Driven Design and Clean Architecture, and I sat on the other side of the table in technical interviews.
    What that tells you
    I know what a large group demands. Security, sign-off chains, legacy nobody is allowed to throw away. And I know how to hand all that on to your teams.
  • Retail — Parisian department store

    Printemps Listes

    listes.printemps.com (opens in a new window)
    My role
    React storefront development
    A wedding and gift-list platform. Catalogue browsing, list management, contribution flows.
    What that tells you
    I ship a public checkout flow under a brand name that doesn’t forgive rough edges.
  • SaaS · built and run single-handed

    SnippetShots

    snippetshots.saru-lab.com (opens in a new window)
    My role
    Design, hosting, operations
    An API that turns code into an image: one request, one clean PNG. Twenty themes, deterministic caching, and no headless browser to babysit.
    What that tells you
    I design frugal systems that cost little to run and wake nobody up at night.

What I run myself

I recommend nothing I don't already run myself. My servers, my containers, my n8n automations, my web-scraping jobs, my language-model integrations, and my React and React Native applications in production.

06 Three ways to start

Small and reversible.

An audit to find out where to act. A sprint to ship something that runs. A retainer, if you want to keep going without hiring. You can stop after any of the three.

01

Audit

Duration
2 weeks
Who it’s for
A leadership team that knows time is leaking somewhere and can’t tell where to start looking.

What you walk away with

  • Four to eight interviews with the people who actually do the work, not only the ones who manage it.
  • Every repetitive task costed in hours per month, against your real volumes.
  • The top ten opportunities ranked by gain and difficulty, with a verdict on each line.
  • A 90-day roadmap, with a first project ready to start.
  • A one-hour readout to your leadership team, and the freedom to stop right there.
Request an audit

03

Ongoing retainer

Duration
Monthly, cancellable
Who it’s for
A company that has shipped its first automation and wants more without hiring.

What you walk away with

  • Supervision of what’s already live: drift, outages, and the models and APIs that change under you.
  • One new project a month, or an improvement to one that’s already running.
  • A monthly 45-minute review, numbers in hand.
  • Your internal champion brought up to speed, and the documentation kept current.
  • No lock-in. Stop next month if you want to and everything keeps running without me.
Discuss a retainer

Don’t know where to act yet? That’s exactly what the audit is for.

No published rates. The number gets written after a first conversation, once we both know what we’re talking about.

07 Your questions

What you’re about to ask me.

The six objections that come up in every first meeting. May as well answer them now.

Where does our data go?

We settle that together before I write a line of code. What can leave the company, what must not. Where it matters, the tools run on infrastructure I deploy and you control. I already run my own that way. It's the same work.

Our tools are old. A lot of them are just Excel.

That’s what I find in most of the companies I walk into. A spreadsheet, a mailbox and one line-of-business application are plenty to start with. We plug into them rather than replace them. Replacement is a different project, much longer and a great deal riskier.

Do we need a technical team in-house?

No. I ship something your teams know how to use, and I document it. If you have a champion in-house, I train them. If you don’t, the retainer covers it for as long as you want it to.

How long before we see something?

Two weeks for the audit, then sprints of a few weeks each. The first automation in production is the goal of the first sprint, not of an eighteen-month plan.

What if it doesn’t work?

We’ll know fast, because every project is measured from the start. What doesn’t pay gets switched off at the next sprint. It’s also why the audit comes before any commitment.

Will we end up dependent on you?

The code, the accounts and the API keys are in your name from day one, the documentation is current, and your champion is trained. If you stop tomorrow, everything keeps running without me, and that’s the only honest way I know to sell any of this.

08 Who’s speaking

I speak business before I speak tech.

14 years of building software taught me that time is rarely lost in the code. It gets lost between the tools, and between the people using them. Independent since 2018, I work from Lyon, remotely, in French and in English, for French SMEs and for one New Zealand start-up.

Based in
Lyon, France · remote engagements, France and abroad
Independent since
2018 · 14 years in software
Languages
French (native), English (bilingual), Japanese (JLPT N5), Spanish (basic)
Education
Master’s in Software Engineering, Université de Rouen (2014) · DUT Computer Science, Le Havre (2010)
Armand Charbonnier
Lyon

Track record

  1. 2018 → today

    Freelance fullstack · Lyon, remote

    React and React Native, Node / NestJS, PostgreSQL, Firebase. More than 40 applications shipped, in France and abroad.

  2. Sep 2023 → today

    SprintMob, freelance collective · Lyon

    Web and mobile for a varied client roster. React Native, from the first wireframe to the store release.

  3. Jul 2022 – Jul 2023

    Finary · Lyon

    Embedded developer, key features across the mobile and web apps.

  4. Oct – Dec 2018

    Mahuki — Te Papa Innovation Hub · Wellington, New Zealand

    Lead developer of an event-management web application for ShowMode Ltd, at the national museum’s incubator.

  5. 2016 – 2018

    Attineos · Rouen

    Analyst-developer. Lead .NET developer for the MATMUT group, DDD and Clean Architecture trainer, technical assessor in hiring.

  6. 2012 – 2016

    FTEL · Rouen

    Analyst-developer. C# and PHP, .NET MVC, Entity, Zend, SQL Server, cross-platform mobile with Xamarin.

  7. 2010

    Dresser-Rand · Le Havre

    First role. Requirements analysis, specifications, data modelling, a multi-user management tool in VBA, and training the people who used it.

09 Contact

Thirty minutes, and you’ll know.

Tell me about the task that eats the most time in your team. In thirty minutes I’ll tell you whether it can be automated and where to start. If the answer is no, you get that too, and it will have cost you half an hour.

First conversation free, no commitment.

I reply within two working days.

Required fields: name, email and message.

What you’re interested in

Three lines is enough.

Your details are used only to reply to you. They go nowhere but my mailbox.

Or write to me directly: [email protected]