── Thinking

Frameworks and POVs from the work.

Original frameworks I've developed and shipped. Each one came from a specific problem, then generalized. They're public because I'd rather argue with smart people about them than guard them.

── featured for marketer · Four-Layer Conversion Framework
framework · 01
featured

Four-Layer Conversion Framework

Every landing page is four stacked decisions - credibility, fit, value, trust - and conversion fails at whichever layer is weakest.

when it applies

Anywhere you're trying to figure out why a page isn't converting and ‘the copy’ isn't a useful answer.

  • ·Credibility · do they believe you exist and matter?
  • ·Fit · is this for them?
  • ·Value · is the trade obvious?
  • ·Trust · is the next step safe?
framework · 02

Context Engine architecture

Context, not tools, is the moat in AI-native services.

when it applies

Any services or knowledge company trying to use AI without losing its institutional intelligence.

  • ·Passive activity ingestion (captures what happens).
  • ·Active knowledge extraction via structured question protocols (captures why it happened).
framework · 03

Three-route channel architecture

For services companies selling into a concentrated buyer segment, three routes dominate, and they compound differently.

when it applies

Services GTM into a concentrated buyer segment.

  • ·Lookalike alliances (empirically dominant).
  • ·Direct executive relationships (high-leverage).
  • ·Portfolio outreach (visibility substrate).
framework · 04

Loop-driven marketing

Linear content engines produce output. Loop-driven engines compound.

when it applies

Any content operation that's been ‘publishing consistently’ without seeing compounding returns.

  • ·Every published piece becomes a context signal for the next, not a sunk cost.
framework · 05

Named-voice methodology

Generic executive profiles are worse than no profile. Voice extraction beats voice imposition.

when it applies

Personal brand work for senior leaders, especially in services.

  • ·Extract each person's voice from existing work, then write in that voice - don't impose a template.
framework · 06

Bucket voice guidelines

A content engine doesn't have one voice. It has buckets, each with its own protocol.

when it applies

Any organization publishing across multiple content types from one brand.

  • ·Thought leadership · Product · Case studies · Operator notes · Recruitment. Each gets its own voice rules.
── next

Want to argue with one of these?

Bring the counter-argument