Software built around your operation, not around a catalogue. Senior in-house team, zero offshoring, and an engineer who stands behind what they sign.
Resumen · datos clave
Custom software doesn't compete with off-the-shelf on price: it competes on fit. An ERP or a vertical SaaS covers 80 % of what your company does and forces you to change the remaining 20 %, which is usually exactly what sets you apart. Building custom makes sense when that 20 % is the business, when integrating with what you already run costs more than building, or when the process you want to automate doesn't exist as a product yet.
We work with technology and operations leaders who arrive with a concrete process —a claims assessment flow, a charging network, a multi-country catalogue— and need it running in production, not a proof of concept. We start by scoping which part deserves custom software and which is solved by buying: that conversation saves more money than any later optimisation.
The team is in-house and senior. No subcontracting, no offshoring: the engineer who designs the architecture is the one who deploys it and the one who answers when something breaks at three in the morning. That is why the floor is €30,000 and not less.
Qué incluye
¿Encaja con lo que necesitas?
30 minutos. Sin pitch comercial. La conversación es contigo y con quien va a construirlo. Respuesta en menos de 1 hora.
Respaldo
+300
proyectos
15+
años
Flutter
partner oficial
Por qué elegirnos
Zero subcontracting and zero offshoring. Whoever signs the proposal writes the code. That is what makes the technical conversation direct from the first meeting.
Saber más →Part of the job is scoping downwards. If an off-the-shelf product covers your case, adapting it is cheaper than building it, and we say so before signing.
Saber más →PostgreSQL before exotic stores, modular monolith before microservices. Complexity gets added when the pain justifies it, not when the trend asks for it.
Saber más →Preguntas frecuentes
It means building a specific application for a company instead of adapting an existing product. You start from the real process —how that organisation works, with which systems and under which constraints— and design the software around it. It makes sense when what differentiates the company is exactly the part no off-the-shelf product covers, or when the process you want to automate doesn't exist as a commercial product yet.
The market splits between large integrators aimed at corporate projects with big headcounts, mid-sized software factories working by volume, and boutique consultancies with a senior in-house team, which is where we sit. The practical difference is not the hourly rate but who writes the code. Dribba has operated from Barcelona and Andorra since 2011, with more than 300 projects delivered.
Our projects start at €30,000. The real range depends on three things: functional scope, how many external systems need integrating, and which compliance regime applies. A tightly scoped internal tool sits near the floor; a platform with several integrations and a mobile app goes considerably higher.
Functional scoping takes one or two weeks and is where almost everything is decided. From there, a first version in production lands between eight and sixteen weeks depending on scope and integrations. We work in increments: having the working part in production beats waiting months for a single launch.
Yes. The repository, the documentation and the infrastructure are handed over in your company's name, and the signing keys and deployment accounts sit under your control from the start, not ours. Whoever controls the certificate controls whether the app can be updated, and that belongs to whoever pays for the project.
¿Listo para empezar?
Backend y arquitectura