AI Agents 10 min read 25 October 2026

Build vs Buy AI Agents: A Decision Framework

Build vs buy AI agents: compare first-year costs, the 1M-conversation crossover and 5 questions that decide it. Score your use cases with our framework.

Build vs Buy AI Agents: A Decision Framework
Part of the Implementing AI Agents guideHow to Implement AI Agents in Your Business

Should you build your own AI agents or buy a packaged platform? Decide per use case, not once for the whole company. Buy when the job is standard (FAQs, scheduling, tier-one support), runs under about 100,000 conversations a year, and lives in tools with ready-made integrations like HubSpot, Salesforce or Zendesk. Build when the workflow is specific to your business, touches internal systems nobody sells a connector for, carries real cost if the agent gets it wrong, or runs at a volume where per-conversation pricing hurts, which usually starts somewhere between 100,000 and 1 million conversations a year. Most businesses end up with a mix: a few bought agents for commodity work and one or two custom agents where the logic is theirs. The five questions and the scorecard below settle it for each job in about an hour.

This post is part of our guide to rolling out agents, which starts at wizeb.com/blog/how-to-implement-ai-agents-in-business. If you've decided to build, the step-by-step version is at wizeb.com/blog/how-to-build-an-ai-agent-for-business, and if you'll hire someone to build it, read wizeb.com/blog/how-to-choose-an-ai-agent-development-company first.

The Problem: One Decision Made for Every Use Case

The build vs buy question usually gets answered at the wrong level. A leadership team decides "we're a platform company" or "we build our own" and applies it everywhere. The platform camp then discovers, six months in, that its most valuable workflow (the one with eleven internal systems and pricing rules nobody else has) can't be modelled in the vendor's flow builder. The build camp spends ten weeks engineering an FAQ bot that a $300-a-month tool would have handled in a fortnight.

Both mistakes cost the same thing: time to value. And the gap between the two options has narrowed. Packaged agent platforms are now genuinely capable, and open-source frameworks such as LangGraph and CrewAI, plus managed agent APIs from the major model providers, have made custom builds far less specialised than they were. That's why a single company-wide answer is almost always wrong, and why the useful question is narrower: for this job, at this volume, with these systems, which option gets us to a working agent fastest and keeps costs sane as it grows?

The Three Options, Defined

  • Buy: a packaged agent platform or the AI tier of software you already use (HubSpot, Salesforce, Zendesk, Intercom). You configure it rather than code it. Typical time to a first production agent: 2 to 4 weeks. Pricing is usually per seat, per conversation or per resolution.
  • Build: a custom agent written against a model API, with your own prompts, tools, integrations, evaluation tests and hosting. Typical time to production: 6 to 16 weeks. You pay for the build once, then model usage and maintenance.
  • Build on a foundation: an open-source framework or managed agent API as the base, with your business logic, integrations and guardrails on top. This is the most common choice for mid-sized businesses now: faster than starting from nothing, and you still own the parts that matter.

What Each Option Really Costs in Year One

Comparing a vendor's monthly price to a developer's quote is how most build vs buy decisions go wrong. Compare first-year total cost instead, including the costs that don't appear on either quote. For a single mid-complexity agent (say, lead qualification with CRM updates), typical ranges look like this:

  • Buy, year one: licence $3,600 to $30,000, depending on seats and volume; setup and configuration $2,000 to $10,000 if you use a partner; integration add-ons and higher plan tiers $0 to $15,000; internal admin time of 2 to 4 hours a week. Per-conversation cost on packaged platforms typically lands at $1 to $3.
  • Build, year one: design and build $15,000 to $60,000; hosting, monitoring and model usage $1,200 to $12,000; maintenance at 15 to 25% of the build cost per year, covering prompt tuning, model upgrades, broken integrations and new edge cases. At volume, purpose-built agents typically run $0.04 to $0.15 per conversation.
  • Build on a foundation, year one: usually 30 to 50% less build cost than a from-scratch build, with similar running costs. Maintenance is lighter because the framework handles orchestration, retries and session state.

