Turning Something Off Without Killing It
The code is not wrong — it is early. The feature is not bad — it is premature. Two environment variables set to true and the entire pipeline comes back.
BuildingA Page That Moves
The marketing site worked the way a resume works — it contained the information without making you feel anything about it. Five waves of changes turned it into something that moves.
DesignManage Everything from One Place
A grid looks nice in a screenshot. Rows work better when you're scanning twenty clients for the one with a red indicator.
PlatformEach Feature Built on the Last
The pipeline summary was reporting 1,700 leads when the real count was 58. Not a hallucination — a missing WHERE clause. Every AI tool method had been querying everyone's data.
BuildingLater Arrived
A disabled: true comment in the action menu was the clue — this had been intentionally deferred during MVP. Ship the feature later. Later arrived.
BuildingPick Up Where You Left Off
Draw a polygon, measure a lawn, save the order. Come back a week later — the polygons are gone. Start over. Redraw every vertex. Hope you remember where the property line was.
BuildingThe System Knows Before You Draw
Before you draw a single polygon, the system now knows approximately how much lawn you're looking at — lot size minus structure, from two APIs firing the moment an address geocodes.
BuildingThe Widget Stopped Saying Come Back Later
The mobile widget used to say: this doesn't work here, come back on a real computer. Now it shows you a quote.
BuildingA Phone Book Is Not a Knowledge Base
The help page had been an accordion — functional in the way a phone book is functional. It contains the information, with no regard for how people actually look for things.
DesignAccepted but Not Paid
A customer accepts a quote. A green banner: 'You've confirmed your services.' Below it — nothing. No payment button. The gap between accepting and paying is where revenue leaks.
Building