The agents
Which agents I build
Three families, and one control screen. Two of these agents run in production today, at a company, every day. Each does one precise task, inside your tools, with your rules — and each stops at the same place: it prepares, you approve.
The three families
Invoicing agent
In productionIt polls a mailbox, recognises delivery notes, reads the attached Excel files and creates draft invoices directly inside the business software. The bookkeeper opens the software in the morning: yesterday's drafts are waiting, they read them and approve.
- It does
- Reads the mail, reads the notes, creates the drafts, flags doubtful lines.
- It doesn't
- It approves no invoice, sends none, and doesn't touch your original files.
- Who for
- A company re-keying at least ten hours a month. Below that, I advise against it.
- Shipped as
- An application installed on your machine, with cryptographically signed updates.
Payroll preparation agent
In productionFrom a schedule, it counts days worked per employee and per country, adds meal and travel allowances, and produces the month's worksheet ready to hand over. The checking work stays entirely yours — but it starts from a filled-in document, not a blank sheet.
- It does
- Reads the schedule, counts, calculates allowances, produces the monthly worksheet.
- It doesn't
- It pays no one, files nothing with any authority, and never edits the original schedule.
- Who for
- A company whose payroll depends on a schedule that has to be recounted every month.
Data collection and monitoring
On requestSupplier catalogues, competitor prices, listings: the data is collected from the web and gathered into a formatted Excel file. Sites that render their data in JavaScript are not a problem — the agent drives a real browser.
- It does
- Collection, cleaning, deduplication on the identifier, formatted Excel export. One-off or recurring.
- It doesn't
- It bypasses no protection and no authentication you wouldn't be entitled to use.
- Who for
- A company tracking prices or rebuilding a catalogue by hand.
When you have several
Two agents are easy to follow. Four means four windows to open and four places to look for what happened overnight. The agents HQ is the single screen where you see them all: what ran, what stopped, what is waiting for approval.
It carries an assistant that answers questions about what the agents did, and it runs locally on the company's machine: no data leaves. It never calculates an amount itself, quotes only the figures the agents provide, and creates or modifies nothing.
What they all share
Whichever agent it is, the same five limits are written into the code from the first line.
- It prepares, you approve. Nothing is finalised or sent to a third party without a human decision.
- It never guesses. A missing value stops the line concerned and is reported to you.
- Your original files are read, never modified.
- It runs at your place. The application sits on your machine; your data doesn't need to leave it.
- You can run it again without me. It is a tool, not a dependency.
And yours?
These three families come from real needs, not from a catalogue. If your repetitive task doesn't look like any of them, describe it anyway: the question isn't whether it fits a box, but whether the time it takes justifies automating it.
| Is it worth it for me? | The full calculation, and the threshold below which I say no. |
|---|---|
| What about my data? | Twelve straight questions and answers on security, timelines and liability. |
| Tarifs et rentabilité | Pricing tiers and an interactive calculator — this page is in French. |
First conversation free. Send me three of your real documents: I'll show you what it looks like, and tell you whether it's worth it.