Skip to Content
Learn

What a site needs

Define audience, goal, primary action, and trustworthy content before generating a website.

What a site needs

A useful website answers four questions visitors can sense in seconds: who it is for, what it offers, why it is credible, and what to do next. This lesson helps you settle those decisions before you write a brief or generate in Creator.

The previous lesson aligned shared language for domains, pages, and publishing. This one turns to decisions: who the first launch serves and what success means.

Learning goals

  • Name one primary audience and one secondary audience at most.
  • State one business or product goal for the first launch.
  • Choose a single primary action (contact, book, buy, apply, subscribe).
  • List facts that must be true and verifiable on the public site, and mark what must never be invented.

Key ideas

Audience before messaging

  • The primary audience is a real decision-maker (for example, “founders of growth-stage tech companies”), not “everyone” or “potential customers.”
  • Allow at most one secondary audience (for example, investors or partners). If their needs conflict, first launch follows the primary audience.
  • Specific audiences keep later headlines, case studies, and form copy from drifting.

One goal for the first launch

  • Keep a single business goal for v1: book a consult, request a quote, complete a purchase, submit an application, or build brand recognition.
  • “Sell, hire, and brand at once” belongs in phases, not in one first launch.
  • The goal decides whether the page set is enough; it is not a feature dump.

One primary action

  • The primary action is the one step visitors should complete—usually the button label (“Book a demo,” “Get a quote,” “Contact us”).
  • Secondary links can exist (for example, “Explore services”), but the primary action should be obvious on the home page and key conversion pages.
  • Too many equal-weight CTAs leave visitors unsure what to click.

Trust before decoration

Names, metrics, certifications, prices, and customer stories on a public site must be verifiable facts.

  • Include what you can source: legal name, location, service boundaries, real cases, quotable testimonials.
  • Omit what you cannot source: invented clients, unverified win rates, industry rankings, exaggerated outcomes.
  • Visual polish can wait; wrong facts cost more once published.

Scope control

  • A clear small site beats an incomplete large one. Keep the path “understand → trust → act” complete.
  • Blog archives, large case libraries, and multi-line product detail can wait if assets are not ready—label them “later,” do not block launch.
  • Scope feeds the next lesson on page types; lock audience and goal here so the page list has a reason.

Example (illustrative only)

Primary audience: founders and legal leads at growth-stage tech companies.
Launch goal: book a first consult.
Primary action: book a consult.
Must verify: full company name and city, service boundaries, public-safe team bios; do not invent client names, win rates, or industry rankings.

You can later fold almost the same text into a Creator brief. This lesson practices clarity first; the manual covers the product steps.

Practice

Write four bullets for your own first launch:

  1. Audience: one primary (optional one secondary).
  2. Goal: one business or product goal.
  3. Primary action: one sentence for the button.
  4. Facts: at least three facts to verify before publish, plus at least one claim or metric that must never appear.

Self-check: could a stranger tell from these four lines who the site is for and what they should do?

In the product

When you are ready to turn this into a brief Creator can use, follow the manual (entry points, structure, submit):

Next lesson: Page types and structure.

Last updated on

On this page