Part of
AI consulting
Strategy

Build vs Buy for Enterprise AI: A Decision Guide

Build vs buy decided layer by layer: build the workflow, highlighted, and buy the platform, such as n8n, and the model.

Build vs buy for enterprise AI is decided one layer at a time: buy the model and the platform, buy a finished product when the job is the same in every company, and build only the workflow that carries your own rules and connects to your own systems. Almost no enterprise has a reason to build a model or an orchestration platform, and almost every enterprise has a few workflows no product will run the way it needs.

The route you pick changes the odds of reaching production. MIT NANDA's report The GenAI Divide: State of AI in Business 2025, based on interviews with 52 organizations, found that tools bought or co-developed with external partners reached deployment about 67% of the time, against about 33% for tools built fully in-house. The authors flag the figures as self-reported and correlational, and they also found that only 5% of custom enterprise AI tools reached production, so a purchase order alone is no answer either. In our AI consulting work, that call comes before any build is scoped.

What does build vs buy mean for AI?

With ordinary software, build vs buy is one decision about one product. An AI system is several layers, and each one has its own answer. The model writes, reads and classifies. The platform runs the workflow, calls the model and retries what fails. The workflow holds your rules: which records to read, what counts as a good answer, when to stop and ask a person. The integrations read from and write to your ERP, CRM and help desk. A finished AI product bundles all four, and a custom build buys the first two and writes the last two.

Seen this way, most builds are mostly bought. The drawing below takes apart a customer service agent we built for Pinkcube, which sells branded merchandise to Dutch and Belgian businesses, and marks which parts were bought and which were written for them.

Every layer except one came off the shelf. The layer we built is the one that knows Pinkcube: which order questions it may answer, how to read a HubSpot deal and its sub-deals, what the Gatekeeper blocks and which of seven ticket categories a chat lands in. The Pinkcube case study shows the agent covering all 168 hours of the week, up from 45 staffed hours.

When should you buy an AI product?

Buy when the job is the same in your company as in everyone else's, and a product already reaches every system the job touches. Meeting summaries, drafting help, search across documents in one suite and the AI features inside a CRM you already pay for all fit. You get updates and support without staffing a team, and you can switch off the subscription when a better product arrives.

The MIT NANDA study found pilot-to-implementation rates of about 83% for generic chatbots such as ChatGPT and Copilot, which users praised for flexibility and familiarity. The same users described custom and vendor-pitched tools as brittle or misaligned with their actual workflows. A general-purpose product earns its place on general-purpose work, and a product sold as a fit for your workflow needs testing on that workflow before anyone signs.

Buying fails in two predictable places. The product cannot reach a system the workflow needs, so the team copies data in and out by hand. Or the product runs the vendor's version of the process, and your team changes how it works to match. If either shows up in a trial, the job belongs on the build side of the line.

When should you build custom AI?

Build the workflow when one of four things is true: no product reaches all of the systems involved, the data must stay inside your own environment, your team needs to change the rules without waiting for a vendor, or the workflow is part of how you win and serve customers. Run each use case through the questions below. Each answer moves it toward one route.

Build or buy, one use case at a time
Five questions decide the route

Is the job the same in most companies, such as meeting notes, email drafts or general questions?

Does a product connect to every system the workflow reads and writes?

Must the data and the run logs stay inside your own cloud account?

Do the business rules change often, and should your own team change them?

Is this workflow part of how you win customers, price work or serve them?

Answer all five questions
0 of 5 answered. Run it once for each use case on your list.
Buy the product when the job is common, a product reaches all of your systems, the data may leave your environment, the rules rarely change and the workflow does not set you apart. If any of those fails, buy the model and the platform and build the workflow on top.
The model and the platform are bought in both routes. What changes is who builds the workflow and the integrations, and who owns them afterwards.

An anonymous example from our own work shows the first condition. A Dutch Odoo implementation partner spent a year trying to automate appointment scheduling for a dental care group inside Odoo itself. We moved the scheduling rules into their own engine, kept Odoo as the system of record with five nightly sync workflows, and let an AI agent place about 1,500 appointments a week for 200 practitioners. Any appointment it cannot place comes with a report explaining why, as the AI agent development page describes.

The third condition is the one buyers underrate. When we built daily MI alerting for IES Limited, the alert thresholds went into a control panel the business edits, and IES made 34 threshold changes in six weeks with zero developer tickets, as the IES daily MI alerting case records. A bought product would have put each of those changes in a vendor's queue.

Build vs buy for AI agents: buy the platform, build the workflow

