AI Automation
I automate emails, documents, CRM/ERP/TMS updates, reporting and follow-up. Exceptions and sensitive actions remain under human review.
Less copy-paste. More follow-up, still under control.
Technical consulting
A concrete problem. A useful solution. A measurable result.
I help technical and operational companies organize processes, connect systems and data, automate repetitive work and accelerate critical software. We start with one concrete problem.
A 20-minute conversation. No commitment. Remote work worldwide, from Barcelona sensio.business@gmail.com
For technical and operational companies
I work with teams that have grown around processes, data and tools that no longer fit together cleanly. You do not need to change everything: you need to identify where time, control or capacity is being lost and solve it within a manageable scope.
- 01
The team copies information between email, spreadsheets, ERP, CRM or TMS.
- 02
You have data and tools, but no clear view of the full flow.
- 03
The software or algorithm behind an important operation is too slow or too expensive.
One offer. Three ways in.
The three lines form one consulting offer. The entry point is the client problem, not the tool or service label.
Digitalization
I connect processes, data, internal software, cloud and private AI around one concrete, measurable operational problem.
A clear view of the flow, without replacing everything.
Process acceleration
I profile and accelerate technical software, critical algorithms and CPU/GPU/HPC workloads with reproducible benchmarks.
A demonstrable improvement in time or cost.
From problem to measured outcome
01
Problem
What happens today and where time, control or capacity is being lost.
02
Systems and data
Which tools, documents, users and constraints are involved.
03
Pilot
The minimum useful solution, with controls and a success criterion.
04
Measured outcome
What improves and which next step makes sense.
What can change in practice
Less manual work
Emails and documents stop being manually converted into records, tasks and repetitive responses.
More control
Data and systems connect, so owners can see what is happening and what remains pending.
More technical capacity
Critical software is profiled and accelerated with a demonstrable improvement, not a generic promise.
How we work
We do not start with a technology. We start by understanding the flow, choosing a manageable scope and defining how we will know it improved.
- 1
Understand
We review the current flow, its data, users, constraints, risks and highest-impact point.
- 2
Design
We define the minimum architecture, pilot scope and success criteria before building.
- 3
Implement
We build, integrate, document and test with real or authorized examples.
- 4
Measure and improve
We measure the outcome, correct exceptions and decide whether expanding makes sense.
The first step is to review a process
In a 20-minute conversation we review the current flow, volume, tools, exceptions and what a valuable outcome would look like. If there is a clear case, a typical pilot lasts 2–4 weeks: one process, closed scope, deliverables and an agreed success criterion.
To prepare, you only need to describe:
- • what happens today
- • who is involved
- • which systems, documents or algorithms are involved
- • which outcome you want to improve
Production experience, not just lab experience
I have shipped AI, data and software systems with real users, costs and operational constraints. That is the work I apply to one concrete process in your company.
- ESA
- Telefónica
- Repsol
- Iberdrola
- EarthPulse
Frequently asked questions
No. We start with the bottleneck that makes the most sense and work around existing tools whenever possible.
Not by default. We define human review, exception rules and traceability according to the process risk.
Yes. The first goal is to validate one concrete improvement before expanding. A typical pilot lasts 2–4 weeks: one process, a closed scope and an agreed success criterion.
I work remotely from Barcelona with companies in Spain and worldwide.
A 20-minute conversation about one process, its users, its data and the outcome you want to improve.
Which process is slowing you down?
Tell me which process you want to improve and I will suggest a concrete first step.
A 20-minute conversation. No commitment.