What to figure out before you ask for a website quote.

01

Start with a person, not a page list.

“We need five pages” says little about what the site needs to achieve. Start with the person visiting, the question they bring, and the action you want them to take. A founder looking for a partner and a returning customer looking for support need different experiences.

02

Name the first release.

Separate what is essential for launch from what can wait. A useful first release should complete a meaningful journey. It does not need every feature you can imagine. Write two lists: “needed to launch” and “possible later.”

03

Take stock of what exists.

Collect your current website, brand assets, draft copy, examples you like, and tools the website must connect to. List who owns each account and who can approve content. Do not put passwords or private customer data in a project brief.

04

Define what “done” means.

Use observable behavior. “Visitors can understand our three services and prepare an inquiry on mobile” is more useful than “make it modern.” Agree on the important journeys, the content to be delivered, and who will maintain the result.

05

Use this six-part starter.

1. Audience: who is this for?

2. Goal: what should they be able to do?

3. Scope: what belongs in the first release?

4. Inputs: what content and systems already exist?

5. Constraints: what timing, budget, or dependencies matter?

6. Success: how will you judge the finished work?

Talk through your idea with us