3-5 pages, standard service structure, clean design, basic SEO, and a contact path.
- Focused page set
- Mobile-first design
- Basic on-page SEO
- Contact path

A practical pricing guide for planning a website rebuild. It will not replace a real scope, but it will help you understand what moves the number.
Three common shapes. Real scope is confirmed once we see the project.
3-5 pages, standard service structure, clean design, basic SEO, and a contact path.
6-15 pages, stronger copy, more proof, local SEO structure, and conversion-focused forms.
Multi-location content, e-commerce, booking, portals, dashboards, integrations, or app-like tools.
Send rough answers to a few questions and I can usually turn around a fixed-price scope within 48 hours.
A realistic must-have list beats a wish list. We can phase the rest.
Prepared content is the single biggest lever on both cost and timeline.
Simple routing is easy; connected pipelines and sequences add scope.
Transactions and accounts change the build from a site into an application.
Service-area structure and content programs are worth pricing separately.
Hosting, updates, and edits can be bundled so the site stays healthy.
Custom layouts, copywriting, integrations, large content migrations, multi-location SEO, complex forms, original photography, and approval cycles. None of that is bad; it just needs to be visible before the project starts.
A clear offer, a small first launch, reusable page patterns, prepared content, fast approvals, and a realistic list of must-haves versus later improvements.
Estimate the shape of the project
Ten pages built from two reusable patterns are different from ten pages that each need original research, copy, layout, media, and functionality. Use the factors below to decide whether your project sits near the lower or upper end of a range.
Lower complexity: approved copy, photos, proof, and page list are ready. Higher complexity: interviews, writing, editing, image sourcing, or stakeholder review are required.
Lower complexity: a small set of repeatable page patterns. Higher complexity: distinct layouts, interactive storytelling, original illustration, or a new brand system.
Lower complexity: a new site with few existing URLs. Higher complexity: a large content inventory, redirects, multi-location pages, or established search traffic that needs careful preservation.
Lower complexity: standard contact forms. Higher complexity: booking, payments, products, accounts, portals, dashboards, CRM rules, or third-party integrations.
Turn the estimate into a scope
Write down the pages and functions required for the first useful launch, then separate the later ideas. Note who will provide content, who approves it, which systems must connect, and whether an event or contract creates a real deadline. Share the current site and examples of the workflows that are failing.
The ranges on this page are starting guides, not an automatic quote. They do not account for every technical dependency, third-party fee, data problem, licensing requirement, accessibility requirement, or approval delay. A final scope should confirm what is included, what your team provides, and what would trigger a change.
Questions
The pages may require different research, writing, layouts, media, migrations, integrations, testing, and approval effort. Page count is only one scope signal.
Yes. A focused first launch can cover the pages and functions needed to explain the offer and capture demand, with later phases planned separately.
Only when stated. Website care, hosting, licenses, content changes, and future improvements should be priced separately or named clearly in the proposal.
No one can guarantee unchanged rankings. Existing URLs, content, links, metadata, redirects, analytics, and indexing should be reviewed carefully to reduce avoidable migration risk.