Start now
Back to Blog

Practical Guide•October 6, 2026•11 Min Read

Web Design Pricing for Freelancers: Price a Brief in One Session

Sketch of pricing tools around title

A web design quote gets clearer when you turn the brief into a list of pages, features, content responsibilities, review rounds, and launch work. In one focused working session, you can build a draft estimate and identify the questions that still need a client answer. If the brief is incomplete, price discovery or make the delivery estimate conditional rather than pretending the unknowns have disappeared.

TL;DR:

  • A fixed fee can suit a defined set of deliverables; hourly work or a paid discovery phase can suit open questions; a hybrid can separate the two.
  • Estimate the sitemap, features, content, integrations, revisions, testing, and handover by phase and role.
  • Make the proposal specific about deliverables, dependencies, fees, payment terms, exclusions, and how changes will be discussed.
  • Choose payment points that fit the project and agree them with the client before work starts.
  • When a request changes the work, document it, estimate its effect, and agree on price and timing before proceeding.

Table of Contents

Pricing Models: Fixed Fee, Hourly, and Hybrid

Fixed fee, hourly, and hybrid pricing each place uncertainty in a different part of the conversation. We've written about when value-based pricing actually fits a creative quote, too; here the immediate job is to price the website work the brief actually describes.

A fixed fee can work when the page templates, features, content responsibilities, and revision rounds are clear enough to estimate. If those details are still moving, hourly discovery gives you room to answer the open questions before setting a delivery fee. A hybrid might set a fee for the defined design and build, then price exploratory or ongoing support by time. For design-sector background, see AIGA's pricing models resource.

  • Choose fixed fee when you can describe the deliverables and assumptions in enough detail to estimate the work.
  • Choose hourly discovery when the client still needs help deciding what the site must do.
  • Choose hybrid when one part of the work is defined and another remains open-ended.
  • Discuss value-based pricing only when both sides can articulate the outcome and how the fee relates to it.

Estimation Workflow: From Brief to Defensible Number

Start with a checklist before assigning hours. Collect:

  1. Sitemap and templates. Count distinct page types as well as pages. Six pages built from two templates differ from six individually designed layouts.
  2. Features. Note forms, search, commerce, integrations, and animation. Describe the expected behavior, not just the feature name.
  3. Content status. Record who writes copy, supplies images, prepares product data, and approves final content.
  4. Revision rounds. Say which stages include feedback and how many rounds are included.
  5. Third-party systems. Identify the CMS, analytics, booking service, payment provider, or other integration and who supplies access.
  6. QA scope. Name the browsers, devices, accessibility checks, and content checks you plan to cover.
  7. Launch and handover. Include redirects, DNS coordination, training, documentation, and post-launch support where relevant.

Break the work into phases such as discovery, design, build, QA, and launch. Estimate hours for each role in each phase, including review and handoffs. Then review your labor costs, overhead, direct expenses, contingency, and intended price as separate inputs. If your hourly cost figure already includes overhead, do not add that same overhead again. Written quote guidance from the Australian Government also emphasizes describing the work, itemizing costs, and stating dates, variations, and payment terms; adapt those details to the client's project and location.

Pro Tip: Check the proposed fee against more than one plausible hours outcome. An estimate is a decision aid, not a promise that every task will take exactly the time assigned.

Say a five-page marketing site calls for design and development. Estimate both roles by phase, then ask whether content entry, integrations, testing, and launch are included in those hours. A scope-first AI estimation workflow can help you build a draft, but you still need to review the work and your own cost inputs.

Illustrative example: If a booking integration is still undefined, quote a discovery phase to map it, or state the integration assumption and what would prompt a revised estimate. That is more useful than burying an unknown inside a single website price.

Proposal Components: Make the Work Clear

