How we shipped the Bineo neobank app for Banorte

What Bineo built with Greelow

Banorte, one of Mexico's largest financial groups, chose to stand up its fully digital bank as a separate product from its incumbent brand. That product is Bineo. Greelow's squad designed, built, and delivered Bineo's mobile application to Banorte, together with the design system that underpins it.

The delivered application covers a full retail-banking customer lifecycle in one iOS and Android build:

• Account opening with national ID capture, biometric verification, and native anti-fraud validation.
• Debit and credit cards, physical and digital, with the full in-app lifecycle.
• Goal-based savings, personal loans, and money movement across transfers, payments, and ATM operations.
• Transactional notifications, in-app support, and continuous product feedback.

The challenge

A digital bank born inside a traditional banking group carries three problems at once. It has to feel distinctive enough that a digital customer recognizes it as a new product. It has to meet the same regulatory bar as the parent bank, without shortcuts. And it has to deliver product velocity without inheriting the legacy core banking release cadence.

Bineo walked into that box with an extra constraint: the mobile app is not a secondary channel, it is the channel. No branch, no relationship manager, no fallback to the parent bank's internet banking for critical operations. If the app does not cover an operation cleanly, that operation does not exist for the customer.

Two requirements shaped the rest of the design. Onboarding had to be the product, because activation defines the business of a digital bank. And the visual language had to be an asset, not a byproduct, because a design system replicated by hand across screens becomes debt that grows faster than the product.

The solution

A full retail banking app in one place

The application covers the customer lifecycle end to end: authentication, onboarding, cards, savings, loans, money movement, notifications, and support. There are no dead ends where the customer has to leave the app to complete an operation.

The compliance and anti-fraud posture is part of the same path that carries every request, not a separate module bolted on after the fact. Every operation leaves an auditable trail the bank's risk team can reconstruct.

The design system as its own product

Bineo's design system is a product of its own, with its own evolution cycle. The app consumes it as a versioned dependency.

That decision has concrete consequences. The team evolving the visual system does not compete with product-feature work for space in the same product. A brand refresh, a palette change, or a typography migration happens in one place and reaches the app through a dependency bump.

A digital bank that wants to hold one visual language for years cannot hand-build it in every screen. Bineo does not.

Discipline that scales with the team

A large squad on a critical product breaks quickly if delivery discipline is left to memory. Bineo's is not.

The environments used to prototype, the environments used to validate, and the environments that carry sensitive credentials are strictly separated. Parallel work by many engineers converges without collision because the rules that keep it safe live in the shape of the application, not in a wiki.

That discipline is what sustained a high cadence of change over quarters without the app turning into a knot.

The outcome

Greelow delivered a full retail-banking application to Banorte. Cards, savings, personal loans, and money movement live in one surface. Compliance and anti-fraud posture live on the same path as authentication, not next to it. The design system evolves on its own cycle and holds the bank's visual language without per-screen rework.

A digital bank that wants to last needs scope, a durable visual language, and a delivery discipline that scales. The code that resolves those three for Banorte was built, tested, and delivered by Greelow.