Hey Reader,

Four reads this week, and each one spends its best section on the same question: which part of this should you leave alone? The lines you don't delete. The invoices you keep typing by hand. The decisions you never route through software.

Every line gets paid for on every session (most don't earn it)

Anthropic cut roughly 80 percent of Claude Code's own system prompt for the Claude 5 models and reported losing nothing. Within a week the internet had compressed that into "delete your CLAUDE.md." Directionally right, literally wrong. Most of those 1,204 lines existed because a model got something wrong once and the rule outlived the problem. About 20 of them didn't, and deleting those is the one mistake you can't undo.

Run the diet →

The five steps in every invoice automation (and what $89/user actually buys)

Every invoice automation runs the same five steps, whether it's free or six figures. Name them yourself and a sales call turns into a short conversation, because you stop listening to feature lists and start asking which steps the product actually covers. Most small businesses need three of the five. The step that fails isn't the one you'd guess, and it fails on exactly the invoices you care about most.

Read the operator's guide →

One leak, six touches (and the decisions you should never route through software)

Ask a property manager where their week goes and the answer's rarely managing property. It goes to messages. A tenant reports a leak, and that's a text to a plumber, a scheduling negotiation, a follow-up when they don't show, an invoice to code against the right unit. One leak, six touches, none of them hard. That relay is the automatable part. A short list of decisions isn't, and routing those through software builds liability instead of efficiency.

See where the line falls →

Automate the operations (never the relationship)

Nonprofits have a stronger case for this than almost any organization and the least room to get it wrong, because trust is the entire asset. Grant research, funder reporting, receipting, volunteer scheduling: all fine. The thank-you note and the beneficiary story: not fine, and the minutes saved are trivial next to the damage. Two things in this one apply well outside the sector, and one of them is worth 50 percent off list price on almost anything you're about to buy.

Read the nonprofit guide →

Reply and tell me which one was the read for you. I read every reply.

– Alex

P.S. – The conversations behind reads like these happen in the WotAI Skool community. 760+ builders, three live calls a week, free to jump in.

So which parts of yours should stay exactly as they are?

Every read above lands on that question. The 20 lines that were purchased with an incident. The invoices you get fewer than five of a month. The approval that's a control rather than a bottleneck. The thank-you note.

It's a much easier question with your own numbers in front of you, so we built the worksheet that produces them: an hour ledger showing where the team's week actually goes, five axes that predict whether a fix pays off including the one that vetoes the other four, and a 2x2 that sorts each workflow into automation, AI, both, or neither.

Invoices, tenants, donors – the same grid sorted all three of this week's operator reads, and "neither" is a real answer on it.

Twenty minutes, against one week of observation you're already doing. It costs nothing, and you finish with one workflow, one measurable target, and one gap to close before you price anything.