THINKING / IDEAS
Ideas.
What I learn designing and building real systems. Opinions backed by experience, not filler.
- 01
How to implement Business Intelligence in a company, step by step
What Business Intelligence is and how to implement it in seven steps: sources, definitions, data layer, reconciliation, dashboards, alerts and adoption.
- 02
Power BI dashboard: how to design one management actually uses
What a Power BI dashboard is, how it differs from a report, examples by area and how to design it so management decides with it. And when Power BI isn’t enough.
- 03
Verifactu API: how to integrate Verifactu into your software or ERP
What a Verifactu API is, what Spain’s tax agency requires from your invoicing system, the 2027 deadlines and how to integrate it into in-house or custom ERPs.
- 04
What is a management dashboard? Types, examples and how to make it useful
What a management dashboard (or scorecard) is, its types, including the balanced scorecard, KPI examples, Excel dashboards and how a scorecard differs from a dashboard.
- 05
A system you can’t evolve isn’t yours
Building a system with AI gets faster every year. What makes it yours is being able to understand it, change it and evolve it without depending on anyone.
- 06
Before building a dashboard, decide what it won’t claim
A dashboard that claims what the data can’t support is worse than none. What to leave out, how to compare and when to stay silent is decided before the first chart.
- 07
Your FITUR 2027 stand: the digital side is decided now, not at build-up
Exhibiting at FITUR 2027 (20–24 January, IFEMA Madrid)? Screens, video walls, QR web apps and visitor data are locked in months before the stand goes up.
- 08
Verifactu software: the problem isn’t the invoices, it’s the data
What Verifactu is, the 2027 deadlines, whether it’s mandatory and which Verifactu software you need. The challenge isn’t the invoice: it’s the data behind it.
- 09
Your AI assistant has to say it’s an AI
Since 2 August 2026, an AI assistant in the EU must disclose that it is one. Designed well, that notice isn’t a formality: it’s part of how the system works.
- 10
Software should fit the business, not the business the software
Standard tools work as long as your processes are standard. When they aren’t, forcing the fit creates friction, manual work and duplicated data.
- 11
What happens when building software stops being expensive
AI makes writing code dramatically cheaper. The bottleneck moves to deciding what to build, designing the architecture, integrating, validating and maintaining.
- 12
When NOT to use artificial intelligence
AI is a tool, not the architecture. Four real systems where the decision was made about which part deserved a model and which part worked better with rules.
- 13
Before selling a digital activation, make sure it can be delivered
An interactive idea can sound great in a proposal, but before selling it, pin down feasibility, scope, devices, risks and real production.
- 14
A video wall shouldn’t just be a pretty video on a loop
What a video wall is, LED or LCD, rental or purchase, and what video wall software does. At an event, the screen can become a live layer of data and experience.
- 15
A stand with technology is a small system running live
When the digital side gains weight, a stand stops being a collection of screens, apps or totems: it becomes a live system that has to work in a real context.
- 16
Your agency doesn’t need to be a software house
Agencies increasingly sell apps, totems, QR/NFC, screens and networking. They don’t need to become a software company to do it well.
- 17
A QR code isn’t a sticker: it’s a door
Before putting a QR code on an event piece, there’s one question worth asking. Because scanning is easy. The tricky part starts right after.
Got a specific problem?
Ideas are fine. Real problems are better. Tell me yours.