Module 01 · Business Evolution

Understanding why businesses change—and why that change creates opportunities for Rundown.

Overview

Businesses are not static.

As they grow, their customers, teams, capabilities, ambitions and market position evolve.

However, the way they communicate that business often evolves much more slowly.

This creates a gap between what the business has become and how the market perceives it.

Most projects do not begin because a business suddenly needs a new website or a new brand.

They begin because this gap has become large enough to affect confidence, credibility or growth.

Understanding this principle is the foundation of every Rundown engagement.

Core Principle

Growing businesses eventually outgrow the systems that helped them reach their current stage.

Growth changes expectations.

As expectations change, existing communication becomes less effective.

This is a natural consequence of business evolution—not poor execution.

Business Reality

Businesses evolve in many ways.

• Revenue increases.
• Teams expand.
• Services change.
• Customers become more sophisticated.
• Markets become more competitive.
• Decision makers change.
• Geographic reach expands.

Communication should evolve alongside the business.

When it does not, misalignment begins to appear.

Common Signs of Business Evolution

Business evolution is rarely announced.

It is recognised through patterns.

Common indicators include:

• The company has significantly grown in size.
• New services or product lines have been introduced.
• The target audience has changed.
• The business has entered a new market.
• Sales have become more complex.
• The company is pursuing larger clients.
• The leadership team has expanded.
• Recruitment has become a priority.
• Existing communication no longer reflects current capabilities.

These indicators should trigger deeper discovery.

Rundown Standard

RD-001 · Diagnose the business before discussing the solution.

Every engagement begins with understanding the business.

Never assume the requested deliverable is the actual problem.

Instead, identify:

• What has changed.
• Why the project exists now.
• What business objective is driving the request.
• Which communication, credibility or digital constraint has emerged.

Only then should recommendations be made.

In Practice

During discovery, the objective is not to gather project requirements.

The objective is to understand business evolution.

Every discovery conversation should answer five questions.

1. What has changed inside the business?
2. Why is this project happening now?
3. What happens if nothing changes?
4. What outcome is the business trying to achieve?
5. Which constraint appears to be limiting progress?

If these questions remain unanswered, discovery is incomplete.

Operator Notes

Good Question

"What has changed in the business over the last two to three years that made this project important today?"

Avoid

"How many pages do you need?"

or

"Do you have websites you like?"

These questions have value later.

They should not begin the conversation.

The Rundown Test

Before recommending any solution, confirm the following.

• I understand what has changed in the business.
• I understand why the project exists today.
• I know the business objective.
• I can identify the primary constraint.
• I understand what success looks like after implementation.

If any answer is No, continue discovery.

Do not recommend a solution.

Related Modules

Next

• Module 02 · Business Constraints

Supports

• Discovery Process
• Product Strategy
• Proposal Structure
• Website Strategy
• Sales System