Choose the starting package by what the site must accomplish, how much distinct content it needs and which business systems it must connect.
Define the main job
- Present one focused offer
- Generate enquiries across several services
- Support deeper content and connected tools
- Sell products and manage transactions
Count genuine page requirements
A service deserves its own page when it answers different questions, speaks to a different audience or needs a distinct search and conversion path.
List the operational functions
- Enquiry forms
- Booking and availability rules
- Payments without a product catalogue
- Products, shipping, tax and fulfilment
Assign responsibility for content
Record what text, imagery, policies and product data already exist, who can approve them and where writing or upload support is needed.
Match the need to a starting point
- Launch One-Page for one concise offer
- Business Website for a structured multi-page presence
- Growth Website for deeper content and one agreed integration
- Online Store for catalogue and checkout requirements
Review the full commitment
Consider the build, optional care, provider subscriptions, ownership, handover, revision limits and the inputs needed to protect the schedule.
Warning signs in a proposal
- A decision based only on the lowest headline price
- No defined page or revision limit
- Unclear ownership after launch
- Recurring fees mixed into the build without explanation
Next step
Use the package builder to turn these decisions into a starting scope and estimate.