Build and buy: why the smartest AI teams do both
Blog post from Lambda
Rising AI API costs have led enterprises to reconsider sending every workload to frontier models, with the text arguing that token budgets limit spending without addressing whether organizations receive sufficient capability for the cost. It proposes a “build and buy” strategy that combines closed frontier models for the most demanding tasks, such as long-horizon research and large-scale orchestration, with self-hosted open-weight models on reserved specialized-cloud compute for most routine production work. While building fully owned AI infrastructure can require substantial capital, power, cooling, and engineering investment, renting all usage through APIs leaves costs, availability, and product roadmaps dependent on external providers. The author contends that modern open-weight models have narrowed the performance gap sufficiently to handle roughly 90% of common workloads, offering more predictable fixed compute costs, greater privacy, resilience against provider restrictions, and opportunities to fine-tune models using proprietary data. The recommended approach is to evaluate existing workflows, retain frontier systems where they are demonstrably necessary or deeply integrated, and shift suitable high-volume tasks to controlled open-model deployments.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Serverless | 2 | 551 | 144 | 73 | -28% |
| Token engineering | 1 | 4 | 4 | 3 | 0% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.