How to Price a Website in 2026: A Freelance Pricing Framework

Pricing a website is one of the hardest parts of freelancing.

Price too low and the project consumes your month. Price too high without justification and the conversation ends. Copy a competitor's rate and you inherit their costs, their market, and their assumptions.

A price is not a number you invent. It is the result of three constraints: what the project costs you, what it is worth to the client, and what the market will bear.

This guide gives you a framework you can apply to the next proposal.

The three numbers behind every price

1. Your cost floor

The floor is the minimum you can charge without losing money.

Start with the number you need to earn per month, then divide by the billable hours you can realistically sell.

Example:

• Target monthly income: 3,000
• Billable hours per week: 20
• Billable hours per month: about 80
• Minimum effective rate: 3,000 / 80 = 37.5 per hour

That number is not your price. It is your floor. It covers your time and nothing else. It does not cover taxes, software, hardware, sick days, sales calls, or the hours you spend on proposals.

Add a buffer for non-billable work. If only 60% of your working time is billable, the real floor is higher.

2. The value ceiling

The ceiling is what the project is worth to the client.

A website that generates leads for a local service business may be worth far more than the hours it takes to build. A portfolio site for a photographer may be worth less in direct revenue but more in positioning.

Value is not a license to overcharge. It is a reason to price the outcome rather than the hours.

Ask:

• What happens if this website works?
• What happens if it does not exist?
• What is the cost of a bad website?
• How many leads or sales would make this a good investment?

3. The market range

The market sets expectations, not your price.

Look at similar providers, but compare scope, not just the number. A 500 website and a 5,000 website are rarely the same deliverable.

Use the market to sense-check, not to set your rate.

Pricing models

Hourly

Simple to start, dangerous to scale.

You are rewarded for being slow and punished for being efficient. Clients cannot budget with confidence.

Use hourly for small, undefined work: audits, fixes, consulting calls.

Fixed price

The most common model for websites.

You define the scope, estimate the work, add a risk buffer, and quote one number.

The risk is scope creep. The defense is a written scope that lists what is included and what is not.

Value-based

You price against the outcome, not the hours.

This works when the outcome is measurable and the client trusts you. It requires a discovery conversation and a clear definition of success.

Retainer

A monthly fee for ongoing work: maintenance, updates, content, support.

Retainers stabilize income and reward long relationships. Define the monthly capacity and what happens when it is exceeded.

A fixed-price formula

A practical quote looks like this:

Estimated hours x effective rate = base cost
Base cost + risk buffer (15-25%) = project fee
Project fee + third-party costs = client price

Example, for illustration only:

• Estimated hours: 40
• Effective rate: 50
• Base cost: 2,000
• Risk buffer at 20%: 400
• Project fee: 2,400
• Hosting, fonts, or stock assets: 150
• Client price: 2,550

The numbers are examples, not market rates. The structure is what matters.

If the estimate is uncertain, increase the buffer or reduce the scope. Do not hide uncertainty in a low price and hope.

Scope: the part that protects the price

A proposal should state:

• Pages and templates: how many, and which.
• Content: who writes it, and what happens if it is late.
• Design: original design or template customization?
• Integrations: forms, payments, CRM, analytics.
• Revisions: how many rounds, and what counts as a round.
• Timeline: start date, milestones, launch date.
• Exclusions: explicitly what is not included.
• Ownership: who owns the design and code after payment.
• Payment terms: deposit, milestones, final payment.

The exclusion list is not negative. It prevents the conversation where "just one more page" becomes three weeks of unpaid work.

Deposits and payment schedules

A common structure:

• 40% deposit to reserve the dates and begin discovery.
• 30% at design approval or the midpoint milestone.
• 30% before launch or on delivery.

For larger projects, add a milestone per phase.

Never start without a deposit. It filters serious clients and covers the cost of the first week.

If a client cannot pay a deposit, the project is not ready.

Change orders

When the scope changes, do not absorb it silently.

A short change order includes:

• What is being added or changed
• The impact on timeline
• The impact on price
• A written approval

This is not bureaucracy. It is how you protect the original agreement and keep the relationship honest.

What to do when the client says the price is too high

Do not discount immediately.

Ask which part is out of budget. Then offer options:

1. Reduce scope: fewer pages, a simpler design, a later phase.
2. Use a template: faster delivery, lower cost, less custom work.
3. Split the project: launch the essential version first.
4. Adjust the timeline: a longer schedule can reduce rush costs.

A lower price with the same scope is a subsidy. A lower price with a smaller scope is a deal.

When to raise your prices

Raise prices when:

• You are booked consistently
• Your proposals close without negotiation
• You are turning work away
• Your scope has grown but your price has not
• You have evidence: case studies, results, testimonials

Do not raise prices in the middle of a project. Finish the current agreement, then update your next proposal.

A useful cadence is once or twice a year, in small increments, with new work only.

Pricing and positioning

Your price communicates who you are for.

A low price attracts clients who optimize for cost. A clear, higher price attracts clients who value the outcome and are more likely to respect the process.

That is not a universal rule. It is a pattern worth noticing.

If you are just starting, price for evidence: a small project, a clear scope, a strong result. Then raise the price as the evidence accumulates. The portfolio guide explains how to present that evidence.

A quick checklist before sending a quote

• I know my cost floor.
• I understand the client's outcome.
• The scope lists pages, features, and exclusions.
• The revision limit is explicit.
• The timeline has dates.
• The payment schedule is written.
• Third-party costs are included or excluded clearly.
• The quote has an expiry date.
• I would be comfortable delivering this for the price.

If one line is missing, fix it before sending.

Final thoughts

Pricing is not a personality trait. It is a process.

Know your floor. Understand the value. Define the scope. Charge a deposit. Handle changes in writing.

You will still misprice some projects. Every freelancer does. The goal is to make the mistake small, learn from it, and adjust the next quote.

If you want help delivering the project after it is sold, explore the services page or start from a ready-made website template.

Keep reading

• How to build a portfolio that gets clients
• Notion for freelancers: a client and project system
• From learning to building

---

Follow The Medamine for more insights on web development, AI, productivity, and digital business.