Yes. It stays in your repository and in your name, with its documentation, and the contract spells out ownership, third-party components and their licenses. You decide who maintains it.

Fixed price or in stages?

If the scope is clear, a fixed price with acceptance criteria. If it is still being defined, in short stages that you approve one by one. We go over it in the first conversation.

What if I already have a custom system that no one wants to touch?

We start by reviewing and documenting it. Then we decide with you whether it makes sense to fix it, replace it in stages or move that part to one of our products.

Does it connect to my ERP or my core system?

Yes, through the interfaces the vendor itself supports, so as not to leave you with custom code inside your ERP that gets in the way when you upgrade it. Which interfaces and permissions are needed, and who provides them on your side, is written into the scope.

Who operates it afterwards?

Your team, with the documentation and the handover; or us, if you so agree with us.

What about security, personal data and traceability?

They are defined as part of the scope: who has access to what, what gets recorded, how personal data is protected and which decisions a person approves.

Custom systems · Critical processes

When no product fits, we build the system your operation needs.

Portals, approval workflows, quoting tools, apps and the internal operation that today lives in spreadsheets and email. We build it, connect it to your ERP, your core systems and your channels, and deliver it to you working, with the code and the documentation in your repository, in your name.

Before we write a single line, we review with you whether something already exists that solves it. Building is the answer only when it makes sense.

Let's talk about your case

Prefer email? Write to us at hola@habil.mx

Trusted by organizations where continuity and security are non-negotiable

BanCoppel
Zurich
Allianz
GNP Seguros
MetLife
Costco
Seguros Multiva
Aserta
Bx+
Veolia
Truper
Argos

When the system does not look like your operation

Your company does something in a way that no package offers out of the box: how it quotes, how it authorizes, how it serves its agents or how it reconciles what it sells against what it collects. Meanwhile, the work is held up by a spreadsheet that only one person understands, a chain of emails and someone who moves data from one system to another by hand.

That works until that person leaves, the volume doubles or an auditor asks who approved what and when. Then what used to cost little starts to cost you in errors, in time and in customers who are kept waiting.

Symptoms your operation already recognizes

«That part of the operation lives in an Excel file that only one person understands.»
Executive managementthe business depends on someone's memory.
«Approvals go by email and no one knows which step the request got stuck on.»
Operationswork held up without anyone seeing it.
«We bought a system, but we still handle half of the operation outside it.»
Financeyou pay for a license and for the manual work as well.
«Every change to the system that was built for us is a project, and the person who programmed it is gone.»
Technologya system that no one dares to touch.
«Our agents or customers ask us for a portal and we send them PDFs over WhatsApp.»
Salesthe competition responds faster.

The solution first, then the code

We do not start with how many programmers you need or which technology to use. We start with another question: what has to stop happening in your operation? Sometimes the answer is to configure what you already have. Sometimes it is one of our products. And when building is truly needed, we build.

If what you have already solves it.

We tell you so, and we help you configure it or connect it, without selling a project you do not need. It fits when the problem is one of use or of connection, not of capability.

If a product covers part of it.

Retícula, Pauta and Cuadre bring together what repeats from one company to another across several sectors. The part they cover is configured instead of programmed. It fits when your process resembles that of many companies.

If building is truly needed.

We build it to measure, connected to your systems and with everything your team needs to maintain it. It fits when that process is exactly what sets your company apart, or what is holding it back today.

What we build

What we build depends on your problem, not on a catalog. These are the most frequent cases.

For your customers, agents and suppliers
- Self-service portals.
  Where your customer, your agent or your supplier looks things up, makes requests and downloads documents without calling anyone: account statements, policies, orders, invoices.
- Quoting tools, simulators and policy issuing.
  They calculate with your rules and your rates, on the web, on a phone or without a connection on a salesperson's device.
- Connected apps and sites.
  For the web, iPhone and Android, talking to the systems your company already uses.
  Digital channels
For your internal operation
- Approval workflows.
  Who requests, who reviews, who authorizes and in what order, with the record of every decision in plain view.
- Internal operations systems.
  What today lives in spreadsheets and email, moved into a system with permissions, history and reports.
- Reconciliations.
  What was sold against what was collected, what was invoiced against what was deposited, what one system says against what the other says.
- Customer onboarding and validation.
  Document capture, identity verification and two-factor authentication, integrated into your onboarding process.
For what you already have
- Connection to your ERP, your core systems and your channels.
  Your ERP —SAP, Oracle, Microsoft Dynamics 365, Odoo, CONTPAQi or another—, the central system of your bank or insurer and your sales channels, exchanging data so that you stop entering the same thing twice.
- Rescue of an existing custom system.
  We review it, document it and leave it in a condition to change, backed by tests, or we plan its replacement in stages.
- Artificial intelligence inside your system.
  To read documents, answer inquiries or prepare actions. The decisions and authorizations your process requires stay in the hands of the responsible people.
  Hábil AI

We start from the systems and processes that work for you today. Replacing something is considered only when it is no longer worth keeping.

How we build it