A useful proposal gives both sides a shared description of the work. It may sit alongside a separate agreement, especially when ownership, licensing, or complex terms matter. Keep the project details concrete:

  • Overview: the client's goal and the proposed website outcome.
  • Scope: pages, templates, functions, and content responsibilities.
  • Deliverables per phase: what the client will receive and in which format.
  • Timeline: stages, review points, and dependencies on client material or approvals.
  • Fees: the priced work and any separately identified expenses.
  • Payment terms: amounts or percentages, due points, and invoice process agreed with the client.
  • Exclusions: work that is outside this quote, such as new copy or an additional integration.
  • Change process: how a new request will be estimated and agreed.
  • Ownership and licensing questions: assets, third-party licenses, and deliverable use that the parties need to settle.

Pro Tip: Write deliverables so the client can recognize them: "five responsive page templates with agreed browser testing" tells them more than "complete design."

If the client has a procurement process or standard agreement, compare it with the proposal early so the scope, fees, and delivery process tell the same story.

Payment Schedules That Fit the Project

Upfront payment, instalments, milestone billing, and payment on delivery are all possible structures. The right mix depends on the project's length, your cash needs, the client's purchasing process, and applicable rules. The Australian Government's guide to payment-term options lists several of these approaches without prescribing one deposit percentage.

  1. Discuss the start point. An upfront amount may suit work that reserves time or incurs early costs. Agree on the amount and trigger instead of assuming a standard deposit.
  2. Match instalments to recognizable stages. Discovery approval, design approval, or launch preparation can make payment points easier to understand than arbitrary dates, when that fits the project.
  3. Describe the final payment. State when the last invoice is due and what deliverables or acceptance step it corresponds to.
  4. Account for client administration. Ask about purchase orders, invoicing details, and payment cycles before locking the schedule.
  5. Put agreed terms in writing. Clear due dates and an invoice contact make follow-up more straightforward.

For a short project, an upfront and final payment might be simple. A longer project may suit several instalments. Our guide to proposal timelines can help align review and delivery milestones with the schedule you agree.

Scope Creep and Change Requests: Agree on Added Work

Exclusions make it easier to spot a new request. If the original quote includes five page templates and the client asks for a sixth, the question is what that page needs, who will produce its content, and how it changes the hours and schedule.

  • Record the requested change, including what prompted it and which deliverable it affects.
  • Estimate the added or removed work and its effect on price and timing.
  • Share the proposed adjustment and get agreement through the process set out for that project before proceeding.
  • Keep the revised scope and decisions in a record both sides can refer to.

Pro Tip: A simple running change log can keep several small requests from becoming one confusing conversation at the end of the project.

The Australian Government's guidance on documenting agreed changes recommends recording variations clearly. The exact approval method will depend on the project and agreement. Our tactics for preventing scope creep offer more ways to set the conversation up before delivery begins.

Common Additional Costs Beyond Design

Some website costs sit outside design and development labor. Hosting, domain registration, a paid CMS or plugin, and licensed assets may be paid directly by the client or purchased through the studio. Clarify which arrangement the quote assumes, who owns the accounts, and which charges recur.

Other possible line items include an outside copywriter, stock photography, fonts, specialist accessibility review, or a third-party service needed for booking or email. Some services bundle features that others charge for separately, so check the actual stack before presenting a cost as unavoidable.

List these costs separately from labor. An estimated expense, a client-paid subscription, and a studio fee are different kinds of number; showing them clearly helps the client understand the proposed budget.

Factors Influencing Pricing Variation

Two sites with the same page count can require different amounts of work. A site using established templates and a simple contact form is a different estimate from one with custom booking logic or a complex content model. The distinction is in the work described, not a generic multiplier for a feature label.

Content readiness matters, too. If approved copy, imagery, and product data are available, you can plan the production sequence more clearly. If they are still being developed, name who owns that work and how the website schedule depends on it.

Integrations need similar attention. Ask what system is involved, who provides access, what data must move, and how success will be tested. A familiar tool can still take time if permissions or data are missing.

Finally, find out who reviews the work. Several stakeholders may require more coordination or consolidated feedback. Estimate the review process the client actually plans to use.

