The $30/month question: when a ChatGPT subscription is genuinely enough

We end a certain percentage of audit calls by telling the owner not to hire us. This log is the pattern behind those calls, written down so you can run the test yourself.

The question isn’t “is ChatGPT good enough?” The models inside a $30/month subscription are largely the same models inside a $50K custom build. The question is where the work lives.

When the subscription wins

A subscription is the right answer when the work is a person, doing a task, in a chat window — and the output goes wherever that person takes it next.

Concretely, that’s things like: drafting and tightening emails, proposals, job ads, and marketing copy. Summarizing a long document before a meeting. Working through a contract clause before calling the lawyer. Translating customer messages. Getting unstuck on a spreadsheet formula. First-drafting an SOP or safety doc that a human then fixes.

If your team’s AI usage looks like that list, a built system will not beat a subscription plus one hour of training on how to prompt well. We’ve seen owners get more real value from teaching three office staff to use Claude or ChatGPT properly than from tooling that cost a hundred times more. Spend the money on the training, not on us.

When it stops being enough

The subscription breaks down at three specific walls, and they’re all the same wall from different angles: the moment the work needs to happen without a person driving it.

Volume. One person summarizing one document is a chat. Forty intake requests a day that each need reading, structuring, and routing is a pipeline. Nobody’s pasting forty things into a chat window at 11pm — which is exactly when the missed-call problem from LOG_02 happens.

Connection. The chat window can’t see your systems. The moment the task is “read the request, check the customer’s history in the CRM, pull pricing from the rate sheet, draft the quote into the template” — that’s integration work. Copy-paste is the tell: if your staff are ferrying text between the chat window and three other tools all day, the subscription has become the bottleneck.

Consistency and data. Chat output varies with whoever’s typing. A process that feeds a system of record — quotes, work orders, compliance docs — needs the same structure every time, with review steps and an audit trail. And if the inputs include customer data, you also need to answer where that data goes, which is a contract and architecture question, not a prompt question. We covered the Canada-residency side of that in LOG_03.

The test

One sentence: is the value in helping a person think, or in removing the person from the loop?

Helping a person think → subscription. Removing the person (or the copy-paste) from a repeating, connected, high-volume process → that’s a build, and now the ROI math from LOG_02 applies.

Most businesses honestly need both — subscriptions for the thinking work, one built workflow for the one process where the economics justify it. If an advisor tries to sell you a custom system for work a subscription handles, walk. And if we ever tell you the subscription is enough, that’s not us being modest. That’s the audit working.