With AI agents, it’s not buy vs build. It’s buy vs build, build, build, build, build

With AI agents, it’s not buy vs build. It’s buy vs build, build, build, build, build

Steve Hind

Steve Hind

|

|

0 Mins

With traditional SaaS you can roughly choose between:

  • Some upfront cost to create the functionality yourself, and then a smaller maintenance cost, and

  • An ongoing SaaS fee that is lower than the upfront build cost, but maybe higher than the maintenance cost

With AI agents, the math is different. The models, architectures, and opportunities are constantly changing. Companies who build their own AI agents have to continue to invest heavily – and be willing to do complete rebuilds – in order to continue to have a competitive product. With consumer expectations rapidly changing this risks either cost blowouts, or getting left behind. This is why we think AI agents aren’t “build vs buy” they’re “build, build, build, build, build vs buy”.

The hidden economics of buy vs build

"How hard could this be to build ourselves?" Every smart engineering leader asks some version of this when they see AI agent pricing. It's a fair question. You've got talented engineers. You understand your business better than any vendor. And the demos make it look straightforward – just hook up an LLM to your help center and away you go.

The key thing folks miss (and that we’ve learned over time building Lorikeet) is that AI agents aren’t like SaaS tools. They require a high ongoing level of investment to stay competitive and performant. 

The Ship of Theseus problem

Remember that philosophical paradox about the Ship of Theseus, the ship that has all its parts gradually replaced? At all times there’s a ship, but eventually none of the original parts remain. That's a useful framing for considering your AI agent.

The underlying AI tech stack is evolving so rapidly that today's best architecture will likely be obsolete in a couple of quarters. We've seen this firsthand at Lorikeet. What worked six months ago is already antiquated. The models change. The context windows expand. The inference speeds improve. The entire approach to handling complex multi-step reasoning shifts.

This isn't about adding features – it's about rebuilding the core engine repeatedly. Your competitors aren't standing still. The vendor ecosystem isn't standing still. So if you're not constantly rebuilding, you're falling behind.

To give a specific example: we think about a three axis optimization for agents: configuration effort, response latency, and response quality. Until mid 2025 we optimized for response latency and response quality and were willing for configuration effort to be higher. As thinking models emerged and got smarter, and as we found faster inference providers, we rebuilt our core agent to instead optimize for lower configuration effort and higher response latency (which we manage so there isn’t a user impact). Our core view is you must be willing to do this from-the-ground-up rethinking on a regular basis to stay competitive.

The real cost calculation

Companies budget for AI agents like they're buying Salesforce or building an internal platform: big upfront investment, then maintenance mode. 

But building an AI agent isn't a one-time 3-month project with a team of 5. It's a permanent commitment to that team, forever rebuilding to keep pace. You're not hiring contractors for a project. You're creating a new department.

Think about what your team of 5 engineers costs annually. Now multiply that by...forever. That's your real build cost. Plus infrastructure.

Most importantly, you also need to factor in the opportunity cost of what else those engineers could be building. It is not universally true, but it is broadly true that most companies are better off investing the marginal engineer in making their core product or service better, rather than building CX tools. The key question is: what is critical to our business that we can’t buy?

Most companies budget for "build once + maintenance" when they should budget for "rebuild quarterly + aggressive R&D." The difference between those two numbers should make your CFO sweat. For CFOs, the time to ask these questions is now, not after it’s too late and there’s a team deep in the sunk cost fallacy.

Why vendors have the edge

We spend every waking hour thinking about one thing: making AI agents that deliver an amazing customer experience. That's it. That's all we do.

Your internal team? They're balancing AI development with your actual business. They're dealing with your legacy systems. They're getting pulled into meetings about Q4 planning.

Meanwhile, we're:

  • Rebuilding our architecture every time a better approach emerges

  • Amortizing that rebuilding cost across our entire customer base

  • Testing across millions of real support tickets to understand what actually works

  • Racing against other vendors who are equally obsessed

Plus – and this is the part no one likes to talk about – VC funding is currently subsidizing the true cost of AI infrastructure. Those GPU costs? The inference pricing? It's all artificially low because vendors are burning cash to capture market share.

When you build internally, you pay full price. Vendors have more flexibility.

The bottom line

The buy vs build decision for AI agents isn't really a decision. It's basic economics.

Unless you believe your CX tooling needs are truly unique and not served by any vendor, you're better off buying. Not because building is hard (though it is), but because building once isn't enough. You have to build, then build again, then build again, then build again...

Partnering with a quality vendor who cares about, and attentive to, your needs is, in our view, the best way forward.

Book a call

See what Lorikeet is capable of

Share this article

Related posts

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.