The wrapper pattern
Proprietary model claim + fixed-price retainer + budget over 50K + no model disclosure clause = wrapper pattern. The product is a thin layer over a frontier API; the value is the prompt engineering, not the model.
Wrappers can be valuable
Some wrappers are excellent businesses. The problem is opaque pricing. If you are paying frontier-model resale + 10x markup with no transparency, the value capture is wrong.
How to verify
Ask for the model disclosure clause. Ask for the data flow diagram. Ask for the switching policy. Ask for the per-token cost pass-through.
When wrappers are fine
When the wrapper does meaningful prompt engineering, retrieval, evaluation, and orchestration. When the pricing reflects the engineering work, not just the model resale.