How Much Should I Charge for a Website? A Practical Pricing Guide

Last updated: July 15, 2026

The short answer: charge enough to cover the real work, the risk you are taking, and the value of the finished site. For many freelancers, that means roughly $1,500 to $5,000 for a polished small-business website, $5,000 to $15,000 for a more involved marketing site, and considerably more for custom applications or ecommerce.

Those are starting ranges, not a rate card you should copy. A five-page brochure site built from approved content is not the same job as a five-page site that also needs positioning, copywriting, photography, a CMS, analytics, integrations, and three rounds of stakeholder review.

The better question is not "What does a website cost?" It is "What will it take to deliver this website well, and what is that outcome worth to this client?"

A sensible starting range#

All figures below are in USD and assume professional freelance work, not a large agency engagement.

These ranges are deliberately broad. Scope, client readiness, technical risk, geography, positioning, and your track record can move a project far outside them.

Upwork currently publishes a $15 to $50 median hourly range for web developers on its marketplace, with expert rates extending from $50 to $200 per hour. The US Bureau of Labor Statistics reports a 2024 median wage of $90,930 for employed web developers. Neither number tells you what to quote, but together they are useful guardrails: marketplace rates can be very competitive, while a sustainable independent rate must cover costs that an employee does not pay directly.

Calculate your minimum sustainable rate#

Start with the income you want the business to produce, then work backward.

(target pay + annual overhead + tax buffer + profit buffer)
----------------------------------------------------------
                 realistic billable hours
= minimum hourly rate

Suppose you want $90,000 in personal compensation. Add $18,000 for software, hardware, accounting, insurance, time off, and other overhead, plus a $12,000 buffer. That gives you $120,000 in required annual revenue.

If you can bill 1,200 hours per year, your floor is $100 per hour. That billable-hour assumption matters. A freelancer may work 2,000 hours in a year but spend a large share of them on sales, proposals, admin, learning, and unpaid support.

Your internal hourly rate does not have to appear in the proposal. It gives you a private way to test whether a fixed-price quote is viable.

Turn the rate into a project price#

Estimate the work in phases instead of guessing one total number.

At an internal rate of $100 per hour, the base project is $11,400. Add a 15 percent risk allowance for uncertain content, stakeholder review, integration surprises, and launch support. The quote becomes $13,110, which you might present as a fixed $13,000 project.

This is much safer than estimating only the coding. Discovery, meetings, revisions, QA, accessibility, deployment, and handoff are all work.

If AI tools make part of the build faster, keep the efficiency. Clients are buying a working outcome and your judgment, not keystrokes. The right way to use the saved time is to improve quality, shorten delivery, or increase your margin. Our guide to AI tools for solo developers covers the tooling side without treating automation as a reason to race to the lowest price.

Add value without inventing a value-based number#

Your cost-based estimate creates a floor. Value helps you decide whether the project should be priced above it.

Ask questions such as:

• What does the current site prevent the business from doing?
• How many qualified leads or sales does the site influence?
• What is one new customer worth?
• Is there a launch date tied to a campaign, event, or funding milestone?
• Will the new system save staff time every week?
• What happens if the project is late or fails?

If a $10,000 site could credibly support hundreds of thousands of dollars in annual business, a $12,000 to $20,000 quote may be reasonable. That does not mean charging an arbitrary percentage of the client's revenue. It means recognizing that high-stakes work usually demands better discovery, more validation, more reliability, and more experienced judgment.

Be able to explain the scope behind the price. "Because you can afford it" is not a pricing strategy.

Use packages to make the decision easier#

A three-option proposal helps clients choose scope instead of negotiating against one number.

Foundation#

• A focused landing page or small brochure site
• Client supplies final copy and brand assets
• One revision round
• Basic analytics, metadata, and launch support

Growth#

• A multi-page marketing site with CMS
• Content structure and design system
• Forms, analytics, basic integrations, and two revision rounds
• Training and a post-launch support window

Custom#

• Strategy, original design, advanced interaction, and custom integrations
• Migration or complex content modeling
• Multiple stakeholder workshops
• Longer QA, launch, and support coverage

Each option needs exact boundaries. Name the page count, templates, integrations, revision rounds, content responsibilities, and support window. A package is useful only when the client can see what changes between tiers.

