The custom AI vs ChatGPT subscription question is almost always the wrong one

I get asked some version of this once a week. Should we build a custom AI tool, or just pay for ChatGPT Team for the staff?

The framing is wrong, but it's wrong in a specific way that's worth pulling apart.

Buying a subscription gets you a fast, capable model and a familiar interface. Twenty dollars a head, working today. The cost of being wrong is approximately zero — you cancel and move on. If your team's main AI use case is "draft emails faster" or "summarize this PDF," a subscription is almost certainly the right answer, and any consultant telling you otherwise is selling something.

Building a custom tool gets you something different: control over what the model knows, where the data goes, how the interface fits the actual job, and what happens when the answer is wrong. That last one is the part most people skip past. A general-purpose chatbot that hallucinates a tax deadline is annoying. A staff-facing tool that hallucinates the same deadline, with your firm's logo on it, is a liability. The custom build's real value is in the guardrails, not the intelligence.

The honest decision tree is something like this. If the work is generic, like writing, summarizing, brainstorming, or light research, buy the subscription. The frontier models are better at general tasks than anything you'd build, and the gap is widening. Pay the seat fee, train your team how to actually use it, move on.

If the work depends on your specific knowledge, your specific workflow, or your specific liability exposure, building something starts to make sense. Not because the AI is better. It's the same model underneath. The wrapper around it is what's doing real work. Citations from your sources. Refusal to answer outside its lane. Logging for compliance. A UI that fits the job rather than a blank text box.

The mistake I see most often is the inverse on both sides. Companies who should obviously buy the subscription get talked into a $60k custom build because it sounds more serious. Companies who genuinely need a custom tool, usually because they have proprietary data they can't paste into a public chatbot, keep paying for subscriptions and watching their team paste sensitive data into them anyway.

If you're trying to think clearly about this, Ben Thompson's writing at Stratechery on aggregation and unbundling is a useful frame, even though he's writing about a different question. The pattern holds: the value isn't in the model, it's in the layer that makes the model fit a real job. Sometimes that layer is "ChatGPT plus a thirty-minute training session." Sometimes it's a $20k build. The skill is being honest about which one you actually need.

Most of the work I take on sits at that decision point. Half of my first calls end with me telling the prospect to buy seats and call me in six months if they hit a real wall. I've written about this dynamic before — the cheaper, more boring answer is usually the one that ships.

If you can't articulate, in one sentence, why a subscription wouldn't solve your problem, you're probably not ready for a custom build yet. And that's a useful answer, not a discouraging one.