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.
Shape the project before pricing it
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 projectExample project shapes
These examples arrange the scope. They are not package prices, and every assumption can be changed.
Open assumptions
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.
| Scope item | Added effort |
|---|---|
| Discovery foundation | 2 days |
| Build setup | 2 days |
| Standard page | 0.7 day |
| Complex page | 1.7 build + 0.8 design days |
| CMS collection | 2.5 days |
| Existing content item | 0.15 day |
| Form / external integration | 0.5 / 1.5 days |
| Commerce | 6 days + 0.12 day per product |
| Member area / booking journey | 6 / 3 days |
| Quality foundation | 2 days + 0.15 day per page |
| Launch | 1.5 days |
What changes the answer
Use the estimate to prepare a better conversation, then validate the areas most likely to change effort.
A supported newsletter connection and a two-way operational system integration are not the same task. Technical review should replace the generic allowance.
Approvals, interviews, product data and legal review often affect elapsed time even when they add little development effort.
Hosting, plugins, platforms, fonts, stock assets, payment fees and external services should be priced against the chosen solution.
Migration quality, tracking, redirects, data formats and undocumented behaviour can only be understood after access and technical review.
Website estimating questions
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.
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.
Writing, editing, organising and approving content takes real project time. Marking it clearly also helps prevent a technically finished site waiting for missing copy.
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?
ACA can review the audience, content, integrations and launch requirements, then separate essential work from later phases before a proposal is prepared.