Automation · AI agents · Internal systems

Every lead handled. Every follow-up sent. Without you.

I design and deploy the systems that run your commercial cycle (prospecting, qualification, follow-up) and the repetitive tasks eating your weeks. Documented, transferable systems, built on ten years of designing and securing critical infrastructure.

Reply within 24 business hours · Quote after scoping · Transferable systems

Qualification flowlive
Form WhatsApp Missed call Qualification RULES · SCORING · ROUTING Scheduled follow-up DEFINED SCENARIO CRM record updated NO RE-ENTRY
Immediate responseto inbound leads
No data entryby hand
Full logtraceable end to end
The reality

It is not a lack of tools. It is a lack of system.

Most teams already have a CRM, a shared inbox and spreadsheets. The problem sits between those tools: humans re-typing, chasing, and forgetting.

Inbound leads wait

A prospect who fills in a form on Saturday night gets a call on Monday, sometimes Tuesday. By then they have contacted three competitors.

Prospecting is done by hand

Searching, copying, enriching, personalising: hours every week spent on work that nothing requires a human to do.

Small tasks pile up

Sorting e-mail, chasing invoices, monitoring, reporting. Each one is trivial; together they take half a day a week.

What I do

My services

Six families of automation. Most projects combine two or three.

Lead qualification and follow-up

The lead arrives, gets qualified, routed and followed up along a scenario defined with you. Form, WhatsApp, missed call, inbox: everything converges into a single, traceable flow.

n8nCRMWhatsAppe-mail

Prospecting and lead databases

Building targeted databases from public sources, then enriching and scoring them. You get a usable base, not a raw export.

Apifyscrapingenrichmentscoring

Inbox automation

Audit, custom taxonomy, automatic classification. The final system is attached to your own mailbox and runs on its own, with no subscription and no dependency on my infrastructure.

GmailApps Scriptclassification

Invoice chasing

Detecting overdue invoices and sending graduated reminders automatically, with immediate exit from the cycle once payment lands.

Airtableinvoicingfollow-ups

Monitoring and data collection

Watching sources (public tenders, competitors, catalogues, listings) and alerting only when a genuinely useful criterion is met.

n8nscrapingalerts

Internal conversational agents

An assistant your team drives from the tools it already uses, with mandatory human approval before any externally visible action.

TelegramLLMPostgreSQL
Who I work with

Two markets I know well

Clinics and medical aesthetics centres

You invest in advertising to generate enquiries, and a share of them is lost for lack of fast handling. I know that journey and where it breaks.

SMEs, independents and startups

Small organisations heavy on sales and admin, with little or no internal engineering time available. Automating what does not warrant a full-time developer.

The industry matters less than the nature of the process. If it is repetitive, triggered by an identifiable event and describable in steps, it can be automated. Describe it to me and I will tell you plainly whether I am the right fit.

Already built

Systems in production

A selection of systems designed and deployed. Clients are not named, as a matter of principle.

IT consulting firm

Automated mission onboarding

Webhook-triggered from the CRM, creating the document tree, updating the tracking base and notifying the team. Built to be idempotent: a replayed trigger never creates duplicates.

HubSpotn8nAirtableGoogle DriveSoftrTelegram
Independent professional

Gmail inbox cleaned and automated

Tens of thousands of messages sorted, a custom folder taxonomy, sender classification and a nightly clean-up. The final system is a script attached to the client's own mailbox: no subscription, no dependency on my infrastructure.

GmailApps Scriptn8n
Internal use

Chat-driven editorial assistant

Drafting, revising and full publication history from a chat conversation, with every version kept and one absolute rule: nothing is published without explicit approval.

Telegramn8nPostgreSQLLLM
What sets me apart

Ten years of critical infrastructure before automation

Ten years before AI

Designing and securing critical infrastructure in banking and retail. Environments where an outage is not an inconvenience.

You are not locked in

Every system is documented and transferable. Where technically possible it runs on your accounts and your tools, not mine.

Idempotency and error recovery

A replayed trigger creates no duplicate; one error does not break the chain. That is exactly what separates a prototype from a system.

Human approval by default

Nothing externally visible (an e-mail, a client message, a post) goes out without approval, unless you explicitly ask otherwise.

How I work

Four steps, no surprises

Scoping

I follow the process as it actually runs, not as it is supposed to. Output: the automation points and what each one saves.

Design

Architecture, choice of components, written specification and a firm quote. You approve before the first line of configuration.

Deployment

Build, tests on real cases, error and replay handling, progressive go-live.

Handover

Documentation, handover, access in your name and monitoring. At the end you can run the system without me.

Frequently asked

What people ask before starting

How long for a first system?

It depends on scope. A targeted automation (e-mail classification, invoice chasing, a monitoring alert) is designed and deployed in a few days. A system spanning several tools takes a few weeks, much of it scoping. I commit to a timeline after scoping, never before.

Does my team need technical skills?

No to use it, yes to change it deeply. The documentation I hand over lets someone comfortable with office tools understand the system and adjust everyday settings. Structural changes mean coming back to me or to another technical provider.

What happens if we stop working together?

The system keeps running. That is a design principle: where technically possible, what I deliver is attached to your accounts and your tools, not to my infrastructure. You keep the documentation, the access and the ability to take over or hand it to someone else.

Is my data sent to AI models?

Only where it is necessary, and it is written into the specification you approve. Many automations use no language model at all: they are rules. Where a model is used, I state which provider, what data reaches it, and what can be anonymised or stripped beforehand.

Do you work with the tools I already have?

That is the default. I plug into your existing CRM, inbox and spreadsheets rather than forcing a migration. I only propose changing a tool when the current one makes automation impossible, and I explain exactly why.

What are your rates?

I quote after scoping. A single automation and a system spanning five tools are not comparable, and naming a price before seeing your process would be guesswork. Scoping ends with a firm quote, before any development.

First conversation

A repetitive process eating your time?

Describe it in a few lines by e-mail: which process, how many times a week, how many people it burdens. I reply with a first read on what can be automated, and what cannot.

Reply within 24 business hours · No commitment · Confidential