Frequently asked questions about custom web and app development

The range exists because «website» means very different things. A presentation site with its sections, its copy, proper technical SEO and a form that actually works does not cost the same as an online shop with payments, stock and invoicing, or as a management application with users, permissions and reports. Before quoting a figure I need to know what it has to do, not how many pages it has.

What moves the price is almost never the design: it is the logic behind it. A form that sends an email takes an afternoon. A form that validates data against the system you already use, generates a document, notifies the right person and files it away is a different project. That is why the first conversation is about what you are doing by hand today, not about how many screens you want.

How it works: we talk at no cost and with no commitment, I write you a proposal with a fixed scope, a schedule and a firm price, and nothing gets invoiced that is not in it. If something new turns up halfway through, it is quoted separately and you decide whether it goes in now or later.

What pushes the price up

Integrations with systems you already use, payments, roles and permissions, custom reports and mobile apps.

What brings it down

A clearly bounded scope, content ready in advance, and starting with the smallest version that already works for you.

What never appears

Fees for using your own software, hidden licences, or surprises at the bottom of the invoice.

I work in frequent deliveries rather than one big reveal at the end. Within days you have a private link where you can watch it take shape, and from then on it updates continuously. That avoids the classic problem: finding out after eight weeks that what was built is not what you had in mind.

A typical website schedule: one week to settle scope, structure and content; two or three for design and development; one for review, final copy, analytics and technical SEO; then launch. In an application the development block is longer and gets split into phases, so the first useful version goes live before the project is completely finished.

What delays a project most is not the code: it is the content. Photos, copy, logos and access to the domain and email. If that is ready, the schedule holds; if not, the clock stops there. I send you a list of what is needed on day one so it does not catch you halfway.

When we close the project you receive the full repository, the documentation to run it and access to everything: domain, hosting, database and external services. All in your name, not mine. If tomorrow you want to continue with another team, they can, without asking my permission.

This is not a minor legal detail. The most common situation a company runs into is wanting to change something on its own website and discovering it cannot: the code lives inside the supplier's closed system, or the licence is billed monthly and expires if you leave. I build on standard, open technologies — React, Next.js, TypeScript, Node.js, PostgreSQL — precisely so that any developer can pick up where I left off.

And the other way round: the fact that you can leave whenever you want is the only real guarantee that I will keep being useful. The relationship lasts because it works, not because you are stuck.

If you are in Mallorca, Menorca, Ibiza or Formentera, we sit down and talk. For a project that touches how a team works — a booking system, a management dashboard, an app for floor staff — spending a morning watching how you do it today is worth more than ten emails.

Outside the islands the project runs the same way: a video call to start, a private link where you follow progress, and WhatsApp or email for the day to day. I work like this with clients across Spain and the practical difference is almost none.

What never changes is who you are talking to: me. There is no account manager passing your message to a team you have never met. You write, and the person writing the code answers.

A project does not end the day it goes live; that is the day it starts getting real users. From then on dependencies need updating when security patches land, the site needs watching, backups need to be restorable for real, and whatever turns up needs fixing.

Maintenance is optional and is not a condition of working with me. You can take the project and run it with your own team — the code is yours and it is documented — or leave it with me. If you do take it on, you know in advance what it covers and how quickly I respond.

What it usually includes: updates and security patches, verified backups, downtime monitoring, periodic performance and search-visibility reviews, and a block of hours for small changes without opening a new quote each time.

Automation always starts with the same question: what do you do every week that is identical every time? Download a file, copy it into a spreadsheet, cross it with another one, send an email. That is a script, and it usually gives hours back every week from the first month.

An AI agent is the next step up: it understands questions in plain language and answers with your business's information, not with generalities. It works for handling the first line of enquiries, filtering the contacts that arrive through the website, summarising internal documentation, or helping your team find what they need without asking a colleague.

The test for whether it is worth it has nothing to do with technology: how many hours a month the task takes, how much a mistake costs when it is done by hand, and how many people repeat it. If all three numbers are small, I will tell you, and we both save the project.

Multilingual done properly is not translating with a button. Each language needs its own address, its own titles and descriptions, and the hreflang tags that tell Google these are the same page in another language and not duplicate content. Without that, the versions compete with each other and none of them ranks.

In the Balearics this matters more than it sounds: some clients search in Catalan, some in Spanish and some visitors in English, and those are different searches with different results. Serving all three in their own language multiplies the surface through which people can find you.

I work in Catalan, Spanish and English. For other languages I build the structure and the technical side and we work with your translator or a professional one: a machine translates words, but it does not know how your business sells.