CASE STUDIES / SELECTED SYSTEMS
Systems I have designed and built.
Every case study tells the same story: the problem, the data, the constraints, what I decided to build and why. No mock-ups and no invented figures: systems that exist.
CASE_01 / Physical + digital
Event Tech
FITUR · MWC · ITB · WTM.
Systems for pavilions, stands and international trade fairs, where apps, screens, devices, data and stand staff have to work together, live, on a fixed date.
PROBLEM Agencies and public bodies have creative ideas that need to become technically possible: data-driven video walls, networking, bookings, participation.
Read the Event Tech case studyCASE_02 / Editorial platform
Rocio.com
A complete editorial platform.
A digital property with around 15 years on WordPress, rebuilt as its own platform: content, events, brotherhoods and a 30-year archive connected in a single system.
PROBLEM The content existed, but it was trapped.
Read the Rocio.com case studyCASE_03 / Business intelligence
AtalayaIQ
Operational data turned into business intelligence.
An intelligence layer over seven years of operational data from a national events company, without migrating its systems: capacity, costs, project risk and alerts in one management view.
PROBLEM Having data is not the same as being able to decide with it.
Read the AtalayaIQ case studyCASE_04 / Multi-tenant platform
Zentia
One real-estate platform that can become many.
A single platform that runs several real-estate agencies, each with its own brand, listings, leads and admin panel, and with each agency’s data isolated in the database itself.
PROBLEM Building a separate platform for each agency multiplies the code, the maintenance and every improvement.
Read the Zentia case study
02 / PROCESS
You bring the problem. I design and build the system.
You do not need to arrive with a solution, or know which technology you need.
- 01 — PROBLEM
What is not working, what costs too much, or what cannot be done today.
- 02 — DATA
What information exists, where it lives and what state it is in.
- 03 — CONSTRAINTS
Budget, deadlines, existing systems, team and regulation.
- 04 — OBJECTIVE
What has to happen for the system to be worth it.
- 05 — SYSTEM
I design and build the system, and keep supporting it after launch.
Do you have a similar problem?
Tell me the problem, the data, the constraints and the objective. If it looks like one of these case studies, you already know how I work.