Typical Pricing Ranges by Project Type

There is no useful universal price for "a website" without the deliverables, dependencies, and responsibilities behind it. A small brochure site, a content-heavy business site, and a custom commerce build can each involve very different design, development, content, and QA work. Their names alone do not establish a reliable fee or market range.

Build your own reference points from completed projects of similar scope. Record estimated and actual hours by phase and role, note outside expenses, and compare the assumptions that changed. Use that history as context for the next quote, while checking that the new brief really is comparable.

How Communication and Feedback Cycles Affect Pricing

Feedback takes time to receive, interpret, discuss, and apply. Specify how many rounds are included at each stage, who consolidates comments, and what counts as a new request. That makes the review work visible in the estimate.

Client response time also affects the schedule. If a launch date depends on copy approval or design sign-off, show that dependency in the plan. Avoid assuming every delayed response creates a fixed number of extra workdays; ask how the client expects approvals to happen.

Set a practical feedback window and discuss what happens if an approval is delayed for an extended period. The aim is a schedule both sides can use, with room to revise it when the inputs change.

Freelancer vs. Agency Pricing Differences

Team structure can affect a quote, but the label "freelancer" or "agency" does not tell you which proposal costs more. Compare the people doing the work, the responsibilities included, the review process, and the deliverables. A solo designer may bring in a developer or copywriter; a studio may have those roles in-house.

Ask what each quote includes: strategy, content, development, QA, project coordination, launch support, and any outside expenses. A lower initial fee can cover less work, while a higher fee may include services the client does not need. Compare like-for-like scope before judging the price.

Neither structure is inherently better. The useful comparison is the proposed work, the people accountable for it, and the support the client expects.

What We'd Tell a Friend About Pricing Confidently

Start with the brief, then write down what you know and what you still need to ask. If the sitemap, integration, content owner, or approval route is unclear, a discovery phase or a conditional estimate can move the conversation forward without treating guesses as settled work.

Show the client how the fee follows the phases, roles, and deliverables. When the proposed budget does not fit, discuss which work changes. That gives both sides a concrete decision instead of a blanket discount.

- Nicolas Robertson

Roadbase: Turn a Brief Into a Draft Proposal

Have a real web design brief ready? Paste it into Roadbase or attach a PDF to generate an editable first draft of phases, tasks, roles, estimated hours, and timing. Review and adjust the work, add your role rates and direct expenses, then check the costs and proposed price before exporting the reviewed plan and quote as a proposal PDF. Start a draft in Roadbase.

Freelancers can explore our freelancer estimates page, and teams with software consulting work can see the consulting-specific page. Check the current plans on our pricing page. Visit Roadbase when you are ready to turn your next brief into a quote you can review with the client.

FAQ

What's the best pricing model for a first-time web design client?

Choose the model that fits how much of the work is known. A fixed fee can suit a defined sitemap, feature list, and revision plan. If key decisions are open, start with paid discovery or quote that uncertain phase by time, then price delivery once the work is clearer.

How much should I ask for as an upfront deposit?

There is no single percentage that suits every project. Consider how much work or outside cost occurs before the next payment, the project's duration, the client's payment process, and local requirements. Agree the amount and due point before work starts.

What should a web design proposal always include?

Describe the pages and functions, deliverables, content responsibilities, review stages, timing and dependencies, price, payment terms, exclusions, and a process for discussing changes. If ownership or third-party licenses matter, address those questions in the agreement as well.

How do I handle a client who keeps asking for extra work outside the original scope?

Record each request and compare it with the agreed deliverables. Estimate the added hours, cost, and timing, then discuss and agree on the adjustment before taking it on. Keep a shared record so the next conversation starts from the same version of the work.

Do freelancers or agencies charge more for the same website?

Either can quote more depending on roles, scope, expenses, and support included. Compare the actual deliverables, who does the work, and which responsibilities each proposal covers rather than assuming one business type has a standard premium.

Recommended