MCI Órbita: The New Way to Track Opportunities (And Why the CRM Became Too Small)

MCI Órbita: The New Way to Track Opportunities

Most sales teams still track opportunities the same way they did in 2005: a CRM with fixed stages, cards dragged from column to column, and a mental spreadsheet about "who is the priority today."

The problem is that customer behavior has changed — and the funnel stage has stopped describing reality. An opportunity can technically be in "Proposal Sent" for 14 days, and no one knows if it's heating up, cooling down, or simply stuck due to lack of context.

The MCI Órbita was born from this gap. It isn't just a prettier CRM. It’s a different unit of observation: instead of static cards in columns, you see living cycles in motion, ordered by what needs your attention now.

The Órbita doesn't answer "what stage is the lead in?". It answers: "who do you need to take care of in the next 30 minutes to avoid losing margin?"

1. Why the CRM became too small

Traditional CRM was designed for a reality that no longer exists:

• Linear journeys (discovery → consideration → purchase) — today, the journey is circular, multi-channel, and full of reopenings.
• A single type of relationship per customer — today, the same customer is in acquisition for one product, retention for another, and support for a third all at once.
• Time as a priority metric (older = more urgent) — when, in practice, intent matters much more than age.
• Stage as truth — when, in practice, the stage is just where someone last dragged the card.

The result is what we call Amnésia Operacional: the company forgets the context of the last conversation, repeats questions the customer has already answered, and burns margin by offering discounts where trust would have sufficed.

The Órbita attacks this at the root: it replaces stages with a heat gradient, seniority with real priority, and cards with living cycles.

2. What is the MCI Órbita

The Órbita is the operational dashboard of MCI — Marketing Conversacional Integrado. It shows, in real-time, all live opportunities in the operation, separated by the type of relationship with the customer:

• Acquisition cycles — those deciding whether to buy.
• Retention cycles — those deciding whether to stay.
• Support cycles — those deciding whether to trust after a problem.

The same company (Tax ID) can appear in all three simultaneously. This isn't redundancy — it’s the truth of the relationship. And that’s why the lens (function filter) in the interface is so important: the salesperson needs to see acquisition cycles; CS sees retention; support sees support. No one needs to see everything, all the time.

Each cycle carries five pieces of information that CRM could never organize well:

These five attributes together become a priority score — and it is this score that orders the queue, not the creation date.

3. Why is it called Órbita?

Think of the universe. Every star has planets, moons, asteroids, and comets orbiting around it. The star's gravity is what keeps everything in motion — and the more massive and bright the star, the more stable and harmonious the orbits around it.

In the MCI Órbita, the customer experience is the star. All operational processes — sales, retention, support, forecasting — are celestial bodies orbiting around it. Not the other way around.

In traditional CRM, the process is the center: the funnel, the stages, the pipeline. The customer is just another data point passing through. In the Órbita, the customer is the gravitational center. When the experience is good, cycles revolve in stable orbits. When the experience fails, orbits become unstable — and that is when the system triggers an alert.

The higher the customer satisfaction, the better the orbit. A satisfied customer moves in a predictable trajectory. An unsatisfied customer is like a comet that has gone off course — and the Órbita shows exactly where they are, so you can bring them back before they escape forever.

The analogy isn't just poetic. It's functional. Every cycle has a trajectory (gradient), a velocity (SLA), a distance (decision state), and a nature (arquétipo). The operator doesn't manage cards — they observe orbits.

4. The living queue: ordered by who needs you now

Open the Órbita and the first thing you see isn't a list of leads. It’s a living queue ordered by real priority, divided into two sections:

Now · Human needed

Cycles with a yellow or red semáforo, expiring SLA, falling gradient, or blocked state. These are the cycles where your presence changes the outcome. If you only attend to these during the day, you’ve already protected most of the margin.

In flow · IAm taking care

Healthy cycles, in motion, with an automated next step. You see them, but you don't need to act. The IAm conducts the conversation within the script and only calls you when the cycle changes color.

Below, a discreet counter: "9,412 cold cycles in automatic nurturing — out of your queue until they heat up." This is confirmation that you aren't losing anything — you just aren't looking at what doesn't need a human eye.

This is the first major difference from CRM: the queue isn't everything that exists; it’s only what needs you now. The rest is taken care of and visible elsewhere.

5. The live dashboard: health, bottleneck, capacity, and forecast

The second screen of the Órbita is the dashboard — designed for leadership, not individual execution. It answers four questions that CRMs answer poorly or not at all:

