the read, not the build.

// how i read it

• ground state. where the thing sits when nothing is pushing on it — the shape it wants.
• displacement. how far it has been pulled off that, and by what force.
• the cost of staying. what the current position quietly bleeds — attention, money, morale — every day it holds.
• the return path. the shortest honest way back, and the one move that opens it.

same lens the framework uses on a person, turned on a product, a system, an org. most stuck things are stuck for a reason nobody has named yet. the read names it.

// what i consult on

• systems — a process that leaks, an architecture nobody trusts, a workflow that fights you.
• product — a feature set that grew without a spine, a launch that won’t land.
• ai strategy — where a model actually helps, where it’s theater, what to build first.
• design — an interface, a page, a flow that says the wrong thing without meaning to.
• the stuck decision — the fork you keep re-opening because no frame made it small.

// what you leave with

• the diagnosis in plain words — ground state, displacement, cost of staying.
• the one move that matters, and why it’s that one and not the ten around it.
• a direction you can act on whether or not i ever touch the code.

if the honest answer is “build it,” i’ll say so — that’s a different offer (builds start at $3,500). consulting is the thinking that comes first. sometimes the read is the whole fix.

// pricing

by the session or by the engagement, depending on how deep the problem runs. reach out with what’s stuck and i’ll name a rate that fits the scope — and if it isn’t a fit, i’ll say so.