AI integration

Off-the-Shelf AI vs Custom AI: How to Decide What to Buy and What to Build
Off-the-Shelf AI vs Custom AI: How to Decide What to Buy and What to Build 150 150 Nadeem Shaikh

Off-the-shelf AI vs custom AI comes down to one question: is the work you want AI to do the same at your company as everywhere else, or does it depend on your own data, rules and systems? If it’s the same everywhere, buy it. If it depends on what makes your business different, that’s the part worth building, usually on top of the AI tools you already pay for.

This week made the choice more pressing. On October 6, SAP began rolling out Joule Work, an AI interface that works across SAP and third-party data, and on October 8 Google Cloud announced the Gemini agent, a universal agent for work. In the same week, Infor published a survey of 2,111 business decision-makers in seven markets in which 68% said off-the-shelf AI doesn’t adequately address their industry’s needs. Infor sells industry-specific AI, so read that number with its source in mind. Still, the gap it describes is one most operations teams will recognize.

What the big platforms now give you out of the box

Built-in AI is getting genuinely useful. SAP says its Knowledge Graph maps more than 7 million data fields to ground Joule in business context, and that Joule Studio lets customers build their own agents while choosing from more than 70 AI models. Google says its Gemini agent plans the work, connects to customers’ business systems, chooses the best model for the job and has built-in cost controls. If you run those platforms, you get a lot without writing code.

The catch is in the word “platform”. Built-in AI works best on the data inside that vendor’s product, and most businesses don’t run on one vendor. Orders sit in one system, contracts in a shared drive, pricing rules in a sales spreadsheet, and the know-how for exceptions with a few experienced people.

When off-the-shelf AI is the right call

  • The task is generic: drafting emails, summarizing meetings, searching files, writing first drafts.
  • The data already lives in the vendor’s product, and the AI feature comes from the same vendor that holds it.
  • Being a little wrong is cheap, because a person reviews the output before it matters.
  • You need value this quarter and nobody on your team could own a custom system yet.

Here, building your own is usually wasted effort. Turn on what you have, train people to use it, and measure whether it saves time.

When custom AI pays off

  • The work depends on your rules: how you price, what you accept, which exceptions need a manager’s sign-off.
  • It crosses systems: a quote that needs your ERP, your shipping carrier and your customer history at the same time.
  • The documents are yours: supplier invoices, purchase orders, inspection reports or contracts in formats no generic tool has seen.
  • Mistakes are expensive, so you need to test against your own past cases and log every answer.
  • Data has to stay in your own cloud account for security or compliance reasons. In Infor’s survey, 33% of leaders named data security, sovereignty or compliance as their single greatest barrier to advancing their AI strategy.

The same survey suggests the fit problem grows with operational complexity: 73% of manufacturing respondents and 76% of distribution respondents said off-the-shelf AI doesn’t fit their needs. If you run a plant or a warehouse, expect generic tools to handle the easy part of the job and miss the part that matters most.

The middle path: buy the platform, build what makes you different

The choice is rarely all or nothing. A practical setup looks like this:

1. Buy the general-purpose layer

Use the assistant that comes with the suite your team already works in for everyday writing, search and summaries.

2. Build the business-specific layer

Build the small pieces that teach AI about your business: a private knowledge base over your own documents, document extraction tuned to your forms, and connections to your systems that respect your existing permissions.

3. Keep the custom pieces portable

AI products change fast, so build custom parts that more than one AI tool can use. SAP, for example, says Joule can connect with third-party AI and agents through the Agent2Agent protocol. Open connections like this, or a custom MCP server in front of your own systems, let you change the front end later without rebuilding everything behind it.

4. Own the evaluation

Whatever you buy or build, keep your own set of real past cases with known right answers and check the AI against it. A vendor demo is not proof that a tool works on your data.

A quick test before you sign or start building

  1. Write down the exact task and who does it today.
  2. List every system and document the task touches.
  3. Run the off-the-shelf option on real past examples.
  4. Note where it fails. If the failures come from missing business context, that context is what you build.
  5. Name the person who owns the result. In Infor’s survey, 15% said no one person has primary responsibility for AI, or that it’s unclear who does.

FAQ: off-the-shelf AI vs custom AI

What is the difference between off-the-shelf AI and custom AI?

Off-the-shelf AI is a ready-made product, such as an assistant built into your ERP, office suite or CRM, that works the same way for every customer. Custom AI is built around one company’s own data, rules and systems, for example an agent that reads that company’s supplier invoices and posts them to its ERP using its own approval rules.

Is it cheaper to buy AI or build it?

Buying is usually cheaper to start because the vendor carries the development cost. Building costs more up front but can pay off when the work is specific to your business, runs at high volume, or would otherwise need heavy manual checking of a generic tool’s output. Compare both on a real task with real data.

Can a business combine off-the-shelf AI with custom AI?

