1. Describe the customer and the useful action
Explain who needs the website and what they need to understand before they act. “Look more modern” is a preference; “make it easy for a mobile visitor to choose the correct service and call” is a journey that can be designed and tested.
- Business: what you do, where you genuinely serve and how you are different.
- Customer: who is making the decision and what they commonly ask.
- Primary action: phone call, qualified enquiry, booking or purchase.
- Evidence: approved work, genuine reviews and information you can substantiate.
2. Separate pages from functions
| Requirement | What to write |
|---|---|
| Content pages | Home, service explanations, evidence, about and contact; name each required page. |
| Functionality | Describe the form fields, booking steps or product options a customer needs. |
| Current site | Provide the URL and identify content or addresses worth keeping. |
| Integrations | Name the tool and business task, not only “CRM integration”. |
| Editing | Say who updates the site and which tasks must be straightforward. |
3. Assign content and approvals
- State who supplies text, images, logo files, product data and permission to use them.
- Name one person who can gather feedback and approve decisions.
- Identify any legal, policy or regulated claims that your business must check.
- Set out who controls the domain, hosting and relevant third-party accounts.
4. Include budget, dependencies and a sensible launch window
Share the available project budget and whether a monthly or one-off route is preferable. Explain any genuine deadline and what depends on it. Content readiness, approvals and external integrations can affect the schedule.
If the scope is uncertain, rank requirements as essential for launch, useful next, or optional later. That makes a staged approach possible without pretending every idea fits the initial package.
5. Define what “ready” means
- Agree the page list and the essential mobile journeys.
- Check forms and integrations using the agreed test process.
- Confirm the content, metadata and migration/redirect checks.
- Demonstrate the everyday editing tasks and document handover responsibilities.
- Agree ongoing care and how to report an issue after launch.
A short brief is enough to start
Send your current URL, business goals, essential pages/functions, content readiness and budget preference. CodingPie can then discuss the suitable service and the facts still needed for a quote. Use the contact email or telephone to send your brief.