Shape the project before pricing it

Free website cost & scope estimator.

Turn pages, content, design, integrations and quality checks into a visible delivery range. Use your own day rate, see where the effort goes, and keep ongoing care separate from the build.

Estimate a website project

Example project shapes

Choose a starting point.

These examples arrange the scope. They are not package prices, and every assumption can be changed.

01 Pages and content

Count reusable page types separately from individual articles, products or case studies.

02 Functions and integrations
03 Quality and handover
04 Commercial assumptions

Use a rate that makes sense for the intended supplier or internal team. The example rate is only there to make the model usable.

Open assumptions

See how the scope becomes effort.

The estimator uses simple delivery-day allowances. They are deliberately visible so you can judge whether the model suits the project before using the range.

ScopeEffort rangeYour rate
Core delivery-day assumptions used by the calculator
Scope itemAdded effort
Discovery foundation2 days
Build setup2 days
Standard page0.7 day
Complex page1.7 build + 0.8 design days
CMS collection2.5 days
Existing content item0.15 day
Form / external integration0.5 / 1.5 days
Commerce6 days + 0.12 day per product
Member area / booking journey6 / 3 days
Quality foundation2 days + 0.15 day per page
Launch1.5 days

What changes the answer

A short form cannot reveal every dependency.

Use the estimate to prepare a better conversation, then validate the areas most likely to change effort.

Integration depth varies

A supported newsletter connection and a two-way operational system integration are not the same task. Technical review should replace the generic allowance.

Content can lead the schedule

Approvals, interviews, product data and legal review often affect elapsed time even when they add little development effort.

Licences remain separate

Hosting, plugins, platforms, fonts, stock assets, payment fees and external services should be priced against the chosen solution.

Existing systems need inspection

Migration quality, tracking, redirects, data formats and undocumented behaviour can only be understood after access and technical review.

Website estimating questions

A useful range starts with a useful scope.

Is this website estimate a quotation?

No. It is a planning range based on the scope, effort allowances and rate entered. A quotation needs a reviewed brief, technical dependencies, responsibilities and commercial terms.

What is a complex page?

A page with a distinct layout, substantial storytelling, interactive elements or unusually detailed content. Ordinary pages built from established components belong in the standard-page count.

Why is content readiness part of website cost?

Writing, editing, organising and approving content takes real project time. Marking it clearly also helps prevent a technically finished site waiting for missing copy.

Does the delivery window equal the effort?

Not exactly. Effort is working time; the window spreads it across calendar weeks. Client reviews, third-party responses and content approvals can extend the elapsed schedule.

Ready to validate the scope?

Turn the planning range into a clear website brief.

ACA can review the audience, content, integrations and launch requirements, then separate essential work from later phases before a proposal is prepared.

Explore website services