Skip to content
ImagineThis.Site

Guides

Planning

Plan the smallest effective website. Use the prompts below to clarify outcomes, audience, scope, proof, and practical choices. Then decide what to ship first.

How to use this

  1. Answer each section in 1 to 2 lines. Keep it simple and specific.
  2. Pick the smallest site that clearly serves your outcome.
  3. Ship that version, then add one proof item per month.
Abstract circle pattern suggesting structure and relationships
Visual: abstract structure map

Outcomes and audience

  • What is the one action a first-time visitor should take?
  • Who is this for, and what do they need to trust to move forward?
  • What problem are they trying to solve, in their words?
  • How do people find you now (search, referrals, events, partners)?

Decide the smallest effective site

One-page site

  • Clear intro, who it is for, proof, next step.
  • Fast to ship; strong for single-offer or early-stage.

Ask: Is one action obvious? What proof best supports it?

Case-study or portfolio

  • Home, about or approach, 2 to 4 case studies, contact.
  • Great for consultants, coaches, studios, and makers.

Ask: Which 2 examples best show outcomes and fit?

Content-led

  • Home, about, articles or resources hub, contact.
  • Works when you will publish regularly and compound trust.

Ask: What cadence is sustainable for the next 90 days?

Content and proof

What you already have

  • Client messages and common questions.
  • Slides, proposals, posts, talks, and notes.
  • Testimonials, outcomes, and before or after examples.
  • Images that show real work or context.

What to show

  • 2 to 4 short case studies with outcome and result.
  • Testimonials with a one-line context.
  • Logos only if they add clarity or trust.

Structure and navigation

  • What are the 3 to 5 core pages and in what order?
  • What is the primary next step on each page?
  • What do you remove to keep it focused and faster?

Editing rhythm and ownership

  • How often will you update content (rarely, monthly, weekly)?
  • Who will own edits and what feels natural for them?
  • What must be easy to change without friction?
  • Where will images and assets live?
  • What is your backup or versioning approach?
  • How will you review and publish changes?

Privacy, analytics, performance, accessibility

  • Any privacy constraints or tracking preferences?
  • Do you need analytics and what decisions will it inform?
  • What legal or compliance notes should appear?
  • Are pages fast and readable by default?
  • Is contrast, font size, and keyboard use considered?
  • Do images have alt text where it helps meaning?

Adjacent channels and integrations

  • Do you need a calendar for calls or sessions?
  • Would periodic email updates help compound trust?
  • Any simple payments or forms needed at launch?
  • Where else should key info stay accurate for discovery?

Budget, timeline, and success

  • What is the budget and the smallest scope that fits?
  • What is the deadline and what is truly required by then?
  • What can wait for a follow-up release?
  • What is your 90-day goal for the site?
  • What indicates it is working (signals, not vanity)?
  • What small habits will sustain it over time?

Launch and the next 90 days

  1. Ship the smallest effective site. Do not wait on perfect images.
  2. Share it with a small circle and collect specific feedback.
  3. Add one proof item per month (case study, testimonial, example).
  4. Review analytics lightly: what do people read and click?
  5. Decide on the next smallest improvement or page.