How Much to Charge for a Website

How much to charge for a website depends on which pricing model you use — fixed-fee, hourly, or value-based — and on scope: a five-page brochure site, a custom CMS build, and an ecommerce platform with inventory sync don't belong on the same price list. Rather than anchoring to a number you saw in a forum post, price from your own delivery cost plus a sustainable margin, and use your packaging to make the comparison with cheaper competitors harder for a prospect to make directly. Most web studios undercharge for the same reason most new service businesses do: it's easier to win a deal at a low price than to defend a higher one, and nobody wants to lose a prospect over a number. The problem shows up later, when a studio has a full client roster and still isn't covering its own overhead, because every project was priced to win the deal rather than to sustain the business. Getting pricing right starts with understanding what you're actually selling, and reviews that justify your rates are part of that story — a prospect comparing three quotes uses more than the number on the page to decide which one represents good value. Three ways to price a website: fixed-fee, hourly, and value-based Fixed-fee pricing quotes a single price for a defined scope — a specific number of pages, a specific set of features, a specific number of revision rounds — and is the easiest model for a client to budget against, since they know the total cost before work starts. The risk sits entirely on your side: if the project runs longer than estimated, you eat the difference unless the contract has a clear change-order process for anything outside the original scope. Studios that price fixed-fee well tend to be the ones with the most disciplined scope documents, not necessarily the most experienced designers. Hourly pricing bills for actual time spent, which protects you from scope creep but makes the total cost unpredictable for the client — a problem for clients who need to budget a fixed amount and a non-issue for clients who are comfortable with an estimate range that can move. Hourly works best for ongoing work with unclear scope at the outset — a redesign where the client isn't sure yet how much needs to change — and works worse for a well-defined new build, where a client reasonably expects to know the total cost upfront. Value-based pricing prices the website according to what it's worth to the client's business rather than how many hours it takes you to build — a lead-generation site for a business that closes high-value deals can reasonably cost more than a similarly-sized site for a business with thin margins per customer, even if the build itself is comparable. This model takes more selling skill to execute, since you're pricing around outcomes rather than deliverables, but it tends to produce the highest margins for studios that can credibly make the case. It also requires genuinely understanding the client's business economics, not just guessing at a number that sounds ambitious. Most studios end up using a blend: a fixed-fee quote for the initial build based on a clearly scoped set of deliverables, with hourly billing reserved for anything that falls outside that scope once the project starts. Whichever model you lead with, put it in writing clearly enough that there's no ambiguity later about what happens when a client asks for "just one more small change" for the fifth time. What actually drives the price A handful of factors do most of the work in determining what a website should cost, regardless of which pricing model you use: Page count and content complexity — a five-page brochure site with content the client provides costs meaningfully less than a twenty-page site with original copywriting, photography direction, and multiple content types. Custom design versus a theme or template — a fully custom design built from scratch takes more hours than adapting a well-built existing theme, and clients don't always understand why that difference matters until it's explained in terms of what custom buys them (a distinct look, no shared design patterns with competitors using the same theme). CMS complexity and client editing needs — a site the client's own team will update regularly needs a more thought-out content structure than a site your studio will maintain going forward, and that structural work is real, billable effort even though it's invisible to the client in the final product. Ecommerce and integrations — inventory sync, payment processing, shipping calculation, and third-party integrations (CRM, email marketing, booking systems) each add real scope, and each is worth pricing as its own line item rather than folding into a vague "ecommerce add-on" that undersells the actual work. Revision rounds — an unlimited-revisions clause, even phrased informally in a sales conversation, is one of the most common sources of a project that quietly runs over budget. Cap revision rounds explicitly in the scope document and price additional rounds separately. Pricing each of these as a visible line item, rather than bundling everything into one number, also makes a lower-budget client's options clearer — they can see exactly what gets cut if they need to come down in price, instead of assuming the whole project is simply unaffordable at your studio. Packaging into tiers clients can compare Most studios land on two or three tiers — a basic package (a template-based site with a handful of pages and client-provided content), a standard package (more custom design, more pages, a basic CMS setup for client editing), and a premium package (fully custom design, ecommerce or complex integrations, ongoing support included). Tiered packaging gives a prospect a menu to choose from rather than a single take-it-or-leave-it number, and it's an easier sales conversation than negotiating a custom quote for every single lead, especially for smaller projects where a custom quote process costs you more sales time than the project itself is worth. Resist the temptation to make the basic tier too cheap just to have a low number on your pricing page. A basic tier priced below what it actually costs you to deliver attracts exactly the clients most likely to ask for scope beyond what they paid for, since they're often price-shopping rather than evaluating studios on fit — and a studio that's used to defending its premium tier against full-scope comparisons has an easier time than one accustomed to negotiating down from an already-thin basic tier. Where reviews and case studies fit into the pricing conversation A prospect comparing three web design quotes is rarely comparing on price alone — if they were, the cheapest quote would always win, and it doesn't. What a client is actually weighing is risk: will this studio deliver what it promised, on time, without the project turning into a drawn-out mess. Reviews and case studies are the fastest way to answer that question before a prospect has worked with you directly, which is exactly why a studio with a thin, stale Clutch or Google profile has a harder time holding a premium price than one with a current, detailed review history. See our broader guide on reputation management for agencies for the mechanics of keeping that profile current across the review sites web studio clients actually check. A specific, detailed case study does more of this work than a generic client-testimonial quote. A prospect weighing whether to pay a premium price wants to see a studio that's solved a problem like theirs before, not just a studio that's generally well-liked — our agency case study template walks through building that out from a project you've already delivered, ideally pulling language directly from a client's actual review rather than writing a quote from scratch. A fictional illustration: a six-person studio, Harrow & Birch Design, spent a year quoting web projects at a flat rate regardless of client fit, losing a meaningful share of pitches to cheaper freelancers it couldn't credibly out-argue on price alone. After building three detailed case studies around its best-reviewed projects and routing every closed project through a consistent review-request step, Harrow & Birch started winning a noticeably larger share of pitches against the same cheap competitors — not because the price changed, but because the pitch now answered the risk question a bare price comparison never could. Raising prices without losing the clients you already have Pricing isn't a one-time decision made when you first set your rate card — most studios need to raise prices periodically as costs, demand, and the quality of their portfolio all shift. Doing this with existing clients, not just new leads, is where it gets uncomfortable, since a client who's been paying your old rate for a year didn't sign up expecting an increase. Give advance notice, explain the change plainly without over-justifying it with internal cost detail that invites an argument, and apply increases consistently across similar clients rather than negotiating a different number with everyone who pushes back. Our general guide on how to raise prices for a small business covers the broader mechanics of this conversation, which apply to a web studio's retainer clients as directly as to any other recurring service relationship. Beyond the build: maintenance and retainers The initial build is usually the smaller part of a website's lifetime value to a studio that also offers ongoing maintenance, hosting, or a retainer for continued updates. Price maintenance as its own clear offering rather than an afterthought thrown in for free to close the original deal — a studio that gives away maintenance to win the build ends up supporting sites indefinitely with no revenue attached, which is a quiet but real drag on margin over time. If retaining clients past the initial build is a priority for your studio, see our guide on agency client retention for the reporting and check-in habits that keep a client renewing a maintenance retainer rather than letting it lapse once the site launches and the relationship goes quiet. Scoping before you quote, not after A quote delivered before scope is actually nailed down is a guess wearing the costume of a number. The studios that price most reliably run a short, structured discovery step before any price goes to the client — a call or a written questionnaire covering page count, who owns content creation, whether the client needs ongoing editing access, and whether ecommerce or third-party integrations are in play. This takes real time upfront, which feels like friction when a prospect wants a fast answer, but it's cheaper than discovering mid-project that the client assumed photography was included when your quote assumed they'd supply their own. Put whatever you learn in discovery into a written scope document the client signs off on before work starts, even for a small project. A scope document doesn't need to be a long legal contract — a one-page summary of what's included, what's explicitly excluded, the number of revision rounds, and the total price is usually enough to prevent the single most common source of a disputed invoice: a client who remembers the sales conversation differently than you do once the project is underway. For larger or more technical projects — anything involving a custom integration, a migration from an existing platform, or a client with an internal stakeholder who wasn't part of the sales conversation — it's worth a short technical discovery pass specifically, separate from the scope-and-price conversation, so an unexpected platform limitation or data migration issue surfaces before you've already quoted a fixed price around an assumption that turns out to be wrong. Common pricing mistakes A few mistakes show up repeatedly across new and established studios alike. Quoting a price before scope is actually clear — before you know page count, content ownership, and whether ecommerce is in play — locks you into a number that rarely survives contact with the real project. Treating every client's "just one small addition" request as free, rather than logging it against the scope document and pricing anything beyond it, is how a fixed-fee project quietly becomes unprofitable without anyone deciding that on purpose. And competing primarily on price against studios with a fundamentally different cost structure — a solo freelancer working from home versus a studio with salaried staff and overhead — is a race that ends badly for the studio with higher fixed costs, regardless of how good the work is. Should I publish my pricing on my website? Publishing at least a starting price or a tiered range helps filter out leads who were never going to afford your work, saving sales time on both sides. Many studios publish tier starting points ("starting at") rather than exact prices, since scope varies enough project to project that a single published number rarely holds up without qualification. How do I compete against freelancers who charge much less? Compete on what a freelancer typically can't offer at the same scale — reliability if the freelancer gets busy with another client, a team that can cover illness or turnover without stalling the project, and a documented process the client can see before committing. Trying to match a solo freelancer's price directly usually means operating at a loss once your studio has any overhead at all. Is it better to quote a range or a specific number during a sales call? A range is usually more honest before scope is fully defined, and it sets expectations without locking you into a number you'll need to walk back once the full scope is clear. Move to a specific number only after you've confirmed page count, content ownership, and any integrations the client needs. Every review from Clutch, G2, Google and UpCity in one inbox → Try Tailwind free. Tailwind runs $5 a month per tool, or $50 a month for the Full plan covering everything, with the first month free and no card required to start.