Hook System
Module 07 · Hook System
Rundown uses a Hook System rather than relying on a single headline or slogan.
Different communication channels require different hooks, but every hook should express the same strategic positioning.
Purpose
This module establishes the principles that guide how Rundown captures attention.
Rather than creating a single marketing headline, Rundown develops a structured system of hooks that can be adapted across websites, proposals, outreach, presentations and future campaigns while remaining strategically consistent.
Core Principle
A hook should make the right client feel understood before attempting to sell a solution.
The purpose of a hook is not to describe Rundown.
Its purpose is to help the client recognise their own situation and continue the conversation.
Why This Matters
Businesses rarely respond to agency-first messaging.
They respond when they recognise their own business challenges.
By beginning with the client's reality rather than Rundown's capabilities, communication becomes immediately more relevant and engaging.
Rundown Definition
Hook
A hook is the opening statement that helps the right client recognise their current business reality and motivates them to continue the conversation.
A hook is not:
- A slogan.
- A tagline.
- A value proposition.
- A positioning statement.
It is the first step of a much larger communication system.
Hook Principles
Every Rundown hook should satisfy the following principles.
Recognition
The client should immediately recognise their current business situation.
Relevance
The hook should clearly relate to the challenges experienced during business growth or transition.
Curiosity
The hook should naturally encourage the client to continue reading or listening.
Business Focus
Hooks should describe business challenges and opportunities rather than creative services.
Strategic Consistency
Every hook should reinforce Rundown's positioning, regardless of the communication channel.
Hook Categories
Rundown organises hooks into reusable categories.
Growth Hooks
Used when businesses are experiencing growth or expansion.
Example themes:
- Growth outpacing communication.
- Increased expectations.
- New stages of maturity.
Transition Hooks
Used when businesses have evolved significantly.
Example themes:
- The business has changed.
- The external representation has not.
- Communication is no longer aligned.
Credibility Hooks
Used when businesses need to strengthen trust and perception.
Example themes:
- First impressions.
- Professional credibility.
- Market confidence.
Decision Hooks
Used to reinforce Rundown's methodology.
Example themes:
- Diagnosis before execution.
- Solving the right problem.
- Strategic thinking before creative work.
Practical Application
Different channels require different hooks.
| Channel | Recommended Hook Category |
|---|---|
| Website Homepage | Growth / Transition |
| Cold Email | Recognition / Decision |
| LinkedIn Content | Growth / Credibility |
| Proposal Cover | Transition |
| Sales Presentation | Decision |
| Landing Pages | Growth / Business Outcome |
The wording may change.
The principles do not.
Operational Standard
Before approving any hook, confirm that it:
- Begins with the client's business.
- Reflects Rundown's positioning.
- Creates curiosity without creating confusion.
- Avoids leading with services.
- Encourages the next step in the conversation.
If a hook primarily describes Rundown rather than the client, it should be rewritten.
Operational Impact
Website
Every landing page should begin with an appropriate hook category rather than a generic headline.
Marketing
Campaigns should select hook categories based on business context instead of using identical messaging everywhere.
Sales
Opening conversations should establish recognition before discussing solutions.
Content
Educational content should begin by identifying a business reality that the audience recognises.
Brand Consistency
All future hooks should reinforce the same strategic positioning regardless of wording.
Decision
Rundown adopts a Hook System consisting of reusable principles and hook categories.
Individual hooks may evolve over time, but every hook must remain consistent with the positioning established in this chapter.
Operational Checklist
Before publishing a hook, confirm:
Related Modules
- Module 04 · Category & Positioning
- Module 06 · Value Proposition
- Module 08 · Messaging Framework