How much does a website cost in 2026? What drives the price

"How much does a website cost?" is the first question almost every client asks — and the honest answer is "it depends on the scope". Website can mean a single page with a contact form or a full online store synced with your warehouse, and those differ in effort by an order of magnitude or more. The price is driven by the number of unique pages or screens, design, integrations, user accounts, languages and how ready your content is.

This post breaks down what actually moves the price and the timeline, so you can walk into any conversation with a developer or studio knowing what you're paying for. You'll also find my starting prices as a reference point — but the real drivers matter more than any number.

#The main project types

Here's the rough ladder, from simplest to most complex. The timelines and "from" prices are the ones I work with as a solo developer — useful for orientation, not a quote. Budget grows roughly in the same order: a landing page is the lightest investment, a full store-ready mobile app the heaviest.

These are starting points, not a price list: the final estimate is fixed after a short brief and doesn't grow unless the scope does. Monthly support after launch starts from €49/month for websites and from €149/month for apps. Package details are on the websites and mobile apps pages.

#Landing page

The cheapest entry point, but not "cheap" if it's done right. A good landing page is copywriting, design, speed and analytics working together. If it's for ads, it has to load fast on a phone — otherwise you're paying for clicks that bounce before the page appears.

#Business site

Most of the cost here is content and structure, not code. How many pages, how many languages, whether you need a blog or a CMS so your team can edit texts without calling a developer.

#E-shop

The jump in price comes from integrations: payment providers, delivery services, stock sync, invoices, email notifications. Each integration is small on its own, but they add up — and each one needs testing with real money flows.

#PWA vs mobile app

A progressive web app runs in the browser but can be installed on the home screen, work offline and send push notifications (on iPhone — only after the user adds it to the home screen). A React Native / Expo app is a "real" app in the App Store and Google Play. PWAs are usually cheaper and faster to ship; store apps win on device features and store presence. I wrote a separate comparison of PWA vs React Native if you're stuck between the two.

#What actually drives website cost

Regardless of the type, these are the levers that move the number up or down:

1. Number of unique screens. Ten pages built from the same template cost far less than ten pages with custom layouts.
2. Custom design vs a ready-made system. A unique design takes more time — but it's also what makes you stand out.
3. Integrations. Payments, CRM, maps, delivery, messengers, third-party APIs. Each one is its own mini-project.
4. User accounts and roles. The moment you have login, permissions and personal data, security and testing effort grows.
5. Languages. Every extra language means translated content, SEO for that language and more QA.
6. Content readiness. If texts and photos are ready on day one, the project moves fast. If not, it waits.
7. The platform. A ready theme, a custom build and a no-code tool have very different cost curves — upfront and over the years. I compare them in WordPress vs custom vs no-code.
8. Support after launch. Hosting, updates, backups, small fixes — worth budgeting for from the start.

#Why quotes for "the same site" differ so much

If you've asked three developers and got three very different numbers, it's usually not greed — they priced three different projects. One imagined a template with your logo, another a custom design with a CMS, the third added copywriting and SEO. Quotes only become comparable when everyone estimates the same written scope. That's what a brief is for.

#What affects the timeline

The biggest delays are rarely technical. From experience, projects slow down when:

• feedback on designs takes a week instead of a day;
• content arrives after the layout is already built;
• the scope quietly grows mid-project ("can we also add…");
• third-party accounts (payments, stores, domains) are set up too late.

App Store and Google Play reviews also add time for mobile apps — plan for at least a few days, and more for the first release.

#How to keep the cost down (without cutting quality)

• Launch the core, then iterate. Split features into must-have and nice-to-have. Phase two is cheaper once real users tell you what matters.
• Have content ready. Texts, photos and prices prepared before development saves both time and revisions.
• Start with fewer integrations. Card payments can wait a month if cash on delivery works for your first customers.
• Consider a PWA before a store app if you mainly need a fast, installable interface.
• Reuse layouts. A consistent set of page templates is cheaper — and usually better UX — than every page being unique.

#Get an accurate estimate: write a short brief

A clear brief is the fastest way to get a real number: goal, audience, rough list of pages or screens, must-haves vs nice-to-haves, integrations, examples you like, deadline and budget range. It doesn't need to be long — I've put a step-by-step guide and a copy-paste template in how to write a website brief.

#TL;DR

• The price depends on screens, integrations, accounts, languages, design and platform — not on the word "website".
• Different quotes usually mean different assumed scopes.
• Most delays come from content and feedback, not from code.
• A short, honest brief with must-haves and a budget range gets you a real estimate fast.

#FAQ

#How much does a simple website cost?

A one-page landing site is the lightest option — on my projects it starts from €590 — but the price still depends on design, copy and integrations like forms or analytics. Instead of trusting generic price lists, describe your pages and features and get an estimate for your scope.

#Why is a custom website more expensive than a website builder?

Upfront, you pay for design and development made for your business instead of a subscription to a shared template. In return you own the code, get better speed and aren't limited by the platform's features.

#Are there ongoing costs after launch?

Yes: domain, hosting, SSL (often free), and support — updates, backups, fixes and new content. Ask about these before you sign, not after.

#Can the price change during the project?

It shouldn't, as long as the scope stays the same. On my projects the estimate is fixed after the brief and grows only if you add new features.

#See your own number

Not sure where your project fits? Open the project builder, pick a website or an app, stack the blocks or screens you need and get a rough estimate in a couple of minutes — no commitment, fr. Then send it to me, and I'll come back with a fixed estimate. You can also browse the services and packages first.