How much to charge for a website when the AI did the building

The published guides mostly agree on a shape. A small business website runs roughly one to eight thousand dollars from a freelancer and higher from a studio, with hourly rates between fifty and two hundred depending on who is writing and where they sit. Those numbers have not moved in years.

They are also numbers nobody sources. Every pricing guide in this genre states its ranges as fact, and not one cites a survey, a dataset or a sample. Treat them as the going rate of an opinion.

Your question is different anyway. You are asking because the build got short. What took a week of evenings takes an afternoon of prompting, and it feels dishonest to send the same invoice.

Here is the answer, and it is not a range. Your price is set by what the finished site is worth to the client and by what other people in your market charge. Your cost is set by your hours. AI moved the second number and left the first exactly where it was. AI made the site cheaper to build. It did not make it cheaper to buy. Cutting your price by the hours you saved hands the entire gain to the client, permanently, for nothing.

What freelancers actually charge for a website

If you need a starting point rather than a philosophy, these are the tiers the ranking guides publish. Each is named so you can weigh it yourself.

A one-page or landing site

Roughly $500 to $1,500. The Website Profit Course pricing guide puts a template-based one-to-three-page site at $500–$1,500. Self Made Web Designer cites $1,000–$5,000 for basic freelance sites.

A five- to ten-page business site

Roughly $2,000 to $8,000. Website Profit Course lists $2,000–$5,000 for a custom five-to-ten-page site. AgentSite's guide opens with "US freelancers charge $1,500 to $8,000 for a small business website in 2026 and agencies charge $8,000 to $15,000." Most solo work lands here, and so does this article.

Anything with a store, a booking flow, or a login

$5,000 and up, with no useful ceiling. Website Profit Course says $5,000–$10,000+. Prismic says a freelance developer "may charge $1,000 for a small website project and $10,000 or more for a larger" one. Once real functionality is involved the number stops being about pages and starts being about risk.

Maintenance sits alongside all three, commonly quoted at $100 to $500 a month. Hourly rates, where they are quoted, run $50 to $200: Website Profit Course says $50–$150, Prismic says $100–$200 in the US and $10–$30 in India, which tells you the hourly rate measures geography more than skill.

Where these numbers come from — and where they do not

Four of the ranking pages were read in full for this article. All four state dollar ranges with total confidence. Not one cites a source.

Dates are the other check. Wix Studio's pricing guide for designers is bylined 25 December 2024, written before an agent could produce a first draft of a site. Prismic's guide carries "2026" in its title and a publication date of December 2022.

This page has no better data, and neither does anyone else on the subject. There is no census of what freelancers invoice, only a circle of guides quoting each other until the ranges harden into common knowledge.

Your price and your cost are two different numbers

Obvious written down, and almost every pricing conversation ignores it.

Your cost is your hours times what an hour of your life is worth, plus the share of monthly overhead this project carries. Self Made Web Designer is the only guide that does the arithmetic: monthly costs divided by projects per month is the floor beneath which a project loses you money. Their example, $5,000 a month across three projects, puts it at $1,667.

Your price is what the site is worth to the buyer, bounded by what they can find elsewhere. A restaurant owner is not buying eleven hours of your attention. They are buying a thing that makes the phone ring.

One rule connects them: price must exceed cost. Above that floor they float independently, and your pricing model decides how tightly you tie them.

• An hourly rate ties them completely, converting every efficiency gain into a pay cut. Charge hourly and start using an agent, and you have already given the savings away.
• A fixed price per project does not break. The client agreed to a number for an outcome, the outcome is unchanged, and your margin is your business.
• Value-based pricing gets stronger, because it was never indexed to your effort.

Quoting fewer hours at the same rate is the worst of the three: it keeps the pay cut and adds an argument about timesheets.

What AI actually took off the cost side

Be specific, because vague claims here are how people talk themselves into vague discounts.

What got shorter: the first draft of the markup and styles, the standard sections you have built two hundred times, the first pass at the copy, the turnaround on "can we try it in green." Most designers carried a personal template library to shorten exactly that work, and an agent does the same job without the part where every project starts by fighting a template. Publishing got shorter too, the part where a finished folder needed an account, a build configuration and an afternoon of reading. That gap was never really about difficulty, and it is largely gone.

Call it a real reduction in the hours a website takes to build. It is why you are reading this. Where those hours went, stage by stage, is its own article; the short version is that the build shrank and the rest of the project did not.

And what it did not take off

Everything here still takes exactly as long as it did in 2023.

