A public presentation website introduces information and directs people to a next step. A custom application also manages logic, private data or transactions. Recognizing the difference early helps avoid a page that looks like a complete service but cannot safely perform the promised work.
Identify what happens after a click
Reading services, viewing projects or opening a public resource can fit a presentation website. Taking a payment, reserving live inventory, signing into an account or handling private records adds requirements beyond the visible page. Write down the complete action and the information it uses, rather than describing only the button or screen.
Consider responsibilities beyond design
A transactional feature may need authentication, permission rules, provider integration, error handling and ongoing operations. Private or regulated information adds further review needs. A generated form should not collect sensitive data simply because it can draw an input box. A convincing interface is not evidence that the underlying system exists.
Use external services intentionally
A clear link to an existing booking or payment provider can be different from building those capabilities into your website. Confirm that you own or manage the destination and that it supports your actual process. Tell visitors when they are leaving the site. Do not imply that a linked provider is automatically configured or endorsed.
Write a useful Custom request
Describe the intended users, their main tasks, information involved and any existing systems. Explain whether payments, accounts or private records are required. Add constraints and questions, but avoid sending secrets, bank details or identity documents through a general request form.
VollSite routes unsupported automatic-generation features to Custom review. A Custom submission is a request for manual evaluation, not an instant quote, payment or delivery commitment. The owner reviews requests separately. Keep the public presentation scope honest while the more complex work is assessed, and never publish a simulated payment or login experience as if it were an operational service.