For custom design and delivery, define what you need handed over before pricing the work. An example user task is more useful than a long list of vague features.
First-version scope
Define the pages and main workflow, then write acceptance criteria. Review revisions and timing in the selected package or approved proposal.
Files and ownership
Define handover files and usage rights for existing components. Portfolio display requires permission. Record separate terms for licensed marks or content.
After handover
Support duration and coverage differ across packages. Establish who maintains the work and how out-of-scope changes are priced. Agency services and the builder workflow are separate engagements.