How much does
a website cost?
How to read an estimate, compare proposals and plan costs after launch. We explain the scope of work, exclusions and an example budget with explicit assumptions.
Scope.
A result you can verify.
Compare more than the final figure: find out which pages, user journeys, integrations and deliverables the proposal includes. The tables and questions below help you build a concrete estimate.
How much does a website cost?
There is no universal price per web page. Two projects with identical menus may require very different amounts of work: in one, an editor changes text; in the other, customers see their own prices, stock levels and order history from a business system. A useful estimate therefore starts with the scope of the project, rather than an average figure found in search results.
iSEO.pro uses three starting price points for corporate websites. These are prices for our services, not market-wide statistics. We agree the scope, schedule and final cost after discussing the requirements.
| Option | Starting price | Requirements we discuss |
|---|---|---|
| Digital start | From $10,600 | A new website and digital foundation: key screens, responsive design, a CMS and basic analytics. |
| Business platform | From $17,670 | Multiple business areas, complex content, different enquiry journeys, a CRM and connected services. |
| Complex workflows | From $29,450 | Customer portals, user roles, data exchange with CRM or ERP systems and custom workflows. |
See our website development section. Licences, external services and ongoing maintenance are agreed separately. A starting price does not mean that every set of features fits that budget. A landing page, online shop or standalone service needs its own scope of work.
The brief version, deliverables, constraints, exclusions, stages and acceptance criteria. An offer that simply says “a turnkey website for one fixed amount” is difficult to compare or manage without these details.
Describe the work before requesting an estimate
Prepare a short project brief. Explain who the website serves, which products it presents, what visitors should do and where staff will receive enquiries. Specify who prepares the text, photographs and data. Even a good supplier cannot accurately estimate unknown content or an integration with a system they cannot yet access.
Count templates and states, not just URLs
Fifty similar product pages may use a single template. But one calculator page needs calculation logic, input validation, loading and error states, and a way to submit the result. In the estimate, distinguish page types, the number of pages to populate and functional modules.
| Too broad | What to clarify | Deliverable to estimate |
|---|---|---|
| “We need a catalogue” | Size, attributes, filters, search, data source and update frequency. | Category and product templates, filtering rules, import and a test dataset. |
| “Connect the CRM” | System, fields, pipelines, owners, authentication and error handling. | An enquiry-transfer workflow with a field list and confirmation that the record was saved. |
| “Make it look good” | Brand, references, content, devices and animation requirements. | A prototype, visual concept, set of screens and component states. |
| “Migrate the old site” | Pages, images, documents, indexed URLs and order history. | A migration plan, URL mapping, trial import and verification of the result. |
Label each feature: essential for launch, possible in a second phase, or still requiring research. This is more useful than promising to “build everything at once”. It shows which costs are necessary for the first working customer journey.
Which work should be visible in the proposal
An estimate need not reveal every internal team activity. But the client must be able to see what each stage delivers and how to verify it. The breakdown below helps identify omissions; it does not prescribe budget percentages.
| Workstream | Deliverable | What to clarify |
|---|---|---|
| Research and planning | Goals, audience, structure, user journeys and prototypes. | Number of interviews, depth of analysis and screens to prototype. |
| Design | Approved designs, responsive variants and interface states. | Design system scope, illustrations, animation and revision process. |
| Development | Working templates, CMS, components and features. | Supported browsers, roles and editing without a developer. |
| Integrations | Data exchange through agreed workflows. | API limits, access, test data and retries after errors. |
| Content and migration | An agreed number of populated pages and verified materials. | Who writes, who approves facts, and who uploads and processes images. |
| Search preparation | Indexing settings, URLs, metadata and sitemap. | What is included at launch and what belongs to ongoing SEO. |
| Testing and launch | Verified user journeys, deployment to the domain and defect resolution. | Devices, data, readiness criteria and rollback procedure. |
| Handover and training | Access, instructions and source files within the agreed scope. | Training format, responsibilities after launch and maintenance. |
“Basic SEO” particularly needs a definition. It might mean only being able to edit title tags, or it might include the section structure, URL migration and technical checks. The same applies to “integration”: a button that opens the CRM and reliable data transfer are different pieces of work.
Why costs can rise with the same number of pages
Custom logic
Personalised prices, different access rights, conditional price calculations and document approval need defined workflows and tests. Consider more than the happy path: what will users see without permission, when a service is unavailable, when there are no results or when a session expires? Include these states before approving the estimate.
Source data quality
Importing a tidy spreadsheet is different from migrating a catalogue with duplicate product codes. Give the supplier a small real sample before the estimate. It lets them check the structure, images, units of measurement and required fields. Saying “we’ll export the data later” pushes uncertainty into development.
Approvers and changes
A new product or order journey introduced after prototype approval changes related screens and tests. Appoint someone to consolidate feedback. Distinguish corrections needed to meet the brief from new requirements; both parties should understand where that boundary lies.
Migration and continuity
Replacing an existing website is more complex than launching on an empty domain: useful URLs, content, forms and analytics need to be preserved. When changing URLs, consult Google’s site migration guidance. The plan should map old pages to new ones, include redirects and provide for monitoring after launch.
What a transparent estimate looks like
Below is an illustrative breakdown of $18,000 for a corporate website. It is not a commercial offer, a set of market-average percentages or a promise that this scope fits every package. It shows how to check the arithmetic and connect costs to deliverables.
| Stage | Amount | Checkpoint |
|---|---|---|
| Research and requirements | $1,800 | Goals, constraints and requirements agreed. |
| Structure and prototypes | $2,160 | The journey from arrival to enquiry is clear. |
| Screen and component design | $3,120 | Designs and required states approved. |
| Development and CMS | $5,880 | The site works in the test environment. |
| Integrations | $2,160 | Transfer of the agreed data has been verified. |
| Testing | $1,200 | Critical defects in user journeys resolved. |
| Migration and launch | $960 | Domain, URLs and monitoring work. |
| Project management | $720 | A plan, demonstrations and a shared decision log are in place. |
| Total | $18,000 | Sum of the listed stages. |
For a real proposal, every line needs a quantity or a scope boundary. For example: “design — an agreed template list”, “content population — 20 pages using supplied materials”, “CRM — one system and two forms”. Without this, a detailed table is still just a detailed name for undefined work.
“Please send the deliverables for each stage, exclusions and conditions for revising the estimate. List separately the materials and access you need from us, who pays for external services and what will be checked at acceptance.”
Calculate the first-year cost of ownership
The launch budget and the operating budget are different figures. The latter includes recurring payments, updates, support, content production and business changes. Advertising and ongoing SEO are usually planned separately: having a website does not automatically generate visitors.
Development is only part of the total
Development: $18,000. Infrastructure and annual subscriptions: $1,440. Maintenance: $360 × 12 = $4,320. Additional content: $2,160. A separate reserve for changes subject to approval: $1,800.
Planned budget: $27,720. The reserve is not automatically treated as spent. This example excludes advertising; all figures illustrate the calculation method, not our maintenance prices.
When requesting prices, check the billing period, included taxes, limits, renewal terms and support scope. “$360 per month” without hours, responsibilities or response times does not tell you who will restore the site after a failure or build a new section.
- Domain and infrastructure: account owner, renewals, backups and server resources.
- Licences: CMS, modules, fonts, paid images and external APIs.
- Maintenance: updates, monitoring, defect fixes and the support request process.
- Further development: new pages, features, text, research and experiments.
The scope of technical maintenance is best defined before launch. This keeps the costs of maintaining a working site separate from the budget for new features.
How to compare two estimates for the same website
- Send the same initial brief. Give every participant the same list of pages, features, integrations and constraints.
- Put the deliverables in one comparison table. Mark each item as “included”, “charged separately”, “excluded” or “unspecified”. The last category must not be treated as free work.
- Check content and migration responsibilities. Find out what the client must prepare and how long that will take.
- Look at how quality is verified. A design demonstration does not prove that enquiries arrive or integrations work.
- Compare first-year costs. Add known mandatory payments and show optional improvements separately.
- Clarify the change process. Who estimates new work, how the budget is approved and how deadlines change.
A price difference may be justified. A team offering a narrower scope does not necessarily do worse work; a broader proposal is not necessarily a better fit. What matters is that the chosen work delivers the required outcome and that exclusions are deliberate.
What to check in the portfolio and meeting
Ask to see a project of comparable complexity and have the team explain its role. Discuss editing, integrations, errors and handover as well as appearance. Real constraints and a clear process are more useful than unsupported promises of “instant top rankings” or a “guaranteed conversion rate”.
Fixed price or time-based billing
A fixed price works well when the result and scope boundaries are already defined. New requirements still need agreement. Time-based billing suits work involving research and frequent reprioritisation, but needs transparent records, a spending limit and demonstrations of completed work.
| Model | What to agree |
|---|---|
| Fixed scope and price | Deliverables, assumptions, stage acceptance and the process for changing scope. |
| Time and materials | Rates, reporting, budget cap, priorities and the right to stop before the next phase. |
| Discovery, then a development estimate | A standalone discovery deliverable that can inform the next decision. |
Do not choose a model by its name alone. Short demonstrations, a clear task list and recorded decisions help under any arrangement. Contract terms and rights transfers are agreed separately; the table above describes project organisation and does not replace those documents.
Reduce the budget while preserving the core journey
Start by reducing uncertainty. Prepare product information and real photographs, and appoint one decision owner. Then remove features that are not needed for the first working customer journey. For example, an enquiry with an attached document may initially replace a complex portal, provided the business process really allows it.
- Use shared components for similar pages while retaining unique content.
- Test an existing module with a real workflow before commissioning a custom alternative.
- Move decorative effects and rarely used features to a separate phase.
- Approve the prototype before designing and programming every screen.
- Run a small trial import before migrating the entire catalogue.
Cutting essential checks of forms, mobile journeys or handover usually shifts costs to after launch. Define readiness criteria first, then decide which secondary features can wait. For acceptance testing, use the step-by-step checklist with testing tools.
What to send for a meaningful estimate
You do not need to write hundreds of pages of technical documentation before the first conversation. Provide enough facts for the team to ask the right follow-up questions. The more important constraints you uncover before the estimate, the fewer revisions it will need during the project.
Include a few references and explain what you like about them: the catalogue structure, clear offer or convenient form. “Make it like theirs” does not define the task or reveal the features behind the appearance. The design process is explained in our guide on creating a website that converts.
Frequently asked questions about website costs
Can you quote an exact price from a reference website?
A reference helps discuss the visual standard and visible structure. It does not reveal integrations, content volume or internal roles. An accurate estimate needs a defined scope and assumptions; a preliminary estimate should explicitly identify uncertainty.
Why is a ready-made template cheaper than a custom solution?
Some planning and interface work is already done. Configuration, content, integrations and testing remain. The saving lasts only while the ready-made solution fits the task without extensive, complex modifications.
Does development include promotion?
Technical search preparation and ongoing promotion involve different work. The development estimate should list the search settings and tasks to complete before launch. Regular work on demand, content and results is discussed separately as SEO.
Should planning be billed separately?
It depends on how the project is organised. For complex work, a separate phase can produce a structure, prototype and more accurate development estimate. Agree in advance which materials will be handed over and whether they can be used independently of the next phase.
How can I tell whether an extra charge is justified?
Compare the new task with the approved scope. Ask which deliverables change, how much work is added and how the schedule is affected. Defect corrections and new features should be treated separately under the agreed terms.
Can AI reduce the cost?
AI can speed up drafts, some illustrations and code preparation. Facts, rights, interfaces, integrations and outcomes still need verification. Assess the finished, tested result, not a promise to automate the entire project with one click.
LET’S ESTIMATE YOUR PROJECT
BASED ON ITS SCOPE
We’ll discuss requirements, content, integrations and constraints, then outline the scope and estimates for each phase.