Preparing a WordPress project brief and quote

A useful project brief does not need to be long. It should explain the problem your website needs to solve and give both sides enough information to discuss the work. Mark uncertain items as “to be discussed” instead of inventing requirements.

Start with the audience and goal

Describe your business, the people you want to reach, and the most important next step for a visitor: understanding a service, sending an inquiry or buying a product. For an existing site, provide its URL and concrete examples of problems.

List pages and features

• Identify the pages, languages and content your team needs to edit.
• Explain any products, orders, bookings, memberships or external systems.
• List content, links and historical data that must be retained.
• Assign responsibility for copy, images, translations and brand materials.

Explain constraints and acceptance

Share a budget range, target milestones and hosting conditions, while distinguishing preferences from confirmed arrangements. A quote should identify deliverables, revision scope, third-party costs and ongoing care. Acceptance should cover the agreed mobile experience, content editing, inquiry storage and actual email receipt, as well as the visual design.

Common questions

Can I ask about an early idea?

Yes. Start with your business, goals and reference websites. We can then identify priorities and the information needed for a useful scope.

Should I send passwords with the brief?

No. Describe the management setup and who can authorize access. If a review requires login, arrange a suitable private handover separately.

Choose a starting point

Explore business websites, online stores, redesign or maintenance, then use your checklist to start the project conversation.