Website Packages
Pricing / Work & Pricing
Compare scope with confidence before discussing a price.
A short package name does not explain the requirements behind a website project. A useful comparison considers what is included, what the business supplies and what remains optional. This guide explains those decisions without creating priced tiers or contractual inclusions.
DECISION MAP / EXPLANATORY DIAGRAM
1
Website package inclusions
2
Content and revision boundaries
3
Scoping dependencies
The decisions that matter
Deliverables and review
Identify page and content requirements, functionality, review stages and acceptance criteria. State how additional requests are assessed rather than assuming unlimited revisions.
Dependencies and ownership
List required access, content, subscriptions and licences. Hosting, payment services and other third parties need an identified owner and a clear cost boundary.
Continuity after delivery
Testing, documentation, handover and any support period should be described in the agreed proposal. Maintenance and improvement should not be inferred from a package heading.
Questions to consider
Does this page offer fixed-price packages?
It explains how to assess scope. Fixed packages, amounts and inclusions should be offered only after their definitions and terms are approved.
Does this page confirm a price, result or availability?
Pricing is by custom quote only, based on scope and relevant dependencies. No fixed package, outcome, start date or ongoing commitment is established by this guide.
Prepare a useful project brief
Describe the current situation, the task you want to support and the decision you need to make. This local preview does not accept enquiries or personal information.