How to Build an AI Agent for Your Business — Without Buying One or Coding It From Scratch

You've decided you want an AI agent. Now you're pricing it — working out how to build an AI agent that fits a company your size — and the market hands you two answers that both feel wrong.

The first is a platform. The Agentforce demo looked impressive, then the quote arrived: prices per conversation, per action, and per seat — numbers that grow the more the thing actually works.

The second is a build. A development shop offered to write you a custom agent on a framework: months of work, a team to manage, and a codebase you now own and maintain. One answer locks you into someone else's product; the other turns you into a software company.

This guide is about the cost math that sits underneath that choice — and a better answer most vendors don't mention, one built for a business like yours. Learning how to build an AI agent that actually pays for itself is less about the technology than about which of these paths you walk down, and what each one really costs once the invoices stop being hypothetical.

Table of contents

• The false choice every vendor frames
• Why "AI agent" stopped meaning anything
• The off-the-shelf answers and what they cost
• The fourth answer: how to build an AI agent by growing one
• What an AI agent really costs, four ways
• Which of your processes actually qualifies
• The substrate is cheap; the expert is the point
• Frequently asked questions

The false choice every vendor frames

Picture the contrast in plain numbers. A platform agent bills you roughly $2 per conversation, or burns credits by the action: cheap for a pilot, then it scales with use until a busy month is a five-figure line item (all platform prices below are sourced and dated to June 2026; pricing changes monthly). A custom build inverts the shape: developer-weeks before anything runs at all, then it's yours to keep working forever.

Both shapes are real. Neither is built for a mid-sized business that wants one process handled well, without a procurement saga or an engineering team.

The framing itself, buy or build, is the trap. It's the question every vendor wants you to ask, because each one has already decided which side of it they sell. There's a third option they rarely mention, and the rest of this article is mostly about its cost, because the cost is where it wins.

Why "AI agent" stopped meaning anything

Before you can price an AI agent, you have to notice that the term has stopped describing one thing. Ask six vendors what an "AI agent" is and you'll get six answers — not because anyone is lying, but because the label maps to at least four different axes at once:

• By interface: a chatbot — conversational, reactive, the kind that answers questions on your website.
• By function: a workflow-automation tool (n8n, Make, Zapier AI) that wires services together, or a coding agent (Claude Code, Cursor) that writes and runs code.
• By access pattern: a computer-use or personal agent (ChatGPT Agent, Operator) that clicks around a screen for you.
• By delivery model: an enterprise platform (Agentforce, SAP Joule, Microsoft Copilot), or a framework you assemble yourself (LangChain, CrewAI, AutoGen).

These categories overlap because they're answers to different questions. A framework can build any of the others; a platform bundles several. That overlap is the whole point: when one word covers a website chatbot and a system that runs your billing reconciliation overnight, the word has stopped carrying information. Credible 2026 surveys of the field describe these labels as a spectrum rather than discrete categories (DataCamp, 2026). For the full taxonomy of what an agent is, see our companion guide on what an AI agent is for business. Here, we need a tighter definition and a different axis.

A business agent, the kind worth paying for, is narrower: a system that runs a real end-to-end process — not a single task, not a chat — largely unattended on a schedule or a trigger, with the tools to take action and a human in the loop on the judgment calls. It sits a few steps up from a simple chatbot in the arc we've called the five generations of AI in business. (A customer-facing chatbot is a different shape entirely; our Royal Finance project is an example of that earlier bucket.)

Once the definition is tight, the only axis that matters for cost is not what kind of agent it is, but how you get one. There are four ways: buy a platform, assemble one from no/low-code parts, build one on a framework, or grow one on a coding-agent substrate. The market's own selection criteria point the same way; serious buyers weigh integration depth, workflow risk, and who maintains the agent after launch — the factor that quietly decides your bill over time. The next four sections are that axis.

The off-the-shelf answers and what they cost

Three of the four paths are things you can buy or assemble today. Here's the shape of each one's cost, with the full numbers in the comparison table below. Every figure is sourced and current as of June 2026; re-check before you sign anything, because these change monthly.

Buy: enterprise platform agents

The platforms bill by consumption, and that is the whole story of their cost. Salesforce Agentforce runs about $2 per conversation, or you pre-buy Flex Credits and spend roughly 20 credits ($0.10) per standard action (Salesforce pricing). Microsoft 365 Copilot is $30 per user per month, with agent actions metered separately through Copilot Studio credits (Microsoft). SAP Joule meters per action too, and licensing analysts warn that customers who don't model adoption can face six-figure annual overage invoices (SAP licensing analysis). ChatGPT Enterprise is sold on a quote basis — OpenAI doesn't publish the number — but third-party reports put it at roughly $50–60 per seat with a 150-seat minimum, a six-figure annual floor before anyone has done any work (OpenAI Enterprise).

