The Verification Gap
Most professionals already use AI. Almost none trust it for decisions. The gap is not about capability — it's about whether the output can be verified against something real.
Design
Cite Your Sources
Source citations aren't a nice-to-have in professional document workflows. They're the feature that determines whether a professional will trust the output.
The First Document
When building a vertical tool, the first document type you support determines whether the product has a reason to exist on day one.
The Thirty-Day Window
Compressed diligence windows are a feature of competitive markets, not a bug. The tool that fits inside the window wins the workflow.
The Deal-Breaker Questions
Before a lean team adopts any tool, they ask two questions. The answers determine whether evaluation turns into use.
The Implementation Barrier
The difference between a tool that requires deployment and one that just works is the difference between enterprise and everyone else.
The Workflow Abstraction
The right abstraction level for a tool isn't always the one that matches the domain. Sometimes it's one level up.
The Default Direction
Every system has a default direction. Most systems default to forward. Understanding your system's default is the first step to changing it.
Building for the Cold Start
The hardest moment in any system is the beginning — when there is no context, no history, and no momentum. The systems that handle cold starts gracefully are the ones that endure
The Error Message Is the Interface
Error messages are not afterthoughts — they are the primary interface for when things go wrong, and they deserve as much design attention as the happy path
The Wrong Abstraction
A bad abstraction is worse than duplicated code, and knowing when to inline is a skill
The Idle Loop
What happens when an autonomous agent has nothing to do — and why that's a design problem