For a typical small-business website in 2026, I would think about the budget in four broad bands:
| Project shape | Useful planning range | What that usually assumes |
|---|---|---|
| DIY or builder-led | About $200 to $2,000 for the first year | You choose the structure, write the copy, make the design decisions, and handle setup yourself. |
| Light professional implementation | About $1,500 to $5,000 | A small, straightforward site with clear inputs, limited custom work, and little migration or integration work. |
| Full professional small-business build | About $5,000 to $10,000 | The provider owns more of the structure, design, setup, testing, and launch, with modest content or migration work. |
| Broader custom or migration-heavy build | About $10,000 to $30,000+ | More strategy, content development, custom patterns, integrations, migration risk, or coordination. |
Those are planning ranges, not a universal rate card. Forbes Advisor puts a DIY informational site at $0 to $450 to start, plus $15 to $150 a month for hosting and apps, with professional design starting at $1,500. Clutch puts a basic freelancer-built 5 to 10 page site at $500 to $5,000, and its broader pricing data says most reviewed web-design projects cost less than $10,000. Its small-business listings also show many $5,000 to $10,000 starting points, with broader custom work above that. The professional bands above are project budgets; hosting, software, and maintenance may be separate.
The important word in that table is planning. A $3,000 site and a $12,000 site can both be reasonable. The price only becomes useful when you understand what job each provider is actually agreeing to do.
Two proposals may both say “five-page website.” One may assume you are supplying final copy, an approved page structure, photos, and a straightforward technical setup. Another may include figuring out what the site should say, organizing the pages, moving content from the old site, protecting search traffic, connecting forms and tracking, and handling launch.
Those are not two prices for the same five pages. They are different jobs hiding under the same label.
Start with what the provider is actually responsible for#
Before comparing totals, compare assumptions:
| Part of the project | A lighter implementation may assume | A broader project may include |
|---|---|---|
| Content | Final copy, proof, and images are supplied | Positioning, messaging, copy, proof selection, and content development |
| Page structure | The page list and hierarchy are already decided | The provider determines what pages are needed and how they fit together |
| Design | An established template or design system is adapted | More page-specific design decisions or custom patterns are developed |
| Existing website | Little content needs to move | Content migration, redirect planning, search preservation, and cleanup are required |
| Technical work | Basic forms and standard platform behavior | Booking, payments, customer relationship management (CRM) connections, tracking, unusual content-management needs, or other integrations |
| Launch | The finished site is published | Launch testing, domain configuration, analytics continuity, vendor coordination, and post-launch support |
Neither side is automatically better. If a business already has strong copy, a clear page plan, good photos, and simple technical requirements, paying someone mainly for implementation can be entirely sensible. If those inputs do not exist, someone has to create or coordinate them.
The mistake is comparing the two as though the provider is only charging for the visible pages.
If you are still deciding what kind of provider should own the work, use the provider-choice guide. This article is about what makes the website project itself cost more or less.
Unresolved inputs and decisions change the scope#
“Website copy included” can mean light editing or developing the business's positioning from scratch. The same applies to page structure, proof, images, pricing language, and design decisions.
A provider can move efficiently when the offer, audience, page plan, source material, and approval path are clear. When those questions are still open, the project includes more than implementation. Someone has to make or coordinate the decisions before the finished site can be good.
Custom design works the same way. A mature component system can handle many common service-business needs without starting from a blank canvas. More custom design becomes useful when the content, brand, interaction, or information genuinely requires different patterns.
Technical complexity can hide behind a simple-looking page#
Two pages can look equally simple and require very different work.
A contact page with one basic form is not the same job as a page that sends leads into a CRM, assigns them correctly, triggers an acknowledgement, records advertising conversions, preserves source information, and behaves reliably across several systems.
Booking tools, payments, customer portals, analytics and advertising tracking, email or CRM integrations, gated content, and third-party systems add implementation and more places for a project to fail if the connections are not handled carefully.
An existing website can make the project harder, not easier#
A rebuild is not always a blank-slate design project. The current site may have pages receiving search traffic, old URLs that need redirects, analytics that should continue working, connected forms, content that has to move, or a domain controlled by another vendor.
That work can matter even when the new site has fewer pages than the old one. Replacing a brochure site that gets little traffic is different from replacing a site that already generates inquiries or ranks for important searches.
If you are still deciding whether the site needs replacement at all, use the rebuild-versus-fix guide first.
Page count and project coordination still matter#
More pages usually create more work, but pages are not equal units. Ten location pages built from one established structure may require less original thinking than four pages with different audiences, messages, proof burdens, and actions.
The way the project has to be run matters too. Several decision-makers, outside writers or photographers, legal review, hard launch dates, changing requirements, or multiple revision paths create coordination and risk that one-owner projects may not have.
Page count belongs in the estimate. It just should not be mistaken for a universal price-per-page formula.
Even similar jobs can be priced differently#
Two competent providers can look at essentially the same job and still charge different amounts because of experience, specialization, demand, efficiency, operating costs, geography, business model, and whether the work is being done by one person or a team.
Risk matters too. A provider who owns a difficult migration or several outside dependencies may price differently from someone whose responsibility ends earlier. Efficiency can move the other direction: an experienced specialist with strong systems may complete familiar work faster.
So a higher price does not automatically mean more work, and a lower price does not automatically mean less competence. Price by itself does not prove quality.
The same applies to pricing models. Fixed prices, project quotes, hourly billing, retainers, packages, and hybrids can all be reasonable when they fit the work. What matters is whether you understand what is included, what can change the price, and what happens when the work changes.
How I handle pricing at ZacWine.com#
I publish current pricing rather than making every buyer ask for it. Where the work is tightly bounded, I can publish an exact price. Where there is a reliable minimum, I can publish a starting point. Larger variable projects such as website builds may need a project quote after I understand the work.
For variable projects, we agree on the project price before I start. Hourly work can still make sense in special cases, but it is not the public or default pricing model.
Compare two quotes by assumptions and exclusions#
Put the two proposals side by side. Use the questions below to compare what's included, what you're expected to supply or handle, what another vendor needs to do, and what's still unclear. Ask each provider to confirm the important gaps in writing.
- Who is responsible for the copy? Are you supplying finished copy, is the provider editing it, or are they developing the messaging and writing?
- Who determines the site and page structure? Is the page map already decided, or is that part of the work?
- How custom is the implementation? Is the provider adapting a proven system, creating new page-specific patterns, or doing some mix of both?
- What happens to the existing website? Who handles migration, redirects, old URLs, analytics continuity, and anything that should not disappear at launch?
- What technical work is included? Forms, booking, CRM connections, payments, tracking, and third-party tools should be named where they matter.
- What is explicitly excluded? Photography, copy, hosting, plugins, paid software, ongoing edits, accessibility work, or outside-vendor work may sit outside the quote.
- What happens at launch and afterward? Ask who handles testing, publishing, domain changes, handoff, bug fixes, training, and post-launch support.
A lower quote can be the better fit if you are prepared to handle what it excludes. If that work still needs doing, account for who will do it and what it will cost before comparing totals.
When you compare website proposals, “How many pages do I get?” is reasonable. The more useful question is: What is this person taking responsibility for?
Once that is clear, the totals become much easier to compare. If you want to see how I currently price my own work, the ZacWine.com Pricing page has the current numbers.