How Much Does It Cost to Build an App in Spain in 2026 (Real Numbers, Three Ways to Buy)

Every week someone asks me what an app costs, and every week the honest answer disappoints them: it costs what the scope costs, multiplied by who you hire, multiplied by who carries the risk when it goes wrong. Anyone who gives you a single number before asking three questions is quoting their own margin, not your app.

I'm writing this from the builder's seat. I've been an engineer since the late nineties, I've run infrastructure for companies where a bad estimate meant a very public incident, and at Conectia I sign the quotes for the squads we deploy. So this isn't a price list. It's the arithmetic I actually use — with the numbers on the table — so you can do it yourself before you talk to anyone, including us.

«How much does an app cost» is three questions wearing one coat

The market treats it as one question because that's what the search box invites. In practice it decomposes into:

1. Scope — how many screens, integrations and states the product has to survive. Not «a marketplace app»; which marketplace, with what payments, what moderation, what happens when a seller disputes a refund at 2 a.m.
2. Team model — a fixed-price agency, freelancers you coordinate, or a senior squad that works inside your company. Same scope, very different cost curves.
3. Risk allocation — who pays when the store rejects the build, when the first developer leaves, when v1 needs a rewrite. This is the line nobody puts in the quote and the one that decides the real total.

Hold those three apart and the ranges below stop looking vague. They look like what they are: a function with three inputs.

The arithmetic, with our own numbers on the table

I'll use Conectia's published rate card because it's the one I can defend in public: all-inclusive, billed in euros on 160 hours a month — 12–16 €/h for an AI Operator, 16–22 €/h for a senior engineer, 22–28 €/h for a senior lead, 30–40 €/h for a senior DevOps/infrastructure lead. A Spanish agency quoting a senior at 60–90 €/h isn't lying either; it's a different model with different overhead. Plug in whichever band matches the channel you're buying from — the structure of the calculation doesn't change.

A focused MVP (one core flow, one platform, no exotic integrations). Two senior engineers, eight weeks, 160 hours a month each:

2 engineers × 2 months × 160 h × 16–22 €/h = 10,000–14,000 €. Add a fractional lead for architecture and code review at a few hours a week and you land at 12,000–18,000 €. That is the honest floor for something you'd put your name on. We package exactly this shape as an 8-week MVP, and the number is the number — no «starting from».

A mid-complexity product (auth, payments, admin panel, notifications, two platforms via React Native). Three engineers plus a lead, four to five months:

3 × 4.5 × 160 × 16–22 €/h ≈ 35,000–48,000 € for the engineers, plus the lead's share ≈ 45,000–65,000 €.

A platform with a real backend and AI features (RAG or an agent in the loop, integrations with the tools your team already lives in, observability so you know what the model is doing). Four to five engineers including an AI/LLM engineer and infrastructure time, six to nine months: 90,000–180,000 €, and the top of that range is where the AI part is genuinely new, not a chat box bolted onto a CRUD app.

Notice what the arithmetic doesn't contain: recruitment fees, a bench you're paying for while you wait, or a discount that vanishes at the second invoice. If a quote you're holding can't be rebuilt from hours × rate × people, ask what the difference is made of.

Three ways to buy, and what each one charges you for

A fixed-price agency. You get a number and a contract. What you're paying for is certainty — theirs, mostly: the price includes a contingency for scope creep, and the change-request process is where that contingency gets recovered. In Spain a mid-complexity app from a reputable agency sits in the 40,000–120,000 € band. The model works well when the scope is genuinely frozen. It works badly for a product that will change every fortnight, which is most products.

Freelancers you coordinate. The cheapest hour on the market: an offshore React Native contractor from roughly 25–35 €/h, a solid Spanish freelance senior at 45–70 €/h. What you're paying for is the hour, and what you're doing yourself — unpaid — is vetting, coordination, continuity and the risk that the person who built the payments module is on another project when it breaks. I've written a full guide to where to hire freelance app developers; the short version is that freelancers are the right answer for a scoped feature and the wrong answer for a product.