We understand the problem.

We look at how it is done today, who does it, where time or money is lost and what would have to happen for it to count as solved.

We agree on the scope.

What is built first, what is left for later, how each part is accepted and how much it costs, before we start.

We deliver in stages.

You see each part working, in a testing environment, before we move on to the next. What does not work is corrected early, not at the end.

We hand the system over to you.

Up and running, with its code, its tests and its documentation, and the handover to whoever will operate it.

It can be a project with a defined scope or a team that builds with you in stages. We decide it together, depending on how clear the scope is.

What is yours when we finish

The system, up and running.

Tested against the agreed acceptance criteria and connected to your systems.

The code, in your name.

In your repository, not in ours. If tomorrow you want another team to maintain it, it can.

The automated tests.

So that every future change is checked before it is released.

The documentation.

What it does, how it is built, how it is installed and what to do if something fails.

The handover to your team.

Sessions and materials for whoever will operate it. If you later prefer that we operate it, we agree on that separately.

Why so many custom systems end up needing a rescue

Programming a system is the easy part. The hard part is keeping control over it when the operation, the volume, the regulation or the systems it connects to change. That requires:

Understanding the operation before the screen.

A system that copies the Excel file as is copies its errors too.

Connecting without breaking what already works.

Your ERP and your core systems have rules, schedules and limits. They have to be respected, not worked around.

Being able to test every change.

Without automated tests, every adjustment is a gamble, and the system freezes out of fear.

Not depending on one person.

Neither the one who programmed it nor the one who uses it: documented and in your name.

Knowing when not to build.

What a product already does well does not need to be programmed again.

That is why success is agreed from the start, with signals you can observe: approvals with a record, less re-entry of data, the process in plain view, faster responses.

We have built it before

In two decades we have built custom systems for banking, insurance, manufacturing and retail in Mexico. Some examples:

The workflow with which a tool manufacturer authorizes the designs of its products, step by step and with the record of each approval.
Online quoting and issuing tools for auto, life, medical expense and property insurance, for the agent network and the bank channel of insurers, including quoting tools that the salesperson uses without a connection.
Savings simulators for retirement, education and investment, and the portal where the policyholder checks the status of their funds.
The identity validation of a bank in Mexico, including the INE lookup.
The interfaces that connected an insurer's central system to its new ERP.

See the case studies

What repeats becomes a product

Retícula, Pauta and Cuadre bring together what we see repeating from one company to another. For you it means something concrete: if part of what you need is already in one of them, that part is configured, not programmed, and the custom project concentrates on what is truly yours alone.

An insurer or lender that needs to launch products and change rates without an IT project?

Pauta

The complete operation, from offer to collection?

Retícula

Invoicing and reconciliation with the SAT?

Cuadre

How to get started

First conversation, at no cost
Project with an agreed scope and deliverable

Frequently asked questions

Is the code mine?: Yes. It stays in your repository and in your name, with its documentation, and the contract spells out ownership, third-party components and their licenses. You decide who maintains it.
Fixed price or in stages?: If the scope is clear, a fixed price with acceptance criteria. If it is still being defined, in short stages that you approve one by one. We go over it in the first conversation.
What if I already have a custom system that no one wants to touch?: We start by reviewing and documenting it. Then we decide with you whether it makes sense to fix it, replace it in stages or move that part to one of our products.
Does it connect to my ERP or my core system?: Yes, through the interfaces the vendor itself supports, so as not to leave you with custom code inside your ERP that gets in the way when you upgrade it. Which interfaces and permissions are needed, and who provides them on your side, is written into the scope.
Who operates it afterwards?: Your team, with the documentation and the handover; or us, if you so agree with us.
What about security, personal data and traceability?: They are defined as part of the scope: who has access to what, what gets recorded, how personal data is protected and which decisions a person approves.

Start with the problem

Tell us which part of your operation is costing you more than it should. In the first conversation, at no cost, we review whether it makes sense to configure, to use a product or to build, and what you would receive in each case.

Let's talk about your case

Prefer email? Write to us at hola@habil.mx

When no product fits, we build the system your operation needs.

When the system does not look like your operation

Symptoms your operation already recognizes

«That part of the operation lives in an Excel file that only one person understands.»

«Approvals go by email and no one knows which step the request got stuck on.»

«We bought a system, but we still handle half of the operation outside it.»

«Every change to the system that was built for us is a project, and the person who programmed it is gone.»

«Our agents or customers ask us for a portal and we send them PDFs over WhatsApp.»

The solution first, then the code

If what you have already solves it.

If a product covers part of it.

If building is truly needed.

What we build

For your customers, agents and suppliers · 3

For your customers, agents and suppliers

Self-service portals.

Quoting tools, simulators and policy issuing.

Connected apps and sites.

For your internal operation · 4

For your internal operation

Approval workflows.

Internal operations systems.

Reconciliations.

Customer onboarding and validation.

For what you already have · 3

For what you already have

Connection to your ERP, your core systems and your channels.

Rescue of an existing custom system.

Artificial intelligence inside your system.