Live · filed from a working practice automationdiary.com
RSS feed 03 · 06 · 2026
Volume I
— Filed from a working practice —
03 · 06 · 2026
automation/diary
est. 2026 · automationdiary.com
Automation, shown not sold.
Filed from inside real work
Cover story · §01 Workflows

The systems I actually run — including the parts that broke.

AI workflows documented from inside a working consulting practice — not tool reviews from someone who opened a free trial yesterday. What survives past the novelty. What I cut. What a senior professional should actually copy.

COVER STORY № 01 / WORKFLOWS
40min
gather → compress → provoke ↑ human · always
"Forty minutes, a real point of view at the end of it." p.3
Features

From this month's filing.

▮ 3 features
▮ 1 cover · 2 inside
Departments · the standing columns

Three sections.
One practice.

▮ updated as work allows
The machine is fast at "here are ten things." You are paid for "here is the one that matters."
— from File No.01 · "The research workflow that replaced my analyst"
The complete archive

Everything filed so far.

▮ 3 filed · 4 planned
TITLE DEPARTMENT EXTENT STATUS
№ 01 The research workflow that replaced my analyst §01 · Workflows 1,800 w · 9 min Live № 02 I tested 4 AI note systems for a year. I kept one. §02 · Tool Decisions 2,200 w · 11 min Live
№ 03 The meeting-notes-to-deliverable pipeline §01 · Workflows 1,900 w · 9 min Planned
№ 04 Why I stopped using AI for the part everyone uses it for §03 · Systems 1,600 w · 8 min Live
№ 05 My entire consulting AI stack — and what each costs me §02 · Tool Decisions 2,400 w · 12 min Planned
№ 06 The proposal-drafting system that tripled my output §01 · Workflows 2,000 w · 10 min Planned
№ 07 How to pick a tool when every review is an affiliate ad §02 · Tool Decisions 1,800 w · 9 min Planned
§04 · Field Outputs · latest from the workbench

The work, shown directly.

The standing promise · how this is made

What you can count on.

▮ the rules this is held to
"

Every workflow here survived real client deadlines before it was written up. If it's in the diary, it actually ran.

Editorial standardonly what is run
"

When something I tried didn't make the cut, I tell you — and exactly why. The failures are the most useful part.

Editorial standardfailures included
"

No sponsored issues. No paid placements. The day a recommendation here is bought, this stops being worth reading.

Editorial standard0 sponsored
"

Affiliate links are marked every single time, and I only point at tools I actually run in client work.

Editorial standarddisclosed always
▮ Written for consultants, operators, and independent professionals who put AI output in front of clients.
Browse the archive

By topic.

▮ 10 active threads
#client-research4 #note-systems3 #proposals2 #judgement5 #meeting-prep3 #tool-cost2 #failures6 #second-brain2 #disclosure4 #enterprise-systems2
THE OPERATOR
AD
About the archive

Filed from inside real work.

A highly experienced practitioner in enterprise systems and AI workflows — working at the intersection of complex client engagements and automation tooling. Not a full-time creator; someone with actual skin in the game.

Every system in this archive had to survive contact with real deadlines, real clients, and real consequences. That's the only filter that counts.

Voice
First-person practitioner
Standard
Only what is actually run
Failures
Always included
Affiliates
Disclosed every time

One real workflow, in your inbox, when it's ready.

No schedule. No filler. No sponsored placements. A new build goes out only when it's worth your ten minutes — usually every 2–4 weeks.

"I'll only send you something I would have written even if nobody paid me to. The day that stops, the newsletter stops."

Cadence Only when a build is worth your ten minutes
NewJust launched
2–4 wkBetween issues
0Sponsored ever