Language es en

Let’s talk

Service

What does not exist, we build.

Data platforms, models, agents, integrations and web applications, integrated with the systems you already have.

The code is in your repository from day one.

We have spent years putting AI into production for companies that cannot afford for it to fail.

AWS technology partner

AWS Partner AWS Qualified Software AWS Retail Competency
Condis
Fiorucci
Perfumeries Júlia
Flormar
Real Sociedad
Atelier
Norauto
Nescafé
Teleadhesivo

What we build

Each piece solves something you do not have today.

Data platforms

Bringing together what sits in several systems so it can be queried.

ETL and unification

Extracting what each system produces, cleaning it and keeping a single version.

Models

Predicting with your data, not with an industry average.

Agents and MCP servers

The agent carries out a whole task and the MCP gives it access to your systems, with your permissions.

Integrations

So that what is new goes into the systems you already use.

Web applications

When the task needs its own screen and there is none.

How we work

In phases, and each one leaves a feature in use.

Each phase starts with the next thing that is needed and ends with it working. You see what is there and decide whether it continues, changes or stops, and only then does the next one begin.

PHASE PHASE PHASE PHASE PHASE NEW FEATURE IN USE WHAT WAS ALREADY WORKING YOUR DECISION

Someone from your company takes part in the team, documentation is written while it is built and you always talk to the people building it. The code lives where you decide, with the exit terms written from the start.

What stays

Software of your own, not a dependency.

Repository

How it arrivesWith its full history from the first commit.

Who uses itYour team, whenever it wants and without asking permission.

Documentation

How it arrivesWritten while it was built, not afterwards.

Who uses itWhoever maintains it, whether us or not.

Maintenance

How it arrivesYours if you want it, ours if you prefer.

Who uses itWhoever you decide. The choice is yours.

Knowledge

How it arrivesIn writing: what each piece does and why it was decided that way.

Who uses itWhoever picks it up later, whether they know the project or not.

Shall we tell you how we would build it?

Tell us what you need to exist and we will tell you how we would approach it and what would need deciding before starting.

Subject: Custom development — what we need does not exist

No commitment You talk to the person who will do the work If it does not fit, we tell you

Frequently asked questions

What people ask before building.

Is the code ours?

Yes, and it is in your repository from the first commit. There is no final delivery where anything gets handed over.

Can we maintain it ourselves afterwards?

That is the goal. That is why someone from your team takes part while it is built and why the documentation is written at the same time.

Do you work with our development team?

Yes, and it is the best way. What we do not do is replace it: if what you need is plain development capacity, we are not the right option.

What if halfway through we see we do not need to build that much?

We cut it back. The phases exist so you can stop, and a decision like that is better taken early.