Cost and scope guide
Custom Websites Scope and Cost Drivers
Custom Websites Scope and Cost Drivers organizes the decisions that matter for organizations planning a new website, redesign, portal, directory, or online service: the current workflow, ownership, implementation choices, rollout risk, and acceptance evidence.
Working artifact
Custom Websites journey map
Use this map to connect visible friction to the handoff, owner, and acceptance evidence that belongs to the custom Websites journey.
| Journey stage | Risk to inspect | Decision to document |
|---|---|---|
| Business and service website development | A template cannot support the required workflow | Responsive HTML, CSS, React and modern web stacks |
| Custom portals, directories and booking systems | The current site no longer represents the business | Laravel, PHP, Node and database backends |
| Responsive redesign and content architecture | Content and navigation have become confusing | Payments, booking, CRM and email integrations |
The five largest scope drivers
A template cannot support the required workflow. Confirm who encounters it, where it occurs, and what changed before it appeared. Then distinguish the visible symptom from dependencies such as responsive HTML, CSS, React and modern web stacks.
- Business and service website development
- Custom portals, directories and booking systems
- Laravel, PHP, Node and database backends
- Payments, booking, CRM and email integrations
- CMS and structured content architecture
What makes an estimate more reliable
For Custom Website Development, confirm account ownership, current exports or backups, recovery options, and recent changes before touching production. Preserve exact errors and timestamps that may disappear after a restart or update.
- Current-system inventory
- Representative user journeys
- Known constraints and deadlines
- Named decision owner
When phasing helps
Frame the first scope around business and service website development and one observable acceptance journey. Treat custom portals, directories and booking systems as a later phase unless the evidence shows it is a true dependency.
- Phase 1: evidence and risk control
- Phase 2: smallest useful outcome
- Phase 3: measured expansion
Estimate preparation checklist
Repair fits when the core remains sound. Extension fits when the boundary around responsive HTML, CSS, React and modern web stacks is understood. Replacement fits when ownership, architecture, or operating risk prevents a responsible change.
- Desired result
- Systems and vendors involved
- Access owner
- Examples and errors
- Definition of done