Skip to content
Kevin

Notes

A running log of the stack.

First-person notes as the systems change. HUD stamps mark shipped, changed, and next. No client roster. No closed-deal theater.

shipped

Lots are not listings

A listing is one way a file becomes visible. The lot was already there: geometry, traces, land questions.

I keep catching myself talking about listings when I mean lots. A listing is a surface. The parcel has a shape, an owner history, and a set of land questions that do not wait for a photographer.

Read the note
changed

Comps are a process

I stopped letting the swarm return a neat set. The packet now keeps why a sale belongs, and where two sales pull apart.

A comp is not a price. It is a sale I am willing to stand next to this lot, plus the reason, plus the seam. If the swarm cannot say why a sale is in the set, it does not get to stay.

Read the note
next

Quiet files still count

A private path is still a file. Next work is the same packet, without pretending the lot is on the market.

Most software assumes a listing. A lot of the work I care about never gets one. The owner is not advertising. The signal is a conversation, a transfer, or nothing yet.

Read the note
next

The human gate stays in the close

Close is not an automated step. Next work is a faster packet: same decision, less scavenger hunt.

I am not handing close to the stack. That is the point of the gate. Agents can gather, link, and draft. They do not get to say the work is done.

Read the note
shipped

The stack starts at the parcel

Agents that do not know the lot are just chat. I wired research to parcel geometry, ownership traces, and comps.

Generic web summaries are easy and mostly useless on a real file. The lot has a shape. The owner has a history. The comps have a street, not a vibe.

Read the note
changed

Underwriting has to be inspectable

I stopped asking the stack for a single number. The packet now keeps sources, seams, and what could not be verified.

A clean score is a temptation. It looks like underwriting and hides the argument. I do not want an 84 of anything on a lot I have not walked in my head.

Read the note
shipped

Follow-up without invented urgency

The loop drafts the next touch from the last real conversation. No fake scarcity. I decide when to reach.

Most follow-up software wants a drip. I do not. If the last conversation was quiet, the next note should be quiet too, or it should wait.

Read the note
changed

Signal before swarm

I used to fire every research agent at once. Signal first: what changed, why it matters, then the swarm.

A full swarm on a quiet file is just noise with better typography. I was burning context on lots where nothing had moved.

Read the note