A website quote is only meaningful when it answers three questions: what will be built, who supplies each input, and what the owner will pay after launch.
Two proposals can both say “five-page website” while one includes conversion copy, forms, responsive testing, redirects, analytics, and launch support and the other includes only a template with placeholder text. Compare the working system, not the label.
Useful cost bands start with scope
A tightly scoped landing page can be the right low-cost choice when the business has one offer, one audience, and one primary action. A service website costs more because visitors need separate service explanations, proof, FAQs, contact paths, and sometimes location context. A revenue website adds payment, intake, booking, qualification, or automation.
Zendory currently lists fixed scopes at $495 for a landing page, $995 for a service website, and $1,750 for a revenue website. Those prices are not market averages. They are a transparent example of how scope can be packaged. A studio, freelancer, platform subscription, or custom agency may price the same need differently.
Complex ecommerce catalogs, membership systems, multilingual content, regulated intake, custom databases, and migrations belong in a custom quote because risk is driven by workflows and data, not only page count.
The nine items that drive the real price
- Strategy: audience, offer, primary conversion, information architecture, and success measurement.
- Copy: whether the owner provides final text or the builder researches, structures, and writes it.
- Design: template adaptation versus a custom system of layouts and components.
- Content volume: unique services, locations, proof, FAQs, team material, and policies.
- Conversion paths: calls, forms, booking, quoting, checkout, lead routing, and confirmation states.
- Integrations: CRM, email, calendar, payments, analytics, reviews, inventory, or external APIs.
- Migration: preserving important URLs, media, metadata, redirects, and measurement during a rebuild.
- Quality assurance: responsive layouts, keyboard use, forms, browsers, performance, and error states.
- Ownership: hosting, subscriptions, maintenance, updates, support, and the cost of future changes.
Calculate the complete first-year cost
Add the build fee, platform subscription, hosting, domain, premium plugins, paid fonts or assets, email tools, third-party booking or ecommerce fees, maintenance, and expected change requests. Then identify which costs repeat in year two.
A lower build fee can become the expensive option if every text edit requires a paid ticket or if a plugin stack needs constant maintenance. A higher fee can still be poor value if it buys visual polish without a clear call, quote, booking, or checkout path.
Ask for a line that states what you own. The domain, analytics property, business listings, copy, photography, and platform access should not become bargaining chips at handoff.
Do not treat launch fundamentals as optional extras
A business site should ship with crawlable navigation, descriptive titles, one canonical version of each page, useful internal links, and a sitemap. Google recommends people-first content and clear page experience rather than a page built around search-engine tricks. Read the Google Search Central guidance on helpful content.
Accessibility is also part of build quality. The W3C WCAG overview organizes accessibility around content being perceivable, operable, understandable, and robust. A quote should include semantic structure, keyboard access, labels, contrast, and visible focus, then state what level of audit is included.
Performance should be measured on real pages, not promised as a vague score. Current Core Web Vitals focus on loading, interaction responsiveness, and layout stability; the web.dev metrics guide explains the field thresholds and why lab tools are only part of the picture.
Choose the smallest architecture that answers the buyer
Use one page when one audience needs one short path. Use multiple pages when each service has different proof, questions, qualification, or search intent. Do not create dozens of near-duplicate location pages simply to look large. Each indexable page should make a distinct decision easier.
A strong local service architecture often begins with Home, Services, one page per important service, About or Proof, FAQs where useful, and Contact or Booking. Add location pages only when the business truly serves and can describe those markets with unique evidence.
If the existing site already ranks or earns links, use the website redesign SEO migration checklist before changing URLs. The migration plan can be more valuable than another decorative page.
Ask these questions before comparing proposals
- Which exact pages and conversion flows are included?
- Who writes, edits, and approves the copy?
- What source material and access must the owner supply?
- How many revisions are included and what counts as a revision?
- Who configures analytics, forms, redirects, metadata, and the sitemap?
- What mobile, accessibility, browser, and performance checks are run?
- What is excluded, and how are additions priced?
- What renews after the first year?
- Who owns every account and asset at handoff?
For a live example, compare the inclusions and exclusions on Zendory pricing, then use the same checklist on any other proposal. The goal is not to make every vendor look identical. It is to reveal where the real scope differs.