05 · 3D

Notes

Notes

Personal notes on methodology, thought leadership, and how we think about the work — including the thesis behind what we build.

05 · 3.1E
Aerial view of intersecting pathways suggesting divergent trajectories

The K-Shaped Company

ALG is a moat — but only when deployed across the full spectrum. And the companies that compound with it share a shape: two arms expanding outward from a single spine. Capability in one direction. Markets in the other.

Read →
05 · 3.2F
Abstract view of a workflow diagram mapped across a whiteboard

Acquisition, Activation, Evolution

Agent-led growth has three phases. Two happen to the client. One happens to the product. Getting the boundaries right between them is the whole design problem.

Read →
05 · 3.3G
Two people in conversation at a table, one listening intently while the other speaks

The Quiet Performer

Every high-performing team has two personas: the quiet performer and the loud performer. The dilemma is always the same. The strategy almost nobody uses is to crown the king before the king crowns himself.

Read →
05 · 3.4H
Overhead view of a strategy session with documents and notes on a table

The Three Fits

Product-market fit is a readout, not a target. The two fits you actually build are problem-market fit and prototype-market fit. Know which one is broken before you spend anything fixing it.

Read →
05 · 3.5I
Tower app interface showing a production-ready UI prototype

The Prototype Is Not the Product

The prototype is cosmetic. No data, no runtime, no connected systems. But it has to look production-ready — because a blueprint that looks unfinished produces an unfinished building.

Read →
05 · 3.6J
Developer working at a desk with multiple screens showing interface designs

Build from the UI

A methodology for building software products: start with the UI, derive the flows, map software to the flows, then build. The prototype is not the warmup. It is the blueprint.

Read →
05 · 3.7K
Empty chairs around a conference table in a quiet office

The No-Show Is the Objection

No-shows are not a memory problem. They are a consent problem. The objection was always there — the cold call just deferred it to a place where no one could answer it.

Read →
05 · 3.8L
Wide shot of a speaker addressing a large audience from a stage

The Greatest Salesperson

Everyone says the CEO is the ultimate salesperson. They are thinking too small. The politician does the same job at a higher stage, with higher consequence, while actively hiding that they are doing it at all.

Read →
05 · 3.9M
Minimalist office environment suggesting quiet authority

Predicted Mechanism, Observed in the Wild (Part One)

I posited that perceived consequence — not copy, not persuasion — is what drives response. This week I found an instance operating in the wild. And I found it by being caught in it.

Read →
05 · 3.10N
Overhead view of a business planning session with documents on a table

Problem Market Fit

Product market fit is something you can only measure after you have customers. Problem market fit is something you can validate before you build anything. That distinction changes everything.

Read →
05 · 3.11O
Abstract overhead view of a business meeting with documents and hands on a table

Outcome vs. Capability

Capability is the ability to do something. Outcome is whether that thing matters to anyone. Confusing the two is one of the most common and costly mistakes in go-to-market.

Read →
05 · 3.12P

Test post from n8n

Full-JSON pipeline smoke test — Claude-shaped payload, no LLM in n8n.

Read →
05 · 3.13Q

Hypothesis before headcount

Why we name the outcome first — then ship in milestones that prove value.

05 · 3.14R

Offer development vs positioning

Plain language we use with clients so scope and value stay aligned.