Why specialized Vertical AI is actually just 90s software in a

Vertical AI startups such as Harvey, Casetext, Cursor, and GitHub Copilot are essentially repackaging 1990s-era specialized software with modern machine learning, according to an analysis of the MaaS (Model-as-a-Service) business model. The article argues that while generalist models like GPT-4 may eventually subsume niche tools, domain-specific data and high costs of error in fields like legal tech and medical AI will sustain a hybrid workflow where specialists handle high-precision tasks.

Why specialized Vertical AI is actually just 90s software in a The mechanics of the Vertical AI shift The core of the MaaS business is simple: take a base model, feed it a massive amount of proprietary domain data, and sell access via a subscription or API. We see this playing out in a few key sectors: Legal Tech: Tools like Harvey or Casetext that understand the nuance of case law far better than a vanilla GPT-4. Medical AI: Systems designed for clinical diagnostics where "hallucinations" aren't just annoying—they're dangerous. Development: Tools like Cursor or GitHub Copilot /en/tags/github%20copilot/ that are optimized for the specific syntax and structural logic of code. From a business perspective, the margins here are wild. The cost of fine-tuning a model on a specific dataset is relatively low compared to training a frontier model from scratch, yet companies are willing to pay a premium for that "specialist" accuracy. The Generalist vs. Specialist Tension There is a loud debate right now about whether these vertical players are just a temporary bridge. The "Generalist" camp argues that as frontier models get smarter, they'll naturally subsume these niche tools. Why pay for a legal AI when the next version of a general LLM can pass the Bar exam with 99% accuracy? The "Specialist" camp argues that domain-specific nuance—the kind found in private, non-public datasets—will always create a moat. Personally, I think the "bubble" talk is overblown. We aren't heading toward a total monopoly by one or two generalist models, nor are we heading toward infinite fragmentation. We're moving toward a hybrid AI workflow. You use a generalist for brainstorming and a specialist for the final, high-precision execution. How to choose your stack If you're building a workflow or choosing a tool, the decision isn't about which model is "better" in a vacuum, but about the cost of error. Low cost of error: Use a generalist. It's cheaper, faster, and more flexible. High cost of error: Go for a specialist. The higher subscription fee is essentially an insurance policy for accuracy. The real danger isn't the price; it's the lock-in. When you build your entire company's knowledge base into a proprietary vertical model, switching costs become massive. The smartest move right now is to maintain a flexible prompt engineering layer that allows you to swap the underlying model as the market consolidates. Next Force-feeding an "I am an AI" response into every LLM is a → /en/threads/5692/ All Replies （0） No replies yet — be the first