How much to charge for web design
Define the finished website before discussing a fee
Ask what a small website needs to do before attaching a price to it. The request may cover a simple information page or a substantial booking or selling workflow. You can give a dependable web design quote by asking what visitors need to do and what the business needs to manage after launch.
Create a page and function inventory. Identify the main layouts, forms, navigation, content collections and third-party services the website will use. State which work your team supplies and which services the customer must arrange separately.
Agree on what completion means. A designed prototype, an implemented site, a migrated site and a launched site are different deliverables. Include the actual outcome you are responsible for, with the required customer approvals and account access.
Estimate discovery and design as working phases
Allow time to understand the audience, business goals and existing content. Review the material the client provides and identify gaps. A discovery stage can resolve uncertainties before you commit to a larger fixed project.
Plan the design work around distinct page types and states. Navigation, forms, mobile layouts, empty states and confirmation messages can require decisions beyond the main desktop page. Price the design system and page work you actually intend to deliver.
State how concepts will be reviewed. Name the client approver and ask for consolidated feedback. Several stakeholders giving separate instructions can turn a simple review into conflicting rounds of revision.
Put content responsibility in the quote
Ask who writes and approves the copy, supplies images and verifies business claims. If you offer writing, photography sourcing or migration, estimate those tasks separately. Supplied content still needs checking and placement.
Inspect existing content before promising a migration price. Old pages, inconsistent formatting, broken media and duplicated material can create unexpected work. Define the quantity and condition included in your estimate.
| Workstream | Question for the scope |
|---|---|
| Content | Who writes, supplies and approves it? |
| Design | Which page types and review stages? |
| Implementation | Which functions and external services? |
| Testing | Which devices, flows and acceptance checks? |
| Handover | What training, accounts and documents? |
Keep brand identity work distinct from web design if the client needs both. A new logo, naming exercise or full copy strategy can materially change the project and deserves an explicit agreement.
Cost implementation from the actual requirements
Estimate building approved layouts, configuring content structures and implementing the agreed functions. Include development setup, coordination and deployment work when your service includes them. Price purchased themes, plugins, fonts or hosting from verified supplier terms.
Work involving customer information, transactions or regulated services may need specialist review. Agree who obtains legal, privacy or other professional advice and what implementation you are supplying. This guide explains pricing a service, not the requirements for a particular website.
When the project uses a separate software provider, record what depends on that provider and what the customer must purchase. Identify the external services the customer will buy and the implementation work your fee covers. Avoid promising functionality before checking that it is available and suitable.
Include testing and handover in the labor model
Plan checks for the agreed visitor journeys, content, links, forms and responsive layouts. Include time for fixing issues within the approved scope. Testing is part of completing the project, not an optional activity left to whatever time remains.
Handover can include account transfer, editing guidance, documentation and a training call. Define what is included and who will maintain access. A client who needs ongoing content help may benefit from a separately priced service.
Build a realistic project schedule around dependencies. Content approval, third-party account setup and stakeholder feedback can affect timing even when production hours stay unchanged. Explain those dependencies in the proposal.
Calculate the fee from complete project cost
Add owner or employee labor, contractors, purchased assets, tools used for the project and a share of overhead. Include communications, insurance, software, bookkeeping and business development in the overhead model. Keep working compensation separate from the planned profit.
Example: These fictional USD figures describe an invented web project. Discovery and design labor cost $900, implementation costs $1,200, testing and handover cost $300, and direct expenses plus overhead add $600. Planning cost is $3,000. At an illustrative 25% margin, $3,000 divided by 0.75 gives a $4,000 project price before applicable tax. This is an example, not an average web design cost.
Use the profit margin calculator to inspect the result. A customer with a smaller budget can choose fewer layouts, less migration or a narrower function set while keeping a useful, complete scope.
For an existing site, list the redirects, old links and account dependencies that your migration scope will handle. Ask the client to identify essential pages and business workflows before estimating. A short content inventory can reveal more work than the visible design suggests and gives both parties an agreed checklist for handover.
Separate new requests from included revisions
Describe the review stages and how changes will be priced. Refining an approved design within the brief is different from adding a new page type or sales workflow. Explain the additional cost and timing before accepting the change.
Keep an agreed support period distinct from ongoing maintenance. Define what correction of delivered work covers and what updates or enhancements require a new service. Have a qualified adviser review contractual responsibilities.
A web design estimate template can keep the phases and deliverables readable. After delivery, compare actual time by phase and record which assumptions caused overruns. Those facts give the next web design price list a stronger foundation than a generic price per page.
A few good questions
Before you get started.
Should I price a website by page count?
Page count is useful only alongside layout variety, functionality, content and review needs. A few complex pages can require more work than many pages using an approved pattern.
How do I handle missing customer content?
Specify who supplies copy and images and when they are needed. Price any writing, sourcing or migration you provide, and explain how late inputs affect delivery.
Is maintenance included in a web design fee?
Define any support period and its limits in the project quote. Ongoing updates, hosting and new features need a separate scope when you offer them.