Yes, and for many businesses that is the practical answer. A common pattern is to use a vendor’s assistant as the everyday interface and build custom pieces behind it, such as a private knowledge base, document extraction or connections to in-house systems.

Get a clear buy-or-build answer

GrtLabs is an AI and software development company in Houston that helps businesses decide which AI to buy and which to build. Our AI Discovery engagement reviews your data, systems and processes and ends with clear build / no-build recommendations. When building makes sense, our AI Factory team designs and ships it, including on AWS or Azure inside your own cloud account. Talk to us about the task you’re weighing.

Custom MCP Server: When Your Business Needs One and How to Build It Safely
Custom MCP Server: When Your Business Needs One and How to Build It Safely 150 150 Nadeem Shaikh

A custom MCP server is a small, controlled service that lets AI assistants and agents read from and act on your own systems, such as your ERP, CRM, database or document store, through one standard connection instead of a new integration for every AI tool. If your team already uses AI assistants and keeps copying data into them by hand, an MCP server is usually the next thing worth building.

MCP stands for Model Context Protocol. It is an open standard that tools like Claude, ChatGPT and Cursor use to connect to outside data and actions. This week shows how fast it is becoming the default: Atlassian rebuilt its MCP server for Jira, Confluence, Loom and Bitbucket and says it now handles more than 15 million tool calls a day, Google moved its MCP Toolbox Java SDK to a stable 1.0, and several data platforms announced MCP access to enterprise data. The big vendors are wiring their products for AI agents. The question for most businesses is how to do the same for the systems that are unique to them.

What an MCP server actually does

An MCP server sits between an AI assistant and one of your systems. It publishes a short list of tools, for example “look up an order”, “list open invoices for a customer” or “create a support ticket”, and describes each one in plain language so the AI knows when to use it.

When someone asks the assistant a question, the assistant picks a tool, the MCP server checks whether that user is allowed to run it, calls your system, and returns only the data the user is allowed to see. Your system never hands its database password to the AI. The MCP server holds that access and decides what goes through.

When off-the-shelf MCP servers are enough

If the data lives in a popular SaaS product, check for an official MCP server first. Atlassian, GitHub, Slack, many CRMs and most major clouds now publish one. Using it is faster and cheaper than building your own, and the vendor keeps it updated.

You need a custom MCP server when:

  • The data lives in a system you built or heavily customized, such as an in-house ERP, a legacy SQL database or a line-of-business app.
  • You want the AI to follow your business rules, for example “never quote below list price” or “only show a customer’s own orders”.
  • You need one tool that pulls from several systems at once, like order status that combines your ERP, shipping provider and support history.
  • Security or compliance means data must stay inside your own cloud or network.

How to build a custom MCP server that is safe to put in production

1. Start with three to five tools, not your whole database

Pick the questions your team asks most often and build a tool for each. Narrow tools with clear names work better than one tool that runs any query. The AI chooses more accurately, and you can see exactly what it is allowed to do.

2. Make reads and writes separate

Read-only tools are low risk and a good first release. Tools that change data, such as creating orders, updating records or sending anything to a customer, should come later and usually ask a person to confirm before they run.

3. Pass the user’s identity through

The MCP server should act as the person asking, not as an all-powerful service account. That way a sales rep sees their accounts, a manager sees their team, and your existing permissions still apply.

4. Log every call

Record who asked, which tool ran, what went in and what came back. When an answer looks wrong, the log tells you whether the data, the tool or the AI was the problem.

5. Keep responses small

Return the fields the AI needs, not whole records. Smaller responses are cheaper to run, faster, and less likely to leak data nobody asked for.

6. Test with real questions before rollout

Write down 20 or 30 questions your team actually asks and check that the assistant picks the right tool and gets the right answer. Run that list again every time you add or change a tool.

MCP server vs. RAG: which one do you need?

They solve different problems and often work together. RAG (retrieval-augmented generation) helps an AI answer questions from documents such as manuals, contracts and policies by finding the right passages first. An MCP server gives the AI live access to systems and actions, such as today’s order status, current stock or creating a ticket.

A simple rule: if the answer is in a document, start with RAG. If the answer is in a system, or the AI needs to do something, you need an MCP server. Many useful assistants use both, with RAG as one of the tools the MCP server exposes.

What to have ready before you start

  • A list of the systems you want the AI to reach, and who owns each one.
  • The top questions or tasks your team would hand to an assistant.
  • How users sign in today (Microsoft, Google or your own login), so permissions can carry through.
  • Which AI tools your team already uses, so the server is tested against them.
  • Where it should run: your AWS or Azure account, or on-premises.

Get help building your MCP server

GrtLabs builds custom AI integrations, agentic AI workflows and AI assistants that connect to the systems your business already runs. If you want your team’s AI tools to work with your own data safely, talk to us about your systems and we’ll help you pick the first tools worth building.