The people behind.

One by one.

• 01

  Maresa Abigail Romero

  First conversation

  The person you talk to before a proposal exists: listens to the problem, learns the context, and puts into words what is actually needed.

  I am Maresa Romero. I study International Trade and come from working in sales, marketing, and project development — which is where you learn to listen to what someone needs before proposing anything, and to negotiate without losing sight of what has to happen for both sides to win.

  At Belica I am the first conversation. I spot where there is an opportunity, learn the context of the business, and turn a need into a concrete proposal with a scope that can actually be delivered. I think like a founder, and that comes down to one thing: the project has to end in growth, not in one more meeting.

• 02

  Braian Leandro Marquez

  Architecture and code

  Decides what it is built with and how it stays up: architecture, infrastructure, and the code someone else will read.

  I am Braian Marquez, co-founder and technical lead at Belica. I have been building software for more than four years, focused on payment systems and banking integrations — a field where precision is not a preference but a requirement.

  At Belica I turn a business problem into an architecture that solves it and holds up over time: I design the backend, define the infrastructure, and see every project through to production.

• 03

  Bruno Ignacio Bordón

  Scope and delivery

  Owns the client relationship and defines scope before a line is written. If something cannot be kept running after handover, it does not come in.

  I am Bruno Bordón, co-founder of Belica. I build software and spend every day in the systems team of a company: support, maintenance, and process optimization — which is where you learn how a business actually works from the inside.

  At Belica I look for where technology adds value and turn a concrete need into something simple, efficient, and able to scale: development, infrastructure, automation, and process analysis. More than building software, understanding the problem and building the right solution for it.

The speed of AI. The judgement of a person who reviews.

Most of the problems that reach us are not technology problems. They are processes that depend on one person, information spread across five systems, tasks still done by hand. Technology is the tool. The work is understanding what is going on and building the exact piece that changes it.

• AI where it helps

  We use it to prototype, write tests, document and migrate: that is where it saves days. Architecture and review are not delegated, and every line goes through a person.

• Short deliveries

  Something running from the first week, then one delivery after another. You see the progress, not a progress report.

• The project stays yours

  Repository, infrastructure and documentation in your name from day one. If tomorrow you carry on with another team, you carry on without asking us.

• Built to be maintained

  We write the code for whoever comes next to understand. Cheap to build and expensive to keep is no good to us, and no good to you.

• Leading-edge standards

  Continuous integration, automated tests, code review and monitoring from the first commit. The same practices as the product teams setting the pace.