Module 06 · Strategic Boundaries

Focus creates expertise. Boundaries protect focus.

Overview

Not every business problem belongs to Rundown.

Not every client is the right client.

Not every project should be accepted.

Strategic boundaries exist to protect the quality of our work, preserve our positioning and ensure that Rundown continues building expertise rather than accumulating unrelated services.

Every opportunity should be evaluated against these boundaries before a proposal is prepared.

Core Principle

Rundown deliberately chooses depth over breadth.

We would rather become exceptional in a clearly defined area than average across many.

Growth should never come at the expense of focus.

What Rundown Owns

Rundown specialises in reducing constraints related to:

• Business communication
• Brand clarity
• Digital credibility
• Website experience
• Visual communication
• Brand consistency
• Communication systems

These represent our core expertise.

What Rundown Supports

Some business objectives are influenced by our work but are not owned by us.

Examples include:

• Marketing performance
• Lead generation
• Sales enablement
• Customer acquisition
• Employer branding

We contribute to these outcomes but do not claim responsibility for them.

What Rundown Does Not Own

The following areas are outside Rundown's strategic scope.

• Product-market fit
• Product quality
• Operations
• Finance
• Human resources
• Legal
• Manufacturing
• Organisational restructuring

Where appropriate, clients should be referred to specialists.

Projects We Decline

Rundown should avoid projects where:

• The requested work does not solve a meaningful business problem.
• Success cannot be clearly defined.
• The client is unwilling to participate in discovery.
• The project is driven solely by personal preference.
• Expectations cannot be managed honestly.
• The primary constraint lies outside our expertise.

Not every opportunity is a good opportunity.

Rundown Standard

RD-006 · Accept projects where Rundown can create measurable strategic value.

Every engagement should satisfy three conditions.

1. A meaningful business constraint exists.
2. Rundown has the expertise to reduce that constraint.
3. Success can be clearly defined.

If these conditions are not met, the opportunity should be reconsidered.

In Practice

Before preparing a proposal, ask:

• Is this the right client?
• Is this the right problem?
• Are we the right partner?
• Can we clearly define success?
• Can we confidently deliver value?

If the answer to any question is "No", pause before proceeding.

Operator Notes

Saying "No" to the wrong project creates capacity for the right one.

Protecting focus is a strategic responsibility, not a sales failure.

The Rundown Test

Before accepting a project, confirm:

• The project aligns with Rundown's expertise.
• The primary constraint is within our scope.
• Success can be measured.
• Expectations are realistic.
• The client is willing to collaborate.

If any answer is No, reconsider the engagement.

Related Modules

Previous

• Module 05 · Rundown Territory

Next

• Module 07 · Rundown Doctrine

Supports

• Qualification
• Sales System
• Product Strategy
• Pricing
• Client Success