Essays - the reading surface
Essays for owners.
Essays argue, for owners: what changed, what breaks, what to do next, with every claim sourced. Each one ends with something you can do. If you read one thing, start with the essay. Operators: the whitepaper lives at its own door.
Nobody Buys Software Anymore. They Describe It.
AI collapsed the price of code and of encoded practice. It did almost nothing to operations and accountability. The real bottleneck moved to the person who can say precisely what they want, and that person is probably not in IT. The essay walks an owner through the change, the spreadsheet precedent, six honest failure modes, and five moves that ship a first build in days.
Read the essayThe rep who outgrew the CRM.
The ground-level builder is often in sales. The CRM told reps how selling was supposed to look: which stages exist, what counts as a deal, who owns the next step. The rep who is handy built their own layer, a quoting tool, a script writer, a research assistant, and the company runs on it. The rep is an asset. The unmapped build is a risk.
Read the field noteSomeone in your building is already building software.
The person who keeps the commission sheet has been writing software on your payroll for years. They are your first internal builder, not your risk. The danger is the unmapped estate, and the fix is to map it, not to stop it.
Read the field noteYou built it. Now you own it.
Building an internal tool is the easy part. Owning it is the job: the maintenance cliff, the verification gap, shadow IT, data gravity, liability. Each failure mode has one rule that contains it, and two rules set on day one do most of the work.
Read the field noteEssays for owners: argued, sourced, and honest about what breaks, written for the person who signs the checks. If you are the operator who would build the thing, the whitepaper shows the machine in enough detail to copy.