"It's just a wrapper" is a common dismissal in machine intelligence circles, implying that any product built on a foundation model API has no defensibility and is one upstream feature launch away from extinction. The critique misunderstands how software value is created.

By that logic, every SaaS product is "just a wrapper" around a database. Salesforce wraps PostgreSQL. Figma wraps a rendering engine. Stripe wraps bank APIs. The entire history of software is layers of abstraction that turn raw capability into something people actually use. The model is the engine, not the car.

That said, critics aren't entirely wrong. Some products truly are thin wrappers: a prompt template, a text box, and a prayer. No proprietary data. No workflow integration. No feedback loops. If a competitor can recreate your product in a weekend using the same API, you don't have a product — you have a demo. The build-vs-buy calculus is brutal in that case.

The real question isn't "is it a wrapper?" but "does it compound?" Defensible products build data flywheels, integrate deeply into workflows, tune to domain-specific needs, and create switching costs that emerge naturally from doing the job well. The model layer is a commodity input; everything above it is where value lives.

Wrapper discourse is a vendor lock-in question in disguise. If your value proposition evaporates when the upstream provider ships a new feature, you were never building a product — you were renting a demo.