Solutions / Automations (pack of 3 flows)
Automations (pack of 3 flows)
So it stops living in copy and paste
I take up to three repeated tasks and leave them running on their own, with an alert when something fails.
What this is
An automation package is up to three tasks that still live in copy and paste: email, spreadsheets, forms and the systems you already use. Each flow has a trigger, conditions and an alert when it fails. The tool can be n8n, Make or code, depending on what you already have. Licences, and anything without an API or an export, are quoted separately. Monthly operation after handover is optional and has a published price.
Experience
At Falabella I mapped processes across the whole commerce journey — catalogue, payment, dispatch, returns — and coordinated teams to fix incidents in that chain. At Wodobox I automated internal and client reporting in Looker Studio. I work with ETL, SQL and Python automation. The package does not promise an eternal operation: it leaves the flows running, tested, and a note on how to switch them off.
How I work
I use two ways of ordering the work. They are not creeds. Each one fits a different moment.
Waterfall
First we write the whole path and what sits outside it. Then we build in that order. It fits when the scope can already be named: a six-screen site, an integration between two systems, an Odoo start with three modules. You know what you will receive before we begin.
Scrum
The work is split into short weeks. Each week something usable is shown, and we decide what comes next. It fits when the detail is still being found: an agent's tone, the question that actually reaches the bot, the priority in a backlog.
The published package is the frame: scope, timing, and what is quoted separately. That is waterfall. Inside it there is a weekly review: we look, we correct, we carry on. That is Scrum. I hold a Scrum Master certificate and Scrum Foundations, plus a Green Belt for when the problem is operational rather than fashionable.
Who it is for
Small or mid-size operations where someone still moves data by hand every day.
What the package includes
- Up to three flows
- Triggers, conditions and error alerts
- n8n, Make or code, depending on what you already have
- A test with sample data and one real case
- A note on what each flow does and how to switch it off
Quoted separately
- Tool licences
- Flows that depend on a system with no API and no export
- Monthly operation after handover