When companies think about a website relaunch, they usually start with pages: homepage, product pages, maybe a few case studies.

That’s the wrong starting point.

A website isn’t a collection of pages. It’s a system designed to drive outcomes.
If you don’t define those outcomes upfront, everything that follows — design, structure, content — becomes guesswork.

At Allsite, we always begin with one question:
What should this website actually do for the business?

Define the primary outcome

Every high-performing website has one dominant goal.

In most cases, that’s pipeline generation — turning visitors into qualified leads.

This needs to be explicit and measurable:

• What counts as a lead?

• Where do conversions happen?

• What actions matter most?

Without this clarity, teams end up optimizing for the wrong things — clicks instead of conversions, traffic instead of pipeline.

Identify secondary outcomes

Your website doesn’t just serve marketing. It supports the entire company.

Secondary outcomes typically include:

• Attracting talent

• Building investor confidence

• Supporting sales conversations

• Establishing trust with all stakeholders

These are not secondary in importance — they shape perception before any interaction happens.

Translate outcomes into system requirements

Once outcomes are defined, you can turn them into concrete requirements.

For example:

• Lead generation → landing pages, clear CTAs, conversion flows

• Sales support → case studies, proof, structured product narratives

• Hiring → employer branding, role pages, culture signals

This is where strategy becomes buildable.

Align stakeholders early

One of the biggest bottlenecks in website projects is misalignment.

Different teams optimize for different things:

• Marketing → campaigns and conversion

• Sales → proof and credibility

• Leadership → positioning and narrative

Defining outcomes upfront creates a shared reference point and removes unnecessary iteration later.

Avoid the page-first trap

Starting with pages leads to fragmented thinking:
“We need a new homepage”
“Let’s redesign the product page”

Instead, think in flows:

• How does someone discover you?

• What convinces them?

• What action do they take?

Pages are just outputs of that system.

Our recommendation

Before you design anything, define:

• Your primary outcome

• Your key secondary outcomes

• The actions that define success

If this isn’t clear, the rest won’t be either.

Because the real question isn’t:
Does the site look good?

It’s:
Does it drive outcomes?