01 / When a package fits
A package works when the outcome is already familiar
A defined package is a strong fit when the business needs a recognised structure, such as a focused one-page presence or a straightforward multi-page service website. The requirements can be described clearly and most of the work follows a repeatable delivery pattern.
Signs a package may fit
- The services and target customers are clear
- The site mainly needs to explain, build trust and generate enquiries
- Content can fit within a known page structure
- There are few or no custom integrations
02 / When custom makes sense
Custom scope is appropriate when behaviour drives the project
A website becomes a custom product when users need accounts, complex booking, personalised content, unusual transactions, substantial integrations or workflows that standard site features cannot support sensibly.
In this situation, early discovery is not an unnecessary fee. It is how the team avoids giving a confident price for requirements nobody has understood yet.
Signs to explore a custom scope
- Different users need different permissions or experiences
- Information must move between several systems
- The business process is unusual or changing
- Failure could have significant operational, privacy or financial consequences
03 / Finding the right scope
Choose the smallest scope that solves the current problem
A package should not be stretched until it behaves like custom software. Equally, a business should not fund a custom platform when a clear website and one standard integration will do the job.
Start by describing what a customer or staff member needs to accomplish. The appropriate structure usually becomes clearer once that outcome, its exceptions and its dependencies are visible.