You already pay for ChatGPT and Grok. Why would you need a custom AI agent?
You already pay for ChatGPT and Grok. Why build an agent?
Picture the owner of a packaging unit in Rajkot. He pays for ChatGPT, his son uses Grok, and the accounts team got Copilot with Microsoft 365. Between them, they draft emails, summarise PDFs and answer half his questions before lunch, and he's right that they help the business.
So when someone pitches him a custom AI agent, his reaction is fair: "I already pay for these. Why would I need one more?"
On the custom AI agent vs ChatGPT question, I mostly agree with him, even though I build custom agents. These tools got a lot more capable this year. What matters is where they stop, and whether your work lives past that line.
What ChatGPT, Grok and Copilot are genuinely good at now
Credit first. Most pages comparing a custom agent with ChatGPT still describe ChatGPT as a chatbot that answers questions. That stopped being true this year.
OpenAI Dots. OpenAI launched Dots at DevDay on 29 September 2026. These are always-on agents inside ChatGPT, each with its own cloud computer and browser. They run in the background, learn your preferences, run on GPT-6 Astra, and you can reach them from ChatGPT, Slack or Teams. OpenAI says Dots "can readily connect to over 4,000 apps" through plugins, and it runs an automatic review before actions that touch your accounts or share information. OpenAI also says, fairly, that it "can still make mistakes". It's rolling out to Pro and Business Premium, with Enterprise in beta.
xAI Grok Bot. Grok Bot launched in beta on 11 August 2026. Its agents sign in to your company software and do multi-step tasks on a cloud virtual machine. There are 220 plugins, including Google Workspace, Slack, Microsoft 365, Salesforce, Notion, GitHub and Jira, and none are installed by default, which I like. It pauses before sending, publishing, buying or deleting, though an "Always Allow" setting skips those pauses. Worth knowing: each account gets one VM, shared by all its bots, logins included. To be fair about scale, Grok has the fewest paid subscribers of the three, and Grok Bot is a two-month-old beta, so far open to some SuperGrok Heavy and Cursor subscribers, with teams promised access later.
Microsoft Copilot. Copilot (formerly Microsoft 365 Copilot) passed 30 million paid seats by Microsoft's FY26 Q4 results on 29 July 2026. Microsoft says your prompts and Graph data aren't used to train its foundation models, and Copilot is covered by its Data Protection Addendum. Copilot Studio goes further: you can build custom connectors to "any publicly available API". If your company already lives in Outlook, Excel and Teams, that's a strong place to start.
For a rough sense of who uses what: Recon Analytics estimated that in January 2026, ChatGPT had 55.2% of paid AI subscribers, Copilot 11.5% and Grok 3.4% (as reported by Stackmatix). It's one firm's estimate, so read it as a direction.
If your work is drafting, research, summarising and acting inside mainstream cloud apps, one of these may be all you need. I'd try that first.
Where they stop: six honest limits
None of these is a bug. A product built for millions of companies can't know how yours runs.
Your systems behind the firewall. The 4,000 apps Dots connects to are popular cloud apps. Tally on the office PC, a 12-year-old ERP on a local server or your internal database usually aren't on that list. Boomi's ChatGPT setup guide puts it plainly: "ChatGPT connects to remote MCP servers over the public internet. Servers behind VPNs or private networks will not connect." You can still reach those systems, with a local connector or a safely exposed endpoint. Copilot Studio also needs a data gateway plus build work to reach on-premises systems. Either way it's custom engineering, on someone's platform.
Your rules, beyond generic approvals. Dots reviews actions before they touch your accounts, and Grok Bot pauses before it sends or deletes. That's a sensible default. What it doesn't know is that your sales team can give, say, 5% off on their own and anything more needs your sign-off, or that no quote leaves without a GST number and a delivery date. In a custom agent I put those rules in plain code that runs every time, so the model never gets to judge whether it followed them.
Token bleed. Agents read, plan, call a tool, read again, and every step costs tokens. In one 2026 study of coding agents (Bai et al., summarised by Stanford's Digital Economy Lab), agentic tasks used about 1,000 times more tokens than code chat, and the cost of the same task varied by up to 30 times. That was coding, so the exact figures won't carry over to your business, but an always-on agent doing everything with one large model gets expensive at volume. A custom build can send narrow steps, like reading an order number or sorting an enquiry, to a smaller, cheaper model and save the big one for the hard parts.
Privacy and India's DPDP rules. The business tiers of all three don't train on your data by default. The quieter risk is staff pasting client data into personal Free, Plus or Pro accounts, where training is on by default unless they opt out. India's DPDP Rules were notified in November 2025, and the core duties (notice and consent, security safeguards, breach notification, cross-border transfers) apply from 13 May 2027. Also, OpenAI's India data residency covers data at rest, and inference ran only in the US as of November 2025. I'm not a lawyer and this isn't legal advice, but if client data is involved you should know where it's stored and where it's processed. A custom build lets you choose both.
Lock-in. Dots runs on OpenAI's models and Grok Bot runs on Grok. If a better or cheaper model comes out next quarter, you wait for your vendor. Copilot is fairer here, since it already works with more than one model family. A custom agent lets you pick a model for each task and swap one out later without rebuilding the rest.
Your edge. This one is opinion. Your competitor can subscribe to the same bot tomorrow, with the same features. What they can't buy is the way you price, qualify and follow up, built into an agent that runs on your data. If a workflow is part of why customers pick you, I'd rather own it than rent it.
Custom AI agent vs ChatGPT, Grok Bot and Copilot, side by side
Here's the comparison row by row. By off-the-shelf I mean Dots, Grok Bot and Copilot.
- Best for. Off-the-shelf: personal productivity and tasks inside popular cloud apps. Custom: one repeated business workflow that runs across your own systems.
- Connects to. Off-the-shelf: thousands of popular apps through plugins, and Copilot Studio adds connectors to public APIs. Custom: those, plus on-premises and legacy systems through connectors built for them.
- Approval rules. Off-the-shelf: built-in pauses before risky actions (Grok Bot lets you switch them off with Always Allow). Custom: your business rules checked in code, plus a person's approval wherever you want one.
- Model choice. Off-the-shelf: the vendor's models, with Copilot offering more than one. Custom: a model per step, replaceable later.
- Data location. Off-the-shelf: set by the vendor's plans and regions. Custom: you choose the provider and region, and can keep sensitive steps on your own servers.
- Cost control. Off-the-shelf: a subscription, with usage handled the vendor's way. Custom: you pay for what each step uses and can route simple steps to cheaper models, but you also pay to build and maintain it.
When is ChatGPT enough, and when is custom worth it?
ChatGPT, Grok or Copilot is probably enough when:
- The work is drafting, research or summarising for you and your team.
- Your tools are mainstream cloud apps: Gmail, Google Sheets, Slack, Microsoft 365, a cloud CRM.
- Volume is low and a mistake is cheap to fix.
- A person reads the output before it goes anywhere.
A custom agent is worth it when:
- The workflow needs on-premises or legacy systems: Tally, a local ERP, an internal database.
- It runs hundreds of times a week, so token costs add up.
- Money or customer data is at stake.
- You have rules a generic approval step can't know about.
- It spans several systems in several steps.
Tip: If you can't write the workflow down on one page, don't build an agent for it yet. Fix the process first. And if it happens five times a month, ChatGPT or Copilot with a person checking the result is fine.
Example: from IndiaMART enquiry to sent quote, step by step
Here's the kind of workflow where I'd go custom. Picture a Rajkot supplier of brass fittings. This is an illustration, not a client.
- An enquiry arrives on IndiaMART. The agent picks it up and reads the product, quantity and delivery city.
- It checks stock and price in the ERP or Tally on the office server through a local connector, so that system stays off the public internet.
- It drafts a quote in your format, with your terms.
- Code checks the draft against your rules: discount within the limit, quantity above the minimum order, required fields filled. If anything fails, the quote goes to a person instead.
- The owner gets the quote on WhatsApp and approves or edits it.
- Once approved, the agent sends the quote to the buyer and logs it with the enquiry in the CRM.
I'm not claiming Dots or Grok Bot can or can't do this with your Tally setup. The local connector and the rule checks are what make it yours, and they're custom work on any platform. We've written more about the IndiaMART side at https://dizilus.com/indiamart-lead-automation/.
If custom, who builds it?
You have three realistic routes: your own developer, an agency, or Copilot Studio if you're deep in Microsoft and your systems can be reached. I've compared the agency and in-house routes honestly at https://dizilus.com/blog/automation-agency-vs-in-house/.
Whoever builds it, ask three questions. Which model runs each step? What happens when the model gets something wrong? Who fixes it when it breaks on a Saturday?
Start with one workflow
Don't start by picking a tool. Pick one repetitive workflow, write down every step, and mark which systems it touches and which steps need a person's judgement.
If it all lives in mainstream cloud apps, try Dots, Grok Bot or Copilot first. If it touches your own systems or your own rules, that's the kind of agent we build. See how we work at https://dizilus.com/ai-agents/, or email the workflow to tea@dizilus.com and I'll tell you honestly which route fits.
FAQ
Can ChatGPT, Grok or Copilot connect to my old ERP or Tally?
Usually it takes extra work. Their plugins cover popular cloud apps, and ChatGPT connects to remote MCP servers over the public internet, so a system behind a VPN or on an office server needs a connector or gateway built for it. Copilot Studio can reach on-premises systems with a data gateway and some build work. Either way, that's custom work.
Is my business data used to train their models?
On the business tiers of ChatGPT, Grok and Copilot, not by default. On personal plans like ChatGPT Free, Plus or Pro, training is on by default unless you opt out, so keep client data out of personal accounts.
Why do AI agents cost more to run than chat?
An agent plans, calls tools and rereads results, and every step uses tokens. One 2026 study of coding agents found agentic tasks used about 1,000 times more tokens than code chat, with the cost of the same task varying by up to 30 times. A custom build can send simple steps to smaller, cheaper models.
When is ChatGPT enough for my business?
When the work is drafting, research or tasks inside mainstream cloud apps, volume is low, and a person checks the output before it goes anywhere. Plenty of businesses never need more than that.
Can I switch AI models later?
With Dots or Grok Bot you use the vendor's models. Copilot already works with more than one. A custom agent can use a different model for each step, and you can swap one out later without rebuilding the rest.
What does a custom AI agent do that a ChatGPT agent can't?
It connects to your own systems, including on-premises ones, checks your business rules in code before it acts, lets you choose a model for each step, and keeps data where you decide. Dots and Grok Bot are improving fast, so judge them on your actual workflow.
Originally published at dizilus.com.
Top comments (0)