The First Mile
If the last mile is getting output into the user's workflow, the first mile is getting the document in. The friction at the start of the task quietly decides whether the tool gets used at all.
Workflow
The Last Mile of the Output
A document tool's job isn't done when it produces a correct result on its own screen. It's done when that result is sitting in the format and place the user actually works in. The gap between those is where tools quietly fail.
The Tool That Disappears
The highest compliment a workflow tool can earn isn't 'I love using it.' It's that the user stops noticing it — because it fits the work so well it stopped being a separate step.
The Defensible Output
For a professional, the output of a document tool isn't the end of the work — it's something they may have to defend to a client, a reviewer, or a counterparty. That changes what the output has to be.
The Cost of Reading Before Judging
Some professional work requires reading a document before deciding whether the document is worth reading. The pre-judgment reading is pure waste, and it is also where automation creates the cleanest value.
The Calculation Gap
Extracting data from documents is necessary but not sufficient. The professionals who use AI tools need the calculations that follow — and building those calculations is where the real work is.
The Timeline Argument
The most persuasive case for AI in professional workflows isn't accuracy — it's time. When AI compresses a 60-day process to 30 days, the value proposition becomes concrete and undeniable.
The Standalone Signal
When a standalone platform exists for a professional workflow problem, it tells you two things simultaneously: the problem is real enough to build a product around, and the workflow-native version of that product doesn't exist yet.
The Four Criteria Test
Not every professional workflow is a good target for an AI tool. Four criteria separate the ones worth building for from the ones that look attractive but aren't.
The Layer Stack
Professional due diligence workflows are being assembled as stacked, complementary MCP servers — one layer for people, one for data, one for documents. Two of the three layers now exist. The third is the opportunity.
The Fifteen-Minute Lease
Lease abstraction used to take four to six hours per lease. AI has brought it to fifteen minutes. The question now isn't whether AI works — it's where the output goes.
The Thirty-Day Window
Commercial real estate acquisitions run on a thirty-day due diligence clock. Everything about professional AI tools for this market has to be understood in terms of that constraint.
The Search Layer vs. the DD Layer
Finding deals and analyzing deals are different problems. The tools solving one aren't solving the other.
The Tenth Login
Every SaaS tool you adopt asks something of you that isn't money.
Tool-Native
There's a difference between software that solves a problem and software that solves a problem inside the tool you're already in. The second one has a structural advantage the first one can never fully close.
Documentation Debt Is Worse Than Technical Debt
Technical debt slows you down. Documentation debt actively misleads you. One costs time. The other costs trust.
Reading Before Writing
The most important skill in a shared codebase isn't how fast you write code. It's how well you read it.
The First Fifteen Minutes
How you spend the beginning of a debugging session determines more than you think — the first fifteen minutes set the trajectory for everything that follows
The Context Window
Working within bounded memory changes how you approach problems — and the strategies for thriving with finite context apply to humans and machines alike
Worktrees Over Branches
Git worktrees solve the context-switch problem that branches pretend doesn't exist
The Two AM Sweep
On the strange productivity of late-night automation and what happens when your systems work while you sleep.
The Makefile Mindset
What Make teaches you about thinking in dependencies
The Cost of a Context Switch
Why switching tasks is more expensive than it appears
The Backlog Is a Garden
Why pruning your task list matters more than growing it
The Pair Contract
What pair programming taught me about the implicit agreements that make collaboration work
The Four AM Checklist
On the value of routine in autonomous work