How Halo Thinks

Growth problems rarely begin where they first appear.

Over the last decade, working across publishers, agencies, consultancies and in-house leadership roles, in industries as different as fintech, travel, SaaS and children's entertainment, the same patterns kept turning up. Different business, same underlying problem, more often than not. Those patterns became the principles below.

Growth is usually constrained by systems before it's constrained by marketing.

Most businesses don't need more leads. They need fewer bottlenecks.

Reporting only earns its place if it changes a decision.

If a report doesn't change what happens next, it isn't doing its job. It's admin.

Build the protection before you need it.

The best systems prevent problems. They don't just measure them after the fact.

Reduce dependency by increasing capability.

The goal isn't to be indispensable. It's to leave a business more capable than you found it.

Complexity is only useful once it's simple enough to act on.

If a founder or a board can't act on it, the analysis isn't finished yet.

Capability should be built into people, not just into systems.

Dashboards don't grow a team. The people running them do.

The method should transfer across industries.

The industry isn't the expertise. The approach is.

Judgement sharpens by sitting in every seat at the table.

Publisher, agency, in-house, founder, each seat teaches something the others can't.

Responsibility should expand deliberately, not by accident.

Growth in scope should be earned and chosen, not something that just happens to you.

Unlike most consultancy values, these principles weren't written first and justified afterwards. They were distilled from recurring patterns across more than a decade of commercial work, then tested against the evidence before being adopted.

Want to see where your business sits against these patterns? Start with a free Commercial Diagnostic, or read how these principles played out in real engagements on Selected Engagements.