The crossover point

At $2 per conversation, 1 million conversations a year costs $2 million on a packaged platform. A purpose-built agent handling the same volume typically runs $80,000 to $150,000 in model and hosting costs, an 87 to 96% reduction, before build and maintenance. Under 100,000 conversations a year, buying almost always wins. Between 100,000 and 1 million, model it carefully. Above 1 million, building usually wins on economics alone, and the real question becomes whether you can execute it.

The Five Questions That Decide Build vs Buy

  1. 1What is the annual conversation or task volume for this use case? Answer this first, from a system count rather than a guess. Under 100K: default to buy. Over 1M: model the build economics seriously. In between, the other four questions decide it.
  2. 2Does the workflow depend on systems with no ready-made connector? Standard tools (Salesforce, HubSpot, Jira, Slack, Shopify) have pre-built integrations, which makes buying easy. Bespoke internal systems, an old ERP or a homegrown database need custom integration work whichever way you go, and once you're writing the integration anyway, the case for owning the agent layer gets much stronger.
  3. 3How much vendor lock-in can you accept? Packaged platforms bind your agent logic to their infrastructure and pricing. If the vendor raises prices 40% next year, your cost structure changes with it. Custom agents are portable: you can swap the model, move the hosting and keep the prompts and logic. Portability costs something today and pays off as insurance later.
  4. 4Do you have AI engineering capability, or a partner who does? Building means someone writes and maintains agent code, designs prompts, runs evaluation tests and debugs model-specific failures. Without that skill in-house or through a partner, a build plan stalls, however good the economics look on paper.
  5. 5What happens when the agent gets it wrong? Regulated or high-stakes work (financial advice, medical triage, legal documents, payments) needs custom evaluation and guardrails that packaged platforms rarely provide at the level required. For low-stakes work like appointment scheduling and FAQs, a platform's built-in safety layer is usually enough.

A Build vs Buy Scorecard You Can Use Today

List every agent use case you're considering and score each one from 0 to 2 on five factors, where a higher score pushes toward building:

  • Volume: 0 under 100K a year, 1 for 100K to 1M, 2 over 1M.
  • Integration: 0 if every system has a ready connector, 1 if one doesn't, 2 if the core systems don't.
  • Differentiation: 0 if every competitor does this job the same way, 1 if you have some of your own rules, 2 if the logic is a reason customers choose you.
  • Risk: 0 if a wrong answer is an inconvenience, 1 if it costs money, 2 if it creates legal or safety exposure.
  • Capability: 0 if you have no engineering access, 1 if you have a partner, 2 if you have an in-house team that has shipped an agent before.

A total of 0 to 3 means buy. 4 to 6 means build on a foundation, or buy now with a clear exit plan. 7 to 10 means build. Two rules override the total: a capability score of 0 means buy or bring in a partner, whatever else the score says, and a risk score of 2 means you need custom evaluation tests even if you buy the platform.

The Hidden Costs on Each Side

When you buy

  • Pricing creep: per-resolution and per-seat pricing grows with your success. The agent that cost $300 a month at launch can cost $3,000 a year later with no change in what it does.
  • Tier upgrades: the feature you need (custom actions, API access, audit logs, single sign-on) often sits in the next plan up.
  • Workflow lock-in: logic built in a vendor's flow builder can't be exported. Switching means rebuilding it, which often costs as much as the original build. You find this out when the price changes, not when you sign.
  • Data access: check whether you can export full conversation logs and use them to evaluate or retrain elsewhere. Some platforms make this hard on purpose.

When you build

  • Maintenance never stops: models get deprecated, APIs change, and edge cases appear in production. Budget 15 to 25% of the build cost a year, or the agent decays.
  • Evaluation is real work: you need a test set of real cases and a way to rerun it after every prompt or model change. Skipping this is the most common reason custom agents quietly get worse.
  • Monitoring and logging: you have to build what a platform includes for free, such as conversation logs, cost tracking, failure alerts and an audit trail.
  • Key-person risk: if one developer understands the agent, that developer is a single point of failure. Documented code and a partner with a handover plan fix this.

