# Website Project Brief and Quote Comparison

Prepared by VASUYASHII. Updated 27 September 2026.
Service: https://www.vasuyashii.com/services/website-development

Copy this blank brief into your own document. Completing it does not submit anything to VASUYASHII. Share only the information needed for a scope discussion; exclude passwords, API keys, customer lists, personal addresses and confidential files. Use dummy records in examples.

## 1. Website purpose

- Public business name and current website URL:
- New website, targeted repair or redesign:
- Intended customers, countries and languages:
- Main visitor action: enquiry / call / booking request / RFQ / purchase:
- Business problem the first release should address:
- Launch dependency or preferred date:

## 2. Pages and content

| Page or template | Visitor question it answers | Main action | Content ready? | Approval role |
|---|---|---|---|---|
| | | | | |

- Number of distinct page layouts:
- Number of service or product records to enter:
- Copywriting, translation and image responsibilities:
- Approved brand assets and public proof available:
- Who updates content after launch, and how often:

## 3. One complete visitor journey

Describe the entry page, information needed, next action, confirmation and team follow-up.

- Context carried into the enquiry, such as a service or product:
- Minimum fields needed for a response:
- Destination for the saved request and notification:
- What the visitor sees if submission fails:
- Which roles need to view or follow up requests:

For a catalogue, define whether stock is descriptive or connected to a live system. For a booking request, distinguish an enquiry from a confirmed reservation. List payment, CRM and messaging integrations separately, including account and fee ownership.

## 4. Existing website and migration

- Public URLs that must be kept:
- URLs being replaced and their intended destinations:
- Existing analytics and Search Console ownership confirmed? Record status only:
- Required content or catalogue migration and approximate volume:
- Backup and rollback responsibility:

Do not paste credentials or private analytics exports into this brief.

## 5. Compare quotations on the same scope

| Item | Included work and quantity | One-time amount | Recurring amount / renewal date | Owner / exclusion |
|---|---|---|---|---|
| Discovery and page plan | | | | |
| Design and revision rounds | | | | |
| Development and content entry | | | | |
| Copy, images or translations | | | | |
| Migration and redirects | | | | |
| Forms and integrations | | | | |
| Domain, hosting and licences | | | | |
| Testing, launch and handover | | | | |
| Maintenance and later changes | | | | |

Specify currency, applicable taxes, payment milestones and third-party usage charges. Avoid counting an annual fee again if it is already included in the build quote. Leave unknown amounts blank until confirmed.

## 6. Acceptance and handover

- [ ] Approved pages, records and content are present on mobile and desktop.
- [ ] The agreed enquiry journey preserves its service or product context.
- [ ] A labelled dummy test verifies the saved request and team notification separately.
- [ ] Invalid or failed submissions do not appear successful.
- [ ] Existing URLs work or reach their agreed replacements.
- [ ] Titles, descriptions, canonicals, sitemap and indexing controls are checked.
- [ ] Analytics captures agreed actions without personal form values.
- [ ] Only approved public images, business information and evidence are published.
- [ ] Domain, hosting, source and account ownership are documented.
- [ ] Backup, rollback, support coverage and change-request terms are agreed.
- [ ] The approved build is checked at its public URL after launch.

These are scope and acceptance prompts, not a fixed package, legal agreement, ranking guarantee or customer-result claim. The final proposal should state inclusions, exclusions and dependencies.