Observed Signal · Oct 21, 2026 · Analysis · Source: UX Collective · Impact: 1/5 · Sentiment: Neutral
Enterprise Buy vs. Build Decisions Now Require UX Input
The article by Patrick Neeman argues that the classic buy-versus-build decision in enterprise software has changed due to AI. Building is cheaper with coding agents, but yearly maintenance costs are often ignored. Buying is easier but includes a vendor's legacy, roadmap, and release calendar. The real trade-off now involves UX considerations: where complexity lands, how tools integrate with chat surfaces like Teams, Slack, and ChatGPT, and who controls the data. The author suggests budgeting 30% annually for build upkeep, testing vendors against prototypes, considering the hidden costs of replacement, and deciding based on whether the component is a commodity or a differentiator. Data residency and model retirement are also critical factors. The article cites various studies, including Menlo Ventures' 2025 report showing 76% of enterprise AI use cases were purchased, and METR's study on coding agent productivity.
The article provides strategic guidance on buy vs. build decisions in enterprise software, relevant to MarTech and AdTech infrastructure decisions, but it is not a specific industry news event.
Track Menlo Ventures Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your Polaris7 workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Menlo Ventures found that 76% of enterprise AI use cases were purchased rather than built in 2025, up from 53% a year earlier.
- A backdoor was introduced into the widely used XZ Utils library in 2024 after an attacker spent years earning the maintainer's trust.
- Google's 2025 DORA Report found that AI adoption still hurts delivery stability.
- METR's randomized trial with 16 experienced developers found they took 19% longer on real tasks with AI tools, yet estimated they were 20% faster.
- A 2022 study of 137 workers at three Fortune 500 companies found they switched between applications and websites about 1,200 times a day, costing nearly 4 hours per week.
Connected Companies & Entities
5 Entities mapped“Menlo Ventures found in its 2025 report that 76% of enterprise AI use cases were purchased rather than built.”
“Google's 2025 DORA Report found that AI adoption still hurts delivery stability.”
“OpenAI introduced apps in ChatGPT and the new Apps SDK in 2025.”
“Anthropic announced the Model Context Protocol in 2024 to connect models to data.”
“IBM surveyed 8,584 technology professionals for its Global AI Adoption Index.”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Framework for Engineering Build-vs-Buy Decisions
This article presents a practical framework for engineering leaders to decide whether to build or buy software capabilities. It reframes the binary "build vs buy" question into a multi-option decision space (build, buy SaaS, buy+customise, open-source+host, partner/outsource) and proposes a four-question test: (1) Is this core to your product? (2) Does a mature market solution exist? (3) What is the true total cost of ownership? (4) What is the blast radius of getting it wrong? The author recommends a default-to-buy policy if the four questions don't resolve a decision within two weeks, and offers a simple 3-year cost model (multiply vendor quote by 1.4; multiply build estimate by 2.5). The piece includes a decision matrix, domain-specific guidance (CI/CD, observability, AI/ML, security), real anonymized case studies, and an annual review template for revisiting decisions.
How to Decide: Build, Buy, or Call an API
A DEV.to post by Sagar Jain presents a simple three-gate decision framework for whether a team should build functionality in-house, buy a vendor product, or call a hosted API. The author recommends calling APIs for commodity AI capabilities (text generation, transcription, embeddings, etc.), buying when a capability is a company's entire product, and building only when the capability is a true differentiator driven by proprietary data or volume economics. The piece stresses designing an easy exit/switch strategy up front so teams can replace vendors later if costs, terms, or scale change.
Redefining UX Processes for the Age of AI
A Medium opinion piece by Patrick Neeman argues that modern UX inherited the rituals and business model of mid‑century advertising agencies — the pitch, the account model, the auteur — and that those habits now undermine outcome‑focused product work in an era where AI changes the cost and nature of execution. The author calls for a reset toward systems, continuous discovery, measurable business outcomes, collaboration over star designers, and loyalty to users rather than the loudest stakeholder. The article cites industry thinkers and research (e.g., McKinsey) to support a shift from deliverables and shows to durable systems and iterative user‑centered measurement.
Receive all future signals for Menlo Ventures & competitors in your briefing
Never miss material M&A deals, leadership changes, account wins, or product rollouts. Polaris7 monitors 20,000+ primary sources 24/7, delivering verified telemetry directly into your executive briefing.