Hidden business rules
Nobody knows where the business rules actually live. They're buried in code, in email threads, in the senior developer's head.
Founded 2016 · CDMX / 10 years
Ten years building what we promise.
We started in 2016 as Ali-Digital Solutions. Today we are rocket code: 190+ rocketeers in CDMX, Madrid, and San Francisco, 200+ platforms in production, 100+ clients in financial services.
01 · The numbers
A decade in financial services.
We didn't invent these. They're the projects, the people, and the offices that support rocket code today.
10
years of experience
+200
platforms in production
+190
rocketeers on the team
+100
active clients
4
offices · MX, US, ES
02 · Our timeline
From 2016 to 2026. A single route.
Nine milestones, from the first client to three countries. Walk it with the arrows, the keyboard, or by dragging.
Milestone 01 / 09
-
2016
The journey began!
Our first client, in Mexico City.
-
2017
We built Mexico's leading insurance platform 🇲🇽
And created Ali-Digital Solutions.
-
2018
We developed Mexico's leading credit origination platforms
-
2019
50+ success stories
Across Fintech and Insurtech.
-
2020
We helped our clients survive the pandemic
-
2021
We evolved into rocket code
New brand, same team.
-
2022–24
Clients across the US and LATAM 🇺🇸
190+ rocketeers, 100+ clients, and expansion to Spain 🇪🇸.
-
2025
10X plan
Multiplying our delivery capacity tenfold with AI.
-
2026
10 years
A decade transforming the financial sector. The next one, we write together.
03 · How we build
Domain-Driven Design isn't a technical trend. It's how we keep software from lying.
Most tech projects start with code. The business domain stays implicit, scattered, and interpreted differently by every team, and that costs a lot down the line.
The problem everyone has
Fragmented language
The business says "Approved Claim." Dev calls it validatedCase. QA tests it as claim_ok. Three versions of the same thing.
Unchecked states
An order can be "approved" and "cancelled" at the same time. Invalid states go undetected until it's too late.
Constant rework
The model shifts every sprint because it was never formalized. Every change breaks something else. The debt keeps growing.
What is Domain-Driven Design?
The business model is the core of the system. The system's architecture, code, and language are built to reflect how the business works, not to optimize the database or the tech stack. Not the other way around.
1
For engineering
The code directly mirrors business concepts. If the business has a "Claim," the system has a Claim object with its own states, rules, and invariants.
2
For the whole team
Everyone speaks the same language. Analysts, developers, QA, and stakeholders use the same terms: which kills ambiguity and rework.
3
For the business
Its rules, exceptions, and processes get formalized and protected by design, not buried in documents nobody reads, but built into the system itself.
Two levels that work together
Strategic level
How is the business organized inside the system?
1
Subdomains
The business splits into parts: the Core Domain, what sets you apart; Supporting Domains, what backs it up; and Generic Domains, what can be outsourced. This keeps you from over-engineering what doesn't matter.
2
Bounded Context
Each part of the system has its own model, language, and rules. What "Status" means in Claims can differ from what it means in Billing, and that's fine.
3
Ubiquitous Language
The business's language is the system's language, no translation layer. If the business says "Suspended Policy," the code says PolicySuspended: across every team.
Tactical level
How is the logic modeled internally?
1
Entities & Aggregates
Business objects carry identity , Claim #1234 is always the same claim, and group into Aggregates that protect their own internal consistency. Only the Aggregate Root can be modified from the outside.
2
Invariants
Rules that can never break: a cancelled loan can't go back to "approved." A closed claim doesn't accept payments. These rules live in the domain, not in the frontend, not in scattered validations.
3
Domain Events
When something happens in the business, the system logs it as a semantic event: ClaimApproved, PaymentExecuted, PolicySuspended. That gives you traceability and a decoupled architecture.
How the market does it vs. how rocket code does it
How the market does it
A technical pattern, without the process behind it
In the market, DDD gets adopted as a technical pattern, fancy folder names and talk of "bounded contexts", without the process behind it.
- ✕ Requirements written once, then forgotten
- ✕ Database designed first, letting the technical model dictate the business
- ✕ Code written with implicit rules
- ✕ Bugs and rework because invalid states surface too late
- ✕ Ad-hoc patches on top of a broken foundation
How rocket code does it
The process starts before the code
The domain gets discovered, formalized, and signed off, and only then do we build.
- ✓ Domain discovery: rules, states, and events extracted
- ✓ Formalized model: state diagrams and bounded contexts
- ✓ Sign-off and freeze: the model locks before development starts
- ✓ Shielded development: code guided by the domain
- ✓ Automatic governance: continuous audit and monitoring
Certified partners
AWS
Advanced Consulting Partner
Google Cloud
Certified Partner
Salesforce
Certified Partner · CRM
Odoo
Certified Partner · ERP
OpenAI
Partnership in process
Anthropic
Partnership in process
How we build · domain before code live
04 · Offices
Four offices. Three continents.
Mexico as main operational HQ, Madrid for Europe and digital marketing, San Francisco for innovation.
🇲🇽
Mexico City
Mexico
Plaza Artz · Anillo Periférico 3720, Jardines del Pedregal, Álvaro Obregón, 01900
🇪🇸
Madrid
Spain
WeWork · Calle de Goya, 36, Salamanca, 28001 Madrid
🇺🇸
San Francisco
United States
Salesforce Tower · 415 Mission Street, San Francisco, CA 94105
05 · Team
Meet the team.
190+ rocketeers. Here are the ones you'll most likely meet in a first conversation.
IH
Ivan Hernández
Chief Executive Officer
LM
Luis Bernardo Macías
CEO Global
DB
Daniel Benitez
Chief Operations Officer
BM
Brice Macías
Chief Technology Officer
MP
Maricela Palma
Sales Director
RP
Rafael de Pina
Sales Director
MV
Montserrat Vergara
Head of Presales
MM
Marco Mendoza
Head of Tech
AL
Alan Lozano
Head of Tech
AS
Azucena Soto
Delivery Manager
AM
Adriana Morales
Human Factor Manager
06 · Values · without empty words
Four rules that actually matter.
We don't decorate walls with the word "excellence". These are the decisions we make, and refuse to make, every day.
We deliver, we don't promise
Every project has a concrete deliverable every two weeks. We don't take on projects where success is subjective.
The code is yours
No lock-in. The client always has repo access and can switch providers without a technical transition cost.
Honesty before sales
If an existing orbit product solves your problem better than a custom build, we'll tell you. If your problem doesn't fit us, we refer you out.
Sector depth
We specialize in insurance, fintech, and banking. A decade of projects gives us context before writing a single line of code.
Contact
Want to meet the team before deciding?
Book a 30-minute call. No sales agenda. Just the technical team with you.