Skip to content

How we work

Four ways to work. One way of being accountable.

Choose how you want to move forward; in all of them an architect with twenty years in systems that cannot fail answers for the work, and in all of them what is built is yours.

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

The four ways

  • Project with a defined scope.

    A defined outcome, in stages and with acceptance at each one. For when you know what you want to achieve and need someone to answer for the result.
  • Managed team.

    A full team —lead, engineers and testing— that delivers end to end. For a product or an ongoing line of work.
  • Nearshore engineering.

    Senior engineers who embed in your team, on your schedule.
    Nearshore page
  • Ongoing partnership.

    Operation, support and improvement after release, with a service-level agreement.

Two ways to deliver. You choose with us which one suits you.

Not every project is governed the same way. When the scope can be fixed and a committee has to sign it, it makes sense to move in stages, each with its deliverable. When the product is discovered as it is built, it makes sense to move in short cycles and reprioritize. In the first conversation, at no cost, we recommend one; they can also be combined.

In stages (V-model)

For scopes that can be fixed, regulated systems, integrations with a core system or an ERP, and projects that your committee approves in phases.

Before anything is built, you already know what will be delivered, in what order and the criteria you will use to accept it; if something changes, you review and approve the impact on scope, schedule or cost before it is carried out.

Six stages, one after the other, each with a deliverable that you review. What makes it a V-model: each test is defined in the stage that gives rise to it —acceptance criteria from Origin, the quality matrix and the integration tests from Design— and is run later: unit and integration tests during Construction, and the quality matrix and acceptance in Testing, before release.

The V refers to the shape of the diagram, not a number: each stage on the way down defines the test that will verify it on the way up.
  1. Origin

    We understand the business need and turn it into a story with its goal, its limits and who decides.

    Deliverable: the requirement story, validated by the person you designate to decide.

  2. Analysis

    We measure what exists today: processes, systems, data and rules, including those that only one person knows.

    Deliverable: the analysis, with the risks and dependencies in view.

  3. Design

    We model the business before the technology —the pieces of the system carry the names and boundaries of your business, not those of the database; this is called domain-driven design (DDD)—, and from that come the architecture, the rule matrices and the test cases, each with its expected result.

    Deliverable: the design and the test matrix: from this point you know the criteria you will use to accept it.

  4. Construction

    We build against that matrix. Each piece arrives with its unit tests and, when it connects to another system, with tests of that connection that can be run again and that your team can run whenever it wants, without depending on us (automated collections, such as Postman's).

    Deliverable: the code in your repository, with its tests, and the collections so your team can run them whenever it wants.

  5. Testing

    A quality review independent of whoever built it runs the full matrix (QA); then your people validate in your own environment (user acceptance testing, UAT).

    Deliverable: the test report with its evidence and the acceptance record.

  6. Release

    We put it into operation with an agreed rollback plan and support during the first few days.

    Deliverable: the user and operations manual, and the rollback plan in case something does not behave as tested.

Agile (Scrum)

For digital products, new channels and projects where the scope is discovered along the way.

Every two or three weeks you review with us progress that works —a finished, tested Increment— and decide what comes next based on what you have already seen, not on what you imagined.

  • Sprint Planning: the goal of the cycle is agreed, along with which items from the Product Backlog can be finished within it.

  • Daily Scrum: fifteen minutes for the team to review progress toward that goal and adjust the plan; you do not need to attend.

  • Sprint Review: a working session with what was built, working, not a presentation; what is learned is used to adjust the Product Backlog.

  • Sprint Retrospective: the team adjusts how it works for the next cycle.

  • In addition, the Product Backlog: visible to you at all times; its order is decided by the Product Owner, a single person with the authority to prioritize whom we agree on with you from the start.

Agile does not mean no control: each story enters with acceptance criteria and leaves with its tests, just as in the staged approach.

What if your project has both? It happens often in large projects: the regulated core system is run in stages and the channels in sprints, with a single person responsible on our side.

Waterfall or Scrum: how to choose the way to run your project

You see the project live, not in a report at the end.

Agility does not depend on the method alone: it depends on how long a question takes to reach the person who resolves it. That is why we work in spaces shared with your team from day one, so a question does not take a week to become a decision.

Direct conversation

A channel shared with your team —Slack, Microsoft Teams or the one you already use— where the people who build are, not an intermediary. Questions are handled there, within a response time we agree on at the start, without waiting for the weekly meeting.

Project board

Every task, its owner, its status and its date in a workspace you have access to —ClickUp, Jira or your own—. You check progress whenever you want, without asking for a report.

Everything is written down

Decisions, agreements and scope changes are recorded in the same space, with the date and who approved them.

In your tools or in ours

If your company already has its tools, we work in them with the accounts you assign us. If it does not, we open a workspace dedicated to your project, and when we finish we hand it over to you with its full history.

Controlled access

Each person signs in with their corporate account and with the permissions you define; when we finish, the access is removed.

Contract with us in Mexico or the United States

Any of our services and any of the four ways can be contracted in Mexico, in pesos, or in the United States through HABIL, LLC, in U.S. dollars and under U.S. law. The work is the same and is performed in Mexico; you choose which company you sign with.

How any of the four begins

With a first conversation, at no cost, and an entry deliverable: a concrete map of your case, with scope, who takes part on your side, what evidence is reviewed and what decision it lets you make.

For your purchasing committee

For Finance:

each stage with scope, acceptance criteria and cost agreed; if the scope changes, we present the impact and approve it with you before executing; the code and the documentation are yours, and at close we transfer the knowledge so you do not depend on us.

For Security:

we work in your repositories and with your access, using each person's corporate account; secure development with automatic review on every change; minimal data and a trail of who did what.

For Compliance:

every delivery leaves its evidence: tests, reviews, approvals and changes.

For Technology:

we respect your standards and your tools; if you have none, we leave you ours, documented.

For Management:

a single person responsible on our side, who answers for the result, with periodic follow-up, clear escalation and risks in view.

At the end:

an orderly exit; you keep everything and can continue with your team or with whoever you choose.

Which one suits you?

Tell us what you need to achieve and in the first conversation, at no cost, we recommend the engagement model and the delivery approach.

Let's talk about your case

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