The Framework Cannot Be the Product

The uncomfortable question anyone building in this space has to answer: even if you find the right patterns, how do you charge for them?

The framework itself cannot be the product. LangChain learned this. They open-sourced their agent framework and shifted commercial focus to LangSmith, an observability platform. The framework is the adoption vehicle; observability is the revenue model. E2B took a different path to the same conclusion — they sell the sandbox infrastructure where agents actually run.

Both arrived at the same structural insight. Give away the opinionated harness. Sell an indispensable piece of the stack that scales with consumption. The alternative — selling the framework itself — runs into the problem that frameworks get commoditized, forked, or absorbed by the model providers. When Anthropic ships built-in orchestration, framework-level features collapse into the model provider's product overnight.

So the strategic question is: what is the critical piece you sell alongside the free framework? It has to be something that gets harder, not easier, as the ecosystem matures. Observability gets harder because the systems get more complex. Sandboxing gets harder because security requirements escalate. Orchestration gets harder because multi-model, multi-harness workflows create session translation problems most teams underestimate.

The defensible move is to pick the hardest infrastructure problem — the one enterprises cannot solve with a weekend hackathon — and own it completely. I've argued separately that the harness matters as much as the model, but the harness is not where you make money. You make money on the part the harness depends on.