Field notes on building and running software: what worked, what broke, and how AI changes the work.
Enterprise Claude bills are a design decision, not a rate you negotiate. The biggest lever isn’t a discount at all; it’s declining to put your whole corpus in context in the first place. A knowledge-graph approach like graphify is the sharpest example, and the rest of the stack compounds from there.
Owning a genuinely hard problem end to end as a product owner building through Claude: forecasting Bitcoin from my own full node, and making honesty about uncertainty the whole point.
Owning the brief as a product owner building through Claude: taking a single-user desktop tool and deciding, store by store, how to turn it into a real-time collaborative canvas that also covers CRM and agile.
A product owner’s bet that brand intelligence could be useful and private at once: set the brief, drew the no-cloud line, and built it through Claude into a self-hosted pipeline that reads the news and answers with citations.
Owning the brief end to end as a product owner building through Claude: how far a genuinely free stack can go when you decide that trust and provenance, not features, are the product.
Owning the brief on a five-model forecasting product and building it through Claude, where the real work was deciding what ‘honest’ had to mean before any number was allowed to ship.
In large companies the blocker to AI isn’t capability, it’s the Security and Legal sign-off. Here’s how Claude’s enterprise controls map to the questions those reviewers actually ask.
Why a governed, company-wide Claude rollout is one of the highest-return moves a company can make right now, from the chair of a product owner who ships and operates software, and now builds applications with Claude.
How a product owner’s job changes when AI does the building: your leverage moves to the brief, the guardrails, and the bar for ‘good’.
What this site is for: a portfolio of applications I owned from brief to production, increasingly built through Claude, and a running log of how I think and learn by building that way.