For most enterprise use cases the answer is a hybrid route: a bought orchestration platform and bought models, with the workflow and the integrations built for your systems. We build on n8n, where Ovidius is an official Select Partner. Teams standardised on Azure keep the same split by building on the Azure stack they already pay for, through Microsoft Foundry. n8n bills per workflow execution, so one run counts once however many steps it takes, and its standard version can be self-hosted in your own cloud account, where the workflows, credentials and execution logs stay. When n8n is the wrong fit for a job, the AI agent platform comparison scores eight platforms against the same four jobs.

RouteYou ownCost grows withMain risk
Buy a productYour configuration and your data exportsSeats or usage, at the vendor's pricesThe product cannot reach a system, or runs the vendor's process instead of yours
Buy the platform, build the workflowThe workflows, rules and integrations, running in your accountModel usage and hosting; self-hosted n8n Community Edition has no fee per runA workflow with no named owner after launch
Build everything in-houseAll of it, including the upkeepYour team's salaries, whatever the volumeHalf the deployment rate of bought tools in the MIT NANDA sample

The hybrid route still means building. You write the business logic, test it against real data and run it after launch, so it needs the same discipline as any software project. What it removes is the work no enterprise should pay for twice: model training, job queues, retries, connectors to common SaaS tools and an editor your team can read. Our guide to how agents connect to your ERP, CRM and data covers the integration layer in more detail.

How do the costs of building and buying compare?

The routes differ less in total than in what the bill grows with. A bought product charges for seats or usage at prices the vendor sets, and the bill grows with headcount or volume. A build on a bought platform costs the build up front, then model usage and hosting every month. A fully in-house build adds the salaries of the people who keep it running, at any volume.

Running costs on a build can be small next to the work it replaces. GoKickflip's content pipeline, built on n8n with about 33 executions per article, spends $1.79 in AI tokens per article and $12.11 including all infrastructure, against $700 for a freelance article before. The GoKickflip case puts the pipeline at $6,317 a year against $364,980 for the human process at equal volume.

To compare routes on your own numbers, the automation ROI calculator turns hours saved, build cost and running cost into a payback month. Our breakdown of what AI consulting costs explains how a build is billed and who carries an overrun under each model, and our guide to what AI consulting is sets out what an engagement contains at each stage.

How to make the build vs buy decision

  1. List the use cases, one workflow each. "Customer service" is a department. "Answer order-status questions from HubSpot and AfterShip" is a use case you can decide on.
  2. Price the manual work. Hours a week, the people doing it and what an error costs. A use case worth little stays manual, whatever the route.
  3. Run the five questions on each. Record the answers, because the reason for a decision matters when someone revisits it next year.
  4. Trial the product on your own data. For anything on the buy side, test the product against the systems and records it will meet in production, before the contract.
  5. Prove the riskiest build first. For anything on the build side, a short AI pilot on your staging systems shows whether accuracy and running cost hold up before the larger budget is committed.
  6. Name an owner for every workflow. Bought or built, someone answers for its accuracy, cost and changes after launch.

If the list is long, the AI Audit does this work across your processes in 4 to 8 weeks and ends in a ranked 90-day roadmap that is yours whether or not you build with us.

Compare before you build
AI Agent Platform Comparison

n8n, Zapier, Sim and the other agent platforms side by side, so you can see which one fits before you build.

Compare platforms

Frequently asked questions

Should enterprises build or buy AI?

Both, at different layers. Buy the model and the platform, buy finished products for jobs that are the same in every company, and build the workflows that carry your own rules, connect to your own systems or set you apart from competitors.

Is it cheaper to build or buy AI?

A bought product costs less to start and grows with seats or usage. A build on a bought platform costs more up front, then model usage and hosting each month, which can be small: GoKickflip's pipeline runs at $12.11 per article including all infrastructure. Compare the two over three years at your expected volume.

What is a hybrid build and buy approach to AI?

You buy the model and an orchestration platform such as n8n, and build the workflow and integrations on top. The workflows run in your own account, and nobody on your team maintains a model or a job queue.

What is the success rate of internal AI builds?

In MIT NANDA's 2025 study of 52 organizations, tools built fully in-house reached deployment about 33% of the time, against about 67% for tools bought or co-developed with external partners. The authors note the figures are self-reported and may reflect differences between the organizations rather than the route alone. If you take the partner route, our list of the top AI consulting companies for enterprise sorts firms by the job each one suits.

Can we start by buying and build later?

Yes, and it is often the right order. A bought product shows which parts of the workflow it cannot handle, and that gap becomes the scope of the build. Check before you sign that you can export your data and configuration, so the move stays open.

If you have a workflow that sits on the build side of the line, book a discovery call. A senior partner will ask which systems it touches and what it costs you today, and tell you whether a product would do the job before we scope a build.

More on this topic

Put your first workflow on the board

Answer a few questions about your team and what you want automated, then a senior partner scopes it with you on the call.