The signature is the same across all four: cheap to start, then the bill climbs with every conversation, action, and credit — and you run your process the vendor's way, because it's their agent.

To be fair, there's a company this is right for. If you're a 5,000-seat enterprise that needs single sign-on, audit trails, procurement-grade support, and governance reviewed by a security team, buying a governed platform can be the correct call. The per-action bill is the price of not having to think about any of that. For a mid-sized business running one or two processes, it's overhead you don't need — but the concession is real, and it sharpens the case rather than weakening it.

Build: frameworks from scratch

The build path starts from the opposite end. Frameworks like LangChain, CrewAI, and AutoGen are open source — the tooling is free. What you pay for is developer time to assemble the plumbing, plus the model tokens the agent consumes once it runs. The cost driver is developer-weeks, and the hidden cost is everything after launch: you now own a piece of software, and someone has to maintain it as models change and the process evolves. You've solved the lock-in problem by becoming a software shop — a fair trade for some companies, but not the business most are in.

The middle path: no-code and low-code

Between buying and building sit the workflow tools. Self-hosted n8n runs about $3–7 a month for unlimited executions, plus your own LLM API fees on top; the cloud tier climbs from roughly $24 to $800 a month as execution volume grows (n8n pricing). Make runs from free to about $29 a month by operation count (Make). These are fast and cheap for simple, well-defined flows, but they hit a wall on complex logic, and you still need someone to build and maintain them. We've written before about the build-versus-buy decision for chatbots; the same logic extends to agents, with one more option than that framing allowed.

The fourth answer: how to build an AI agent by growing one

The fourth path is the one we use, and it's how to build an AI agent for your business without either a six-figure platform or a development team standing up framework plumbing.

The mechanism is a general-purpose coding agent used as an automation substrate — the approach behind the AI agents we build for clients. Instead of configuring a vendor's fixed agent or assembling framework plumbing by hand, you give a capable coding agent (Claude Code is the one we run) your actual process. It writes the scripts and small tools that carry out that process, and those tools live as plain files in your own repository. When a step turns out to be brittle, the next iteration produces a better tool for it. The agent doesn't replace your process; it grows around it.

Three things keep this honest, and each one matters for what it costs.

A human directs and reviews — every time. The phrases "writes its own tools" and "self-improving" describe a human-directed engineering loop: a person and the agent iterate the prompts, scripts, and tools together, each cycle a little better. It is not the model retraining or modifying itself, and it is not autonomous, unsupervised tool-building. The judgment calls stay with a person. That human-in-the-loop design is structural, not incidental — and it's most of what you're paying for.

"Grow" is not "no-code." Someone has to drive the coding agent — you, if you have the skill in-house, or a partner who does. Don't let anyone sell you "anyone can do this." The substrate is cheap; the driver is not free.

The substrate has to be capable. A real business agent needs a capable model with a large context window — the two together, multiplied, not traded off. The model has to be good enough to reason about your process and have enough context to hold it in mind at once. Lightweight or small-context models can't carry a genuine end-to-end process, no matter how cheap they are. This is a real technical requirement, not a slogan.

One honest caveat on lock-in. The grow path has lower lock-in than a platform, because your process lives in portable files and scripts you own — but it isn't zero. You still depend on a capable model provider. The accurate way to say it: your process is portable, and you choose the model. That's a materially better position than a platform that owns both.

Does it work? This site's own publishing pipeline runs on exactly this substrate — keyword research, drafting, multi-critic review, and publishing, driven by a coding agent under human direction. One article it produced holds an average position of 3.75 in search, as of our June 2026 data. We don't claim hours saved we can't measure; that's the proof we can.

What an AI agent really costs, four ways

Pin down the real AI agent development cost and it splits into three layers: one-time costs (build and integration), recurring costs (license, model tokens, hosting, connector fees, and maintenance labor), and the one almost every vendor omits — the human-in-the-loop expert who keeps the agent honest. Platforms hide the token line inside credits; nobody puts the expert on the invoice. Here's the comparison with all four paths and the lines made visible.

* The substrate's license is a small, public figure: a Claude Code subscription runs about $20 a month on Pro or $100 a month on Max, or you run on API tokens directly — Claude Opus 4.8 is $5 per million input tokens and $25 per million output, with prompt caching cutting repeat input costs by roughly 90% (Claude pricing, as of June 2026). The point of those numbers is only this: the substrate is cheap relative to per-action platform billing.

