Topic hub
Building things people trust, at the level of the details.
Product thinking and technical architecture for founders who ship: what to build, what to cut, how to reason about complexity, and why the boring engineering decisions quietly determine the outcome.
The next discovery layer isn't search or an answer engine, it's the agent's own catalog of callable tools. If a planner can't find and invoke your capability, you don't exist in the workflows leaving the human web.
An agent's planner picks tools by reading a name, a description, and an input schema, then betting on the best fit. Winning that bet is a craft, and it lives in the contract, not the marketing.
Agent capability is bounded by the action space and feedback you expose, not the model's raw IQ. Most "our agent isn't smart enough" complaints are misdiagnosed environment-design problems.
Most durable production value comes from small, specialized models doing bounded jobs under deliberate orchestration. That's not a budget compromise; it's often the more robust and defensible design.
Enterprises are re-running the RPA hype cycle with agents, and the thing that killed RPA — brittle integrations, dirty data, undocumented exceptions — is exactly what kills agents. The binding constraint is data legibility, not model quality.
Your database schema is a frozen set of assumptions about what your business is. Once thousands of features depend on them, they constrain strategy far more than your language or framework ever will.
Get new Tech & Product essays — and the best of the other six pillars — delivered as they publish.