Skip to content
ImagineThis.Site

Guides

Planning

You know you need a website. Now the question is what it should do. Planning does not mean having every answer in advance. It means getting clear enough to choose the right first version.

Use this to prepare for the conversation.

This page is not meant to become homework. It is a way to notice the decisions that matter most before a website takes shape.

  • Answer briefly. A sentence or two is enough.
  • Focus on what the site needs to accomplish first.
  • Bring rough notes, examples, links, or questions.
Abstract circle pattern suggesting structure and relationships
Visual: abstract structure map

What should the site do?

Every website exists to help someone take a step. The step might be booking a call, understanding your work, visiting a location, reading more, making a purchase, or deciding you are credible.

  • What should a first-time visitor understand within thirty seconds?
  • What action should they take next?
  • What would make the site successful in the next 90 days?

Who is it for?

A website works better when it speaks clearly to the people it is meant to serve. You do not need to define everyone. You need a useful sense of who matters most.

  • Who is the site primarily for?
  • What are they trying to understand, solve, or decide?
  • What would help them trust you enough to take the next step?

What belongs in the first version?

Many website projects become harder than they need to be because everything is treated as equally important. A strong first version gives the site a clear job and leaves room to grow.

Needs to launch

The pages, sections, or details the site needs in order to be useful immediately.

Can wait

Good ideas that may matter later, but do not need to slow down the first version.

Might not belong

Features, pages, or flourishes that add complexity without helping the visitor.

What proof already exists?

You may already have more useful material than you think. A first version of a website is often shaped from existing examples, messages, images, notes, and conversations.

Useful material

  • Client messages and common questions.
  • Testimonials, reviews, or informal praise.
  • Project examples, photos, outcomes, or before-and-after notes.
  • Presentations, proposals, posts, talks, articles, or drafts.

Questions to ask

  • What examples best show the quality of the work?
  • What do people usually ask before they are ready?
  • What existing material could be reused or reshaped?
  • What is missing, but important enough to create?

How will the site evolve?

Some sites stay mostly stable for years. Others grow through articles, events, resources, new projects, or changing offers. The expected rhythm affects the structure and the tools.

Mostly stable

Best when the site mainly needs to explain who you are, what you do, and how to begin.

Occasionally updated

Good for adding new proof, changing offers, updating photos, or improving copy over time.

Actively maintained

Useful when publishing, events, resources, memberships, or ongoing communication are central to the site.

Before we talk

You do not need a complete plan. A few rough answers are enough to begin a useful conversation.

  • What should the site help people understand or do?
  • Who matters most as the audience?
  • What examples, links, images, or materials already exist?
  • What feels confusing, missing, or unresolved?
  • What would make this project worthwhile in the next 90 days?

Bring your ideas, questions, examples, rough notes, or half-formed thoughts. We can shape the rest together.

The plan does not need to be perfect. It just needs to be clear enough to start.