Custom software, built from scratch and built to work

What we build

Everything that usually falls under "from scratch": the whole product, or the tool your business is missing.

• Complete MVPs and SaaS, from idea to production
• Custom ERPs for specific sectors: real estate, insurance brokers, distribution…
• CRMs adapted to your actual sales process
• Online stores and marketplaces
• Automations that remove manual work between your tools
• Booking, appointment and customer-area portals
• Dashboards with the numbers you actually look at

Built to work first time

A well-planned project built from scratch doesn't get rebuilt. That's why every development starts with architectural judgement - stack, structure, scalability - decided by a CTO, and ends with real QA: what we deliver works in production, not just in the demo.

And what do you get in the first delivery, two weeks after starting? Something real: the architecture decided and documented, the environments deployed and a first screen working. Not much yet, but real, not a document of intentions. From there, every delivery adds up.

We deliver with a 6-month warranty, full documentation, mentoring for your team and a conversational assistant built on all your development's documentation. If tomorrow you want to carry on with your own team, you can.

Signs you need custom software

Not everyone needs custom software, and telling you so is part of our job: if your case is an online store with a standard catalogue, your answer is probably WooCommerce, not us (in Spanish). But there are clear signs the moment has come:

• You run the business on spreadsheets nobody understands or dares to touch
• You pay for several generic tools and none fits your actual process
• Your team loses hours copying data from one system to another
• You have a product idea and no technical partner to build it
• Your sector's software is old, expensive, or forces you to work its way

Technology: Azure and the Microsoft ecosystem

We build on Microsoft Azure: the cloud where an MVP starts cheap and scales without migrations when the product takes off. Infrastructure as code, automated deployments and separate development and production environments from day one.

That also protects your investment: Azure and the .NET/TypeScript ecosystem are among the stacks with the most professionals available, so the day you build your own team you won't depend on an exotic technology only we know. It's the other side of our exit plan.

And the documentation assistant we deliver with every product runs on the same Azure services, inside your subscription: your knowledge doesn't leave for a third party.

An assistant that knows your product

While we develop, we document everything: architecture decisions, data structure, why something was done one way and not another, how it's deployed. And on top of that documentation we build a conversational assistant that answers questions about your specific product - not about programming in general: about yours.

Why it matters: the biggest risk of hiring external development is that the knowledge leaves with the team. Our declared goal is for you to stop needing us, and this is what makes it genuinely possible. When you scale down or pause, the knowledge stays with you in a format you can query - not in a PDF nobody opens.

In practice it's useful for three things: getting a new developer up to speed without depending on us, resolving how-does-this-work questions without opening a ticket, and understanding why a technical decision was made eight months ago without email archaeology.

And so there's no fine print: the assistant answers about your product and its documentation. It doesn't write code or make decisions - that's what people are for, yours or ours.

Be wary of fixed project prices

Almost the whole industry sells a fixed project price. It sounds reassuring, but it hides a trap: no two projects are alike. A SaaS with payments and a dashboard, a sector-specific ERP and an assistant for an online store have nothing in common. Whoever gives you a fixed price before knowing the scope can only be doing one of two things: padding it upwards (you overpay) or giving an optimistic estimate that will be renegotiated as soon as the real scope appears. The other red flags - and the seven signs of a good partner - are in how to choose a development team without being technical (in Spanish). And the quote that stands out as cheap gets an article of its own: cheap build, expensive maintenance (in Spanish), on where the difference gets recovered later. The best explanation of why an itemised quote wins, though, isn't about software at all: it's the locksmith's quote (in Spanish).

What can be fixed is something else: the rate (€70/hour) and the minimum commitment (one delivery a month, €2,800). The total isn't set by a salesperson: you decide it, because it depends on how much you want to advance each month. There are only two dials to adjust:

• How many people: from one to six, across development, UX, QA and architecture/CTO
• How much dedication: from half-time to full-time

Your budget sets the pace, not our calendar

This is the real difference. If one month you can invest more, we move faster. If a lean month comes, we scale down. What matters is not stopping: the product moves forward every month, without waiting to gather the budget for one big block.

And when the project changes (and it will), it adjusts on the go: no contract renegotiation, no annexes, no drama.

What it costs

Development at €70/hour, hiring monthly dedication with a delivery every two weeks. Each delivery, 40 hours of work, is €2,800.

For projects that need it, we add profiles: from one to six people across development, UX, QA and architecture. Small teams on purpose: they perform better.

Every profile bills at the same rate. For each delivery we decide together how the hours split between development, design and QA depending on what needs building: there's no fixed percentage because no two deliveries are alike.

As a reference: a simple internal tool or an automation is usually solved in one or two months of partial dedication; a SaaS-type MVP - user accounts, one core feature done well, dashboard and payments - typically lands between two and four months; a custom ERP for a specific sector, somewhat more, due to the weight of data modelling. The full numbers, with examples by product type, are in what it costs to build an MVP in 2026 (in Spanish).

Not ready for product yet? A landing page (€990) or a brand manual (€690) is enough to start validating.

Frequently asked questions