ChatGPT vs a Custom Build: How Montana Operators Should Actually Decide

Most small businesses in the Flathead already have a chatbot tab open. ChatGPT for a draft email. Claude for a messy spreadsheet. That is useful. It is not a system. A system answers the same question at 9 p.m. on a Sunday. It lives on your site, on the phone line, or in the tools you already pay for. It has an owner and a stop button. A tab you open when you remember does none of that. On 13 May 2026, Anthropic launched [Claude for Small Business](https://www.anthropic.com/news/claude-for-small-business). OpenAI sells [ChatGPT Business](https://chatgpt.com/business/) as a team workspace. Both are real products. The question for a Kalispell clinic, a Bigfork service shop, or a local manufacturer is which of three lanes you actually need. ## What the vendors actually shipped Anthropic describes Claude for Small Business as a toggle inside Claude Cowork. Connect Intuit QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, and Microsoft 365. Pick a job. "Claude does the work; you approve before anything sends, posts, or pays." It ships 15 agentic workflows across finance, operations, sales, marketing, HR, and customer service, plus 15 skills: payroll planning against QuickBooks and PayPal, a month-end close packet, invoice chasing, HubSpot campaign work with Canva assets. On access: "If an employee can't see something in QuickBooks or Drive today, they can't see it through Claude." And: "We don't train on your data by default on our Team and Enterprise Plans." OpenAI positions ChatGPT Business as a workspace, not a personal Plus account on a company card: "ChatGPT Business gives teams a secure workspace with connected company plugins, shared context, and agentic workflows." ChatGPT Work takes a goal, plans, executes, and checks in "when your input or approval is needed." Same page: "Your data is never used for training our models," with encryption, SSO, and multi-factor authentication. Use that lane when the work already lives in those tools. Skip it when the work lives on your public website, or across systems that do not share a customer record. ## Lane 1: Packaged AI inside one vendor Start here if the job already happens inside QuickBooks, PayPal, HubSpot, Google Workspace, or Microsoft 365, and a person can approve each send, post, or payment. Example: a Whitefish accountant in tax season. The books are in QuickBooks. PayPal settlements are the messy part. Claude's month-end and invoice workflows are aimed at that. Do not hire a builder to recreate a close packet the vendor already ships. If the source of truth is already a connected app, a human reviews output, and the public website is not in the loop, subscribe. Write a one-page paste-in rule. Revisit in 90 days. That path does not require Mahlum Innovations. ## Lane 2: An AI-infused website and front-desk workflow Most local operators do not lose work because they cannot draft an email. They lose it because the website cannot answer a real question, the phone hits voicemail after 5, and nobody logs the lead. An [AI-infused website](/websites) is a public system grounded in your services, hours, pricing, and FAQs, structured so Google and answer engines can cite you. Growth and Advanced add conversational AI, lead capture, optional voice reception, and admin automation wired to tools you already run. Published website tiers are on [/pricing](/pricing): Essentials at $1,200, Growth at $2,800, Advanced AI builds from $5,200 to $9,600 and up. That is not a ChatGPT wrapper with a new coat of paint. Example: a Kalispell clinic. The same questions come in after hours: hours, new patients, self-pay versus insurance, first-visit prep, how to book. A tab on the owner's laptop does not help the person on their phone at 8:12 p.m. A site that answers from approved content, and hands a human the rest, does. Example: a Bigfork service shop. People call to ask if you can look at a unit next week. If the site cannot speak to services, service area, and how to request a slot, staff are repeating the homepage. Lane 2 is the fix. Lane 1 is not. Choose lane 2 when the bottleneck is the public edge: questions, booking intent, after-hours coverage, or answer engines with nothing structured to cite. If you are not sure what those engines see, run a free [AI Visibility Audit](/audit) before you rebuild. If the services page is vague, the on-site assistant will be vague. ## Lane 3: A custom build when the work spans systems A custom build is not "ChatGPT with our logo." It is a production system trained on your data and wired into the stack that already runs the business. That is [AI systems](/ai-systems) work: a defined workflow, defined integrations, a defined success metric, then a fixed-scope proposal. Custom work is scoped after a discovery call. Website tiers are published. I will not quote a consulting range here. You are in lane 3 when at least two of these are true: - The workflow crosses systems that do not share a customer or job record. - You need to own the logic, the logs, and the off switch. - A person retypes the same facts between tools every day. - Packaged connectors do not cover the system of record you actually use. Example: a local manufacturer. Summarizing a production meeting is lane 1. Flagging a quality issue from the line and opening a work order in the system you already run is lane 3. Those are not the same project. Example: a med spa with a booking tool, a payments tool, and a spreadsheet of memberships. If staff copy names between all three, a HubSpot skill will not close the gap. The work is the handoff. Not every recurring job needs a custom platform. If it looks like a named role with a bounded workflow, look at [AxiomAI](/hire) first. If you lack a one-sentence problem and an honest read on your data, start with [building your first AI strategy](/blog/building-your-first-ai-strategy) or the free [AI Readiness Assessment](/ai-readiness-assessment). ## A decision test you can run this week Write the job in one sentence: "We waste time or lose work because X." If you cannot finish it, do not buy. 1. Does this job already live in QuickBooks, PayPal, HubSpot, Google, or Microsoft 365? If yes, try the vendor workflow for two weeks with a human approval step. 2. Does the customer hit this job on your website or phone first? If yes, you are in lane 2, not in a chatbot tab. 3. Does a person copy the same record between two or more systems to finish the job? If yes, you are looking at lane 3, or at a catalog employee that already maps to that function. 4. Who owns the output when it is wrong? If the answer is "whoever had the tab open," you do not have a system yet. If 1 is yes and 2 and 3 are no, stay on the vendor. If 2 is yes, price a website against the published tiers. If 3 is yes, talk about systems, not prompts. ## When you should not hire me I am a one-engineer firm in Bigfork. I turn work down when the honest path is a subscription. Do not hire Mahlum Innovations if Claude or ChatGPT already covers the job inside tools you pay for, or if you want a month of "trying AI" with no owner and no data rules. Do not hire me for a brochure site with no questions, no booking path, and no integrations. Do not hire me if the facts still live in inboxes and paper. I build systems. I do not sell slide decks. A clinic should not treat a vendor Business plan as a HIPAA design. "Not used for training" is not a workflow that keeps protected information in the right system. Sort that out before anyone pastes a chart note into a chat box. If lane 1 or a catalog employee is the fit, I will say so on the call. ## FAQ ### Is ChatGPT or Claude enough for a small Montana business? Often, yes, for internal drafts and work that already lives in the connected apps. They are not a front desk, and they are not a system of record you own. ### When is an AI-infused website the better spend? When the customer hits you on the web or the phone first, and staff repeat answers the site should already know. That is the [websites](/websites) product: structured content, on-site conversational AI at Growth and above, optional voice and admin automation at Advanced. ### When do I actually need a custom build? When the workflow spans systems, needs an audit trail you control, or depends on data the vendor connectors do not see. Then it is a scoped [AI systems](/ai-systems) engagement, not a better prompt. ### What does this cost? Websites have published tiers on [pricing](/pricing). Custom platforms are scoped after a discovery call. The first conversation is free. I will not quote a range before the work is defined. ## Next step If the job is internal and already sits in QuickBooks or Google Workspace, turn on the vendor tools this week and write the approval rules down. If it is the website, the phone line, or a workflow that crosses systems, [book a free discovery call](/contact). Bring the one-sentence problem, the tools you already pay for, and an example of the handoff that breaks. We will pick a lane. If the right lane is "keep the subscription," you will hear that. **Related reading:** - [Building Your First AI Strategy](/blog/building-your-first-ai-strategy) - [Build vs. Buy AI: A Guide](/blog/build-vs-buy-ai-decision-guide) - [What Does AI Strategy Actually Cost?](/blog/what-does-ai-strategy-cost)