Charge separately for ongoing work#

The launch fee should not quietly include permanent support. Offer a care plan or retainer for work such as:

• dependency and platform updates
• uptime and form monitoring
• backups and recovery checks
• small content changes
• analytics reporting
• conversion experiments
• priority support

A simple care plan might start at $150 to $500 per month. Active growth work can run from $1,000 to several thousand dollars per month because it reserves actual delivery capacity.

Also pass through or clearly itemize recurring third-party costs. Hosting, domains, premium plugins, email delivery, stock assets, and payment fees belong in the commercial conversation. For example, Stripe's standard US pricing was 2.9 percent plus 30 cents per successful domestic card transaction when checked for this article. Rates vary by country and payment method, so link the current pricing page in your proposal instead of hard-coding an old fee.

Protect the price in your proposal#

A good price can still become a bad project when the scope is vague. Your proposal or statement of work should include:

• the specific deliverables and page templates
• who provides copy, images, legal text, and product data
• how many revision rounds are included
• the milestone and feedback schedule
• browser, device, accessibility, and performance expectations
• what counts as a change request
• the payment schedule
• ownership, licensing, cancellation, and launch terms
• the post-launch support period

A common structure is 40 to 50 percent upfront, a milestone payment after design approval, and the balance before launch or handoff. For longer projects, monthly billing can keep cash flow aligned with delivery.

Do not absorb payment-processing fees by accident. If a client pays a $10,000 invoice by card through a processor using a percentage-plus-fixed-fee model, the fee is part of your cost. Build normal payment costs into the price, or offer bank transfer where appropriate and lawful.

When to charge hourly#

Fixed pricing works best when the outcome and boundaries are clear. Hourly or weekly billing is usually safer when:

• you are inheriting an unknown codebase
• the client cannot define the final scope yet
• the work is exploratory
• priorities will change every week
• you are providing ongoing implementation capacity

For ambiguous work, sell a paid discovery phase first. A $1,000 to $3,000 discovery engagement can produce requirements, a sitemap, technical decisions, risks, and a reliable implementation quote. It also tests how you and the client work together before either side commits to the full build.

My practical recommendation#

If you are early in your freelance career, do not start by trying to perfect value pricing. Build a defensible floor, estimate the complete scope, add risk, and quote a fixed project with clear limits.

For a typical professional small-business website, $2,500 to $7,500 is a reasonable conversation range. Move lower only when the scope is genuinely smaller or the project has strategic value you have consciously chosen. Move higher when you own strategy, content, custom design, integrations, migration, or business-critical risk.

Then review every finished project. Compare estimated hours with actual hours, note where revisions expanded, and update your model. Your last ten projects are eventually more useful than any generic pricing guide.

FAQ#

How much should a beginner charge for a website?#

A beginner can use the same cost-and-scope method as an experienced freelancer. For a small, clearly bounded site, a starting project range of $1,000 to $3,000 may be reasonable. Do not promise strategy, custom software, unlimited revisions, and ongoing support at that price. Reduce scope, not professionalism.

Should I charge hourly or per project?#

Charge per project when the deliverables and approval process are clear. Charge hourly, weekly, or through a paid discovery phase when the codebase, requirements, or priorities are uncertain. Even with fixed pricing, keep an internal hourly estimate to protect your margin.

How much should I charge for a five-page website?#

Page count is only one input. A five-page site with supplied copy and a template could cost $1,500 to $3,500. The same five pages with strategy, custom design, copywriting, CMS modeling, integrations, and stakeholder workshops could cost $5,000 to $15,000 or more.

Should hosting be included in the website price?#

Include setup and launch work in the project scope, but identify recurring hosting and service fees separately. The client should know which accounts they own, what renews, and what your ongoing management fee covers.

How many revisions should I include?#

One or two structured revision rounds per major phase is common. Define a revision as feedback on the approved scope, not a new direction or new feature. Price additional rounds and change requests separately.

Sources#

• Upwork: Web Developer Hourly Rates - marketplace ranges and rate factors, checked July 15, 2026
• US Bureau of Labor Statistics: Web Developers and Digital Designers - 2024 employee wage and outlook data, checked July 15, 2026
• Stripe Pricing - standard US online card pricing, checked July 15, 2026