When does the 'no framework' pattern beat reaching for LangChain or LlamaIndex?

The right way to think about framework choice is as a tax versus benefit tradeoff. A framework absorbs composition complexity, observability wiring, provider abstraction, and higher-order patterns like agent loops. In exchange you pay overhead. Extra dependencies, learning curve, type coupling, per-call latency cost, feature lag versus the underlying provider SDK. The no-framework pattern, raw provider SDK plus your own small composition layer, wins when the things the framework absorbs are not actually present in your codebase. Four concrete conditions tip the scale. First, small surface area: one or two prompts that you can hold in your head. There is no composition complexity for a framework to absorb. Second, day-one provider features: when you need OpenAI's brand-new capability this week, not in 4 to 8 weeks when the wrapper exposes it. Third, a one or two engineer team: you do not need a shared mental model across many contributors. Fourth, a tight latency budget: per-call overhead from callback dispatch and object construction matters at hundreds of QPS. The framework wins at the other end of the spectrum. Complex composition, multi-engineer teams, mature observability requirements, agent loops with many tools. The decision is not ideological; it is whether the tax is justified for your specific workload.

Frameworks earn their keep by absorbing four things: composition complexity, provider abstraction, observability wiring, and higher-order patterns like agent loops. The no-framework pattern wins when these absorptions are not actually present in your codebase. Four concrete conditions decide the call. **Small surface area.** Two or three prompts in total, no chain composition, no agent loop. There is nothing for the framework to absorb. A 60-line file using `openai.AsyncOpenAI` directly is clearer than 60 lines of `ChatPromptTemplate` plus `RunnableSequence` plus `StrOutputParser` for the same result. **Day-one provider features.** Provider SDKs ship new capabilities, OpenAI prompt caching, Anthropic computer-use, Gemini structured outputs, weeks or months before any framework wrapper catches up. If you need the feature this week, raw SDK is the only option. **Small team.** One or two engineers do not need a shared mental model imposed by a framework's conventions. They can hold the system in their heads. The framework tax is largest when the team is smallest, because the maintainer count is zero and you pay all the cost yourself. **Tight latency budget.** Per-call framework overhead, callback dispatch, object construction, type coercion, adds milliseconds. At hundreds of QPS with sub-second SLOs, that overhead is the difference between hitting the SLO and missing it. The framework wins at the opposite end: multi-prompt systems with complex composition, many engineers needing shared conventions, mature observability requirements, agent loops with many tools, RAG pipelines with rerankers and routers. The failure mode to avoid is reflexive adoption. Reaching for LangChain because everyone else does, on a project where the framework absorbs almost nothing, is paying tax for no return.