Projects

What I've built

Every case follows the same order: the problem, what was put in place, what changed. These are systems I built and keep running; three of them are explained on video.

01Emails

The inbox sorted before 7 a.m.

The problem: A general inbox that receives about sixty emails per business day. Sorting by hand takes an hour every morning, and about once a month an important request gets lost between two newsletters. It is not an email problem, it is an attention problem.
What was built: Automatic filing on arrival. Routine replies drafted, for approval. Escalation of urgent requests to a manager, with a phone alert for critical cases. Four successive versions; the latest runs continuously.
The result: The inbox is sorted before 7 a.m. Urgent cases surface the same day. Nobody had to learn a new tool: everything happens in the existing inbox.

What I learned from itA trigger with no filter on the inbox once produced a loop: the system was replying to its own messages. The guard that prevents it is part of everything I have delivered since.

The system explained in two minutes. The YouTube player only loads when you click.

02Invoices

Invoices that enter themselves and chase themselves

The problem: Supplier invoices are entered by hand. Payment reminders go out when someone thinks of it. Outgoing invoices are written one at a time. The invoice you forget to chase costs more than the one that takes ten minutes to enter.
What was built: Three linked automations, in a single workbook: the service agreement generated and sent for signature; outgoing invoicing, with automatic reminders when due; and the reading of incoming invoices, coded to the chart of accounts, with anomaly detection (unusual amount, unknown supplier, duplicate). The sales tax registration threshold is monitored automatically.
The result: Data entry disappears, reminders go out on their own, and the yearly total can be read at a glance. System built and tested; rollout in progress.

03Security

The audit that finds the passwords hidden in your automations

The problem: An automation built in a hurry often contains access keys written in plain text, triggers open to anyone who knows the address, no timeouts and no error handling. Nobody notices until something has leaked.
What was built: An automated audit that goes through every automation in an account and produces a report on seven points: secrets in plain text, unauthenticated triggers, missing error handler, missing timeouts, sensitive data kept in the history, orphan triggers, risky steps with no justification. A second tool automatically fixes the most frequent point.
The result: What used to take a day of reading takes a few hours, report included. And every system I deliver goes through that same list before going live.

The audit explained in four minutes. The YouTube player only loads when you click.

04Research

Hours of video summarized in a few minutes of reading

The problem: Following a dozen video or document sources a week takes several hours of viewing, most of which brings nothing.
What was built: A family of automations that fetch the content, summarize it (in two passes for long formats) and drop a structured summary into a document or a spreadsheet. Scheduled cadence, cap per run, deduplication.
The result: Reading goes from several hours to a few minutes per source.

What I learned from itVideo platforms block data-centre addresses. An automation of this kind cannot run just anywhere. It is the kind of detail that makes the difference between "it works on my machine" and "it works at your place".

05Guide

A guide sent, a contact recorded, with no one involved

The problem: A downloadable PDF guide is useless without follow-up, and doing it by hand doesn't hold beyond a few sign-ups.
What was built: An online form, immediate delivery of the guide by email, the contact recorded in a spreadsheet and a notification. Two languages, on a server I control. The guide form on this site is that system.
The result: A complete chain from the click to the contact record, without anyone touching it.

Get the guide

And you

Does your case look like one of these?

Write to me. Twenty minutes are enough to know whether it can be automated, and I tell you frankly when the answer is no.

Tell me about your needs