• The brief. Working out what the business sells, and to whom, before anyone writes a heading. A client who could answer that precisely would not need you.
• The parts that were never the build. Copy that sells rather than describes, the SEO groundwork, image optimization, the accessibility pass. An agent helps with all of it and finishes none of it.
• Getting content out of the client. The one that eats calendars. Nothing about an agent shortens the four weeks it takes someone to send their photos and opening hours.
• The decisions. What goes above the fold, what gets cut, when to say an idea will not work. An agent will happily build the wrong thing beautifully.
• Checking it on real devices. Not the preview.
• The handoff. The domain, the access, who edits it in March.
• Responsibility. If it breaks, they call you.

Look at where a client project spends its calendar and the build was rarely the largest block. It was the block that felt like work.

The hours you saved are not free hours

Two things quietly eat the savings, and only one is obvious.

The obvious one: reviewing what the agent produced. Reading it, catching the confidently wrong bit, fixing what it invented. That scales with how much you let it write unsupervised.

The less obvious one is that people are bad at measuring their own speedup. In July 2025, METR ran a randomized controlled trial on experienced open-source developers: sixteen developers, 246 real issues on repositories they had contributed to for years. Beforehand they expected AI to speed them up by 24%. Afterwards they believed it had, by 20%. Measured, they took 19% longer.

Run the margin math on your own numbers

The calculators in this genre ask your experience level and hand you a range. That is a horoscope. This takes ten minutes with your last invoice and tells you something true.

1. Step 1Start with what you chargedTake the price of your most recently completed project. One real number, not an average.
2. Step 2Count every hour it really tookInclude the brief, the calls, the chasing, the revisions, the handoff. Not just the hours that felt like production.
3. Step 3DividePrice divided by hours is your actual rate on that job. It is usually well below the rate you tell people you charge.
4. Step 4Subtract your overhead shareTake your monthly business costs, divide by projects per month, and subtract that from the price before you divide again. This is your real margin.
5. Step 5Now ask the only question that mattersRe-run steps two and three using the hours that project would take you today. Then ask how many more of those projects you can actually sell this month.

Step five earns the exercise. If a project took 40 hours and now takes 16, your effective rate went up two and a half times, but only on the projects you book. Saved hours convert to money only if there is demand waiting to fill them. Otherwise you have bought free afternoons, which no client pays for.

Almost every argument for cutting your price assumes you make it up in volume. Check that the volume exists. For most solo practices the binding constraint was never production capacity, it was finding the next client.

If you pass the savings on, you cannot take them back

A discount is not an event. It is a new number in a client's head, and in the heads of everyone they refer you to. Quote $1,200 for something you used to quote $4,000 for, and $4,000 is gone from that relationship and its referrals. Prices ratchet down easily and up with enormous friction.

There is a collective version too. Market rate is the average of what everyone in your market will accept, so if enough people index their prices to their build time, the band moves down for all of them and the tools that made the work faster transfer the surplus to buyers.

Where cutting the price is genuinely right: breaking into a new niche where you need two portfolio pieces more than the money; a deliberately cheap productized package with one page, fixed scope, one revision, used as a front door; a client whose budget is real and whose work you want. Those are decisions. Discounting because the software got faster is a reflex, and the client did not even ask.

What the site still costs to keep alive

The build is a one-time number. The site is not. Whatever you decide about price, do not let these fall off the invoice.

The domain has an annual cost somebody keeps paying, and the site needs an address with HTTPS, so pointing the client's domain at it is a step someone owns. Content updates after handoff are the forgotten item: changing one line on a live site is quick, and "quick" is not "free". Someone holds the access. And if you promised ranking, the SEO work does not stop on launch day.

Bundle maintenance into one monthly fee rather than itemizing, because one number is easier to sell than six.

One honest limit while scoping: a static site does not by itself receive a form submission or process an order. That needs a service behind the page, so know which side of the line the project falls on before you quote it, and decide early whether the client wants a site or an application. The economics here only hold for the first.

Where Birta fits

Birta is the publishing layer after the agent. The finished page goes live from the same conversation that produced it, at a real HTTPS address, and stays editable from there: change one file, publish again, roll back if the change was wrong. You can point the client's domain at it and see the project's traffic.

Where it stops: it publishes sites, not applications. Video and PDF files are not served. A connected agent can declare a contact form and get its submissions in the panel, so that line item is no longer separate work to price. Taking payments is not something Birta does, so price that accordingly rather than assuming the host covers it.

None of this changes what you should charge. It changes how many of the hours in step two are still there.

Frequently asked questions