Directions Brain

Vertical Use-Case-Led Brain

8 min read

Vertical Use-Case-Led Brain

Definition

The strategic repositioning of the Brain (context-os-brain) from a generic horizontal context layer into a vertical, use-case-led product: pick the workflows that genuinely require deep cross-team context, build the agents that win those workflows, and let the Brain be the secret sauce / moat sitting underneath. Articulated most clearly by guy-barkat in 2026-05-27-directions-vertical-pivot-and-prediction-markets and reinforced by saar-arbel.

Key points

  • Ceiling argument. A generic “wiki-like Brain” cannot be sold for $1M ARR — buyers will not pay enterprise prices for “store our files better.” A vertical, use-case-led product can attribute concrete output (X% faster delivery, replaced agency contract, blocked compliance regression) — that unlocks six-figure-plus deals.
  • Reverse the design direction. Today the team starts from “structure the data” and asks “what can agents do on top.” Guy’s argument: invert. Start from the highest-value agentic workflow you can credibly own, and design the Brain shape backward from that workflow’s context requirements.
  • The “Wonderful for X” pattern is the proof point. notch (Wonderful for regulated industries / call centers — where maor-naksh is moving), alta (Wonderful for revenue cycle, by Stav and team) are real, funded executions. The pattern works.
  • Champion + ROI matter. A vertical product has a clear champion (the buyer who personally wins from the workflow improvement). A horizontal Brain has no obvious champion — it’s “useful to everyone but owned by no one.”
  • Don’t jump the vertical pick. Guy explicitly pushed back against jumping to construction or healthcare without first checking the team’s home turf (hi-tech enterprise — etoro / monday-shaped) for un-served use cases. The home turf may be the right vertical because the team understands it.
  • Compatibility with the agent-native thesis. This framing extends agent-native-go-to-market rather than replacing it: the Brain is still queryable by agents day-1, but the agents are yours, not anyone’s, and you sell on their workflow output. Pricing model can ride the agent’s token usage (Cursor-like 20% margin on tokens) instead of seat-based wiki licensing.
  • 2026-06-13 stricter rule: output before platform. The team now treats “stores context better” as insufficient. The wedge must be framed around a buyer-visible output: higher AM book-of-business, closed-loop revenue optimization, construction exec visibility, or another measurable workflow.
  • Sequoia pushes the same rule further: sell the work. 2026-03-05-sequoia-services-the-new-software says the stronger AI-native position is not merely “tool for X” but “the work gets done.” That reinforces the Brain direction only if the Brain sits under a vertical autopilot or service, not if it stays a horizontal context layer.
  • 2026-06-14 process rule: problem before Brain. Saar explicitly warned against falling in love with Brain as the solution. The team should first collect painful problems from AM, revenue-cycle/marketing, and construction, then decide whether Brain is the right substrate.
  • Generic Brain infrastructure is not the startup wedge. Nizan’s concern: Claude/OpenAI/Google will likely ship context management as built-in infrastructure. The startup opportunity is a vertical flavor - the data model, input quality loop, and agents that make Brain useful for AM, construction, or another workflow.
  • 2026-06-16 refinement: job title is not the vertical. The AM/CS wedge split into at least three workflow archetypes: enterprise relationship AM (mixpanel), high-volume B2C seller success (fiverr), and renewals-management-wedge (cymulate). All sit near CS/AM, but the data shape, buyer, ROI proof, deadline, and first agent differ. The vertical pick has to name the workflow and operating model, not just the department.
  • 2026-06-20 decision: vertical product beats generic Brain. The team made the cut more explicit: do not try to win as the horizontal company Brain against Databricks/Microsoft-scale infrastructure. Build a product for a specific vertical/use case that uses human-in-the-loop-accountability as part of the wedge.
  • External growth-market pressure points the same way. a16z’s software-refounding thesis says AI-native products must move total company growth, not just add chatbots to old SKUs. That reinforces ai-native-products-must-move-company-growth and the team’s output-first rule: the Brain should sit underneath a product that owns measurable workflow value, usage, or outcome volume.

Evidence

Open questions

  • Which vertical first? No longer settled. 2026-06-02 working answer was account-management-vertical. 2026-06-13 added revenue-cycle-brain as the larger vision and construction exec visibility as the warmest POC. 2026-06-14 reset the process around interviews/problems before demos. 2026-06-16 further split AM/CS into enterprise AM, scaled seller/customer success, and renewals-management-wedge; the next validation loop should decide which workflow earns focus.
  • What vertical makes human-in-the-loop-accountability a buyer-visible output rather than hidden infrastructure?
  • Is the right unit “Wonderful for vertical X” (one product per vertical) or a Brain platform with vertical packs on top? The former is simpler; the latter scales better.
  • How much of the monday-agents-month catalog actually requires a Brain vs being thin Cursor wrappers? Mining required.
  • Pricing: per-seat licensing of the Brain itself, or token-margin on agent usage, or hybrid? Not resolved.
  • Does this reposition sacrifice the “first-to-market on horizontal context-OS” claim, or strengthen it because the wedge is sharper?

Graph View

Backlinks