Read the table honestly and the grow column does not say "free." The license is small and the build is low, because the agent generates its own tooling under direction. The real cost sits where it belongs: the human-in-the-loop expert who turns a capable coding agent into your business agent and keeps it producing work you'd sign your name to.

So what does a client actually pay? Two things, stated separately on purpose. There's the substrate — the cheap, public line above, which the client runs on their own account. And there's the expert retainer — the engagement that supplies the person who directs the substrate. The substrate cost is not the service price; conflating the two is exactly the mistake the platforms encourage. The agent is cheap to run. The expertise to run it well is what you're buying.

Which of your processes actually qualifies

The grow path is powerful, but it is bounded, and an honest cost guide has to draw the boundary. A process is a good agent candidate when it meets three tests.

• It's repeatable. It happens often and follows a recognizable pattern. A monthly reconciliation qualifies; a once-a-decade decision does not.
• It's computer-based. The inputs and the actions both live in software the agent can reach. If a step requires a phone call or a physical signature, that step is outside the agent's hands.
• It's review-tolerant. A human can check the output before it becomes consequential, and an occasional error during the learning phase is survivable.

That third test is where the boundary bites. Some processes are not good candidates no matter how repeatable they are: a loan approval, a regulatory filing, a medical or legal decision, anything high-stakes or compliance-critical where an unreviewed error is a serious problem. Low-frequency, one-off tasks don't qualify either — there's nothing for the agent to learn against. "Almost any process" is the marketing version; the true version has these edges.

Notice that the review-tolerance test is exactly why the human-in-the-loop expert is structural, not optional. The agent earns its keep on the processes a person can check, which means a person has to be in the loop by design. That's not a cost you can engineer away. Working out which of your processes pass these tests is the first thing our AI consulting work does on any engagement.

The substrate is cheap; the expert is the point

Put the four paths side by side and the trade is clear. Buy is fast but locked-in, and the bill grows with use. Build is yours — and yours to maintain. Grow keeps your process portable, runs on a cheap substrate, and is directed by an expert — the right shape for a mid-sized business that wants one process handled well.

The grow path needs a driver. That's the real answer to how to build an AI agent on a budget: the substrate runs cheap, and the expert who turns a coding agent into your business agent — and keeps it honest — is the service you're buying.

If that's the path that fits your business, that's what an AI agents engagement with us is. We drive the coding-agent substrate and staff the human-in-the-loop expert who turns it into your agent. The substrate is the cheap part; the judgment is the point.

Frequently asked questions

How much does it cost to build an AI agent?

How much an AI agent costs depends entirely on the path. A platform agent is cheap to pilot and then bills by consumption — roughly $2 per conversation, or per-action credits that reach five or six figures a year at scale. A custom framework build is free tooling plus developer-weeks of labor, with maintenance you own. The grow path runs on a small, public substrate cost — a coding-agent subscription of roughly $20–100 a month, or API tokens — plus the real cost: the human-in-the-loop expert who directs it. The cheapest line item is never the deciding one; the expert and the maintenance are.

Can I build an AI agent without a development team?

Yes, but not without someone who can drive the work. On the grow path you don't need a development team standing up framework plumbing — the coding agent writes the scripts and tools itself, under human direction. What you do need is a person who can direct and review it. When we run the engagement, that's our domain expert: your team scopes the process and signs off on results, not writes code. It is not no-code, and anyone who says "anyone can do this" is selling you something.

Should I buy an AI agent platform or build my own?

For most mid-sized businesses, neither cleanly. Buying a platform is the right call if you're a large enterprise that needs governance, single sign-on, audit trails, and vendor support — the per-action bill buys all of that. Building from scratch makes sense only if you're prepared to own and maintain software. For a company that wants one or two processes handled well, growing an agent on a coding-agent substrate usually fits better: lower lock-in, a cheap substrate, and an expert in the loop. Whether you build an AI agent for business in-house or have a partner create one, the grow path keeps the process yours.

What's the cheapest way to run an AI agent?

On a pure license basis, the grow path's substrate is cheapest — a coding-agent subscription of roughly $20–100 a month, or API tokens with caching that cuts repeat input costs by about 90%. But "cheapest to run" is not "cheapest to own": the cost that decides your total bill is the expertise that directs the agent and the maintenance that keeps it working. A platform that looks cheap in a pilot becomes the most expensive option once consumption scales; a cheap substrate without an expert produces work nobody can trust. Price the whole picture, not the license line. See our cases for how this looks in practice.