Foundations

The manifesto states the why.
This document states the how.

What HME84 is in concrete terms, how the process works, the framework we use, and what we honestly do not do. For anyone who wants to understand before reaching out.

If you are looking for the studio's philosophical stance, it lives in the Manifesto. This document is operational.

Definition

A studio that steps in before building.

HME84 does not start by selling a solution. It starts by listening to a real problem — and deciding whether technology has something useful to contribute, or whether the honest answer is to leave things alone for now.

We combine technical judgment, editorial judgment and brand sensitivity. They are not separate layers: they are the same perspective applied to the same problem.

The value is not in the code. It is in the reading that precedes the code.

HME84 works with businesses that already have reality: customers, operations, friction, pending decisions. A bakery, a pet store, a clinic, or a boutique hotel do not need the same scope — but they do need the same judgment.

What we are Honest reading of ideas, systems, and problems. Diagnosis before code. A blueprint the client can use even if they do not build with us.
What we are not Generic consultancy. Inflated digital transformation. Custom development by default. Big-consultancy promises for small businesses.
Where we operate from Mexico City and remote. Individually led, with project-based collaboration when the scope needs it. No perfect brief required.
Working framework

Loop84 / Root84 / Glow84.

Direction before reaction.
Roots before growth.
Shine without disguise.

Three phases, one way of judging. Not every project reaches the third. Sometimes Loop84 is enough — and the most honest deliverable is clarity without spending on what you do not need.

01 Loop84 Direction

Act, correct, do not react.

Loop84 tells you how to act, what to correct, and when not to react. It turns noise, urgency, and technology anxiety into a clear next action.

We listen without an agenda. We map what actually exists: what is used, what is paid for, what repeats, what creates friction. We separate real urgency from digital fashion. The result is not always "something needs to be built" — sometimes the most honest diagnosis is clarity with no additional spend.

Assessment comes before building: the other steps depend on what we find here. The only exception is GBC Hotfix, a one-off, tightly scoped intervention on a specific problem; if the problem turns out to be bigger, we document it and propose the right path.

02 Root84 Roots

Strong roots before growth.

Root84 organizes what sustains the business: tools, processes, subscriptions, costs, messaging, flows, and operational decisions. Before adding new layers, what already exists has to work well.

Root84 does not build anything new. It makes what already exists work better — and that often matters more than any additional tool. An organized stack is easier to run, to pay for and to understand.

This phase focuses on consolidating what is already there, not on adding tools.

03 Glow84 Shine

Shine without disguise.

Glow84 builds the visible layer of the business without disguising it. Digital presence, microsites, assistants, flows, bots, and tools that express what you already are better — not what you think you should look like.

When the diagnosis confirms that building makes sense, we build. Lightweight does not mean lesser: it means transferable. The client can understand it, maintain it, and not get trapped in blind dependency. When a project uses AI, we define the task it supports, the information it receives, how its output is reviewed and when a person steps in.

Geek enough to build it. Chic enough to make it belong.

Important note: each phase ends with a useful deliverable, even if the project does not advance to the next. What the proposal defines is transferred: the Loop84 document, the Root84 organization and what is built in Glow84 become yours on the agreed terms, subject to the third-party licenses (platforms, APIs, subscriptions or open-source components) that each one keeps. No continuity traps.
Base offer

Three entry points.

Not every conversation starts from the same place. These are the concrete ways HME84 works.

01

Loop84 Blueprint

We listen to your idea, business, or system and turn it into a clear diagnosis: what exists, what is missing, what creates noise, what creates value, and whether it makes sense to build something — or not. Includes reading of the real problem, current state, alternatives, and suggested path.

From 9,900 MXN + VAT. The document is yours even if you do not build with us.
02

Cost & Stack Review

We review your subscriptions, licenses, platforms, and workflows to detect duplicated spend, oversized tools, features already included in what you pay for, and solutions that no longer match the current business.

6,500 MXN + VAT, credited toward a Blueprint or a route if hired within 30 days.
03

Scoped development

When the diagnosis shows that building is the best path, we build. Only what closes the case: microsites, assistants, bots, flows, lightweight platforms, and tools connected to channels the business already uses.

Always after assessment, never by default. The final price is set after the Blueprint.
The filter

What HME84 does not do.

Knowing what HME84 does not do is as important as knowing what it does. This saves both of us time.

Generic consultancy without real technical judgment.
Inflated digital transformation to justify budget.
Custom development as the default answer to any problem.
Empty packages designed to look complete.
Unnecessary complexity when a simple tool solves the case.
“AI solution” promises without a real prior assessment.
Dependency on proprietary tools that trap the client.
Projects where the deliverable cannot be used without HME84.
Process

What working with HME84 looks like.

01

First conversation

You do not need to arrive with a perfect brief or a finished idea. The first conversation is to understand the real problem — not to sell a service. If HME84 is not what you need, we say so on that same call.

02

Diagnosis and map

We listen, ask questions, review what exists. We separate what is urgent from what is important, and what is real from what is fashionable noise. The result is an honest reading of the case — not a pitch to convince you to build something.

03

Clear deliverable

There is always a concrete deliverable: a blueprint, a stack review, a suggested path. The document is yours. You can take it to another team, execute it yourself, or use it to make an informed decision.

04

Real next step

If it makes sense to keep working together, we define the next step with clear scope and expectations. If it does not, we say that too. The proposal separates the development price from running costs: third-party APIs, domains, licenses and subscriptions are quoted separately. We work remotely, by video call, with direct communication and no intermediaries.

Orchestration with judgment

The model changes.The judgment remains.

An architecture for preserving context, deciding within limits and coordinating work across different engines and tools.

01 / Explore

Analysis and
research

Explore, compare and frame questions.

  • ChatGPT
  • Claude
  • Gemini
  • Perplexity

Examples of supporting interfaces and services.

02 / Coordinate

Judgment + context

  • Goals and authority

    Studio leadership defines intent and scope.

  • Agents with identity

    Clear responsibilities and handovers.

  • Evidence and permissions

    Every action has limits and a trail.

THE ENGINE IS INTERCHANGEABLE

03 / Build

Execution and
presentation

Turn decisions into reviewable work.

  • Codex
  • Claude Code
  • Canva

Examples of tools, depending on the task.

Interactive diorama, in SpanishMeet the house: the agents and what each one does

Own operating base

Local first. Cloud depending on task, capability and permissions.

Identity

Roles and responsibilities.

Context

Sources and persistent memory.

Control

Permissions and limits on action.

Traceability

Health, logs and evidence.

Agent mentoring program

Learning to answer for the work.

Independent judgment · evidence · progressive autonomy.

If an engine fails

  1. Detect

    Record the failure and the point of work.

  2. Transfer

    Hand over with context, if there is validated capability.

  3. Pause

    Preserve the state if there is no safe handover.

MODEL ≠ AGENT ≠ SYSTEM

Conceptual view, updated on September 30, 2026. The applications are examples, not an inventory of active integrations. It does not certify availability or automatic handover: handover depends on validated context and capability.

If your business already works but its digital layer is not keeping up — let's start by understanding what is going on.

Start a conversation

View services Read manifesto