1. What is the IAm (Índice de Amnésia Operacional)? — % of cycles stuck or reopened without memory. The higher it is, the more margin is being burned due to lack of context.
2. Where is the operation stuck? — distribution of cycles by decision state, with the median days stalled. The state with the highest median is the bottleneck of the week.
3. Can the team's capacity handle it? — load vs. capacity per person, with overload alerts.
4. How much will we close in the next 30 days? — the sum of the pT (probability of closing in 30 days) of each acquisition cycle, divided by arquétipo.

The dashboard recalculates with every movement. This isn't an end-of-the-month report — it’s a piloting instrument. When the bottleneck shifts from "Comparison" to "Experience," the leader changes the team's direction that same day, not at the next meeting.

6. The predictive: simulate before promising

The third screen is where MCI becomes a business decision tool, not just an operational one. The Predictive feature takes what the Órbita already knows about the real arquétipos in your base and lets you simulate scenarios:

"I want to sell 40 units, with an average ticket of $4,500, an acquisition cost of $600, and an average journey of 21 days. Do I have the people for this? Which arquétipo should I invest in?"

You fill in four variables — desired sales, journey time, acquisition cost, and average ticket — and the system simulates 9 combined scenarios using the real distribution of arquétipos in your base. The answer isn't an average: it's where the money is actually available.

This changes the conversation with the board of directors. Instead of "I'll try to hit the goal," the manager enters the meeting with: "To hit 40, I need to double the Estudioso pipeline or accept a 22% higher CAC in Explorador. Which do you prefer?"

No CRM does this. Not because it’s hard — but because a CRM doesn't know arquétipos, only stages.

7. Arquétipos: replacing "lead qualification"

In CRM, qualification turns into BANT, MEDDIC, or a free-text field that the salesperson fills out in a rush. In the Órbita, every cycle has a conversational arquétipo — a stable pattern of how that person makes decisions:

• Estudioso — seeks evidence, converts with trust, not pressure.
• Explorador — active curiosity, still immature criteria.
• Fiel — already trusts you; the risk is taking them for granted.
• Decidido — high intent, short window; the risk is friction.
• Turista — high volume, low intent; the mistake is wasting a salesperson on them.

The arquétipo doesn't come from the salesperson's hunch. It comes from observed behavior in conversations — questions asked, response time, depth of criteria, objection patterns. This is what MCI calls the Conversation Score.

Practical result: the team stops treating a Turista like an Estudioso (wasting time) and stops treating a Decidido like an Explorador (burning urgency).

8. Decision states: the missing axis in CRM

Parallel to the arquétipo, each cycle has a decision state:

1. Exploration — discovering if the problem exists.
2. Comparison — choosing between options.
3. Purchase — closing terms.
4. Experience — the first 30/60/90 days of use.
5. Reopening — returned after a silence (with or without memory).

The state is dynamic: the customer moves up, down, and reopens all the time. CRM pretends this is an exception. The Órbita assumes this is the rule — and orders the conversation accordingly.

The arquétipo × state combination is the true "qualification" of the opportunity. A Decidido in Purchase requires a different move than an Estudioso in Exploration, even if both are in the same funnel "stage."

9. Amnésia Operacional: the metric nobody measured

The metric that most surprises those who enter the Órbita for the first time is the IAM — Índice de Amnésia Operacional. It measures the fraction of cycles stuck or reopened without memory of what was discussed before.

In operations without MCI, this number usually sits between 30% and 55%. In other words: one out of every two customers is being served as if it were the first time — repeating questions, redoing briefings, losing the trust that had already been built.

Every point of IAM has a direct cost: in the Órbita, the dashboard shows estimated additional CAC per point of amnesia. When leadership sees that 600 dollars more in CAC comes from amnesia, the conversation changes. It’s not "let's buy another tool" — it’s "let's fix the context."

10. What changes in the team's routine

The Órbita does not replace the CRM in cold data recording (registration, invoices, contracts) — it replaces the CRM in living operation: prioritization, conversation, decision, and forecasting.

11. How to start (without tearing down what exists)

The MCI Órbita does not require a big-bang migration. The healthiest path:

1. Connect a conversation source (WhatsApp Business, business email, website chat) and let MCI listen for 30 days.
2. Let the system discover the arquétipos in your base — they emerge from real behavior, not a workshop.
3. Deploy the Órbita only to a pilot team (3 to 5 people) for 2 business cycles.
4. Compare the IAM before and after — it’s the most honest metric to show the board.
5. Expand when the pilot proves itself.

The CRM continues to run as a system of record. The Órbita takes over the living operation. In 60 to 90 days, the team stops opening the CRM daily — not because it's forbidden, but because the Órbita answers the questions that matter faster.

In one sentence

The MCI Órbita is what happens when you stop organizing opportunities by where they are and start organizing them by how they behave, what they feel, and what they are worth in the next 30 days — with living memory, real priority, and forecasting by arquétipo.

It’s not a better CRM. It’s the next layer — the one the CRM never managed to be.