Questions to Ask a Vendor Before You Buy

  1. 1What will we pay at 3x and 10x our current volume? Get it in writing.
  2. 2Can we export our flows, prompts and full conversation history in a usable format?
  3. 3Which model runs underneath, and can we choose or change it?
  4. 4How do custom actions reach our internal systems, and which plan includes that?
  5. 5What logs do we get for auditing what the agent said and did?
  6. 6What happens to our data, and is it used to train anyone's model?

If a vendor can't answer the first two clearly, treat that as the answer: you're buying lock-in along with the software.

Example: A Professional Services Firm's Hybrid Stack

Here is a realistic example of how the framework plays out. A B2B consultancy with 80 staff and a sales team of 12 mapped three agent opportunities: inbound lead qualification, client onboarding and project status updates. They scored each one separately instead of picking a single approach.

Lead qualification scored 2: about 40,000 interactions a year, a standard workflow, and a tight HubSpot integration. They bought it through HubSpot's AI tier. It took three weeks to go live and costs about $300 a month for triage, enrichment and routing, with no custom code.

Client onboarding scored 8: a bespoke workflow across 11 internal systems, with document generation, approvals and rules that vary by client type. No packaged option could model it at a sensible price, so they built it. The build took eight weeks, and onboarding now needs 90% less manual work across document prep, system provisioning and stakeholder updates.

Project status updates scored 5: 200+ updates a week across active engagements, simple logic, but enough volume for per-message pricing to bite. They built a lightweight agent on a framework, which runs at about $80 a month against more than $2,000 at the platform's per-message price.

The outcome

Three use cases, two approaches, one stack. All three agents were in production within 11 weeks, which is faster than building everything and much cheaper at scale than buying everything. Each agent sits where its volume, complexity and risk say it should.

What Typically Gets Bought vs Built

  • Usually bought: FAQ handling, appointment scheduling, standard lead routing, tier-one customer support, internal HR questions and IT helpdesk. These are well-defined jobs with pre-built templates and few integrations.
  • Usually built: proprietary workflow automation, high-volume processing where per-transaction cost matters, deep integration with internal systems, regulated-industry work, and any workflow where the logic is a competitive advantage you don't want inside someone else's platform.
  • Usually built on a foundation: everything in between. Mid-sized businesses with some technical capability increasingly default to this, because it's faster than starting from nothing and more flexible than a platform.

How to Decide in One Working Session

  1. 1List every agent use case on the table, even the vague ones.
  2. 2Pull real volume numbers for each from your systems.
  3. 3Score each one with the scorecard above, with the person who runs the job in the room.
  4. 4Buy the low scorers now. They're your quick wins and they build confidence.
  5. 5Pick the single highest scorer as your first custom build, and measure it against a baseline from day one. Our guide to measuring returns is at wizeb.com/blog/how-to-measure-ai-agent-roi.
  6. 6Review the mix every six months. Volume grows, vendors change prices, and a bought agent can earn a rebuild.

How WizeB Helps You Make the Call

We don't have a platform to sell you, so we have no reason to push one answer. Every AI agent engagement at WizeB starts with a use-case map that scores your candidates on volume, integration, differentiation, risk and capability, then recommends buy, build or build on a foundation for each. Where buying wins, we tell you which tool and help configure it. Where building wins, we build it with evaluation tests, logging and a handover plan so you aren't dependent on us. And where you've already bought, we check whether the platform still makes sense at your current volume.

Get an independent build vs buy read

Bring your list of agent use cases and we'll score them with you in a working session, then tell you which to buy, which to build and what each will cost in year one. Start at wizeb.com/services/ai-agents.

Ready to act on this?

We build exactly what this article is about.

Tell us about your situation — we'll come back with a realistic assessment.