A directly employed senior squad on a flat monthly rate. This is what we do, so read it with that in mind. The engineers are employees, not contractors; they're vetted by CTOs who still ship code (we accept about 3 % of applicants); they work six hours a day inside your time zone; and the invoice is one flat fee per engineer per month, from 2.5k € a month for the Pilot Sprint, with a 30-day replacement guarantee and zero recruitment fee. What you're paying for is continuity and accountability — the same people at v3 as at v1, and a delivery manager whose job is to make the estimate true.

Let me concede the strongest case against us plainly: if you need one screen fixed by Friday, a freelancer beats a squad on price and speed, and pretending otherwise helps no one. The squad model only pays when the app is the product and the roadmap is longer than the first release.

The costs the quote hides are the ones that decide the total

Every model above has a second column that rarely makes it into the first conversation. From the incidents I've actually watched:

• Store review. Apple and Google reject builds for reasons that look arbitrary until you've seen a hundred of them: privacy labels, in-app purchase rules, missing account-deletion flows. Each rejection is a week of a senior engineer, which at agency rates is a four-figure line item nobody budgeted.
• Year-one maintenance. The industry rule of thumb is 15–25 % of the build cost per year for OS releases, dependency updates and the bugs users find that testers didn't. A 50,000 € app is a 60,000 € app by the end of the first year. Nobody's hiding it; it's just not in the headline.
• The rewrite. This is the expensive one. A 25 €/h build that gets bounced by review, can't pass a security questionnaire from your first enterprise customer, or simply can't be extended by anyone but its original author gets rebuilt. I've seen the rebuild cost more than a senior squad would have cost from day one — twice. The cheapest hour and the cheapest app are rarely the same purchase.
• Coordination. The hours you spend running freelancers are real hours. Founders who track them honestly tend to find a 20–30 % overhead on the engineering total. That's your time, priced at whatever your time is worth.

The real cost of an app is the cost of the version that survives contact with users, not the cost of the first build. Price the survival, not the launch.

One rule for picking the channel

If I were the CTO you're about to hire, this is the rule I'd apply before looking at a single quote:

1. Is it a feature or a product? A scoped, bounded piece of work — a freelancer, and run your own vetting (a paid test, real references, a review of shipped code).
2. Is the scope frozen? Genuinely frozen, written down, unlikely to change for three months — a fixed-price agency is a fair deal.
3. Will the same team need to be there at v3? Then buy continuity: a squad or an in-house hire. Between those two, run the year-one numbers — the nearshore cost calculator does it with published benchmarks and the developer cost breakdown has the region-by-region rates.
4. Whatever you pick, insist on the arithmetic. Hours × rate × people, plus a named line for maintenance. A vendor who won't show it is asking you to buy their margin blind.

Do that and «how much does an app cost» becomes a question you can answer yourself, to within twenty per cent, before the first call.

Three things people ask right after the ranges

How much does a simple app cost to build?

A genuinely simple app — one core flow, one platform, standard authentication, no payments — comes in at 8,000–18,000 € when built by senior people who won't need to rebuild it: two engineers for six to eight weeks at the 16–22 €/h band, plus a lead's time. Below roughly 5,000 € you are buying either a template or a build that will need doing again; above 20,000 € for that scope, ask what the extra is paying for.

How much do developers charge per hour in Spain?

In 2026 a Spanish freelance senior charges 45–70 €/h; a local agency bills a senior at 60–90 €/h; an offshore contractor starts around 25–35 €/h with the vetting on you. A directly employed nearshore senior on our model is 16–22 €/h all-in (22–28 €/h for a lead), which in practice lands 26–71 % below an equivalent local hire — the gap is the cost of living where the engineer is employed, not a discount on seniority.

Is a freelancer cheaper than a company?

Per hour, yes — usually by a wide margin. Per finished, maintained app, only when the work is scoped and short. Once you add the coordination you do yourself, the continuity risk and the probability of a rewrite, a freelancer is cheapest for a feature and a company or a squad is cheapest for a product. The honest comparison is year one, not the first invoice.

If you're at the point where the spreadsheet has more assumptions than numbers, talk to a CTO — we'll size the scope with you and show the arithmetic, whichever channel you end up buying from.