# Next.js project brief

An original Ampliflow planning template. Version: 23 September 2026.
Source: https://ampliflow.ai/nextjs-development-agency#nextjs-project-brief

Copy this file into your preferred document editor and fill in the blanks.
This is not a quote, agreed scope, completed assessment or promise of results.
Leave unknowns marked as unknown. Do not add passwords, access tokens or personal customer records.

Project name:
Prepared by:
Date:
Current website, if any:

## 1. The business job

Who needs to use the website?
What are they trying to do?
What currently gets in their way?
What evidence shows this is a problem?
How would you recognise an improvement?
Why consider Next.js, and what simpler option should also be assessed?

## 2. The first complete journey

Where does the person arrive?
What do they need to understand or provide?
What happens when they complete the task?
What happens if information is missing or a connected system fails?
Who checks the journey on mobile, desktop and with a keyboard?

## 3. Content and connections

What must the team be able to edit without a developer?
Who approves and publishes changes?
Where does the information come from?
Which systems must connect, and who owns each connection?
What information is public, and what needs restricted access?

## 4. What must survive

Which existing pages and URLs matter?
Which forms, enquiries, content and search journeys need preservation?
Where is the current search and enquiry baseline recorded?
Who compares the replacement against the existing website?
Who can decide to postpone launch or restore the previous version?

For a migration, use the separate page-parity ledger:
https://ampliflow.ai/blog/wordpress-to-nextjs-migration-seo-checklist

## 5. Evidence for acceptance

For each important journey, record:
- Task to test:
- Expected result:
- Page or environment:
- Device and browser:
- Date and reviewer:
- Observed result:
- Evidence location:
- Unresolved issue and owner:

Keep proposed checks separate from checks that have actually passed.
Review editing tasks, accessible journeys, forms, search signals and performance.
A dated lab performance score is not a field measurement or a guarantee of future scores.

## 6. Ownership after launch

Who controls the domain, source code, hosting and content?
What access and handover evidence will be provided?
Who handles routine updates and failures?
What is included in the proposal and what requires a separate agreement?
Which third-party charges or ongoing responsibilities need clarification?
What remains excluded, undecided or dependent on someone else?

## Compare the proposals

Agency:
What it understood:
What it proposes to build:
What evidence it will provide:
Assumptions and exclusions:
Questions still unanswered:
Decision and reason:

Evidence guide: https://ampliflow.ai/blog/choose-nextjs-development-agency-uk
Technical release checks: https://ampliflow.ai/blog/nextjs-seo-app-router-checklist
Official production checklist: https://nextjs.org/docs/app/guides/production-checklist