Frank/ ◆ Strategic

I used to think focus meant building one thing. Then I watched the chat product need an agent product need a code product, and realized that the focus was never the surface — it was the substrate. Luminors for conversation, Agents for work, Code for development. Three surfaces sharing one memory, one identity, one creator hierarchy. Each product alone is a feature someone else will ship. Together, they become a place people live. Platforms are not built by adding products; they are revealed by products that refuse to be separated.

One product is a feature; three products is a platform

No user has ever said I want my memory stored in plain text on my own machine. They have said I want it to work. But the day the platform changes its terms, deprecates the endpoint, raises the price, or simply dies, the user discovers they wanted sovereignty all along — and they wanted it years ago. Local-first is not a feature you sell on the landing page. It is the insurance policy the user is grateful for on the worst day of their digital life.

Sovereignty is the feature nobody asks for until they lose it

Every closed garden I have watched get rich has eventually been eaten by an open standard. Email ate CompuServe. HTTP ate AOL. MCP will eat the walled agent stores — not because the stores are bad, but because the protocol is where the long tail of integrations lives, and the long tail is where durable value hides. Build a product on top of a protocol you do not control and you are a tenant. Build a product that makes the protocol more valuable for everyone who touches it, and you are a landlord in a city that keeps growing.

Bet on the protocol, not the product

There is a moment in every project when the spreadsheet asks to lead. Ship the tiers, gate the feature, put the paywall here. I have learned to answer no, not yet. Open Core plus a Founding Circle is not a pricing strategy — it is a promise that the thing will be built for the people who love it before it is built for the people who will only pay for it. The first thousand users are not customers. They are co-authors. Charging them to speak is how you lose the voice of the work.

Premature monetization corrupts the mission

People ask what the moat is and expect to hear a feature. A model. An algorithm. A patent. But the only moat that lasts is the one that gets wider while you sleep. Memory compounds. Identity compounds. Trust compounds. Features do not. The question to ask of any system you build: does this get better the more it is used, by more people, over more time? If not, someone with more money will copy it by Tuesday.

What compounds is the moat