Why Charging Per Page Is Killing Your Web Design Profits
Per-page pricing is the most common mistake in freelance web design. It rewards low-effort projects and punishes high-value ones. Here's what to charge for instead.
A potential client asked me last month: “How much do you charge per page?”
I told her I don’t charge per page.
She paused, confused. “What do you charge for then?”
Per-page pricing is the default model most freelance web designers fall into early, and most never leave. It feels logical. More pages, more work, more money. The math is clean. The client understands it. Quoting takes five minutes.
It’s also the single biggest reason most freelance web designers underprice their work.
Here’s why per-page pricing is broken, and what to use instead.
What’s wrong with per-page pricing
The fundamental problem: pages aren’t units of work. They’re units of content. A simple 10-page brochure site can take 40 hours. A complex single-page e-commerce site can take 120 hours. If you’re charging the same per page, you’re losing money on every complex project and overcharging clients who actually need a simple build.
Let’s break this down with a real example.
Site A: A 10-page brochure site for a local consultant. Home, About, 5 service pages with similar templates, Contact, Privacy, Terms. Each page has a paragraph of copy, a hero image, and a CTA. Total estimated build time: 35 hours.
Site B: A single-page e-commerce landing page for a SaaS product. Custom checkout flow, payment processing integration, dynamic pricing calculator, email automation hookup, A/B testing setup, mobile-optimized purchase funnel. Total estimated build time: 80 hours.
At €300 per page:
- Site A pays you €3,000 for 35 hours of work. That’s €86/hour.
- Site B pays you €300 for 80 hours of work. That’s €3.75/hour.
The per-page model has you working for €3.75 an hour on the project that took twice as long.
This isn’t a corner case. It’s the norm. Per-page pricing systematically underprices complex work and overprices simple work, which means your most valuable clients are the ones you lose money on.
The wrong reaction: “I’ll just charge more per page”
The instinct is to raise the per-page rate. €300 becomes €500 becomes €700.
This doesn’t fix the problem. It just shifts the math. The consultant who needed 10 simple pages now gets quoted €5,000 and goes somewhere cheaper. The SaaS company that needed a complex landing page now pays €700 instead of €300 — still nowhere near the actual value or work required.
You scared off the simple projects you were overcharging and you’re still losing money on the complex ones.
The model itself is wrong. You can’t fix it with arithmetic.
What to price for instead
A better question: what are clients actually paying for?
They’re not paying for pages. They’re paying for the outcome — a website that helps their business. The work required to deliver that outcome depends on:
- What functionality is needed (forms, e-commerce, integrations, custom logic)
- How much complexity the design requires (custom layouts, animations, responsive behavior)
- What the client is providing (content, images, brand assets) and what you need to create
- What strategic work is involved (information architecture, copywriting, SEO setup)
A 3-page site with a custom booking system and integrated payment processing is more work than a 12-page site with a standard CMS template. The pricing should reflect that.
The base-plus-add-ons model
The structure that works for most freelance web designers: base price plus add-ons.
Base price is what every project starts at. It covers the standard deliverables: a set number of core pages (usually 3-5), responsive design, CMS integration for content updates, basic SEO setup, accessibility compliance, and a 30-day warranty.
This base is your floor. It’s what every project requires regardless of size. For most freelance designers running €5K+ projects, the base sits between €3,500 and €7,500 depending on experience level.
Add-ons are everything beyond the base. Each add-on has a fixed price:
- E-commerce setup (basic, 5 products): €1,500
- E-commerce setup (catalog, 50+ products): €3,500
- Multi-language support (2 languages): €800
- Multi-language support (each additional language): €400
- Custom booking or scheduling system: €1,200
- Newsletter or marketing automation integration: €600
- Custom animations or interactions: €800-€2,000
- Accessibility audit (WCAG AA): €1,200
- Additional pages beyond the base 5: €350 each
- Content strategy and copywriting: €1,200-€4,000
These numbers are illustrative — yours will be different based on your market and experience. The point is the structure.
When you quote a project, you start with the base, add what the project specifically needs, and the total is the sum. The client sees a line-item breakdown of exactly what they’re paying for.
Why this works better than per-page pricing
It prices the work, not the artifact. A 3-page e-commerce site with a custom booking system costs more than a 10-page brochure site, which matches the actual work required.
It makes negotiations objective. When a client pushes back on price, you don’t argue about your value. You ask them which add-on to remove. The conversation is about scope, not your worth.
It makes upselling natural. When you’re walking the client through the quote, you can add or remove add-ons in real time. “If you also want SEO content support, that’s an extra €1,200 to add a copywriter to the team.” Easy decision, no awkward sales pressure.
It documents the scope precisely. The line items become the deliverables list. Anything not in the quote is out of scope. This prevents scope creep before the project starts.
It scales. When you raise your rates, you raise the base and adjust the add-ons proportionally. The structure stays the same. You don’t have to redo your entire pricing model.
The first time you try this
You’ll feel the same hesitation as the first time you raised your rates. Quoting €6,500 instead of €3,000 (5 pages × €600) feels like more than the project is worth.
Until you remember the project includes a custom booking system, multi-language support, accessibility compliance, and ongoing CMS training. That’s not a €3,000 project. It’s a €6,500 project. The per-page model was hiding everything you were doing.
The other thing that happens: your first few quotes will get pushback. “Wait, why is this €6,500?” That’s not a sign the price is wrong. It’s a sign the structure is new to them. Walk them through the line items. Show them what each add-on includes. Let them decide what to keep or remove.
In my experience, when clients see the breakdown, they don’t ask for discounts. They ask which add-ons they can remove to hit their budget. That’s the conversation you want.
The clients you’ll lose, and the clients you’ll keep
Switching from per-page to base-plus-add-ons will cost you some clients. Specifically, the clients who were looking for the cheapest possible 10-page website. Those clients were never going to be profitable for you anyway. They were getting the consultant-level project at the brochure-site rate.
The clients you’ll keep — and the new ones you’ll attract — are the ones who understand they’re paying for complexity, not page count. They’re the ones with real budgets, real businesses, and real expectations.
These clients are the foundation of a sustainable freelance practice. They pay on time. They give clear feedback. They refer other businesses like theirs.
The per-page pricing was filtering them out. You were attracting the wrong clients with a pricing model that signaled “I work cheap.”
How to make the switch
Don’t overthink it. Pick a base number that reflects your minimum viable project. List 8-12 add-ons that cover the most common requests. Write a one-page document that shows your standard package and add-on menu. Use it on the next quote.
Tweak it after each project. Did you forget to include something in the base? Add it. Was an add-on consistently underpriced? Raise it. Within three months, you’ll have a model that prices accurately and quotes faster than per-page ever did.
The clients pay more. The work feels more proportional. The quotes get signed faster because the breakdown is transparent. And you stop having the “wait, this took how many hours?” reckoning at the end of every project.
Per-page pricing is the freelance designer’s training wheels. At some point you have to take them off.
debrieft generates quotes from a base-plus-add-ons structure automatically. Set your base and your add-on prices once, and every new quote uses them. Your client gets a portal. You get a dashboard. Both in sync. Try it free at debrieft.app