Diagnosis before spectacle.
Technology is not used to impress. It is used when it helps something work better than before.
Erik Garcés · Founder HME84 · Mexico City
Erik Garcés, behind HME84
Seeing order where others see chaos.
Some profiles are explained by job titles. This one is not. In HME84, Erik operates as a way of reading systems: listening before building, separating noise from priority, and turning ambiguity into a sensible next action.
I design digital systems, brands, and AI-assisted tools for businesses that need to organize operations, communication, and decision-making.
Not to translate. To solve. Data, product, and technology with business judgment, enterprise experience, and hands-on execution.
01 · listen
Before proposing, understand what problem actually exists.
02 · organize
Separate anxiety from tools, real debt from opportunity.
03 · build
Only when there is a clear reason to do so.
This page is not a list of titles. It shows how HME84 thinks when a business does not know whether to build, pause, or clean up.
Systems that can actually be operated.
Good design does not end in the prototype. It has to support conversation, decision, continuity, and maintenance.
Clarity without performance.
AI, data, and product only have value when they land in real context: business, costs, people, flow, and responsibility.
This is not a full chronology. It is evidence of capacity: regulated environments, data governance, BI, adoption, and enterprise operations brought into a practical way of deciding.
BCE · Orange
Regulated environments, data governance, and enterprise adoption.
Data Governance and MDM blueprint work in contexts where architecture, information, regulation, and adoption had to speak precisely to one another.
Danone · BBVA
BI, analytics, and business decision-making.
Work with information, processes, and operations in organizations where data is not decoration: it affects costs, priorities, and direction.
HME84
Built practice, not just recommendations.
Brand, web, assistants, and operational systems designed as a living architecture: useful, editable, and honest.
Evidence
What gets built shows how HME84 thinks.
Guardian, Loop84, and Miranda do not appear as trophies. They are living prototypes of how HME84 turns ambiguity into usable systems.
The public layer is a reading, not the full workshop.
The page shows the thinking. The depth starts in conversation.
Guardian
First contact with context.
An example of how a first conversation can become useful context, without pretending the human part stopped mattering.
Loop84
Operational continuity.
An example of how to make the real state of work visible: risks, blockers, and the next safe action.
Miranda
AI-assisted visual judgment.
An example of assisted visual criteria: image reading, taxonomy, and product decision-making.
The most valuable diagnosis is not the one that sells. It is the one that tells the truth.
If something needs to be built, it gets built. If not, there also has to be enough judgment to say so.
AI does not replace judgment. It makes it more demanding.
Next conversation
Technology works better when there is judgment behind it.
HME84 reads systems quietly: what hurts, what matters, and what should be built, adjusted, or left alone.
If this way of thinking matches what you are trying to organize, the next conversation can begin there: no performance, no pressure, just a clearer read of the problem.